Most recruiting teams collect plenty of data. The problem is that data sitting in an ATS, a spreadsheet, or a hiring manager's inbox does not help anyone make a decision. A candidate pipeline report solves that by pulling the right numbers into a single, structured view so you can see where candidates are, where they are getting stuck, and what your hiring capacity looks like over the next 30 to 90 days. This guide walks through exactly how to build one, which metrics belong in it, and how to turn that report into a reliable forecasting tool.
What Is a Candidate Pipeline Report?
A candidate pipeline report is a structured summary of every active role in your organization, showing how many candidates sit at each stage of the hiring funnel. Think of it as a snapshot combined with a trend line. At a glance, it tells you how healthy each open requisition is, whether sourcing is keeping pace with demand, and how close each role is to a hire.
Unlike a simple headcount report or a time-to-fill log, a pipeline report is dynamic. It reflects what is happening right now and, when tracked over time, reveals patterns that support longer-range planning. Teams using a purpose-built tool like recrrofy can pull this data automatically from the candidate pipeline without manual exports.
A pipeline report is not the same as a recruiting dashboard. A dashboard shows live metrics. A pipeline report is a structured document, produced on a cadence (weekly, biweekly, or monthly), that enables comparison across time periods and roles.
How to Build a Candidate Pipeline Report from Scratch
Step 1: Define Your Pipeline Stages
Before you can report on a pipeline, every role needs to move through the same stage definitions. Common stages include: Applied, Screened, Phone Interview, Hiring Manager Interview, Final Round, Offer Extended, and Offer Accepted. If your stages vary by department, standardize them at least within job families so the data is comparable.
Inconsistent stage definitions are the single most common reason pipeline reports become unreliable. Take the time to align with hiring managers on what "screened" actually means before you start pulling numbers.
Step 2: Choose a Reporting Cadence
Weekly reports work well for high-volume hiring or roles with tight deadlines. Biweekly or monthly cadences are appropriate for executive searches or when open requisitions are fewer than ten. Whatever you choose, stick to it. Consistency is what makes trend analysis possible.
Step 3: Identify Your Data Sources
Your pipeline report needs to draw from at least three sources: your ATS (for stage counts and timestamps), your sourcing channels (for applicant volume by source), and your offer management system (for acceptance rates and offer-to-start timelines). recrrofy consolidates these through its resume screening and offer management features, which reduces the manual reconciliation that plagues teams using disconnected tools.
Step 4: Build the Report Template
A practical template includes one row per open requisition and columns for each pipeline stage. Additional columns should capture the role's target start date, current stage distribution, days open, and a status flag (on track, at risk, stalled). The status flag is what turns a data table into something a VP of Talent or a CFO can act on in a ten-minute meeting.
Metrics Every Candidate Pipeline Report Should Include
The following table covers the core metrics, what they measure, and why they matter for forecasting.
| Metric | What It Measures | Why It Matters for Forecasting |
|---|---|---|
| Applicants per Stage | Volume of candidates at each funnel stage | Identifies bottlenecks and predicts time to next hire |
| Stage-to-Stage Conversion Rate | Percentage advancing from one stage to the next | Reveals where candidates drop off and informs sourcing targets |
| Time in Stage | Average days candidates spend at each stage | Flags process delays before they push out a start date |
| Time to Fill | Days from requisition open to offer acceptance | Sets realistic expectations for workforce planning |
| Offer Acceptance Rate | Percentage of offers accepted | Affects how many offers you need to extend to hit headcount goals |
| Source-to-Hire | Which sourcing channels produce accepted hires | Guides budget allocation for future requisitions |
| Pipeline Coverage Ratio | Active candidates relative to open roles | Indicates whether sourcing volume is adequate |
Pipeline Coverage Ratio Explained
The pipeline coverage ratio compares the number of qualified candidates in process to the number of open roles. A ratio of 3 to 1 is a reasonable minimum for most roles, meaning three viable candidates for every open seat. For highly competitive roles in engineering or data science, a 5 to 1 ratio is safer. If your report shows coverage below 2 to 1 on a role with a near-term start date, that is an early warning signal to escalate sourcing immediately.
Stage Conversion Rates and What They Tell You
Conversion rates are where a candidate pipeline report earns its keep. If your screen-to-phone-interview conversion is 40 percent but your phone-to-hiring-manager conversion is only 12 percent, the problem is not sourcing volume. It is interview calibration. That insight tells you to run a hiring manager alignment session before spending more on job board advertising.
Track conversion rates by recruiter and by hiring manager separately. Significant variation between team members often points to process gaps or calibration issues that training can fix quickly.
Using the Report to Forecast Hiring Needs
Working Backward from Start Dates
Once you know your average time to fill by role type, you can work backward from any target start date to determine when sourcing needs to begin. If your average time to fill for a mid-level software engineer is 42 days, and you need three engineers starting in Q3, sourcing should open those requisitions no later than the first week of the preceding quarter. Your pipeline report surfaces this automatically when it includes target start dates alongside current stage counts.
Modeling Headcount from Pipeline Velocity
Pipeline velocity measures how quickly candidates move through your funnel. To calculate it, multiply the number of active candidates by your average conversion rate, then divide by the average time in your pipeline. The result gives you an estimated number of hires per week or month based on current pipeline health. This number is valuable input for quarterly business reviews and for conversations with finance about when backfills or new headcount will actually land.
Scenario Planning with Pipeline Data
Suppose your sales organization plans to expand by 15 account executives over the next two quarters. Your historical pipeline report shows that converting one AE hire requires an average of 18 applicants at the top of the funnel, with a 22-day average time to fill. You can now model exactly how many sourcing activities are needed per week and flag any weeks where your current pipeline falls short. That is the kind of analysis that moves talent acquisition from a reactive function to a strategic partner at the planning table.
recrrofy's candidate pipeline view supports this type of scenario modeling by tracking stage progression in real time, so your reports reflect current data rather than last week's export. Teams on the Growth or Pro plans can also use JD generation to pre-build job descriptions for anticipated roles before official requisitions are opened, cutting days off ramp-up time when hiring approval comes through.
Common Mistakes That Undermine Pipeline Reports
Reporting on Volume Without Conversion
A pipeline with 200 applicants and a 2 percent hire rate is not a healthy pipeline. It is a screening burden. Always pair volume metrics with conversion rates so the report tells a complete story.
Skipping the Historical Baseline
A single pipeline report in isolation is useful. Pipeline reports compared against a baseline are powerful. Store your reports consistently so you can compare this quarter's conversion rates to the same period last year, or measure the impact of a new sourcing channel over time.
Not Sharing the Report with Hiring Managers
Pipeline reports are often treated as internal recruiting documents. They should not be. Sharing a simplified version with hiring managers creates shared accountability for interview turnaround times, reduces ghosting at the offer stage, and gives business leaders the visibility they need to adjust headcount plans when market conditions change. Tools like recrrofy support collaborative hiring workflows through interview scheduling features that keep all stakeholders aligned without requiring separate status meetings.
Putting It All Together
A candidate pipeline report is most valuable when it is consistent, shared, and tied to business outcomes. Start with a clean stage definition, pick a reporting cadence you can maintain, and include the seven core metrics outlined above. Once you have two to three reporting cycles of data, layer in forecasting by applying your historical conversion rates and velocity numbers to upcoming headcount plans.
For teams scaling quickly, the manual work involved in producing these reports every week becomes a bottleneck of its own. That is where a platform like recrrofy earns its keep. Whether you are on the Free or Growth plan or running an enterprise-scale hiring operation, automating the data collection behind your pipeline report frees your team to spend time on analysis and decisions rather than spreadsheet maintenance. The goal is not a better report. It is faster, more confident hiring decisions backed by real data.
Last updated: