The Paused and Resumed job statuses are system default statuses designed specifically to support accurate labor time tracking when a technician temporarily stops work on a job and then returns later the same day. These statuses include built‑in system logic that cannot be modified. Using them incorrectly, or outside of their intended purpose can result in inaccurate labor tracking and reporting.
Best Suited for:
- Back Office administrators
- Dispatchers and schedulers
- Users responsible for job workflow configuration
- Teams monitoring labor time accuracy
Important Information:
- Paused and Resumed include system automation that cannot be modified
- They must be used together to track labor time correctly
- They are intended only for same‑day job pauses
- Incorrect usage will result in inaccurate labor reporting
Best Practices:
- Use Partially Completed for next‑day returns
- Do not mix Paused with Started or Completed
- Rename statuses only for clarity, not behavior changes
- Hide Paused and Resumed if they are not part of your workflow
What the Paused Status Does:
The Paused status temporarily stops labor time tracking for the current job. Key behavior:
- Labor time is stopped for the current day
- The job remains active
- The technician is expected to return to the same job later the same day
System Logic Behind Paused and Resumed:
Paused and Resumed are system default statuses with built‑in automation. Important details:
- Paused has logic that stops labor time
- Resumed has logic that restarts labor time
- This logic cannot be changed
- Renaming the statuses does not alter their behavior
If you do not want system logic tied to a status, a custom status must be created instead.
When to Use Paused and Resumed:
The Paused and Resumed statuses should be used only in these scenarios:
- A technician takes a break during a job
- A technician leaves temporarily and returns later the same day
Paused must always be followed by Resumed to ensure labor time is tracked correctly.
When Not to Use Paused and Resumed:
Paused and Resumed should not be used in the following situations:
- When returning to the job on a different day
- After the job has been moved to Completed
- When Resumed is selected without Paused being selected first
- When Paused is followed by Started instead of Resumed
Using Paused and Resumed outside of their intended workflow will cause labor time to track incorrectly.
Returning to a Job on a Different Day:
If a technician needs to return to a job on a different day, the correct status is:
- Partially Completed
Paused and Resumed are not designed for multi‑day job returns. If Partially Completed is used and the technician returns later the same day, labor time will not track correctly. In same‑day scenarios, Paused and Resumed must be used instead.
Why Paused Must Be Followed by Resumed:
Paused and Resumed work as a paired sequence. Correct sequence:
- Paused → Resumed
Incorrect sequences that break labor tracking:
- Paused → Started
- Resumed without Paused
- Paused → Completed
The system requires Resumed to correctly restart labor time after a pause.
Renaming Paused and Resumed:
Paused and Resumed can be renamed for clarity. You can rename them by navigating to:
- "My Office" > Click Estimate & Job Statuses > Click Job Statuses
- Click the pencil icon beside the status
- Update the status Name
- Save
Important clarification:
- Renaming does not change system logic
- Automation remains intact regardless of the name
Restricting Technician Visibility:
If your technicians:
- Do not take breaks during jobs
- Do not return to jobs later the same day
You may choose to:
- Hide the Paused and Resumed statuses from technician views
- Prevent technicians from selecting these statuses
This helps reduce confusion and prevents accidental misuse.