FieldCampPipeline Stages & Configuration | FieldCamp
Configure pipeline stages, transitions, and automation rules for service requests in FieldCamp. Customize colors, stage order, required fields, and workflows.
Accessing Pipeline Configuration
Go to Settings > Pipeline Configuration. Only Admin and Superadmin roles can access this page. See Roles and Permissions for details.
You will see a list of all objects grouped into two sections:
- System Objects — Jobs, Visits, Clients, Requests, Estimates, Invoices, Products/Services
- Custom Objects — Any custom objects you have created with pipelines enabled
Each row shows the object name, description, and the number of stages and transitions configured. Click Requests to open the request pipeline settings.
AI-First: Ask About Pipeline Config
Open the Command Centre and ask:
- "What stages does the request pipeline have?"
- "How many requests are in each stage?"
- "Show me the pipeline configuration"
See AI Skills for all available commands.
Default Request Stages
FieldCamp ships with 12 request stages organized across three categories:
| Category | Stage | Description |
|---|---|---|
| Requests | New Request | Just created, no action taken |
| Requests | Unscheduled | Captured but no inspection scheduled |
| Requests | Overdue | Past expected response date |
| Pipeline | Inspection Scheduled | Site visit booked |
| Pipeline | Inspection Complete | Site visit done, ready for quoting |
| Pipeline | Quote Created | Estimate prepared, not yet sent |
| Pipeline | Quote Sent | Estimate delivered, awaiting response |
| Pipeline | Converted | Turned into a job, estimate, or invoice |
| Archived | Lost - No Response | Customer never responded |
| Archived | Lost - Rejected | Customer rejected the quote |
| Archived | Cancelled | Request cancelled |
| Archived | Duplicate | Duplicate entry, kept for records |
Managing Stages
Viewing Stages
Open the Stages tab to see all configured stages. Each stage has:
| Property | Description |
|---|---|
| Label | The display name your team sees (click to edit inline) |
| Value | Internal slug identifier used by the system |
| Color | A color picker to assign a visual color to the stage |
| Category | One of three categories: To Do, Doing, or Done |
Creating Custom Stages
- Click Add Stage at the bottom of the stage list
- Enter a label (e.g., "Pending Approval")
- Pick a color from the color picker
- Select a category (To Do, Doing, or Done)
- Click Save
Reordering Stages
Use the up/down arrow buttons next to each stage to change the display order. The order determines how columns appear on the kanban board.
Deleting Stages
Click the trash icon next to any custom stage to remove it. System stages (marked with a badge) cannot be deleted.
Before deleting a custom stage, make sure no requests are currently in that stage. Move or reassign records to a different stage first. FieldCamp will block deletion if records still exist in the stage.
Managing Transitions
The Transitions tab controls which stage changes are allowed. Each transition defines:
| Property | Description |
|---|---|
| From Stage | The starting stage (or "Any" to allow from all stages) |
| To Stage | The target stage |
| Button Label | Optional custom text for the transition button |
| Required Capabilities | Which user roles can perform this transition |
| Conditions | Optional rules for when the transition is available |
Click Add Transition to create a new one. Select the from and to stages, optionally set a button label and required capabilities, then save.
For example, you might create a transition that only allows Admins to move requests from "Quote Sent" directly to "Converted" — ensuring quotes are properly reviewed before conversion.
Automation Rules
The Rules tab is where you set up automation that runs when requests change stage. FieldCamp supports seven types of computed rules:
Status Propagation
Automatically moves a parent record to a specific stage when child records reach a certain stage. For example, when all visits for a request are marked complete, the request moves to "Inspection Complete."
Child Creation
Creates child records when a request reaches a stage. Supports three generator types:
- Single — creates one child record
- Date Range — creates one record per day in a date range
- Recurrence — creates records on a repeating schedule
Action
Triggers an action on another object when a stage transition occurs. Can update fields on a target object or create new records.
Cascade Delete
Defines what happens to related records when a request is deleted:
- Hard delete — permanently removes related records (cannot be recovered)
- Soft delete — marks related records as deleted but keeps them in the database for recovery
Validation
Runs before a request is created or updated. Enforces required fields, min/max values, format patterns, and custom rules. If validation fails, the save is blocked with an error message.
Side Effect
Triggers background actions when a request reaches a stage — updating child records, emitting workflow events, recalculating data, or syncing with integrations.
Auto-Calculation
Sets field values automatically based on related data. For example, calculate a request's estimated value from its line item amounts.
Rules apply to all pipeline objects, not just requests. The same rule engine powers Jobs, Visits, Clients, Estimates, and Custom Objects. Configure each object's rules separately from its pipeline settings page.
Table View and Graph View
At the top of the Pipeline Configuration page, switch between:
- Table View (default) — lists all objects with their stage and transition counts
- Graph View — a visual data model diagram showing all objects and their relationships as a network, with color-coded connections (One-to-Many, Many-to-One, Many-to-Many, Action)
The graph view is useful for understanding how request data flows to jobs, estimates, and invoices after conversion.
Saving Changes
When you make changes, an unsaved changes indicator appears in the header. Click Save to apply all changes at once. All stage, transition, and rule changes are validated on save — if something is invalid, you will see an error notification.
Test transitions before going live. After configuring new stages or transition rules, create a test request and move it through each stage to make sure your rules work as expected. Pay attention to required capabilities — a field technician may not have permission to perform certain transitions.
FAQ
Can I delete a system stage?
No. System stages are built into FieldCamp and cannot be deleted. You can only delete custom stages, and only when no records are in that stage.
What is the difference between hard delete and soft delete?
Hard delete permanently removes related records — they cannot be recovered. Soft delete marks them as deleted but keeps them in the database, allowing recovery later. Choose the strategy per cascade rule.
Who can access Pipeline Configuration?
Only Admin and Superadmin roles. Dispatchers, field technicians, and other roles cannot view or modify pipeline settings. See Roles and Permissions.
How do I automatically move a request when an inspection is complete?
Use a Status Propagation rule. Configure it so that when the child visit reaches "Complete," the parent request moves to "Inspection Complete."
Related Articles
- Requests Overview — what requests are and the full lifecycle
- Sales Pipeline Kanban — the visual pipeline board
- Converting Requests — what happens when requests reach the Converted stage
- Roles and Permissions — who can configure pipelines
- Workflow Automation — automate actions beyond pipeline rules
Sales Pipeline & Kanban | FieldCamp
Manage service requests on FieldCamp's visual kanban board. Drag and drop requests between pipeline stages to track leads from initial inquiry to conversion.
Converting Requests | FieldCamp
Convert qualified service requests into jobs, estimates, or invoices in FieldCamp. Learn what data carries over, what happens after conversion, and best practices.