Recruiting numbers that survive the meeting

Time to fill gets disputed, funnel counts disagree with the tracker, and source of hire depends on who built the report. This module rebuilds recruiting on stage events you own, with numbers that tie to headcount and cost.

RuleEvery recruiting metric on these pages computes from one event fact, so any two reports that disagree are one query away from the reason.

Neverpublish a recruiting rate whose clock, population, and stage definitions are not stated on the page that shows it.

◆ The pagesone model, eleven pages, every number tied.

Page	What it answers
The recruiting star	The event-grain model everything else reads: stage transitions with real timestamps, requisition snapshots, and the hire handoff into Core HR.
Time to fill	The disputed number, with the clock stated: which start, which stop, median beside mean, and why backdating bends the delivered version.
The hiring funnel	Stage conversion counted from events instead of current states, so the funnel and the tracker stop disagreeing.
Source of hire	Attribution fixed once, then the funnel per source, with starts that tie to the headcount page.
Cost per hire	What a hire actually costs, joined from finance and payroll, total and by source.
Requisition aging	Open requisitions by age band, the chase list, from daily snapshots.
Offer acceptance	Offers to acceptances and acceptances to starts as two separate rates, every decline with its reason.
Stage velocity	The 44-day median fill decomposed stage by stage; the days go to decisions and notice periods, not sourcing.
Interview load	336 interviews and 21 interviewer hours per start: the cost hiring puts on everyone else’s calendar.
New hire retention	Cohorts followed forward by source; the ranking flips when cost is divided by the hires who stayed.
Hiring plan vs actual	Starts against the promised plan version: 20 planned, 16 started, the gap named by department.

◆ Why events, not statesthe one design decision behind the module.

Delivered recruiting reports read the current state of requisitions and applications: one primary data source per report, stage timestamps buried in business process history, and filled positions that keep showing open until a start date passes. Every recurring dispute traces back to reading states instead of events.

The owned model stores every stage transition as a dated event row. Counts, conversion, elapsed time, and aging all become arithmetic on that one fact, and the quarter's 16 starts on these pages are the same 16 hires the headcount page reports and the payroll module prices. One population, one story.

◆ Where the numbers tiethe cross-module arithmetic the battery checks.

Number	Value	Also appears on
Starts, March to May 2026	16	Hires on the headcount history table: 6 + 5 + 5.
Starts in May	5	May hires on the same table; the five fills timed on time to fill.
Funnel bottom	16	The funnel and the source table both end at the same 16.

Sample values are illustrative, never client data.

Use case

Problem

Recruiting metrics are disputed in every review because each report reads current states with its own hidden definitions.

What we build

An event-grain recruiting model in your warehouse, with four reports computed from one fact and definitions stated on the page.

What you get

Recruiting numbers that recompute to the same answer from any seat and tie to headcount and payroll.

Want recruiting numbers nobody relitigates?

We ship the event model and the four reports, tied to your headcount, in 10 days.

Talk to us

Terms on this page

battery: The automated set of checks, including the crossfoot arithmetic, run on every build of this catalog.
stage event: One dated row per application stage transition. The grain of the module.
data source: The population a delivered report reads. One primary per report.
business process: Workday’s workflow engine. Stage timestamps live in its event history.
requisition: The approved opening a hire fills.
start: A hire’s first day. Where recruiting hands off to headcount.
conversion: The share of one stage’s candidates reaching the next.
tie: A check that two independently built totals agree.