A candidate applies on Monday. By Friday, nobody in the business can tell them what happens next.

The recruiter thinks the manager is reviewing applications. The manager assumes HR has already screened them. A panel is booked before anyone agrees what the role must achieve. What looks like a talent shortage may actually be a process nobody owns.

A good hiring funnel is not impressive because it has many stages. It is useful because each stage answers one question, produces one piece of evidence and has a clear owner. Candidates can understand it, and the team can defend its decisions.

Draw the handoffs before the stages

The role brief and scorecard should already exist before the funnel is designed. Treat them as the input, then draw what happens each time a candidate moves from one person to another.

For every handoff, write down four things:

  • The evidence that must arrive with the candidate.
  • The person who owns the next decision.
  • The latest date for that decision.
  • The message the candidate receives, even if the answer is “still under review.”

This exposes the gaps that stage names hide. “Manager review” is not a process when three managers share an inbox and none has a deadline. “Interview” is not ready when the panel has no scorecard or question owner.

A small team can use a single page. The point is not software; it is making waiting, ownership and transfer visible before a live application enters the system.

Give every stage one job

Map a short route from application to decision. For a small team, it might be:

  1. An eligibility check for genuine non-negotiables.
  2. A short screening conversation about the role and practical alignment.
  3. A structured interview against the scorecard.
  4. A brief, role-relevant work sample where appropriate.
  5. References, final review and offer.

Do not repeat the same general interview three times with different people. If a stage adds no new evidence, remove it.

Google’s public hiring video describes its own use of trained interviewers, standardised rubrics, work samples and review layers. That is a description of one large employer, not a universal template. A five-person business does not need a hiring committee. It does need a second reviewer for important decisions and a record of why the selected evidence met the agreed standard.

Make the evidence visible

Candidates should know what each stage is designed to assess. Tell them whether an interview will focus on customer judgment, technical knowledge, team leadership or another defined capability. If there is an exercise, explain the format, expected time and whether any preparation is required.

This does not reveal a secret answer. It gives people a fair opportunity to show relevant ability.

Keep work samples short, consistent and close to the real job. A payroll candidate could identify errors in fictional records. A sales candidate could prepare a short discovery plan for an invented customer. Do not ask applicants to complete productive client work for free, and provide a reasonable alternative where the format creates an accessibility barrier.

Separate scores before the discussion

Panel interviews become vulnerable to the loudest opinion when everyone discusses the candidate before recording an assessment.

Give each interviewer the same core questions and scoring anchors. Immediately after the interview, each person should note the evidence they heard and score it independently. Only then should the group compare its reasoning.

The discussion should sound like “Which example supports that score?” rather than “Did you like her?” Familiarity and confidence can feel persuasive without predicting performance. Written evidence makes disagreement useful because the panel can locate the gap instead of negotiating around a feeling.

Put communication inside the funnel

Candidate communication is not an extra courtesy added when someone remembers. It is a stage with an owner and deadline.

At application, confirm receipt and describe the likely process. After a live interview, state when the candidate should expect an update. If the timeline changes, send a short update even when there is no decision. Close the loop with people who have invested time in an assessment.

A simple tracker can hold the candidate, current stage, decision owner, next action and promised update date. A small team does not need expensive software to stop avoidable silence.

Be careful with promises. “We will reply by Thursday” creates a clearer obligation than “We will be in touch soon.” If Thursday is unrealistic, give a date you can keep.

Review the funnel after every hire

Speed matters, but it is not the only measure. After a recruitment round, ask:

  • Where did candidates wait without a decision?
  • Which stage repeated evidence already collected?
  • Did interviewers use the scorecard consistently?
  • Were any capable applicants blocked by a requirement unrelated to the work?
  • Did the person appointed receive an accurate picture of the role?

Then check the scorecard with the new hire and manager after roughly three months. The aim is not to claim that one hire proves the process works. It is to learn whether the evidence you collected was connected to the work that followed.

A transparent funnel will not remove uncertainty from hiring. It does something more practical: it prevents uncertainty from becoming chaos. Candidates understand the journey, managers know what they own, and decisions rest on evidence the team agreed to seek.

Sources and limits

Google’s video explains Google’s process at the time of publication; it is not proof that every stage will suit another employer. This article is an original operational synthesis, not a transcript or legal advice.