Begin with a clear My Day view

The technician should immediately understand the next job, location, scope, timing and important site context.

  • Show the next scheduled job and meaningful changes.
  • Surface site instructions and known system context.
  • Keep dispatch changes visible and acknowledged.

Make drive, arrival and onsite events intentional

Use explicit Start Drive, Arrive or Check In, Check Out and Start Drive events instead of relying on passive location tracking.

  • Capture location only when a disclosed event needs it.
  • Keep raw event timestamps immutable.
  • Derive timecards while allowing audited corrections.

Put the work sequence in the technician's path

Scope, assets, work performed, parts, photos, notes and test results should be captured in the natural sequence of the job.

Design principle

Every required field should have a reason to exist at the moment the technician sees it.

Treat parts and evidence as part of the job

Parts usage affects inventory and job cost; photos, readings and notes affect service quality and future troubleshooting.

  • Consume stocked or serialized material against the job.
  • Capture before/after evidence where it matters.
  • Preserve commissioning results as structured history when possible.

Finish with customer signoff and a clean checkout

Confirm what was completed, what remains, who accepted the work and when the technician left.

  • Summarize work in customer-readable language.
  • Capture signature or acknowledgment where required.
  • Flag unresolved work before completion.