The Complete Repair Service Workflow: From Intake to Collection
A full walkthrough of the seven-stage repair status workflow — intake, quoted, accepted, in progress, completed, collected, and cancelled — explaining what happens at each stage, who is responsible, and what triggers the transition to the next step.
Key Takeaways
- A structured seven-stage workflow eliminates ambiguity and ensures every repair follows the same predictable path from intake to collection.
- Each status transition is triggered by a deliberate action — not a timer — so accountability is clear at every step.
- The intake stage captures all critical information upfront, reducing callbacks and misunderstandings later in the process.
- Quoting and acceptance stages create a documented agreement between shop and customer before any work begins.
- The completed-to-collected handoff is where many shops lose track; a formal collection stage prevents devices lingering unclaimed.
- Cancelled repairs should still be recorded in full so the shop retains a complete audit trail and can analyse lost-revenue patterns.
Why a Structured Repair Workflow Matters
Repair shops that rely on informal status tracking — sticky notes, verbal updates, or a single 'in progress' label — inevitably lose visibility as volume grows. A structured workflow divides the repair lifecycle into discrete, well-defined stages so that every member of staff knows what has been done, what needs doing next, and who is responsible. This predictability benefits customers too: they receive timely updates at each transition and never need to chase the shop for information. From a business perspective, a formalised workflow also produces clean data. When every repair passes through the same stages, you can measure average turnaround time, identify bottlenecks, and benchmark individual engineer performance. Without consistent stages, reporting is guesswork. The seven-stage model — intake, quoted, accepted, in progress, completed, collected, and cancelled — covers the full spectrum of outcomes and is flexible enough to accommodate quick fixes that skip the quoting stage as well as complex multi-part repairs.
Stage 1 — Intake
Intake is the moment a customer hands over a device and the shop assumes responsibility for it. The goal at this stage is to capture everything needed to diagnose, quote, and ultimately return the device. This includes the customer's contact details, a description of the fault in the customer's own words, the device make, model, and serial number, and any cosmetic damage noted at the point of handover. Documenting pre-existing damage is essential — it protects the shop against later disputes about scratches or dents that were already present. A photograph attached to the repair record is the gold standard. The intake stage also records the customer's preferred communication channel (WhatsApp, email, SMS, or phone) and any urgency notes. Once intake is complete, the repair moves into the diagnostic queue. In a well-run shop, the intake stage should take no more than three to five minutes per device.
Stage 2 — Quoted
After a technician has diagnosed the fault, the repair moves to the quoted stage. Here the shop records the proposed fix, the parts required, the labour estimate, and the total price. The quote should be itemised so the customer can see exactly what they are paying for — transparency builds trust and reduces disputes at collection. The system sends the quote to the customer via their preferred channel and the repair remains in the quoted state until the customer responds. It is good practice to set a follow-up reminder — if no response is received within 48 hours, a polite nudge can recover repairs that would otherwise stall. The quoted stage is also where margin visibility matters. By recording the cost price of parts alongside the customer-facing price, the shop can see gross margin per repair before any work begins, enabling better pricing decisions over time.
Stage 3 — Accepted
When the customer approves the quote, the repair transitions to the accepted stage. This is a critical legal moment: the customer has now agreed to the scope and price of the work, and the shop has a mandate to proceed. The accepted stage is the trigger for parts allocation. If the required parts are in stock, they are reserved against the repair so they cannot be sold or assigned elsewhere. If parts need to be ordered, the repair remains in the accepted state with a 'parts on order' flag until stock arrives. Accepted is also the appropriate moment to schedule the repair into an engineer's workload. Shops with multiple technicians benefit from an assignment system that matches repair type to engineer skill set — a phone screen replacement should not be queued behind a complex motherboard rework if a specialist is available for the latter.
Stage 4 — In Progress
The in-progress stage begins when an engineer physically starts work on the device. Moving a repair into this state signals to the rest of the team that the device is on a workbench and should not be disturbed. During this stage, the engineer may add internal notes — observations about additional faults discovered, photos of internal components, or time logs. If additional work is needed beyond the original quote, best practice is to pause the repair, issue a revised quote, and wait for customer approval before continuing. This prevents scope creep and protects the shop against customers who refuse to pay for undisclosed extras. The in-progress stage is typically the longest in duration and the one most prone to bottlenecks. Monitoring average time in this stage, segmented by repair type, is one of the most valuable metrics a shop manager can track.
Stage 5 — Completed
A repair moves to completed when the engineer has finished the work and tested the device. Testing is non-negotiable — returning a device that fails on first use destroys customer confidence and generates costly rework. The completed stage triggers a customer notification informing them that the device is ready for collection. This message should include the shop's opening hours, the total amount due, and accepted payment methods. Internally, the completed stage is also the moment to finalise the repair record: confirm the parts actually used (which may differ from the original quote if substitutions were made), record the actual labour time, and attach any post-repair photographs. Clean data at the completed stage feeds accurate reporting downstream. Devices should not remain in the completed state indefinitely. Setting a retention policy — for example, notifying the customer again after seven days and reserving the right to charge storage after 30 — protects the shop against abandoned devices.
Stage 6 — Collected
Collection is the final positive outcome. The customer arrives, pays for the repair, and takes the device. At this point, the system should record the payment method and amount, generate a receipt, and — critically — start the warranty clock. Automatic warranty activation on collection means the shop does not need to remember to apply it manually, and the customer's warranty period is calculated from the day they actually received the repaired device, not the day the work was completed. The collection stage is also an opportunity for a brief quality check with the customer present. Inviting them to power on the device, test the repaired function, and confirm satisfaction while still at the counter prevents call-backs and disputes. Any issues identified at this point can be resolved immediately, which is far cheaper than a return visit. Once collected, the repair record is closed but retained permanently for warranty reference and reporting.
Stage 7 — Cancelled
Not every repair reaches completion. A customer may decline the quote, fail to respond, or request the device back unrepaired. The cancelled stage captures these outcomes. It is important that cancelled repairs are not simply deleted — they contain valuable data. Analysing cancellation reasons reveals whether the shop's pricing is out of line, whether certain repair types are consistently declined, or whether communication gaps are causing customers to disengage. When a repair is cancelled after parts have already been ordered or allocated, the system should release those parts back to general inventory automatically. If a diagnostic fee applies, the cancellation workflow should prompt the cashier to collect it before releasing the device. A well-designed cancellation process ensures the shop does not absorb costs silently and retains a complete picture of demand, including demand that did not convert into revenue.