Technician Flow
Last reviewed: 2026-06-13
Maintained by: Engineering
ZGRID includes a dedicated technician path so field work does not have to be squeezed into resident or manager interfaces. The technician experience stays connected to the same issue and operational state as Manager Desk, while keeping the mobile surface focused on jobs and execution.
Current Scope
The technician flow currently includes:
- technician onboarding
- technician setup continuation
- technician job visibility
- technician issue detail handling
- technician profile access
Onboarding
Technician onboarding is API-backed rather than being a simple static registration form.
Current shape:
- invite resolution and specialty listing happen through the shared backend contract
- setup and profile completion prepare the technician for job access
- onboarding state is part of the same auth and role model used across the platform
Job Flow
Technicians use the mobile surface for the work that matters in the field.
Current shape:
- technicians have a dedicated route group and job list
- issue detail handling is scoped to the technician role and the relevant job context
- the flow stays connected to the same issue lifecycle used by managers and the API
Relationship to Manager Desk
Technician work is not a separate subsystem.
In practice:
- managers coordinate operational work through Manager Desk
- technicians receive the relevant execution view through mobile
- both sides rely on the same backend workflow state for assignments, status, and visibility
Design Principle
The technician flow exists to keep field execution focused without breaking the shared operational model.
That means:
- role enforcement stays in the API
- issue and job state stays shared with manager-side operations
- the mobile surface stays purpose-built for execution rather than configuration-heavy tasks