Job Photos Checked Against What Was Asked For and Billed
No more jobs signed off on a photo nobody read. No more charges with nothing behind them. No more disputes four months later that you settle because arguing costs more than conceding.
Who it's for
Anyone closing down jobs on photo evidence. Adaptations, repairs, planned works, compliance visits, anything a client can query later.
What it saves you
The disputed invoice, the recall visit, and the work written off because you cannot prove it happened.
Set up time
Most businesses are live within a week.
The problem
Nobody reads the photos
Not properly. A job comes back with six images attached, someone glances at the thumbnails, and it is closed.
Most of the time that is fine, because most of the time the work was done and the engineer photographed it. But the photos are the only evidence you will ever have, and nobody is checking that they show the work that was actually requested, or that they support what is about to be invoiced.
So a job closes with three items on the bill and photographs of two. A job closes with a picture of a van, a wall, or last visit's work. A job that asked for a grab rail and a ramp closes with a clear photo of the grab rail and nothing else. Almost none of this comes down to anyone being dishonest. It is an engineer at the end of a long day, and an office with two hundred jobs to close this week.
Checking it properly means holding three things side by side: what the client asked for, what the photos show, and what the customer is being charged. That is ten minutes a job. Nobody has ten minutes a job.
Where it costs you
The bill for this arrives late, which is what makes it easy to ignore.
A query comes in four months after the visit. The site has changed. The engineer has moved on, or cannot remember. Your evidence is six photos nobody examined at the time. At that point you have three options and two of them cost money. Send someone back to re-evidence it, or credit the line and move on. The third option is to argue it out with a client you want to keep, which costs you goodwill instead of money.
The same gap works in the other direction, and that one is pure lost revenue. Work that was done but never evidenced does not get billed at all, because the person invoicing cannot see support for it and takes the safe route.
Both outcomes are decided at close down, in the ten minutes nobody has spare.
What the automation does
When a job is closed down, Build Concierge:
- Reads the completion photos. It looks at what is in them, rather than only checking that they exist.
- Reads what was requested on the job, and the costs recorded against it.
- Checks the three agree. Is the requested work visible? Do the charges have evidence behind them?
- Lets the job close where everything lines up, which is most of the time.
- Holds it where it does not, naming the specific gap. This item was requested and is not visible. This charge has nothing supporting it.
Tighter where it matters
You set the level by priority or value, so a £120 routine repair and a £4,000 adaptation do not get the same scrutiny.
What you get
- Jobs closing on evidence rather than assumption.
- What you invoice matching what was requested and what the photos show was done.
- Client queries answered from the record, with the evidence already attached, instead of an investigation.
- Work that was done getting billed, because the evidence supports it.
- Gaps found while the engineer is still contactable and the site is still as they left it.
Ways to run it
Photos against scope
The lightest version, and a sensible first step. Checks the requested work is visible before close down.
Photos against scope and cost
The full check. Adds the job's financial lines, so a charge with nothing behind it is caught as well.
Tiered by priority or value
Routine work gets the light check. High-value or high-risk work gets the full one. Run as separate rules over the same job types.
Hold, or flag and continue
Either stop close down until someone looks, or let it through carrying a flag for review. Most businesses start with the second and tighten later.
What you need
- Photos captured on the job, through your engineers' app, worksheets or job cards.
- The requested scope recorded on the job somewhere readable, rather than buried in an email thread.
- A decision on what happens when a check fails, and who picks it up.
Getting set up
- We look at a batch of jobs you have already closed. Real, recent ones. This shows what your photos typically contain and where the gaps genuinely are, which is rarely where people expect.
- We set the thresholds with you. Too strict and your team spends a week clearing flags and stops trusting it. The first pass is deliberately loose.
- We run it in report-only mode. It reports what it would have held for a week or two, so you tune it before it stops anything.
Common Questions
For this kind of check, yes. Whether there is a grab rail, whether a new unit is in place, whether the image shows work at all or is a photo of a van. It is not assessing workmanship, and it should not be asked to.
It gets flagged, someone looks, and the job closes. That is the right outcome. If the evidence is not clear enough to satisfy you, it will not satisfy your client either, and it is better to find that out now.
No, and it is worth saying that out loud internally before you switch it on. The overwhelming majority of flags are a missing photo, not missing work. Teams generally find it takes pressure off, because close down stops being a judgement call somebody can be blamed for later.
It runs in seconds. The only jobs it holds up are the ones that would have caused a problem later.
Then this is not the automation to start with. Talk to us about getting capture right first. The rest follows easily.
Yes. Where a job requires a specific shot, such as a pre-work safety photo, a meter reading or a certificate, it can check that specific evidence is present rather than just checking photos exist.
Ready to send it back before it becomes a job?
Get in touch with the Build Concierge team and we’ll set it up around the way you work.
More from the knowledge centre
Duplicate Jobs, Stopped Before They're Raised
No more second job because the order came in twice. No more engineer sent to an address a colleague visited yesterday. No more credit note to unpick it afterwards.
Incomplete Instructions, Sent Straight Back
No more jobs raised with "TBC" in the contact field. No more engineer travelling to an address nobody can get into. The missing detail chased at the front door, in seconds, by the person who has the answer.
Friday Fives: quotes turned into POs, unconfirmed jobs pulled from the diary
Five automations that turn supplier quotes into coded POs, keep unconfirmed jobs out of the diary, action subcontractor paperwork, surface real job margin and catch parking costs.
Parking Costs and Fines, Captured Against the Job
No more parking costs disappearing into the business because nobody put them on the job. No more fines surfacing weeks later with the penalty doubled. No more expenses typed up from a note on a van dashboard.
A Job's True Margin, Calculated on Demand
No more margin reviews that never happen because pulling the numbers takes an hour. No more costs missed because someone eyeballed the financial lines. No more quoting on gut feel.
Subcontractor Paperwork, Read and Actioned Automatically
No more subcontractor emails sitting unread in a shared inbox. No more scrappy completion emails someone has to decipher and retype. No more invoices paid against work nobody logged.
Duplicate Jobs, Stopped Before They're Raised
No more second job because the order came in twice. No more engineer sent to an address a colleague visited yesterday. No more credit note to unpick it afterwards.
Incomplete Instructions, Sent Straight Back
No more jobs raised with "TBC" in the contact field. No more engineer travelling to an address nobody can get into. The missing detail chased at the front door, in seconds, by the person who has the answer.
Friday Fives: quotes turned into POs, unconfirmed jobs pulled from the diary
Five automations that turn supplier quotes into coded POs, keep unconfirmed jobs out of the diary, action subcontractor paperwork, surface real job margin and catch parking costs.
Parking Costs and Fines, Captured Against the Job
No more parking costs disappearing into the business because nobody put them on the job. No more fines surfacing weeks later with the penalty doubled. No more expenses typed up from a note on a van dashboard.
A Job's True Margin, Calculated on Demand
No more margin reviews that never happen because pulling the numbers takes an hour. No more costs missed because someone eyeballed the financial lines. No more quoting on gut feel.
Subcontractor Paperwork, Read and Actioned Automatically
No more subcontractor emails sitting unread in a shared inbox. No more scrappy completion emails someone has to decipher and retype. No more invoices paid against work nobody logged.
Duplicate Jobs, Stopped Before They're Raised
No more second job because the order came in twice. No more engineer sent to an address a colleague visited yesterday. No more credit note to unpick it afterwards.
Incomplete Instructions, Sent Straight Back
No more jobs raised with "TBC" in the contact field. No more engineer travelling to an address nobody can get into. The missing detail chased at the front door, in seconds, by the person who has the answer.
Friday Fives: quotes turned into POs, unconfirmed jobs pulled from the diary
Five automations that turn supplier quotes into coded POs, keep unconfirmed jobs out of the diary, action subcontractor paperwork, surface real job margin and catch parking costs.
Parking Costs and Fines, Captured Against the Job
No more parking costs disappearing into the business because nobody put them on the job. No more fines surfacing weeks later with the penalty doubled. No more expenses typed up from a note on a van dashboard.
A Job's True Margin, Calculated on Demand
No more margin reviews that never happen because pulling the numbers takes an hour. No more costs missed because someone eyeballed the financial lines. No more quoting on gut feel.
Subcontractor Paperwork, Read and Actioned Automatically
No more subcontractor emails sitting unread in a shared inbox. No more scrappy completion emails someone has to decipher and retype. No more invoices paid against work nobody logged.





