Scheduling & Pipeline Boards is the workflow at /estimates/board. ServiceFlow uses three complementary surfaces: Pipeline settings (/settings/pipeline) define stage names and columns used by boards and filters. The path is lead or intake, then an estimate on the list or on /estimates/board, then customer approval.
Boards - Estimates to Board to /estimates/board - Jobs to Board to /jobs/board Calendars & dispatch - Jobs to Calendar to /jobs/calendar. Scheduler to /scheduler (tabs: calendar, column, timeline, routes) Settings - Settings to Pipeline Settings to /settings/pipeline Guides & docs - Scheduler guide. · Timeline docs · Calendar docs · Routes docs - Feature guides: Scheduler & Dispatch, Timeline View. Calendar View Move estimate and job cards between pipeline columns on boards. Open card details, assign owners, and filter by stage. Switch from Jobs list to Board or Calendar view toggles. Schedule approved work on Jobs to Calendar or Scheduler views. Configure pipeline stages (admin) to match how your team talks on the phone. Link marketing and intake leads into the same pipeline, see Marketing Automation. Admin configures pipeline stages before boards match your process. Use the calendar when the question is "who is where at 10." Sending the estimate, collecting a deposit.
Overview
ServiceFlow uses three complementary surfaces:
Lead / intake → Estimate (list or board) → Customer approves → Job (list or board) → Calendar / Scheduler → Complete
| Surface | Menu path | URL | Purpose |
|---|---|---|---|
| Estimates board | Estimates → Board | /estimates/board | Kanban sales stages (draft → sent → approved, etc.) |
| Jobs board | Jobs → Board | /jobs/board | Production stages (scheduled → in progress → done) |
| Jobs calendar | Jobs → Calendar | /jobs/calendar | Timeline scheduling (technician rows, drag-and-drop) |
| Scheduler | Scheduler | /scheduler | Full dispatch: calendar overview, column view, timeline, routes |
Pipeline settings (
/settings/pipeline) define stage names and columns used by boards and filters.How to access
Boards
- Estimates → Board →
/estimates/board - Jobs → Board →
/jobs/board
Calendars & dispatch
- Jobs → Calendar →
/jobs/calendar - Scheduler →
/scheduler(tabs: calendar, column, timeline, routes)
Settings
- Settings → Pipeline Settings →
/settings/pipeline
Guides & docs
- Scheduler guide · Timeline docs · Calendar docs · Routes docs
- Feature guides: Scheduler & Dispatch, Timeline View, Calendar View
How do you move estimate and job cards between pipeline columns on boards?
Move estimate and job cards between pipeline columns on boards.
- Move estimate and job cards between pipeline columns on boards.
- Open card details, assign owners, and filter by stage.
- Switch from Jobs list to Board or Calendar view toggles.
- Schedule approved work on Jobs → Calendar or Scheduler views.
- Configure pipeline stages (admin) to match how your team talks on the phone.
- Link marketing and intake leads into the same pipeline—see Marketing Automation.
Prerequisites
- Admin configures pipeline stages before boards match your process.
- Jobs need technicians and scheduled dates to appear on calendars.
- Role permissions for estimates, jobs, and scheduler as appropriate.
Step-by-step
Run a sales standup on the estimates board
- Go to Estimates → Board (
/estimates/board). - Scan columns for stuck deals (sent but not approved, etc.).
- Drag cards forward when status changes or open a card to send/update the estimate.
Move production on the jobs board
- Go to Jobs → Board (
/jobs/board). - Move jobs from Scheduled → In Progress → Completed as field work progresses.
- Open jobs that need scheduling and note unscheduled work.
Schedule from calendar
- Open Jobs → Calendar (
/jobs/calendar) or Scheduler (/scheduler). - Place unscheduled jobs on technician rows (drag-and-drop or schedule modal).
- Confirm crew assignments to avoid double-booking—see Scheduler & Dispatch.
Align pipeline language
- Go to Settings → Pipeline Settings (
/settings/pipeline). - Rename stages to match office vocabulary (for example, “Awaiting deposit” vs “Approved”).
- Save—boards and list filters pick up the new labels.
Example: one sold estimate that has to show up on tomorrow's board
The path is lead or intake, then an estimate on the list or on
/estimates/board, then customer approval, then a job on /jobs or /jobs/board, then a time on /jobs/calendar or /scheduler. Pipeline settings at /settings/pipeline name the stages those boards use. Renaming a stage there changes the column label. It does not move existing records by itself.Drag on the estimate board updates sales status. Drag on the job board updates production status. Those are different columns. Approving an estimate does not put a truck on the calendar until someone converts or creates the job and gives it a date and a technician. The scheduler tabs (calendar, column, timeline, routes) are views of jobs that already have schedule data. An unscheduled job stays in the unscheduled queue until it is placed.
Use the estimate board in a sales meeting and the job board in a production meeting. Use the calendar when the question is "who is where at 10." Sending the estimate, collecting a deposit, and completing a service form are separate guides. This page is only the handoff between those stages. A user who can view estimates but not update them can see the sales board and cannot drag. The same split exists for jobs.
If a card will not leave Draft, check the required fields on that board's transition instead of adding another pipeline stage. Extra stage names do not bypass a missing customer, date, or address.
Current limitations
- Boards show stage movement; they do not replace detailed scheduling—always confirm times on a calendar view.
- Bulk schedule and side-panel route optimize shortcuts show “coming soon”—use Route Planning or schedule individually.
- Multiple calendar entry points (Jobs calendar vs Scheduler tabs) overlap—teams should agree on a primary dispatch screen.
- Pipeline configuration changes do not retroactively remap historical reporting buckets without data cleanup.
Roadmap
- Bulk scheduling from the scheduler side panel for batch-assigning unscheduled jobs.
- Tighter board → calendar actions (for example, schedule directly from a job card).
- Optional automation when estimates approve (auto-create job and propose schedule slot).
Edge cases when sales and production disagree
An estimate can be Approved on the sales board while the job is still Draft on the production board. That is normal until someone schedules it. Do not drag the job to Completed because the estimate was approved. Completed means the field work is done.
Pipeline settings rename columns for the boards that use those stages. They do not create a new calendar. If a renamed stage no longer matches the status the job API accepts, dragging fails the same way an illegal job-board move fails. Keep stage names aligned with the statuses the job and estimate guides list, or use the boards' own columns and leave pipeline settings for labels your reports already expect.
Unscheduled work is invisible on the timeline and visible in the scheduler queue. If the morning meeting "lost" a job, check Unscheduled before you create a second copy.