Building a pipeline

Every organization starts with Standard three-round, marked as the default:

Application received → Phone screening call → Round 1 gate → AI interview → Round 2 gate → Final round (interview with your team) → Hire, Hold or Close.

• The round 1 gate compares the combined resume and call score with your threshold and moves passes on automatically.
• The round 2 gate compares the AI interview score and only suggests; a person confirms.
• Candidates who could not be reached or declined the call get a browser link to the AI interview instead.
• The final round moves someone to Hire only when the panel recommends it (most scorecards say hire). Otherwise they wait for a person to record the outcome.

Choose which pipeline new roles use under Settings → Hiring → Default hiring pipeline. A drive's own Pipeline for new roles, when set, comes first for roles created in that drive.

Give it a name and description and start from the Standard three-round flow or a Blank canvas. The builder opens with:

• Palette, a panel that stays open on the left: every step type, grouped into Stages, Decisions, Actions and Ends, with search. Drag a step onto the canvas or click it. A step that still needs setting up shows an amber dot. On a narrow screen, Add step opens it.
• Canvas in the middle, with Tidy to arrange it neatly.
• Story or Settings on the right. The Story describes the main path in plain sentences, lists every outcome, and shows anything not connected yet in amber. Click a step to see its settings instead.

Every step has outputs, such as *Passed*, *Near miss* and *Below threshold* on a score gate. Drag from an output dot to the next step. Click a connection to choose what it does:

• Move the candidate, optionally only when a Condition matches. When an output has several connections, they are tried top to bottom and the first match wins. The one without a condition is the otherwise.
• Also do this on the side: send an email, notify the team, add a tag or add to the talent pool, without moving the candidate. Side connections are dashed.
• Wait before moving on: a delay of up to 365 days on the move.

Every step except Application received and the ends also has If nothing happens: “If stuck for N days, follow …” the output you choose. 0 days means never.

A condition is a set of rules joined by all or any. Rules can test:

Operators: equals, does not equal, is greater than, is at least, is less than, is at most, contains, does not contain, is empty, is not empty.

Press Describe it, write your process in plain words (or Use the example), and press Build it. In about ten seconds you get a preview with the story, the questions still to decide, and what was assumed. Nothing reaches the canvas until you press Put it on the canvas, and nothing is saved until Save draft.

Outcomes you did not mention are left unconnected and listed as questions. Good news is never routed to a close or hold.

Validate checks the pipeline; it also runs live as you edit. Errors block publishing: for example, exactly one Application received step, required settings filled in, the main outputs of gates, calls, tests and interviews connected, loops that pass through a wait, and webhook addresses that are secure. Warnings point out things like a missing end step, unreachable steps or a Close without a rejection email.

Simulate lets you enter scores, call facts, form answers, source, tags and outcomes for an imaginary candidate and Run simulation. The path they would take is listed and highlighted on the canvas.

Save draft stores your work. Publish creates a new version (v1, v2 …). Candidates keep the version they started on, so publishing never changes anyone already in progress. Versions shows how many candidates are on each version and lets you migrate them to a newer one on purpose.

Export and Import move a pipeline between organizations as a file.