Repair or replace: make service decisions traceable
A practical decision record for repair shops that need consistent estimates, approvals and handovers.

A repair-or-replace decision is rarely just a technical judgment. It affects the estimate, the promised completion date, the parts order and the explanation at handover. If the reason only lives in a technician’s memory, the next call from the customer starts from zero.
Record the decision while the evidence is available
A useful record fits on one screen and answers five questions:
| Field | What to capture |
|---|---|
| Item and condition | Part, device or vehicle area; visible findings and relevant test result |
| Options | Feasible repair and replacement paths, including dependencies |
| Cost and time | Estimated labour, parts, availability and expected completion window |
| Recommendation | Why one path is preferred, including any uncertainty |
| Approval | Who approved which scope and when |
Photos, measurements and supplier availability should be attached or linked to the order, not stored in private chats. The European Commission explains that the GDPR requires personal-data processing to have a legal basis and follow principles such as purpose limitation and data minimisation; collect only the evidence needed for the service case and control who can access it. European Commission: EU data-protection framework
Separate facts from the recommendation
“Replace it” is not a decision record. Start with observable facts: crack location, diagnostic value, corrosion, wear limit or failed test. Then state the options and assumptions. A part that is available today can make replacement sensible; a repair may be better when the replacement would delay an otherwise safe job. The goal is not to force a single answer, but to make the trade-off reviewable.
Make the record useful at handover
At completion, compare the approved option with the work actually done. If the scope changed, show the date, reason and new approval. A short summary on the invoice or handover note reduces ambiguity later: what was found, what was agreed, and what follow-up is sensible.
A structured work-order workflow can keep these notes, approvals and attachments together, but the process matters more than the tool: the person answering the phone should be able to reconstruct the decision without guessing.
Common questions
Is a photo always necessary?
No. Use evidence that is proportionate to the decision. A clear test result or technician note may be enough; photos help when they make the finding easier to understand.
What if the customer chooses the lower-cost option?
Record the option, the stated limitations and the approval. Do not silently substitute a different scope later.
Should every uncertainty be written down?
Record uncertainties that can materially change cost, timing, safety or the recommended work. This keeps the estimate honest without turning the note into a technical report.
Keep reading
Instant invoice payments: reconcile transfers with confidence
A practical routine for invoice numbers, payment references, and daily matching when customers pay by instant bank transfer.
Read article
Reconciling card payments: a clean daily terminal close
A practical routine for matching terminal totals, receipts, payouts and unresolved differences for each trading day.
Read articleService keys at intake: a clear handover routine for repair shops
How repair businesses can link keys, access cards and codes to the right job and avoid confusion when the customer collects.
Read articleReady to win back your evenings?
Start for free or get advice with no obligation. We set everything up — you carry on with the repairs.
14-day free trial · Setup included · Cancel any time