> ## 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.
# Setting Up ClearPath Status Action Flows
> Configure the instructions, action buttons, and widgets a FieldPulse tech sees at each job status, then attach the flow to a job or job template.
> **Who uses this:** Admins build Status Action Flows in Company Settings; technicians follow them in the field. **Availability:** Included with your FieldPulse subscription at no extra cost.
A Status Action Flow tells your team exactly what to do during each status of a job — the instructions to read, the buttons to tap, and the job details to see on screen. Status Action Flows are part of [ClearPath](https://www.fieldpulse.com/features/clearpath), and you build one flow per service on top of a Custom Status Workflow you already use.
## Overview
A Status Action Flow adds the detail to a Custom Status Workflow. The workflow is the blueprint — the high-level statuses a type of work moves through — and the flow specifies the exact actions and instructions for each of those statuses. Flows can be as simple or as complex as you need, and each one is built from three pieces:
* **Status Instructions** — the written steps for the technician at that status.
* **Action Buttons** — quick-tap buttons that complete a task without navigating through multiple screens.
* **Widgets** — the job details shown on the Focus View screen, in the order you set.
Build a separate flow for each service you offer. If your business handles water heater, sewer line, and faucet installations, each service gets its own Status Action Flow while all three use the Installation Custom Status Workflow as their blueprint — so each flow can name the specific forms to fill out and the safety or regulatory measures that apply to that service.
**Action Buttons**, **Status Instructions**, and **Focus View** can be used independently or in tandem with one another.
## Video walkthrough
## Before you begin
* Build the **Custom Status Workflow** you want to guide first. A Status Action Flow attaches to an existing workflow, so its statuses have to exist before you can add actions to them. [Workflow Design Overview](/jobs/workflows/designing-your-workflow) covers what a workflow needs and what makes one efficient.
* To start from a proven structure, copy one of the [workflow blueprints](/jobs/workflows/blueprints) for installations, standard service calls, and emergency jobs.
* Decide which services need their own flow, and list the statuses in each workflow you will configure.
## Step-by-step setup
Create the flow first, then configure its statuses one at a time — steps 2 through 5 cover a single status, so repeat them for every status in the workflow.
### 1. Create the flow
1. Go to **Company Settings**, open the **Jobs** tab, then the **Custom Status** subtab.
2. On the workflow you want to guide, select **Manage Status Action Flows**.
3. Add a flow and name it for the service it guides — Water Heater Install, Sewer Line Install, Garage Door Install.
### 2. Write the Status Instructions
Open a status in the flow and write its **Status Instructions** — what you want the technician to do during that step of the workflow. List the instructions in numerical order so the technician can follow them top to bottom.
### 3. Add the Action Buttons
Add **Action Buttons** for the tasks the technician should complete at that status. You can add 0 to 10 custom-labeled buttons per status, drawn from 27 unique actions — creating an estimate or invoice, filling a form, clocking in and out, taking photos, sending a customer communication, generating a job report, and more.
Label each button in the words your team uses. Name a button "Complete Install Checklist" rather than "Fill out Custom Form."
### 4. Choose and order the Focus View widgets
Widgets display the job's details in an easy-to-read format and appear only on the Focus View screen. Up to 32 unique widgets are available, and you add, remove, and reorder them per status so your techs see everything they need and nothing they don't. The [ClearPath Widget Details](/jobs/workflows/clearpath/widget-catalog) describes every option.
Our best-practice recommendation is to include at minimum these widgets in this order, top to bottom: **Job Title**, **Job Status**, **Status Instructions**, then **Action Buttons**. Keep **Action Buttons** toward the bottom of the layout, where they are easier to reach with a thumb.
Each status also carries three toggles that set how much freedom the technician has on the screen — see the Settings reference below.
### 5. Check the layout in Mobile Preview
Use the **Mobile Preview** on the right side of the screen while you choose widgets, to see how the screen will appear to your team. The preview does not update with the information you have entered — it is a mock-up, so use it to confirm the layout and widget order rather than to check real job data.
### 6. Add the flow to jobs and job templates
Once a Status Action Flow is configured, add it to Job records and to Job templates — see [Setting Up Job Templates](/jobs/jobs-tasks/creating-job-templates):
1. When you create a Job record or Job template, select the **Status Workflow** you want to use.
2. In the **Status Action Flow** field that appears, choose the flow that will guide your team through the job.
Only the Status Action Flows associated with the Custom Status Workflow you selected are available in the dropdown menu for you to choose from.
## Settings reference
Three toggles control how much freedom the technician has at each status:
| **Toggle** | **On** | **Off** |
| ------------------------------------------- | ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| **Display Action Menu** | The technician has access to the green **Actions** button and its menu | The technician has access only to the Action Buttons you selected |
| **Ability to Change Status** | The technician can change the job's status manually | The technician cannot move the status forward manually and must use the designated buttons to advance or pause the job |
| **Restrict User Access to Focus View Only** | The technician cannot navigate away from the Focus View you set up for each status | The technician can move around the rest of the app |
With **Display Action Menu** on, the green **Actions** button appears on the job:
**Ability to Change Status** decides whether a technician can set the status by hand, and **Restrict User Access to Focus View Only** keeps the technician on the Focus View screen — a simplified interface that reduces distractions and holds the focus on the key tasks:
## FAQs
### Do I need a separate Status Action Flow for every service?
Not required, but recommended. Create one Status Action Flow per service type so each job gets instructions that fit the work. See [Setting Up ClearPath Status Action Flows](/jobs/workflows/clearpath/status-action-flows).
### How many Action Buttons can I add to a status?
Add 0 to 10 custom-labeled buttons per status, drawn from 27 available actions.
## Related articles
* [ClearPath Overview](/jobs/workflows/clearpath/overview)
* [How to Use ClearPath in the Field (Focus View)](/jobs/workflows/clearpath/focus-view)
* [ClearPath Widget Details](/jobs/workflows/clearpath/widget-catalog)
* [Workflow & ClearPath FAQs](/jobs/workflows/clearpath/overview)
* [Workflow Design Overview](/jobs/workflows/designing-your-workflow)
* [Workflow Blueprint Details](/jobs/workflows/blueprints)
Your setup is working when a technician opens an assigned job, reads the instructions for the current status, and finishes that status with the buttons on screen — without calling the office to ask what comes next.
## Related topics
- [ClearPath Overview](/jobs/workflows/clearpath/overview.md)
- [ClearPath](/jobs/workflows/clearpath/index.md)
- [ClearPath Widget Details](/jobs/workflows/clearpath/widget-catalog.md)
- [How to Use ClearPath in the Field (Focus View)](/jobs/workflows/clearpath/focus-view.md)