A service job, end to end
This is an example architecture, not a client engagement. The operation is composite and the names are generic.
Context
A distributed service operation: customers, dispatch, field teams, assets, parts and billing, across multiple locations and several systems.
Operational constraint
Each boundary is a place where context can be lost. The job does not fail at any one step; it accumulates ambiguity until closeout, where the cost lands as rework and delayed billing.
Customer reports a faultDecides: Service desk
| Function | State it is left in | Decides | System of record | Finds out |
|---|---|---|---|---|
| Request | State it is left in:Logged with the customer's words, not the asset's history | Decides:Service desk | System of record:CRM | Finds out:Immediately |
| Dispatch | State it is left in:Assigned on availability, not on what the job needs | Decides:Dispatcher | System of record:Scheduling tool | Finds out:Same day |
| Technician | State it is left in:Arrives without asset history or parts | Decides:Technician | System of record:Nothing portable | Finds out:On site |
| Finding | State it is left in:Real scope differs from the reported fault | Decides:Technician | System of record:Notes and photos | Finds out:On site |
| Quote and approval | State it is left in:Waiting on a decision nobody owns | Decides:Nobody defined | System of record:Email | Finds out:Days |
| Parts | State it is left in:Ordered against an unconfirmed scope | Decides:Parts desk | System of record:Inventory | Finds out:After approval |
| Closeout | State it is left in:Billing reconstructs the job from fragments | Decides:Administration | System of record:ERP | Finds out:Weeks |
A dashed marker means the handoff has no defined owner and depends on a person carrying the context.
How to read it
- The expensive step is not the visit. It is the approval loop that has no owner and no state.
- Three boundaries depend on a person carrying context that no system holds.
- Billing is slow because the job was never in one place; administration is reassembling it after the fact.
- Lifecycle ownership and an approval state with a defined owner fix more here than a new mobile app would.