Skip to content

Measurement

What is a hiring funnel?

A funnel is not the shape of a hiring process, it is its measure: it counts how many candidates are left at every stage and shows where the process narrows. This guide covers the stages, which panel status maps to which step, and how a blockage is read.

5 steps

The Application Funnel card on the dashboard counts Pending, Reviewing, Interview, Accepted and Hired

8 statuses

Application status takes eight values in the schema; the funnel draws five of them, the rest are side exits

Every move on record

A status change writes an audit entry and a domain event; who moved an application to which step and when can be read back

8 minute readUpdated: 1 August 2026

Quick answer

A hiring funnel is the countable form of the stages applications to a posting pass through on the way to a hire. Every stage is narrower than the one before it: at each transition a candidate either moves forward or leaves the process. In the GoTeam panel the funnel is measured with five steps: Pending, Reviewing, Interview, Accepted and Hired. The step counts come from the whole application pool, not from a date range.

What a funnel is and why it is called one

A hiring funnel is a countable structure that shows which stage each applicant to a position is in. The name comes from its shape: all the applications sit at the top, at every stage some are eliminated or step out on their own, and one hired person is left at the bottom. Narrowing is not a fault of the process, it is how the process works. The real question is not that the funnel narrows, but where and by how much.

The same structure travels under several names: application funnel, candidate funnel, sometimes recruitment pipeline. They all mean one thing: a system that follows an application stage by stage and keeps a count at each one. The term changes, what it measures does not.

A funnel is also not a report you build, it is a by-product of the process. If the application statuses are properly defined and every status change is recorded, the funnel is already there. If the statuses are loose, the funnel is meaningless too: Reviewing starts to mean something different for everyone.

  • A funnel is not a list of stages, it is the count at each stage. The stage list gives you the process, the numbers give you the funnel.
  • Moving from one stage to the next is a human decision. The system records the decision, it does not make it.
  • An eliminated candidate is a side exit of the funnel, not a step of it. Mix the two up and every conversion reading breaks.
  • A funnel is only as true as the steps you measure. A stage you do not measure stays outside it.
Paper cards on an off white surface narrowing from top to bottom, the single card at the bottom in cobalt blue.
Narrowing is not a fault of the process; what has to be measured is where the narrowing happens.

The stages of the funnel and their counterparts in the panel

GoTeam keeps application statuses in a fixed set, and the funnel on the dashboard draws five of them as steps. The order comes from code and is not assembled by hand in the panel: Pending, Reviewing, Interview, Accepted, Hired. The count runs over job and internship applications together, so two flows land in one funnel.

The table below ties the stage on paper to a status that genuinely exists in the panel. Stages without a counterpart were left out: a stage you cannot measure decorates the funnel, it does not make it more accurate.

The funnel stage and its counterpart in the GoTeam panel
Funnel stageStatus in the panelWhat it means
Application receivedPendingFirst step. The record is open, CV analysis has started in the background, nobody has looked at it yet.
ReviewReviewingSecond step. The position fit score and the evidence cards are read here.
InterviewInterviewThird step. The status exists on every plan, interview scheduling opens from the Professional plan up.
AcceptanceAcceptedFourth step. Document and information requests are attached to the candidate from here.
HireHiredFinal step. The candidate moves into an employee record.
EliminationRejectedNot a step, a side exit. It never appears in the funnel bars, it appears in the list and in the filters.
Two people at an office desk looking together at a single printed page, one of them holding a finger on it.
What changes a step is always a person making a decision.

The two statuses that stay outside the funnel

Two of the eight statuses in the schema belong to life after the hire: Terminated and Dismissed. They never enter the funnel, because the funnel measures the road up to the hiring decision. Putting them on the same chart mixes two separate questions: how many candidates were hired and how many of the hired are still here are not the same question.

Why a rejection is not a step

A rejected application is counted in none of the funnel bars. The reason is logical: the funnel measures progress, and a rejection is where progress ends. If rejections were a step, the total would swell every time and the ratios between steps would lose their meaning.

Reading the drop at a step as the number of people eliminated is wrong. The drop holds both the eliminated and the ones still waiting at that step. Anyone looking for the number of eliminated candidates goes to the Rejected filter in the application list, not to the funnel.

Why every transition goes on record

When the status of an application changes, the work finishes in a single database transaction: the record is updated, an audit entry is written and a domain event is produced. The changed field, the old value, the new value and the user who made the change are kept together.

If you move back from Accepted or Hired while that application still has an open document or information request, the system raises a warning; the transition only continues once a reason is written. That is the gate that stops the funnel from being quietly played backwards.

Which metric is measured where

The numbers about the funnel are not gathered on one screen. The Application Funnel card on the dashboard gives you the step counts, the KPI cards give you the volume trend, the application list gives you the records one by one. The most common reading mistake is mixing up which one measures what.

Three separate clusters spread out on a paper surface: a stack of folders, a fan of paper strips and a row of cards, the folder in the middle in cobalt blue.
Three screens, three questions. Once you mix up what each one counts, the number is right and the answer is wrong.

The Application Funnel card: cumulative

The funnel card groups every job and internship application that has not been deleted by status. The date range picker does not touch this card: pick 7, 30 or 90 days and the funnel still counts the whole pool. The percentage next to a bar is the ratio of that step to the first step.

That choice is deliberate and worth holding in mind as you read: the funnel does not answer what happened this month, it answers where the pool stands right now.

KPI cards: per period

Incoming applications, AI evaluations, sent emails, Drive imports and error counts are measured for the selected period and compared with the previous period of the same length; a daily breakdown line sits underneath. The funnel card shows the stock, the KPI card shows the speed of the flow. Whether the first step is growing is read here.

  • The comparison is against the previous period of equal length, not against the same period a year earlier.
  • On the error metric an increase is bad, and the panel shows it in the reverse colour.
  • The observability dashboard is open from the Mini plan up.

What is not measured

This is usually the most useful section of a measurement guide. GoTeam does not count posting views; how many times a posting was opened is not held in the data model. The topmost measured step of the funnel is the incoming application, not the person who saw the posting. Time between stages and time to hire are not ready made metrics either: the timestamps sit in the audit log, there is no average on screen.

  • The route an application took into the panel is recorded: the career page form, manual entry from the panel, or a Drive import.
  • Posting views and conversion rate by source are not measured.
  • Which day and which hour applications arrive can be seen through a day and hour breakdown.

Working out where the funnel is blocked

A blockage is a gap between two neighbouring steps that is wider than the natural narrowing of the process. There is no universal number for how wide the natural narrowing is, and there is no publishable conversion measurement for this product either. The method below hands you no threshold, it hands you the place to look.

The method has three steps. First find which two steps carry the largest drop on the funnel card. Then separate whether that drop comes from elimination or from an untouched pile. Finally go down to that step own screen and read the records one by one.

The symptom and where to look in the panel
SymptomWhere to look
The first step swells while the second is nearly emptyThe Pending filter in the application list. This is not an elimination problem, it is a pile nobody has looked at.
Review fills up but nobody reaches an interviewThe decision bands of the position fit score. Does the spread of strong, review and weak match the criteria of the posting.
On one posting nobody clears the required criterionThe candidates carrying a closed gate badge and the required criteria list of the posting. Is the criterion really required.
Acceptances happen, hires do notThe open document and information requests attached to accepted applications. This is usually where the process waits.

What happens when you change a criterion

When the criteria of a posting change, the fit scores tied to that posting are marked stale and a re-evaluation is offered. Since a candidate and posting pair is charged once, rescoring spends no extra credit.

That makes it possible to open a blockage by experiment: loosen a criterion and watch how the second step of the funnel moves. Measuring instead of guessing is the only real piece of advice in this guide.

Common mistakes

A badly built funnel does not give you wrong answers, it gives you none: the numbers flow and not one of them turns into a decision. The mistakes below are the ones we see most often at setup.

  • Using statuses as decoration. If a candidate has been invited to an interview and the status is still Pending, the funnel measures how far behind the panel is, not the process.
  • Reading a cumulative funnel as a period. The funnel card counts the whole pool; the sentence 40 applications came in this month comes from the KPI card.
  • Taking the drop between steps as elimination. That drop holds both the eliminated and the ones waiting in the queue.
  • Rejecting without a reason. A rejection with no reason is the most expensive line in the funnel: the number falls and the reason disappears.
  • Mistaking an AI suggestion for a decision. The system never changes the status of an application on its own; it ranks and it flags, a person moves the step.
  • Mistaking the funnel of one posting for the funnel of the company. The dashboard adds every posting together, and a blockage specific to one posting disappears inside it.
A person standing in a meeting room going through a thick stack of paper while a seated colleague rests a hand on their chin, thinking.

Frequently asked questions

No. An applicant tracking system is where the process runs: applications, statuses, notes, transitions. The funnel is a summary of the numbers that system produces. You cannot build a funnel without a tracking system, but you can use a tracking system without ever looking at a funnel.

That is how the textbook funnel is drawn, but a step you cannot measure does not go into the funnel. GoTeam does not count posting views, there is no such counter in the data model. In the panel the top step of the funnel is the incoming application, and every ratio is calculated against it.

Nowhere in the bars. A rejection is a side exit, not a step; the funnel counts only Pending, Reviewing, Interview, Accepted and Hired. Rejected candidates are reached through the status filter in the application list.

No. The system never changes the status of an application by itself and it eliminates nobody on its own. The fit score and the decision band only produce a suggestion; the action that changes a step always runs on a user approval and is written to the audit log.

Yes. The dashboard funnel adds internship applications to job applications over the same statuses, it does not draw two separate bars. Anyone who wants to see them apart switches between the job and internship tabs in the application list.

All of it. The 7, 30 and 90 day choice on the dashboard moves the KPI cards and the trend charts, not the funnel card. The funnel counts every application that has not been deleted, so it answers the question of where the pool stands right now.

Read your funnel with your own data

The step counts and the blocked points are already sitting in the panel. Let us walk through the setup together.

Contact Us