Overview
Project stages define how work progresses from sale to completion. Keeping them clean and current helps every team member understand what happens next.
Why this matters first: Better stage structure improves visibility, customer communication, and automation reliability.
Prerequisites
Admin access to database stage settings
Agreed stage names and process order
Internal policy on required stage inputs
Step-by-Step Instructions
Part A: Open Job Stage Settings
Go to Manage Database → Database.
Open Stages → Job Stages and choose the job type.
Review current stage list before making edits.
Part B: Edit Existing Stages
Use left Edit toggle to enable/disable stages.
Use Trash to remove outdated stages.
Use right Edit to change stage details (name, video URL, include in path, required flags).
Edit stage inputs (labels/keys/required settings) as needed.
Part C: Add New Stages
Click Add in Job Stages.
Enter stage details, then click Add to save.
(Optional) Configure advanced controls like Bypass Required Fields or user-specific visibility.
Pro Tips
💡 Rename stages carefully—changes can affect reports, automations, and customer portal wording.
⚠️ After major stage edits, run a test project to verify automations still trigger at the right time.
Real-World Example
An energy storage installer added separate stages for “Permit Revision” and “Utility Re-Submission.” This gave leadership better visibility into delays and improved forecast accuracy.
Troubleshooting / FAQ
Question | Answer |
Stage updates not reflected for users | Ask users to refresh and verify they are in the correct job type pipeline. |
Automations stopped working after rename | Update automation conditions that referenced old stage names/keys. |
Can't delete a stage | Stage may be locked by dependencies or active records; disable first, then migrate data. |
Change Log Summary














