Arrival promise matched
Confirm the work completed matches the job description, approved variation, or documented change.
jack.boutique specialised ebook
A compact quality-control rhythm for small local service businesses that want fewer avoidable return visits.
A callback is not just a return visit. It is a signal that one part of the job promise was unclear, unchecked, undocumented, or handed over too fast. The useful question is not “who made a mistake?” but “where did the job lose its proof?”
The final ten minutes decide whether the customer remembers calm competence or a rushed exit. Walk the work area, test the thing you repaired or installed, photograph the finished state, and explain the one behaviour the customer should expect next.
Use these checks as a lightweight field rhythm. Pick the checks that fit your trade, then make them visible on a phone note, job sheet, or van card.
A good handover is plain, short, and specific. The aim is to remove mystery without over-promising. Say what was done, what was tested, what to watch for, and how to contact you if something looks wrong.
At the end of the week, review callbacks by trigger, not by blame. Look for repeated missing photos, unclear exclusions, parts delays, rushed testing, or customer expectation gaps. Then change one checklist line for next week.
Confirm the work completed matches the job description, approved variation, or documented change.
Take one clear photo showing the starting condition or access issue.
Take one clear photo showing the finished work from the customer’s useful angle.
Record model, serial, part number, fixture type, or appliance reference where relevant.
Check trip hazards, sharp edges, water, dust, tools, packaging, and access points.
Run the installed/repaired item through its normal use, not just a quick power-on.
Where safe, test under likely real use: hot/cold cycle, load, pressure, flow, opening/closing, or repeated start.
Show the customer the finished result or explain exactly where the completed work is.
Explain any normal short-term noise, smell, settling, condensation, residue, or drying time.
If the work needs curing, drying, cooling, isolation, or rest time, state the time clearly.
Return keys, panels, covers, cupboards, gates, ladders, switches, and isolation points to the expected state.
Remove waste or document what will remain and why.
Check timers, thermostats, app settings, valve positions, remotes, codes, or preferences.
If a temporary fix or partial repair was done, name the limitation before leaving.
Give one clear next action only: monitor, book follow-up, replace part, approve quote, or no action.
Say what is covered by the work and what is not covered without sounding defensive.
Confirm invoice, deposit, balance, or quote status without pressuring the customer.
Tell the customer the best channel for photos, questions, or urgent follow-up.
Document any discovered damage, pre-existing issue, or risk area before leaving.
If access/noise/shared infrastructure matters, state who needs to know.
Mention filters, batteries, seals, bulbs, cartridges, chemicals, or parts that will need replacement.
Leave a small note, sticker, message, or photo annotation for unusual use instructions.
Repeat exclusions that are likely to cause misunderstanding later.
Record rain, heat, blocked access, pets, dust, power outage, or other condition that affected work.
If follow-up is needed, put a date or trigger on it before leaving.
If another person may get the callback, post the job note where the team will see it.
Mark low/medium/high callback risk so office follow-up can be prioritised.
Write one sentence: “Next time we should…” while the job is still fresh.
“I’ve tested the job in normal use and taken the final photo. The main thing to expect is [normal condition]. If anything looks different from that, send us a photo here and we’ll check it.”
“This is safe as a temporary fix, but it is not the final repair. The next step is [action]. I’ve noted the limitation so nobody treats this as fully resolved.”
“The easiest way to avoid trouble is [simple habit]. If you forget, it is not a disaster, but this is the pattern that keeps it working properly.”
“That part sits outside today’s approved job, so I do not want to pretend it is covered. I can note it and send a separate option if you want it priced properly.”
“I’m marking this for follow-up on [date/trigger]. If you notice anything before then, send a photo and the job number so we can connect it quickly.”