AI with Michal

Weekly hiring funnel report

A recurring summary that tracks candidate movement across every hiring stage for the past seven days, surfaces where volume stalled, and signals whether open requisitions are on pace for their target close dates.

Michal Juhas · Last reviewed May 5, 2026

What is a weekly hiring funnel report?

A weekly hiring funnel report is a recurring summary that tracks candidate movement across every stage of the hiring pipeline for the past seven days. The goal is early detection: if phone screens are flat while applications spiked, that mismatch surfaces a week before the queue overflow becomes a recruiter complaint. If interviews are running but offers are not, you have a calibration or approval delay the weekly cadence identifies before it compounds into a missed hire date.

The report works best when it is short enough to read in five minutes and consistently formatted so trends are visible across weeks, not buried in changing layouts.

Illustration: weekly hiring funnel report showing ATS stage counts flowing into a dashboard card with per-stage delta arrows and an amber bottleneck flag, a TA lead branching to sourcing and escalation decisions, and a trend strip of weekly snapshots below

In practice

  • A TA ops lead at a 600-person company sets up a Friday afternoon Slack summary that pulls the week's stage counts from the ATS API, compares them to the four-week rolling average, and flags any req where forward movement dropped below the team's baseline. The hiring manager reviews the same summary in their Monday briefing.
  • A recruiter running four open reqs keeps a simple Google Sheet with stage counts by req. Each Monday she enters last week's numbers, checks whether any req is coverage-negative (fewer candidates in late stages than the expected close rate requires), and either sources more or escalates to the hiring manager.
  • A TA leader presenting to the VP of People uses the weekly report data to explain why time-to-fill for engineering roles is tracking two weeks longer than the prior quarter. The stage breakdown shows interviews completing on time but offers taking four additional days to generate, pointing to an approval chain issue rather than a sourcing problem.

Quick read, then how hiring teams use it

This is for recruiters, sourcers, TA, and HR partners who need the same vocabulary in pipeline reviews, status calls, and capacity planning. Skim the first section when you need a fast shared picture. Use the second when you are deciding what to pull from your ATS or how to structure the reporting rhythm.

Plain-language summary

  • What it means for you: A weekly hiring funnel report shows how many candidates moved through each stage last week and whether that pace is normal, slow, or fast for the req.
  • How you would use it: Check it at the start of each week to spot reqs with thin coverage, stages with unexpected drops, and roles where forward movement has stalled.
  • How to get started: Export stage counts from your ATS for one req for the past four weeks. Put them in a simple table. That is your baseline. Repeat weekly.
  • When it is a good time: Any time you have at least two active reqs and a hire deadline you care about. The cadence pays off most when multiple reqs compete for sourcer time.

When you are running live reqs and tools

  • What it means for you: The weekly report is the heartbeat check for your pipeline. It does not tell you why something is off, but it tells you which stage to investigate before it becomes a miss.
  • How to use it: Pull stage counts by req from your ATS weekly. Compare the current week to the prior four-week average. Flag any stage where movement dropped by more than 30 percent. Route the flag to the owner of that stage.
  • How to get started: If your ATS has saved reports, set one up now for stage counts by req, scheduled to send Friday at 5pm. If not, use the ATS API through ATS API integration to pull data into a shared sheet or Slack summary via workflow automation.
  • When it is a good time: Weekly when reqs are active. Monthly when headcount is frozen. The cadence should match the urgency of your pipeline.
  • What to watch for: Activity metrics sneaking in (calls made, emails sent) instead of stage movement. A report full of effort data with no transition data is a status report, not a funnel report. Ensure definitions are consistent across recruiters before you trend the data.

Where we talk about this

On AI with Michal live sessions, weekly funnel reporting comes up in both the AI in recruiting and sourcing automation tracks. AI in recruiting sessions cover how to structure the report, which ATS exports to use, and how to use a prompt to generate a plain-English interpretation from stage data. Sourcing automation sessions add the operational layer: wiring ATS stage counts to a Slack bot or a shared sheet without manual entry. Start at Workshops and bring your current ATS name and reporting setup so the feedback is grounded in what you actually have, not a hypothetical stack.

Around the web (opinions and rabbit holes)

Third-party creators move fast. Treat these as starting points, not endorsements, and double-check anything before you wire candidate data.

YouTube

Search "hiring pipeline dashboard recruiting metrics" for TA practitioners showing ATS reporting setups and weekly review formats. Look for videos where the presenter walks through an actual report rather than a vendor feature demo.

Reddit

r/recruiting has threads on what TA leaders track weekly and what gets cut. Searches for "pipeline reporting ATS" and "TA metrics weekly" surface practitioner views on what works and what turns into admin overhead.

Quora

"What metrics do recruiting teams track weekly?" surfaces answers from TA ops practitioners who explain which stage transitions carry the most predictive signal and which are vanity counts.

Weekly vs. monthly reporting cadence

CadenceBest forRisk
WeeklyActive reqs with near-term deadlinesOver-managing if nothing changed
MonthlyHeadcount planning, trend analysisMisses bottlenecks until they compound
Ad hocEscalations, executive asksNo trend line to reference

Related on this site

Frequently asked questions

What is a weekly hiring funnel report?
A weekly hiring funnel report is a recurring summary that captures candidate movement across every stage of the hiring pipeline, from applications received through offers accepted, for the past seven days. TA leads and ops teams use it as an early-warning system: if applications are on pace but phone screens are low, something broke at the sourcer level or in the inbound flow. If screens are high but interviews are low, the scheduling or handoff is the bottleneck. The report does not replace deeper analysis, but it surfaces where to look before a missed deadline forces the conversation. Pair it with hiring funnel conversion rates for rate context.
Which metrics belong in a weekly hiring funnel report?
The core metrics are: applications received by req and source, phone screens completed, interviews scheduled and completed, offers extended, and offers accepted or declined. Add time-in-stage averages if your ATS exposes them, because velocity shifts show before volume does. Secondary metrics depend on team focus: diversity stage breakdown for tracked reqs, sourced candidates added to pipeline, and recruiter-to-screen conversion per open req. Keep the report short enough to read in under five minutes. A weekly report that requires a deck to interpret loses cadence. Link deeper cuts to talent acquisition metrics for quarterly reviews.
How do you build a weekly hiring funnel report without automated ATS exports?
Most ATS platforms export a CSV or have a saved-reports feature that can be scheduled. If yours does not, build a lightweight Google Sheet with one row per req and manual stage counts entered by each recruiter on Friday afternoon, then automate the rollup formulas. The key discipline is consistency: same fields, same definitions, same day each week. Without consistent definitions, "interview completed" means different things to different recruiters and the trend line becomes noise. Once you have two months of clean data, use workflow automation to pull stage counts through the ATS API and remove the manual entry step.
How does AI help produce and interpret weekly hiring funnel reports?
AI in this context does two things: it reduces the time spent assembling data, and it flags anomalies a busy TA lead might skim past. A prompt fed the current week's stage counts and the prior four-week average can produce a plain-English interpretation in seconds: "Applications are up 20 percent but screens are flat, suggesting inbound quality dropped or screeners are behind." More sophisticated setups pull ATS stage data through an API, compute week-over-week deltas, and push a formatted summary to Slack. The human job shifts from assembling to deciding. Apply a human-in-the-loop review before any AI interpretation drives sourcing or budget decisions.
What are the most common mistakes in weekly hiring funnel reporting?
The most common mistake is reporting activity instead of movement. Counting resumes reviewed or calls made is effort reporting, not funnel reporting. The signal is transition rates between stages, not raw counts. A second mistake is inconsistent definitions across recruiters: one person counts a screen completed when the call is logged; another counts it only when notes are entered. A third is forgetting to break down by req type, so high-volume roles mask zero movement on a critical role. A fourth is using the report as a retrospective rather than a decision trigger. If the numbers change and the meeting agenda does not, the report is decoration.
How do weekly funnel reports connect to pipeline coverage decisions?
Pipeline coverage answers whether you have enough candidates at the right stages to hit hire targets, and the weekly report is the recurring check. If a req has one candidate at the offer stage and the close rate is 60 percent, you need at least two more in parallel to make the number. Reviewing this math weekly rather than monthly means you catch a thin pipeline three weeks before a missed start date, not after. Connect the weekly report to your hiring funnel conversion rates by req type so coverage decisions are calibrated to your actual conversion history, not aspirational benchmarks.
Where do AI with Michal workshops cover weekly hiring funnel reporting?
Live sessions in the AI in recruiting track cover how to structure a weekly report, which ATS exports to pull, and how to use a short AI prompt to generate a plain-language summary from stage data. Sourcing automation sessions go deeper into wiring ATS stage counts to a Slack bot or a shared sheet without manual entry. Join a workshop to practice building a reporting template you can take back to your team the same week. Continue in membership office hours to refine it against your specific ATS and reporting cadence. The Starting with AI: the foundations in recruiting course covers responsible data interpretation before you automate.
Illustration: a single membership pass connects to workshops, courses, Q&As, and the resource library

Annual membership

All workshops, courses, and premium materials

Members get live workshops, courses, recordings, and member-only resources. One pass for the year.

See membership →

← Back to AI glossary in practice