HiringPipelines
Hiring a line operator isn’t hiring a board member. Build as many named pipelines as you have kinds of hiring, each with its own stages in its own order; keep every applicant’s position through them on the record.
One process per kind of hiring. Not one process for all of them.
Trades, volunteers, the board: pipelines that can look nothing like each other, because every posting picks its own, defaulting to yours.
- As many named pipelines as you have kinds of hiring
- Stages in your order, each marked review, interview or decision
- One pipeline is the org default; new postings start there
- Every posting names the pipeline it runs on
- Renaming a stage applies everywhere the pipeline is used
Where everyone actually is. Stage by stage, not one status field.
Each applicant carries a row per stage, so the record can tell apart what they have finished, what they are in now, what is still ahead, and what you deliberately skipped.
- Each applicant has their own line for every stage, not one overall status
- Pending, active, completed, and skipped told apart
- A skipped stage stays visible, because skipping it was a decision
- The application itself carries only the outcome
- Notes and a 1–5 rating survive the meeting they came from
Where they came from. Kept, not reconstructed.
Every application carries its source, the campaign parameters on the link that brought it, and the page that referred it, so you find out which of your channels is actually working.
- The source that brought them in
- Campaign, medium and term, where the link carried them
- The page that referred them
- Kept on the application, not inferred later
One board, every applicant
The stages you drew across the top, the people you are considering underneath, and no reconstruction required to see who is waiting on you.
Then the yes. An accepted stage decision is where the offer starts.
No. Stages are a structure and a record of where people are: moving somebody is always an operator action, and it is recorded as theirs. There are no automated transitions, no ageing timers and no gates that advance on their own.
Postings reference the pipeline, so a rename or a reordered stage applies everywhere it is used. That is the intent: a pipeline is your process, and your process changes. Where you want a genuinely different process, build a second pipeline rather than editing the first.
Because skipping one is a decision. A trade test waived for somebody who has certified elsewhere is worth being able to see six months later, and a stage that silently disappears looks like a stage nobody ran.
Not today. An interview stage records that somebody is at it and what the reviewers made of them; the meeting itself still lives in your calendar. We would rather say that plainly than imply a scheduler that is not there.