Jobs — pipelines, stages, and statuses

A pipeline is the template for a kind of work — its stages, the order they run in, the colours and rules per stage. You typically have one pipeline per type of job: a "Renovations" pipeline, a "Microblading touch-up" pipeline, a "Legal matter" pipeline.

Manage pipelines under Jobs → Pipelines.

Creating a pipeline

1. Jobs → Pipelines → New Pipeline.
2. Give it a name and an optional description.
3. Add statuses in the order they run in. Each status has:
   • A name ("Quoted", "Deposit paid", "On hold")
   • A colour for the kanban board
   • A flag — Is terminal (the job is finished — Won) and Is cancelled (cancelled / lost), used by reports.
   • A flag — Is visible to customer — when off, customers don't see this status in their portal (handy for internal-only states like "Awaiting parts").

The order of statuses is set by drag-and-drop. Order matters because the kanban board renders left-to-right in this order.

Statuses you'll typically want

A standard service pipeline:

1. New / intake (visible)
2. Quoted (visible)
3. Deposit paid (visible) — the job is committed.
4. In progress (visible)
5. Awaiting parts (internal — hidden from customers)
6. Final review (visible)
7. Completed (visible, terminal — counts toward "won" in reports)
8. Cancelled (terminal + cancelled — counts toward "lost")

Multiple pipelines

You can have any number of pipelines. Each job picks one when it's created. Jobs can't move between pipelines once chosen — if you need to re-categorise, archive the old job and start a new one.

Editing pipelines after jobs exist

Renaming a status is safe — existing jobs flow through. Deleting a status that jobs are currently in will block until you move those jobs to a different status (the system will prompt you).