> ## Documentation Index > Fetch the complete documentation index at: https://helpdocs.servinix.com/llms.txt > Use this file to discover all available pages before exploring further. # Job lifecycle > The job status stages a Servinix work order moves through—from Assigned to Closed—what each stage means, and how transitions trigger time and billing events. # Job lifecycle Every job in Servinix moves through a series of statuses that reflect where the work stands — from the moment a dispatcher schedules it to the moment payment is collected. This article explains each status, who drives the transition, and what happens at each stage. ## Two parallel state machines Servinix tracks job progress on two levels: * **Job status** — the shared state of the job itself, visible to every technician assigned to it and to dispatchers in the portal. * **Technician status** — the per-tech position, because multiple technicians can be assigned to a single job and each moves through the field independently. ### Job statuses | Status | What it means | | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Scheduled** | The job is created and assigned but no technician has started travel. | | **Dispatched** | A technician has accepted the job and started traveling to the site. The job has also reached this status when travel is marked complete but work has not yet started. | | **In Progress** | At least one technician has tapped **Start work** on site. The job clock is running. | | **On Hold** | The job is paused for the whole team — work stops and the timer suspends. Any assigned technician can trigger a pause via the **Step away from job** sheet. All technicians see the paused state simultaneously. | | **Payment Pending** | Field work is done (all tasks complete, **Finish work** tapped) but payment has not yet been collected. | | **Done** | Work and payment are both complete. The job is closed. | | **Cancelled** | The job was cancelled by a dispatcher or admin before or during execution. | ### Technician statuses Each technician on a job independently holds one of these statuses: | Status | What it means | | ------------- | -------------------------------------------------------------------------- | | **Available** | Not assigned to an active job. | | **Assigned** | Assigned to a scheduled job but travel hasn't started. | | **On Route** | Travelling to the job site (travel started via the **TRAVEL** button). | | **On Site** | Arrived at the address (**I'm Here** tapped) but has not yet started work. | | **Working** | **Start work** tapped — actively working the job. | | **On Break** | Took a personal break (does not pause the job for teammates). | ## How a job moves through the lifecycle **Scheduling:** A dispatcher creates the job in the portal and assigns it to one or more technicians. The job enters **Scheduled** status. Technicians see it in their Schedule tab. **Travel:** The lead technician opens the job in the mobile app and taps **TRAVEL**. The job moves to **Dispatched**. The app shows the EN ROUTE screen with live travel time, distance, and a button to open maps navigation. **On site:** When the technician arrives, they tap **I'm Here**. Their personal status becomes **On Site**. The job stays **Dispatched** until someone taps **Start work**. **Working:** Each technician taps **Start work** (or the configured label for your workspace) to begin. The first tap transitions the job to **In Progress**. Subsequent taps by other technicians on the same job are accepted without changing the job status again. **Task work:** The technician works through the task checklist on the On Site Working screen, marking each item complete. Tasks with attached forms must be submitted before the item counts as done. **Step away:** If a technician needs to step away personally, they tap the **Break** or **Pause** tool on the working screen, which opens the Step Away sheet. Taking a personal break moves only that technician to **On Break** — teammates continue unaffected. Choosing **Pause for everyone** moves the whole job to **On Hold**. **Finishing:** When all tasks are marked complete, the **Finish work** button (or the configured label) becomes active. Tapping it ends the job clock and advances the job toward closing. The app moves to the Wrapping Up screen where the technician can capture a customer signature, review the invoice, and collect payment. **Payment:** The technician can send a payment link via SMS or email, or record a cash or check payment on the spot. Once payment is collected, the job closes as **Done**. If payment is skipped, the job sits as **Payment Pending** and appears in the Completed tab for follow-up. ## Related * [Accept and travel to a job](/field-service-management/jobs-and-work-orders/accept-and-travel-to-a-job) * [Complete job tasks](/field-service-management/jobs-and-work-orders/complete-job-tasks) * [Start and end a shift](/field-service-management/scheduling-and-dispatch/start-and-end-a-shift) * [Schedule a job](/field-service-management/scheduling-and-dispatch/schedule-a-job)