ORIGINAL COMPANY-CONTEXT PRACTICE
Reconcile service work recorded while equipment is offline
Original practice scenario: A hypothetical field technician records a repair and spare-part usage without connectivity. Another team changes the work order before synchronization. Design conflict handling.
Written for independent practice using company context; this is not a verified question from a company interview.
A REASONED APPROACH
Model answer.
Keep technician observations separate from centrally authorized work-order state. Offline entry should preserve useful evidence without silently overwriting changes that the technician could not have seen.
Work through it
- Assign stable work-order, task and local-operation identities, recording the version viewed by the technician and the time of each observation.
- Merge independent observations where valid, but route conflicting task closure, replacement or quantity decisions through an explicit review state.
- Reconcile spare-part consumption and work completion idempotently, retaining the source operation and any later correction rather than replaying the same offline action twice.
Tradeoffs to discuss
- Local capture improves field continuity but delays conflict discovery; strict online authorization reduces ambiguity while limiting offline usefulness.
Common pitfalls
- A successful sync acknowledgment must distinguish stored evidence from approved completion.
- Device clock time is not enough to decide whose edit should win when teams worked concurrently.