I build recruitment dashboards by stakeholder because a recruiter, hiring manager, and executive do not need the same level of detail. The underlying definitions should stay consistent, but each view should make the next decision obvious.
Example 1: recruiter operations view
The recruiter view is action-oriented. I put current work first:
- Open requisitions by priority and owner
- Candidates waiting for recruiter action
- Candidates waiting for hiring manager feedback
- Interviews scheduled this week
- Overdue next actions
- Stage aging by requisition
- Offers awaiting a response
I include candidate ID, requisition ID, current stage, next action, action owner, and due date in the detail table. A red status without those fields creates anxiety but does not tell anyone what to do.
Example 2: hiring manager view
The hiring manager needs a concise view of pipeline health for their roles. I show:
| View | Useful detail |
|---|---|
| Funnel | Candidates by stage and conversion to the next stage |
| Candidate slate | Current candidates, stage, strengths to test, and next step |
| Interview health | Feedback completion and overdue decisions |
| Source mix | Sources producing candidates who reach interviews |
| Role aging | Days open, current bottleneck, and agreed action |
I avoid displaying unstructured interview comments on the summary page. The manager should be able to see the decision needed, then open the approved candidate record for evidence.
Example 3: leadership portfolio view
For a hiring leader, I summarize across departments:
- Open roles by department, priority, and status
- Hires and offers by period
- Time in process by role group
- Roles without qualified pipeline
- Source progression across the portfolio
- Approved spend and cost per hire, where data is complete
- Candidate experience or process-health exceptions
This view needs filters for department, recruiter, location, level, and date range. I label partial data instead of presenting an incomplete portfolio as a precise result.
Example 4: sourcing view
The sourcing dashboard compares channels using the same attribution rule. I show sourced candidates, response or application activity where available, recruiter screens, interviews, offers, hires, and disposition reasons by source.
I focus on progression rather than volume. A channel with fewer candidates may be useful if the candidates progress further, while a high-volume channel may create review work without producing a strong slate. I include a source-definition note so referrals, direct outreach, job advertising, and agency submissions are not mixed casually.
Example 5: workload and service view
This view helps a recruiting operations lead see whether the process can keep its commitments:
- Active requisitions per recruiter
- Open candidates per recruiter
- Interviews awaiting scheduling
- Feedback awaiting submission
- Time to respond to candidates
- Roles with missing intake decisions
- Requisitions with no activity in the review period
I use this view to allocate help and remove blockers. I do not use raw activity counts as a standalone performance ranking because role complexity, hiring volume, and process design affect the numbers.
Example 6: quality and experience view
When the organization has reliable outcome data, I connect hires to the agreed quality measure, such as a defined manager review or first-deliverable completion. I pair that with offer declines, withdrawals, stage delays, survey feedback, and missing communication steps.
I do not create a quality metric from opinions that were not collected consistently. If the data is limited, I show the limitation and use process-health measures such as completed feedback, documented disposition, and timely follow-up.
Build views from shared definitions
Before publishing a dashboard, I create a definitions table:
| Metric | Definition | Owner | Refresh |
|---|---|---|---|
| Time to fill | Approved opening date to agreed close date | Recruiting operations | Weekly |
| Offer acceptance | Accepted offers divided by offers made | Recruiting operations | Weekly |
| Stage aging | Current date minus stage entry date | Recruiter | Daily or weekly |
| Cost per hire | Included recruiting spend divided by hires | Finance or recruiting operations | Monthly |
I document exclusions, date rules, and missing-data handling. Then I test each view with a recruiter and a hiring leader. If either person cannot identify the owner and next action behind an exception, I simplify the view.
The best recruitment dashboard is not the one with the most charts. It is the set of views that gives each stakeholder enough context to act without changing the meaning of the data.