Job Status Logic and Customization Overview – Service Fusion

Job statuses are essential to managing workflow in Service Fusion. Each default status has specific logic tied to it, which affects how jobs behave in the system. While Service Fusion allows for flexibility and customization, it is not recommended to disable any of the default statuses, as doing so may disrupt workflow functionality or make jobs invisible on dashboards.

Best Practices:

Avoid disabling default statuses unless absolutely necessary
Review the logic tied to each default status before customizing your workflow
Use renaming strategically, but be aware of the underlying system behavior
When creating new statuses, understand that they will not inherit system logic

Customizing Statuses:

All statuses listed in My Office > Estimate & Job Statuses can be renamed, including default statuses
Renaming a status does not change its logic
- Example: Renaming the On The Way status to Waiting on Parts will not stop the system from tracking drive time when selected in the worker app

Short Codes and Custom Statuses:

Short Codes indicate the logic behind a status
Custom statuses do not automatically have system logic applied

Impact of Inactivating Statuses:

Inactivating a status with system logic will cause jobs in that status to become invisible
Jobs with inactive statuses will not appear on the Jobs Dashboard, Dispatch Grid and Calendar
If a job cannot be found, check the status settings in My Office > Estimate & Job Statuses

Default Job Statuses and Their Logic:

Name	Status Category	Short Code	Logic / Actions
Unscheduled	Open Jobs	01_UNS	Job created with no start date; technician may or may not be assigned
Scheduled	Open Jobs	02_SCH	Job has a date but no technician assigned
Dispatched	Open Jobs	03_DSP	Job has a date and assigned technician
Delayed	Open Jobs That Are In Progress	04_DEL	Job has been delayed
On The Way	Open Jobs That Are In Progress	05_OTW	Technician enroute; begins Drive Time; may trigger customer notifications
On Site	Open Jobs That Are In Progress	06_ONS	Technician has arrived; stops Drive Time; may begin Labor Time
Started	Open Jobs That Are In Progress	07_STA	Technician begins work; starts Labor Time
Paused	Open Jobs That Are In Progress	08_PAU	Technician leaves site temporarily; stops Labor Time; must be followed by Resumed
Resumed	Open Jobs That Are In Progress	09_RES	Labor Time resumes after a pause; must be preceded by Paused
Cancelled	Open Jobs	11_CXL	Job cancelled via the More menu on the job screen
Partially Completed	Open Jobs That Are In Progress	16_PCMP	Technician will return on a different date; stops Labor Time
Completed	Open Jobs That Are In Progress	10_CMP	All work completed; job ready to be invoiced; stops Labor Time
Job Closed	Closed Jobs	12_CLS	Job closed for later invoicing or after invoice deletion
Invoiced	Closed Jobs	14_INV	Job has been invoiced
To Be Invoiced	Closed Jobs	13_BLL	Invoice not yet sent; job cannot be edited until status is changed
Paid In Full	Closed Jobs	15_PID	Must be manually applied; restricts ability to send the invoice on Field Worker App

Paid In Full – Explanation:

The phrase Paid In Full is used in two different contexts in Service Fusion, which can cause confusion:

1. Invoice Status (Dashboard View):

Appears under the "Invoiced" section on the Jobs Dashboard
Indicates that the invoice has no remaining balance
The job status remains Invoiced, but the invoice is fully paid

2. Job Status (Closed Jobs):

Appears under the "Closed" section of the Jobs Dashboard
Indicates that the job status has been manually changed to Paid In Full
This status does not automatically apply when payment is received
Must be manually updated by the user

Note: In the field worker app, jobs with the Paid In Full status lose the ability to email or print the invoice PDF. To restore these functions, change the job status back to Invoiced.