Keep reassigned work from being silently completed offline
Dispatch reassigns a job while the original technician is underground. That device later uploads completion against the old assignment. Preserve the technician’s work while honoring current server authority.
- Focused work estimate
- 3h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Authorization · Conflict resolution · Distributed state
Estimated field mix
- Mobile40%
- Security30%
- Distributed systems30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
The fictional Vale facilities team services equipment in basements with poor reception. Technicians receive assigned work orders, record checks, and attach synthetic equipment photos. The practice app uses an on-device database and a stub sync service; background location tracking is excluded.
Setup prerequisites
- Synthetic work orders and a revisioned sync contract
- An emulator with controllable connectivity and app lifecycle
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- FIELD-102 · Commit a completed checklist item before showing it saved
- FIELD-101 · Tell technicians which work orders are available offline
- FIELD-103 · Make inspection inputs usable with large text
- FIELD-104 · Keep photo evidence attached after the app is suspended
- FIELD-105 · Explain why a work order is not ready to finish
- FIELD-106 · Drain the sync queue without duplicating completed visits
Acceptance criteria
- Sync includes the assignment revision that authorized the offline visit.
- Reassignment rejection moves local work into an explicit review-required state without marking the job complete.
- The technician can inspect their unsynced notes and a redacted export while server-only actions remain blocked.
Implementation constraints
- Do not automatically apply old work to the new assignee; supervisor resolution is a documented stub contract.
Verification to include
- Sync a completion with the current assignment revision and confirm acceptance.
- Reassign before reconnecting and reject the old revision; retain local work and prevent repeated automatic completion retries.
Deliverables
- Reassignment conflict flow and preserved-work recovery fixture
Rollout and recovery
Pilot with forced reassignment scenarios; disable offline finishing if authority conflicts cannot retain work safely.
Value of the work
For the engineer: Practice durable local state, mobile lifecycle recovery, and conflict resolution in realistic offline workflows.
For the team: Review whether an engineer can protect field work through crashes, interrupted uploads, and reassignment.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.