# Recruitment Funnel Analytics: practice workbook
Talent Engineering Academy | An education initiative by Vitae
Edition 2026.09 | Updated 2026-09-24
Course: https://talentengineering.org/courses/recruitment-funnel-analytics

Build trustworthy hiring metrics, interpret bottlenecks and avoid misleading comparisons.

## Your deliverable
A recruitment metric dictionary and decision dashboard specification.

Use fictional information. Keep your completed work in your own secure notes. Exercises and capstone work are self-directed, not independently assessed.

## 1. Decision and metric definition

Your notes:



## 2. Numerator, denominator and event times

Your notes:



## 3. Cohort and exclusions

Your notes:



## 4. Open cases and missing data

Your notes:



## 5. Segment and uncertainty

Your notes:



## 6. Action owner and review cadence

Your notes:



## Lesson exercises

### 1. Define events before metrics

Define seven hiring events and the unit of analysis for each.

Your response:


Worked example: One team counts interview scheduled as interview completed while another counts attendance. Their conversion rates cannot be compared until the event definition is aligned.

Self-review guidance: Include a rule for rescheduling and non-attendance. A scheduled event is not completed evidence. State how missing timestamps will be reported rather than silently excluded.

### 2. Measure flow and waiting separately

Calculate stage waiting times for five fictional cases, including one still open and one cancelled.

Your response:


Worked example: A report shows a lower average hiring time after several difficult vacancies were cancelled. The interpretation must disclose the cancellations rather than claiming that the process became faster for comparable roles.

Self-review guidance: Report completed-case statistics separately from open-case age and cancellations. Explain the start and end events. Do not treat excluded difficult cases as evidence of improvement.

### 3. Diagnose bottlenecks with context

Investigate a fictional queue using inflow, outflow and three case notes.

Your response:


Worked example: Twelve applications wait for review because a hiring manager changed the brief, not because the recruiter stopped working. The action resolves requirements before adding reminder automation.

Self-review guidance: Identify at least two plausible explanations and the next evidence needed. If the process is unstable, describe the trend rather than presenting a steady-state formula as a precise prediction.

### 4. Report decisions, not decorative numbers

Write a one-page dashboard specification with five metrics and two decision rules.

Your response:


Worked example: A weekly report recommends fixing brief approval because repeated rework explains most observed delay. It includes the affected case count, an alternative explanation and a two-week pilot, rather than merely colouring a time metric red.

Self-review guidance: For every metric, identify the action it can inform and its limitation. Include at least one quality guardrail and one measure of unfinished work.

## Portfolio review
Check that your work is internally consistent, distinguishes facts from assumptions, names decision owners and explains its limitations. Revise gaps before using the method in real work.

## Further reading
- [CIPD: Recruitment](https://www.cipd.org/uk/knowledge/factsheets/recruitment-factsheet/): Professional context for the recruitment lifecycle.
- [MIT: Little's formula and queueing systems](https://web.mit.edu/urban_or_book/www/book/chapter4/4.4.html): Technical background for interpreting work in progress, throughput and flow time.

Original educational scenarios. References provide further reading and do not imply endorsement. Check current official rules and appropriate professional advice for real legal, financial or regulated decisions.