The estimate must retain its version and approval per service or part, separating diagnosis from authorization to begin.
Index
A customer may accept only part of a proposed repair; a single authorization does not show what the workshop may perform.
The rule that changes the scope
The estimate must retain its version and approval per service or part, separating diagnosis from authorization to begin.
Service software may support simple approval; an extension handles partial choices and revised estimates without losing acceptance.
The customer should see an item's explanation before approving it. If a part depends on a declined service, the system must show that relationship and request a new decision rather than generate an incoherent workshop instruction. Add an estimate whose total changes after partial approval to testing. The executable version must remain linked to the accepted set while a later proposal stays under review until explicitly confirmed.
Specify operational deliverables
- Associate each proposed item with the observed defect and corresponding service.
- Separate approved, declined and awaiting-response items with clear execution boundaries.
- Keep the accepted version when another repair is added after disassembly.
Test the exception before acceptance
In a hypothetical scenario, a customer approves two activities and declines a third; the executable work order must include only the authorized set.
Reference for assessing scope
NN/g: writing task scenarios for usability testing
Prepare your project with Quantum9
Bring a partially accepted estimate and the process for communicating new findings.