The Wrong Answer on a Worksheet, Caught
No more work described in a report and then never priced. No more quotes lost to a box ticked at the end of a long day. The answer gets checked against what the engineer actually wrote.
Who it's for
Anyone whose engineers flag further work on a worksheet, where that answer decides whether a quote gets raised.
What it saves you
The revenue that never arrives, and never shows up as a loss because nobody knew it was there.
Set up time
Most businesses are live within days.
How does the check work?
One question on the worksheet carries a lot of weight. "Further works or actions required?" gets answered yes or no, and that answer sets the job's outcome status and decides whether anything gets quoted.
- Build Concierge reads what the engineer wrote in their report and checks it against the answer they gave
Where the report describes work that plainly needs pricing and the answer says it doesn't, the job gets flagged with the discrepancy, a corrected answer, and how confident it is.
What the automation does
Because it's one field among thirty, at the end of a job, and it doesn't look important.
The engineer's just finished. They're writing up what they found, and they write it properly, because that bit matters to them. Then there's a dropdown near the bottom of the form, and they pick one, and they move on to the next job.
Nobody's being careless. It's the same reason any of us get a form field wrong:
- the answer looks like admin, not like a decision
- the consequence of getting it wrong isn't visible from where they're standing
- the report they just wrote already says what they found, so the box feels like a formality
Except it isn't. That box is what triggers the quote
What a missed quote costs
Work it out on your own numbers.
Take your average value of remedial work found on site. Multiply by however many jobs a month come back with further works described. Then take a guess at what percentage of those get the box ticked wrong.
Most people guess low, because there's no way to know. That's the actual problem here. A missed quote doesn't show up anywhere. There's no report of revenue you didn't bill, no flag, no exception list. The job closes clean, the work goes elsewhere or never happens, and nothing in your system ever tells you.
Ways to run it
- Reads the engineer's report, the full write-up rather than just the answer field.
- Reads the answer they gave on the "further works required" question.
- Compares the two. Does the report describe work that would need pricing?
- Lets it through when they agree, which is most of the time.
- Flags it when they don't, naming what the report said, offering the corrected answer, and stating how confident it is in that correction.
It doesn't overrule the engineer.
It raises a question for a person to settle, on the small number of jobs where the write-up and the answer point different ways.
What you need first
- A worksheet question that decides whether work gets quoted, with a consistent set of answers.
- Engineers writing up what they found in enough detail to be read. If reports are one-line, there's nothing to check the answer against.
- A decision on who picks up a flagged job.
Getting set up
- We look at closed jobs. A batch of recent ones, to see how often the report and the answer already disagree. This usually settles the business case on its own.
- We tune the threshold with you. Too sensitive and your team clears flags all week. The first pass is deliberately cautious.
- We run it in report-only mode. For a fortnight it tells you what it would have flagged, without changing anything.
Common Questions
No. It flags the disagreement and offers a corrected answer. A person decides.
Worth saying out loud to them before it goes live. Most flags turn out to be a rushed dropdown rather than anything else, and it means an engineer who found real work gets credit for finding it rather than losing it to a mis-click.
Then it can't help, and it says so rather than guessing. That's usually a signal worth having about report quality generally.
It gives you a confidence level with each flag, so low-confidence ones can be handled differently or ignored entirely.
Yes. An engineer who ticks yes when the report describes nothing quotable is the same check in reverse, and it saves the office chasing a quote that was never needed.
Yes. It reads your question and your answer options as they are.
Catch the answer that doesn't match the report
Get in touch with the Build Concierge team and we’ll set it up around the way you work.
More from the knowledge centre
Friday Fives: fault history, worksheet checks, allowances costed
Five real automations from the Build Concierge platform, picked for the week of 4 September.
Survey Findings Sorted and Counted for Pricing
No more reading a forty-page report with a tally sheet. No more two people categorising the same findings differently. No more remedial found on site because the wording didn't match what somebody expected.
Shift Allowances and Night Shifts Costed Automatically
No more checking finish times against a rate card. No more allowances missed because nobody spotted the hours. No more engineers chasing money they're owed.
Jobs Raised as a Group, Checked as a Group
No more a note added to one job and invisible on the other eleven. No more working through a group job by job with the quote open alongside. The group behaves like one piece of work, because that's what it is.
A Machine's Full Fault History, Back in Seconds
No more ringing the workshop to ask if anyone remembers this machine. No more opening job after job to piece together what happened last time. Text the serial number, get the history back.
Friday Fives: duplicates stopped, photos checked, costs coded
Five automations that stop duplicate jobs before they're raised, send incomplete instructions back to the sender, check completion photos against what was asked for, code costs the moment they land and strip supplier detail off quotes.
Friday Fives: fault history, worksheet checks, allowances costed
Five real automations from the Build Concierge platform, picked for the week of 4 September.
Survey Findings Sorted and Counted for Pricing
No more reading a forty-page report with a tally sheet. No more two people categorising the same findings differently. No more remedial found on site because the wording didn't match what somebody expected.
Shift Allowances and Night Shifts Costed Automatically
No more checking finish times against a rate card. No more allowances missed because nobody spotted the hours. No more engineers chasing money they're owed.
Jobs Raised as a Group, Checked as a Group
No more a note added to one job and invisible on the other eleven. No more working through a group job by job with the quote open alongside. The group behaves like one piece of work, because that's what it is.
A Machine's Full Fault History, Back in Seconds
No more ringing the workshop to ask if anyone remembers this machine. No more opening job after job to piece together what happened last time. Text the serial number, get the history back.
Friday Fives: duplicates stopped, photos checked, costs coded
Five automations that stop duplicate jobs before they're raised, send incomplete instructions back to the sender, check completion photos against what was asked for, code costs the moment they land and strip supplier detail off quotes.
Friday Fives: fault history, worksheet checks, allowances costed
Five real automations from the Build Concierge platform, picked for the week of 4 September.
Survey Findings Sorted and Counted for Pricing
No more reading a forty-page report with a tally sheet. No more two people categorising the same findings differently. No more remedial found on site because the wording didn't match what somebody expected.
Shift Allowances and Night Shifts Costed Automatically
No more checking finish times against a rate card. No more allowances missed because nobody spotted the hours. No more engineers chasing money they're owed.
Jobs Raised as a Group, Checked as a Group
No more a note added to one job and invisible on the other eleven. No more working through a group job by job with the quote open alongside. The group behaves like one piece of work, because that's what it is.
A Machine's Full Fault History, Back in Seconds
No more ringing the workshop to ask if anyone remembers this machine. No more opening job after job to piece together what happened last time. Text the serial number, get the history back.
Friday Fives: duplicates stopped, photos checked, costs coded
Five automations that stop duplicate jobs before they're raised, send incomplete instructions back to the sender, check completion photos against what was asked for, code costs the moment they land and strip supplier detail off quotes.