Explain why a work order is not ready to finish
Finish visit is disabled with no explanation when a required reading or photo is missing. Technicians tap through every section to find the blocker.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Workflow modeling · Validation · Offline UX
Estimated field mix
- Mobile100%
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.
Acceptance criteria
- A completion summary lists missing required answers and attachments with navigation actions.
- Optional notes never block completion.
- Finishing offline creates a pending completion operation and labels it as awaiting sync rather than server-confirmed.
Implementation constraints
- Derive readiness from the current local revision and the downloaded checklist version.
Verification to include
- Fill the required inputs and finish offline; a pending operation is visible after restart.
- Remove a required photo and leave optional notes empty; only the photo blocks completion.
Deliverables
- Completion-readiness summary and offline finish cases
Rollout and recovery
Enable the summary before completion changes; pause finishing if checklist versions cannot be resolved.
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.