Candidate statuses and pipeline

A candidate's status is where they are in your hiring process. You move them by dragging — a row in the table, a card on the board — and every move is recorded. The default set covers a normal pipeline, and you can change it to match yours.

The default statuses

A new organization starts with six:

Most teams find this is enough. Add stages when your process genuinely has more steps — not because an empty column feels tidy.

Moving a candidate

1. In the table, drag a candidate's row to a new status. On the board, drag their card to a new column.
2. The move saves immediately. No confirm step.

Every status change is logged on the candidate's timeline — who moved them, when, and from what. So "why is this person in Offer?" always has an answer, and it isn't a guess.

Customizing the status set

Statuses are set per organization, so the whole team works the same pipeline.

1. Go to Settings → Organization.
2. Find the statuses list. Add a status, rename one, or reorder the set.
3. Save. The new set applies everywhere candidates appear.

Adding and renaming are safe — nothing moves, candidates just see the updated labels. Removing a status is the one that needs care.

Hired is not just another column

Moving a candidate to Hired does one extra thing: it locks them to that job. A hired candidate is done — they're not getting dragged back to Interview, and they won't surface as available for other roles.

That's deliberate. Hired means hired. If you moved someone there by accident, you can still correct it, but treat Hired as a decision and not a casual drag.

Limits

Statuses describe a candidate's stage for a single job. The same person applying to two roles has a status in each, tracked separately — advancing them for one job doesn't touch the other. Statuses also don't enforce order: nothing stops you dragging Applied straight to Offer if that's a move you actually want to make.