Skip to content
Resources Tools About Contact

Candidate Pipeline Metrics

Candidate pipeline metrics describe the health of the candidates in progress: how many you have, whether they are moving, and whether there are enough relative to the roles you need to fill.

Part of the HR metrics hub — the analytics layer of the hiring funnel. It connects to employer operations for planning and to the staffing layer when you need to bridge a gap.

What it measures

Pipeline metrics include coverage (active qualified candidates relative to open roles), velocity (how fast candidates move), and ageing (candidates stuck without progress). Where funnel metrics describe conversion, pipeline metrics describe the current stock and its movement.

They are a real-time, forward-looking view.

Why it matters

A thin or stalled pipeline predicts future fill problems before they show up as vacancies. Monitoring coverage and velocity lets you act early — source more, or unblock stuck candidates — rather than discovering a gap when a role is already overdue.

It connects directly to vacancy rate and time to fill.

Formula

Pipeline coverage = Active qualified candidates ÷ Open roles

Active qualified candidates — candidates in progress who meet the bar for the role
Open roles — roles currently open of that type

A ratio, not a percentage. Define "active" and "qualified" consistently — stale or unqualified candidates inflate coverage without helping.

Worked example: With 24 active qualified candidates across 6 open roles, coverage is 24 ÷ 6 = 4 candidates per open role.

Inputs you need

  • Counts of active, qualified candidates
  • Open roles by type
  • Stage timestamps to measure velocity and ageing
  • Consistent definitions of active and qualified

How to read it

Coverage is only meaningful with honest definitions of "active" and "qualified" — a high ratio built on stale candidates is misleading. Read coverage with velocity: a large but frozen pipeline is not healthy.

Watch ageing candidates; long-stuck candidates usually drop out, quietly shrinking real coverage.

Common mistakes

  • Counting stale or unqualified candidates as coverage.
  • Looking at volume without velocity.
  • Ignoring ageing candidates until they drop out.
  • Treating all open roles as needing equal pipeline depth.

Operational considerations

  • Define "active" and "qualified" and prune the pipeline to them.
  • Track velocity and ageing, not just counts.
  • Set coverage targets weighted to critical roles.
  • Act early when coverage or velocity slips, before vacancies bite.

Use this metric inside the operating cadence: plan with workforce planning and headcount planning, anticipate demand with hiring forecasting, and check it against workforce capacity planning.

Free, printable planning resources

Plan, screen and onboard consistently as you measure. No signup, no gating.

For informational purposes only. This is neutral, educational guidance on how an HR or recruitment metric is defined, calculated and interpreted — not legal, tax, financial, compliance or employment-law advice. It contains no salary or compensation data, no workforce or sector statistics, no benchmarks or averages, no fabricated studies and no software, vendor or provider rankings. Worked examples are simple arithmetic illustrations of a formula, not claims about any real population. Define and apply your own metrics consistently, and confirm specifics with qualified professionals.

Practical HR resources, by email

Templates, hiring insights and workforce updates. No spam — unsubscribe anytime.

FAQ

Frequently asked questions

How is pipeline coverage calculated?

Divide active, qualified candidates by open roles of that type. It is a ratio — candidates per open role — not a percentage.

What makes coverage misleading?

Counting stale or unqualified candidates. Define "active" and "qualified" honestly and prune to them.

Why track velocity and ageing?

A large pipeline that is not moving is not healthy. Velocity and ageing show whether coverage is real.

Do you provide pipeline benchmarks?

No. This page is educational and avoids benchmarks. Set your own targets by role criticality.