Daily Operation and Workflow Procedures
This domain tests the repeatable start-of-shift, in-shift, and end-of-shift routines that keep work flowing and records complete. Expect questions on device state, job queue handling, sync checkpoints, exception logging, and handover.
Core rules and concepts
- Start of shift: charge or swap battery, power on, confirm time and network, run a scan test, confirm the assigned work queue, and check free storage.
- Treat the work order as the unit of work: open it, capture required evidence, update status at each transition, and close only after the record is validated and synced.
- Sync at defined checkpoints, not only at the end of the shift. Good checkpoints are after each completed job and before any break longer than the queue can hold.
- Log exceptions as they happen: damaged tag, missing part, no signal, wrong location. Exceptions are data, not noise.
- End of shift: confirm queue empty or explain remaining items, confirm sync status, swap or charge battery, and write a handover note naming open jobs and device faults.
Worked example
A technician starts an eight-hour outdoor shift at -5 C with a battery at 38%. Correct action: swap to a fully charged battery before leaving the warm cabin. Reasoning: cold reduces usable capacity and the device may shut down early; a mid-shift swap in the field risks losing the queue if the device is not powered down correctly. The technician records the swap, confirms the clock and signal, runs a scan test, and only then opens the first work order.
Traps that cost marks
- Relying on sleep mode for a full shift instead of a charged battery.
- Closing a job before sync confirmation.
- Saving all syncing for end of shift.
- Omitting exception notes, which makes later reconciliation impossible.
- Handing over without naming open jobs and device faults.