Guides
Appliance repair SOP checklist: version, review and change log
An appliance repair SOP checklist goes stale at the skills match. Version it, review it quarterly, log each change and tie outside rules to the step they touch.
What to take away
- A daily checklist of eight items (intake, triage, skills match, routing, arrival prep, parts loop, work documentation, return visits) only stays true if the document itself is managed.
- Put a version number, a review date and one owner in the header.
- Review it every quarter, and again within 30 days of any complaint that reaches a manager.
- Log each change as one linedate, what changed, who approved it.
- Tie every outside rule to the one step it touches, so a rule change points to a single review.
What belongs in the header
Give the document a version number, a review date and one owner in the header. Those three fields answer the questions that follow a bad day: which list was in use, when it was last checked, and who decides what changes.
The owner is usually the service manager, or the owner in a two-van operation. One name matters because a list owned by everyone is reviewed by no one. The version number lets a technician and the office confirm that they are reading the same page.
When to review it
Review the checklist quarterly against last month's callbacks, parts delays and near misses. Re-read it within 30 days of any complaint that reaches a manager. A list that changes weekly is too unstable to train against.
| Trigger | What to re-read | Who owns it |
|---|---|---|
| Quarter end | The whole list | Checklist owner |
| A complaint reaches a manager | The items it touched, within 30 days | Service manager |
| A callback or safety near miss | The step where the problem started | Checklist owner |
| A new or changed outside rule | The one step the rule attaches to | Checklist owner |
| A technician joins, leaves or gains a ticket | Item 3, the skills match | Service manager |
Most items break at the same point in the day, and that point is the route. The buffers and reserved capacity for urgent calls set out in how to schedule appliance repair jobs without delays are what the rest of the list quietly assumes.
Where a checklist goes stale first
Rot starts in item 3. A skills matrix nobody updates sends gas work to a technician without the ticket, and the route collapses before lunch. The hiring and training guide covers how that matrix is built and refreshed.
Arrival prep goes next. Both items are maintained by hand, and neither shows up in the day's revenue, so nobody notices the decay until a job goes wrong. That is why the trigger table puts every change of staff or ticket against item 3.
Keeping the change log
Log changes as one line each: date, what changed, who approved it. Update the dispatch system the same day, so the version technicians see matches the paper copy. Shops comparing dispatch software should check that it can show a version at all.
A log this short gets used. Reading it before the quarterly review shows which step keeps moving, and a step that keeps moving may need a clearer owner rather than another edit.
Outside rules as review triggers
Each outside rule belongs to one named step, so a change in the rule points to one review rather than a rewrite. Local licensing and gas permits sit outside the list but change what a technician may legally do.
- Item 2, triagegas odor, active leaks and electrical damage are sorted here, before the job is routed.
- Items 1 and 7, warrantycapture warranty status at intake and state terms at the appliance. The FTC guide to federal warranty law notes that federal law prohibits disclaiming implied warranties on a consumer product if you offer a written warranty for it or sell a service contract on it.
- Item 7, opening the machineOSHA's lockout/tagout standard, 29 CFR 1910.147, covers servicing and maintenance of equipment where unexpected energization or stored energy could injure employees. The PPE rules in 29 CFR 1910.132 apply before a technician starts work.
The appliance repair licensing and compliance guide is the companion read before you rewrite item 3.
A bad-day test before each review
Test the list against a bad day, not a planned one. Ask whether the parts coordinator and the dispatcher could still rebuild a late van's afternoon from reserved capacity. Each item needs one named owner and one clock time, because without both the list describes work instead of assigning it.
- Every item has one named owner and one clock time.
- The route holds if one van is late.
- The version in the dispatch system matches the version in the header.
- The last complaint to reach a manager has been traced to an item.
- The change log has an entry for every edit since the last review.
