How to Set Up a Hiring Pipeline for a Small Team

Most small teams design their hiring pipeline by copying a diagram from a much larger company: seven stages, a gate at each one, and a naming scheme borrowed from a 400-person recruiting org. Two weeks later the board is full of candidates parked in stage three and nobody trusts it.

The problem usually isn’t discipline. It’s that the pipeline was modeling two different things in one list of columns — how far along a candidate is overall, and which specific interview they’re waiting on. Separate those and a small-team pipeline gets much simpler to run.

What Does a Hiring Pipeline Actually Track?

Two things, and they answer different questions.

Candidate status answers “where does this person stand?” It’s the overall state of their candidacy, and it’s the same vocabulary across every role you hire for, which is what makes it useful for reporting and for weekly review.

Interview stages answer “which conversation is next, and with whom?” These are specific to a role. A customer support role might have a screen and a hiring-manager conversation. An engineering role might add a practical exercise. Both roles use the same statuses.

Conflating them is what produces those seven-column boards. Once you split them, the status list stays short and stable, and the process detail lives where it belongs — on the role.

What Statuses Does a Small-Team Pipeline Need?

Fewer than you think. In Plural, an application moves through a small, fixed set of statuses:

• Submitted — the application arrived and hasn’t been triaged.
• Shortlisted — worth talking to, not yet scheduled.
• Interviewing — actively moving through the role’s interview stages.
• Hired — offer accepted.
• Rejected — you decided not to move forward.
• Withdrawn — the candidate stepped out.

That’s the whole vocabulary, and it’s deliberately fixed rather than configurable. A shared status list means “shortlisted” means the same thing on every role, so your weekly review and your reporting are comparing like to like.

Notice what isn’t a status: offer. For most small teams, offers are a matter of days and a handful of candidates, and a dedicated stage mostly creates a column with nothing in it. Track it as an interviewing candidate you’re closing, and move them to hired when they sign. If you reach the point where multiple offers are outstanding at once and approvals are involved, revisit that — but don’t build for it on day one.

How Many Interview Stages Should You Run?

Two to three for most small teams.

A defensible default: a screen conversation to confirm fit and expectations, then a substantive conversation with the hiring manager. Add a third when the role genuinely needs it — a practical exercise for a technical role, or a conversation with the team the person will work alongside.

Be honest about the cost of a fourth stage. Every stage is another scheduling round, another few days of elapsed time, and another opportunity for a strong candidate to accept somewhere else. Small teams win offers on speed more often than on process depth. Spending that advantage on a stage you added because a template suggested it is a bad trade.

In Plural, interview stages are configured per role in order, and each one carries the details that make scheduling work without a back-and-forth thread: the interviewer for that stage, whether the candidate books into your connected calendar availability or an external booking link, how long the slot is, how far ahead candidates can book, and which hours on which days you’re actually available. Set that up once when you open the role and scheduling largely stops being your problem.

Who Owns Moving Candidates Forward?

One person per open role. Usually the hiring manager.

That person is accountable for one thing: every candidate in the pipeline gets advanced or rejected each week. They don’t have to conduct every interview or write every rejection themselves, but the decision that a candidate has been sitting for nine days is theirs to notice.

Other interviewers contribute reviews. They don’t own movement. This distinction sounds bureaucratic for a five-person company, and it’s exactly the opposite: shared ownership of a pipeline reliably produces no ownership at all, which is how candidates end up parked in interviewing for three weeks while everyone assumes someone else is on it.

If you’re on a plan with a limited number of hiring managers, this actually helps — it forces the question of who genuinely needs to run a pipeline versus who just needs to interview and leave feedback.

How Do Shared Review Criteria Keep Quality Consistent?

Define what you’re evaluating once, and reuse it.

Plural handles this with a review matrix: a set of weighted criteria, each with a numeric rating scale, that you configure at the organization level and can override for a specific role when it needs different criteria. When an interviewer completes an interview stage, they’re prompted to rate the candidate against those criteria and add notes, which produce a weighted score on the candidate record.

Three practical rules:

Keep it to three to five criteria. A fifteen-item rubric is a rubric nobody completes. Short and consistently used beats thorough and abandoned.

Tie the criteria to the job description you published. If a criterion doesn’t map to something in the role, either the criterion is noise or the job description is wrong. Both are worth fixing.

Collect reviews before the debrief, not during it. Independent ratings gathered right after each interview are the entire point. If everyone submits their review in the room after hearing the hiring manager’s take, you’ve built an elaborate way of recording one person’s opinion.

The value isn’t the number. It’s that when two people disagree about a finalist, you can see exactly which criterion they diverged on, which turns a forty-minute debate into a five-minute one.

How Do You Keep the Pipeline Honest?

A weekly fifteen-minute pass, run the same way every time.

Start with the oldest candidates, not the newest. Newest candidates are exciting and get attention on their own; the oldest ones are where trust in the pipeline goes to die. For each one: decide, or reject. “Let’s leave them for now” is the answer that quietly turns your pipeline into a graveyard.

Then close what’s stalled. A role that hasn’t moved in a month is either not a priority — in which case close it and tell the candidates — or it’s blocked on something specific, in which case name the blocker. And send the rejections. Small teams under-send rejections because they feel bad, then wonder why the candidate experience gets mentioned in reviews.

A useful health check: can any hiring manager open the pipeline and, for every candidate, say what happens next and who’s doing it? If yes, the pipeline is working. If not, no amount of extra stages will fix it.

The Bottom Line

A hiring pipeline a small team will actually maintain has a short fixed status list, two or three interview stages per role, one named owner, three to five shared review criteria, and a fifteen-minute weekly pass through the oldest candidates first. Nearly every pipeline problem at small scale traces back to one of those five being missing, not to a missing feature.

If you’re building this while moving off a spreadsheet, How to Replace Spreadsheet Hiring With an ATS covers the migration order. For the broader case on what to buy at your size, read What Is an ATS for Small Businesses?, and if you’re comparing vendors, see ATS comparisons and alternatives.