Recruiting Funnel & Time-to-Fill Analytics: Finally Answer Why Is This Taking So Long

The problem this kills

Every recruiting leader gets the same question: "Why is this role taking so long?" And almost nobody has a clean answer. The data is trapped in the applicant tracker, and the moment someone asks for the real numbers — where candidates fall out, which source actually produces hires, how long reqs sit in each stage — it turns into a frantic CSV export and an afternoon of pivot tables that nobody fully trusts.

So decisions get made on gut feel. The agency invoice gets renewed because "it feels like they send good people." Headcount budget gets defended with anecdotes. The hiring manager who sits on candidates for three weeks never gets called out, because nobody can point to the stage where the time actually goes. And every month the same report gets rebuilt from scratch, slightly differently, by whoever has time.

Worse, the numbers are usually subtly wrong: a reopened req double-counts its days, a cancelled search inflates the average time-to-fill, and the same candidate appears twice because two recruiters touched the same pipeline. The report goes to leadership anyway — because the deadline doesn't wait for clean data.

This tool replaces all of that with a real, governed dashboard your team can trust.

What you'll build

A simple internal web app for your recruiting and HR ops team. You import your pipeline stage history (every time a candidate moved from one stage to the next, with the date), your req open and close dates, and the source tag for each candidate. The tool then computes the metrics that actually answer the "why so long?" question:

• Funnel conversion — how many candidates pass from each stage to the next, and where the biggest drop-off is.
• Source of hire — which sources (referral, agency, job board, inbound) produce applicants versus actual hires, and what each hire costs you in pipeline.
• Time in stage — how many days candidates sit in each stage, so you can see whether the delay is screening, the hiring manager, or the offer.
• Time to fill — defined precisely (req open to offer accepted), with reopened and cancelled reqs handled correctly so the average isn't poisoned.

Then the human gate: the recruiting manager opens the monthly snapshot, sees flagged data problems (negative durations, missing dates, suspicious outliers), corrects or excludes them, writes a short commentary, and approves the snapshot. Only then is the report emailed to leadership. You also get a clean CSV export of every underlying metric.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — your exact pipeline stages and what they're called, how your ATS exports stage history, how you tag sources, how you define "filled," and the messy realities like reopened reqs, withdrawn candidates, and roles with no clean close date. It reflects a short tailored spec back to you and waits for your thumbs-up before building anything, so the funnel matches your hiring process — not a generic template that assumes everyone runs the same five stages.

From there it walks the agent through the data model, the pipeline and req import with a dedupe key, the metric engine (funnel, source, time-in-stage, time-to-fill), the dashboard, the data-quality flags, the manager review-and-annotate snapshot, the approval gate, the emailed report, and the CSV export. Every step ends with a ready-to-copy prompt. There's a full "No ATS API yet?" path that uses a Google Sheet / CSV as the data source and produces a clean metrics CSV — so you can build and run the whole thing this weekend regardless of which applicant tracker you're on.

The governance it includes (this is the point)

Recruiting data is people data, and the report drives budget and headcount decisions — so the controls aren't optional. The plan builds in login so only your team can use the tool, row-level security so you only ever see your own organization's pipeline, a complete audit trail of who edited which data point and who approved which snapshot, a hard human-approval gate so no report reaches leadership until the recruiting manager signs off on the numbers and commentary, and duplicate guards (keyed on req ID + candidate ID) so the same candidate's stage moves can't be counted twice.

Who it's for

Recruiting managers, talent-acquisition leads, and HR ops who get asked "why is this taking so long?" and have never had a clean answer. If you can explain your hiring stages and where your pipeline data lives, you can build this — and walk into the next leadership meeting with real numbers instead of a shrug.

You've got this — start with the plan, paste the first prompt, and answer the interview. You'll have your first funnel on screen before the weekend's out.