This post covers how to build recruitment dashboards that earn their place: what a dashboard actually is, why the reports you already have do not help, the four worth building, and what your system needs to support.<\/p>\n
<\/span>What a recruitment dashboard is<\/span><\/h2>\nA recruitment dashboard is a single view that brings together the measures behind one recurring decision, refreshed automatically, and read by someone who will act on it.<\/p>\n
Each part of that matters. One decision, or it becomes a wall. Refreshed automatically, or it stops being updated by March. Read by someone with authority to change something, or it is a report nobody opens.<\/p>\n
Most of what gets called a dashboard fails the last two.<\/p>\n
<\/span>Why the stock reports do not help<\/span><\/h2>\nThey count activity, not conversion<\/h3>\n
This is the central problem. Activity is easy to measure and weakly related to revenue.<\/p>\n
Recruiterflow’s data across 2,100+ firms makes the point bluntly: top-quartile firms add fewer candidates than everyone else, 800 against 930, and place 5.21 per recruiter against 1.38 (Source: The Economics of Recruiting<\/a>).<\/p>\nA dashboard that ranks recruiters by candidates added will reward the wrong behaviour. The measure that separates the two groups is screening to submission, 50.1% against 36.1%, and it rarely appears on a stock report at all.<\/p>\n
They report on the period, not the cohort<\/h3>\n
Standard reports answer “what happened in September”. That mixes candidates added in September with placements from searches that started in June.<\/p>\n
The question worth answering is what happened to the candidates who entered in June, tracked forward. Cohort reporting is how you see whether a change you made in July did anything, and almost no default report is built that way.<\/p>\n
They average across desks that do different work<\/h3>\n
One number for the whole firm hides everything. A contract desk and a retained desk have completely different funnels, so a blended submission-to-interview rate describes neither.<\/p>\n
Any dashboard worth building segments by desk, discipline or engagement type before it shows a single average.<\/p>\n
<\/span>Start from the decision<\/span><\/h2>\nThe rule that makes dashboards useful: name the decision first, then work backwards to the smallest set of numbers that changes it.<\/p>\n
“How is recruitment doing” is not a decision. “Which of my six recruiters needs help with client submissions this month” is. So is “which three clients should we stop working” and “is this search going to land”.<\/p>\n
If nobody can name what they would do differently based on a chart, the chart does not go on the dashboard.<\/strong> That single test removes most of what usually gets built.<\/p>\n<\/span>Four dashboards worth building<\/span><\/h2>\nThe desk dashboard<\/h3>\n
One row per recruiter, one column per funnel stage, conversion rates rather than counts.<\/p>\n
The column that matters is screening to submission, because that is the largest leak in the industry at 11.3% (Source: The Economics of Recruiting<\/a>). A recruiter converting at 20% and one converting at 45% need completely different conversations, and an activity report shows them as identical if they made the same number of calls.<\/p>\nThe client dashboard<\/h3>\n
One row per client, showing submissions, interviews, placements and the time between them.<\/p>\n
Most firms discover two or three clients absorbing a disproportionate share of delivery while converting far below average. That is not a performance problem, it is a decision about who you work for, and it only becomes visible when the data is grouped by client rather than by job.<\/p>\n
The source dashboard<\/h3>\n
Where candidates come from, measured all the way to hire rather than to application.<\/p>\n
The channel differences are larger than most firms assume. Referrals take about 20 candidates to make a hire and convert interview to hire at 78.92%. LinkedIn takes 283 candidates and converts at 17.36% (Source: The Economics of Recruiting<\/a>).<\/p>\n![\"The](\"https:\/\/recruiterflow.com\/blog\/wp-content\/uploads\/2026\/05\/5-1024x342.png\")
<\/a><\/p>\nBoth are worth using. But a source report that stops at applications will tell you LinkedIn is your best channel, and a source report that runs to placement will tell you the opposite.<\/p>\n
The pipeline health dashboard<\/h3>\n
Not how many candidates are in each stage, but how long they have been sitting there.<\/p>\n
A search with twelve candidates at interview stage looks healthy until you see that nine of them have not moved in three weeks. Ageing by stage is the measure that predicts a search going quiet, and it is the one most often missing.<\/p>\n
<\/span>What your system needs to support it<\/span><\/h2>\nFour capabilities, and it is worth checking before you plan the dashboards rather than after.<\/p>\n
\n- Custom fields that report.<\/strong> Many systems let you add a field but will not let you group or filter by it. If engagement type is a free-text note, no dashboard can segment by it.<\/li>\n
- Cohort filtering.<\/strong> The ability to select candidates or jobs by entry date and follow them forward, rather than only reporting on activity inside a date range.<\/li>\n
- Owner-level segmentation.<\/strong> Every measure needs to break down by recruiter, desk and client, or you are stuck with firm-wide averages.<\/li>\n
- Export.<\/strong> If the answer to a new question requires a support ticket, you will stop asking new questions.<\/li>\n<\/ul>\n
Before building anything, run a database audit<\/a> on the fields the dashboard depends on. A dashboard built on a field that is populated 40% of the time reports confidently and wrongly, which is worse than no dashboard.<\/strong><\/p>\n<\/span>Decide the metrics before the layout<\/span><\/h2>\nThe useful sequence is decision, then measure, then layout. Most dashboard projects run it backwards and start with the chart.<\/p>\n
Getting the measures right is its own piece of work, and the recruiting metrics<\/a> that belong on a firm’s dashboard are a shorter list than most people expect. The wider discipline of recruitment analytics<\/a> covers how to read them once they are in front of you.<\/p>\nRecruiterflow’s reporting builds these views from the records your team already keeps, segmented by recruiter, client and engagement type, without an export or a spreadsheet in the middle.<\/p>\n
\nBring the one question your current reports cannot answer to a demo<\/a>, and we will build that view against your own data.<\/p>\n<\/blockquote>\n
They count activity, not conversion<\/h3>\n
This is the central problem. Activity is easy to measure and weakly related to revenue.<\/p>\n
Recruiterflow’s data across 2,100+ firms makes the point bluntly: top-quartile firms add fewer candidates than everyone else, 800 against 930, and place 5.21 per recruiter against 1.38 (Source: The Economics of Recruiting<\/a>).<\/p>\n A dashboard that ranks recruiters by candidates added will reward the wrong behaviour. The measure that separates the two groups is screening to submission, 50.1% against 36.1%, and it rarely appears on a stock report at all.<\/p>\n Standard reports answer “what happened in September”. That mixes candidates added in September with placements from searches that started in June.<\/p>\n The question worth answering is what happened to the candidates who entered in June, tracked forward. Cohort reporting is how you see whether a change you made in July did anything, and almost no default report is built that way.<\/p>\n One number for the whole firm hides everything. A contract desk and a retained desk have completely different funnels, so a blended submission-to-interview rate describes neither.<\/p>\n Any dashboard worth building segments by desk, discipline or engagement type before it shows a single average.<\/p>\n The rule that makes dashboards useful: name the decision first, then work backwards to the smallest set of numbers that changes it.<\/p>\n “How is recruitment doing” is not a decision. “Which of my six recruiters needs help with client submissions this month” is. So is “which three clients should we stop working” and “is this search going to land”.<\/p>\n If nobody can name what they would do differently based on a chart, the chart does not go on the dashboard.<\/strong> That single test removes most of what usually gets built.<\/p>\n One row per recruiter, one column per funnel stage, conversion rates rather than counts.<\/p>\n The column that matters is screening to submission, because that is the largest leak in the industry at 11.3% (Source: The Economics of Recruiting<\/a>). A recruiter converting at 20% and one converting at 45% need completely different conversations, and an activity report shows them as identical if they made the same number of calls.<\/p>\n One row per client, showing submissions, interviews, placements and the time between them.<\/p>\n Most firms discover two or three clients absorbing a disproportionate share of delivery while converting far below average. That is not a performance problem, it is a decision about who you work for, and it only becomes visible when the data is grouped by client rather than by job.<\/p>\n Where candidates come from, measured all the way to hire rather than to application.<\/p>\n The channel differences are larger than most firms assume. Referrals take about 20 candidates to make a hire and convert interview to hire at 78.92%. LinkedIn takes 283 candidates and converts at 17.36% (Source: The Economics of Recruiting<\/a>).<\/p>\n Both are worth using. But a source report that stops at applications will tell you LinkedIn is your best channel, and a source report that runs to placement will tell you the opposite.<\/p>\n Not how many candidates are in each stage, but how long they have been sitting there.<\/p>\n A search with twelve candidates at interview stage looks healthy until you see that nine of them have not moved in three weeks. Ageing by stage is the measure that predicts a search going quiet, and it is the one most often missing.<\/p>\n Four capabilities, and it is worth checking before you plan the dashboards rather than after.<\/p>\n Before building anything, run a database audit<\/a> on the fields the dashboard depends on. A dashboard built on a field that is populated 40% of the time reports confidently and wrongly, which is worse than no dashboard.<\/strong><\/p>\n The useful sequence is decision, then measure, then layout. Most dashboard projects run it backwards and start with the chart.<\/p>\n Getting the measures right is its own piece of work, and the recruiting metrics<\/a> that belong on a firm’s dashboard are a shorter list than most people expect. The wider discipline of recruitment analytics<\/a> covers how to read them once they are in front of you.<\/p>\n Recruiterflow’s reporting builds these views from the records your team already keeps, segmented by recruiter, client and engagement type, without an export or a spreadsheet in the middle.<\/p>\n Bring the one question your current reports cannot answer to a demo<\/a>, and we will build that view against your own data.<\/p>\n<\/blockquote>\nThey report on the period, not the cohort<\/h3>\n
They average across desks that do different work<\/h3>\n
<\/span>Start from the decision<\/span><\/h2>\n
<\/span>Four dashboards worth building<\/span><\/h2>\n
The desk dashboard<\/h3>\n
The client dashboard<\/h3>\n
The source dashboard<\/h3>\n
<\/a><\/p>\nThe pipeline health dashboard<\/h3>\n
<\/span>What your system needs to support it<\/span><\/h2>\n
\n
<\/span>Decide the metrics before the layout<\/span><\/h2>\n
\n
![\"Book](\"https:\/\/recruiterflow.com\/blog\/wp-content\/uploads\/2026\/07\/2Notetaker-1-1024x280.png\")
<\/a><\/p>\n