> ## Documentation Index > Fetch the complete documentation index at: https://help.fieldpulse.com/llms.txt > Use this file to discover all available pages before exploring further. # Workflow Blueprint Details > Copy a ready-made Custom Status Workflow into FieldPulse for installation jobs, standard service calls, or emergency work, then adjust the statuses. > **Who uses this:** Administrators build Custom Status Workflows in **Company Settings**, a section only the Administrator role can view; the whole team then sees a job's current stage from its status. **Availability:** All regions. A Custom Status Workflow is the set of statuses a [job](https://www.fieldpulse.com/features/job-management) moves through in FieldPulse, from the first call to a paid invoice. This page holds three ready-made workflows for the three service types businesses most often offer — installation services, standard service calls, and emergency services. Replicate any of them in your own FieldPulse account, then adjust the statuses to match how your business runs that service. ## Overview Each blueprint below is one complete Custom Status Workflow, listed in the order the statuses run, with the status type each one uses. Build them in **Company Settings**, on the **Jobs** tab, under the **Custom Status** subtab. These Custom Status Workflows are unique to the job/service record. The status type is what tells FieldPulse how to treat a status — whether it relates to time recording, a pause, or a completion. To set yourself up for success, first read [Workflow Design Overview](/jobs/workflows/designing-your-workflow), which covers what a workflow is, the key steps and statuses a workflow needs, and what makes a workflow efficient. Build each workflow in the [Custom Status workflow builder](https://webapp.fieldpulse.com/administration/company/service/custom-status) — create each status with a name, color, symbol, and type, drag the statuses into the order you want, and select one workflow as the default. ## Installation service workflow Use this blueprint for jobs that need a systematic setup, from the first opportunity through a paid invoice. | **Order** | **Status name** | **Status type** | | - | - | - | | 1 | New Opportunity | New | | 2 | Installation Scheduled | Any | | 3 | On the Way | Travel Time | | 4 | Prep & Inspection | In Progress | | 5 | Install in Progress | In Progress | | 6 | Testing & Clean Up | In Progress | | 7 | Install Complete | Any | | 8 | Invoice Paid & Complete | Completed | | 9 | Paused | Pending | | 10 | Canceled | Canceled | The screenshot below shows this workflow in a sample account, where a few statuses have slightly different names (Installation Schedule, On the Road, Pending). Name your statuses however suits your team. The Installations custom status workflow in Company Settings, showing its statuses in order as colored chips - New Opportunity, Installation Schedule, On the Road, Prep & Inspection, Install in Progress, Testing & Clean Up, Install Complete, Invoice Paid & Complete, Pending, and Canceled - each with an edit and a remove icon ## Standard service call workflow Use this blueprint for maintenance and general or preventative work. | **Order** | **Status name** | **Status type** | | - | - | - | | 1 | New Service | New | | 2 | Service Scheduled | Any | | 3 | Driving to Service Site | Travel Time | | 4 | Service in Progress | In Progress | | 5 | Service Go Back Needed/Required | In Progress | | 6 | Service Complete | Any | | 7 | Invoice Paid & Complete | Completed | | 8 | On Hold | Pending | | 9 | Canceled | Canceled | The screenshot below shows this workflow in a sample account, where step 5 is named simply Service Go Back. Name your statuses however suits your team. The Standard Service Call custom status workflow in Company Settings, marked as the Default workflow, showing its statuses in order as colored chips - New Service, Service Scheduled, Driving to Service Site, Service in Progress, Service Go Back, Service Complete, Invoice Paid & Complete, On Hold, and Canceled ## Emergency service workflow Use this blueprint for work that needs a quick response, which often means fewer statuses. | **Order** | **Status name** | **Status type** | | - | - | - | | 1 | New | New | | 2 | Emergency Dispatch Scheduled | Any | | 3 | En Route | Travel Time | | 4 | On-Site | In Progress | | 5 | Service Complete | Any | | 6 | Invoice Paid & Complete | Completed | | 7 | Paused | Pending | | 8 | Canceled | Canceled | The Emergency custom status workflow in Company Settings with a Set as default link beside its name, showing its statuses in order as colored chips - New, Emergency Dispatch Scheduled, En Route, On-Site, Service Complete, Invoice Paid & Complete, Paused, and Canceled ## Tips * **Decide who owns each status.** Consider which team member or members are responsible for the action items attached to every status before you put a workflow in front of your team. * **Plan the workflow on a spreadsheet first.** Use the [workflow planning spreadsheet](https://docs.google.com/spreadsheets/d/1T7Sw99CGnGWJ4VxKDgAUqFDhvQah_qpca6yQ6lfxv1Y/copy?gid=1649040090#gid=1649040090) to design your workflows before you build them in the FieldPulse web app. * **Watch the session recording.** [Video walkthrough: setting up workflow foundations in FieldPulse](https://www.loom.com/share/7bffd3957c8e4f8999b5b3fc3039a3dc) records the FieldPulse360 live session on building these workflows.