The KPIs a recruitment agency manager should actually track

It's tempting to track activity metrics — placements made, CVs sent — but those measure output, not necessarily whether the agency is running compliantly or serving clients well. The more useful KPIs tend to be leading indicators of a problem before it surfaces.

What's actually worth watching

• –Workers approaching the 12-week AWR threshold in the next two weeks
• –Incomplete onboarding steps — right to work, DBS, KID — for anyone due to start
• –Timesheets unsubmitted or unapproved past their expected date
• –Right to work or DBS records due for renewal or follow-up

The pattern across all of these: they're only useful if they're visible without someone having to go and check manually. A worker who quietly crosses the 12-week mark without anyone noticing is a compliance gap that existed the whole time — it just wasn't visible until it was pointed out from outside.

Activity KPIs still have a place — just not this one

None of this means activity metrics are worthless. Placements made, time-to-fill, CVs sent — these tell a manager whether the desk is commercially healthy, and they're legitimate numbers to track for that purpose. The point is narrower: they don't tell you anything about compliance risk or client-side service quality, and treating them as a full picture of how the agency is doing leaves the leading indicators above unmonitored by default.

Turning a KPI into an action, not just a number

A dashboard showing three workers approaching the 12-week AWR threshold is only useful if someone owns what happens next — confirming the comparator pay and conditions with the hirer, updating the worker's terms, and making sure the change is reflected in payroll and timesheets before the threshold is actually crossed. A KPI that's visible but has no defined owner or next step tends to become background noise within a few weeks, which defeats the purpose of tracking it at all.

Setting sensible thresholds

• –Flag AWR-approaching workers at two weeks out, not on the day they cross — there needs to be time to act
• –Flag incomplete onboarding steps daily for anyone due to start within the week, not just at the point a start date has already arrived
• –Flag overdue timesheets as soon as they miss the expected submission point, not only once payroll is at risk
• –Review right to work and DBS renewal dates on a rolling basis well ahead of expiry, not in the same week they lapse

What this looks like for a manager running multiple desks

Across several consultants and client accounts, the same four categories above compound quickly — a handful of near-threshold workers, a few incomplete onboarding steps, and a couple of overdue timesheets on each desk adds up to a genuinely large number of live risks at any one time. The value of tracking these centrally, rather than trusting each consultant to manage their own, is that a manager can see the whole agency's exposure in one place rather than discovering a gap only when a specific hirer or worker raises it.

This is worth stressing for a manager weighing whether it's worth the effort to set this up: it isn't a request for a new system built from scratch or a new set of forms for consultants to fill in. It's a request to make existing records answer a different, more useful question than they currently do — which is a considerably smaller undertaking than it might first sound.

Building these KPIs from records you already keep

None of these four categories require new data collection — they're derived from records an agency should already be keeping: assignment start dates for AWR tracking, onboarding completion status, and timesheet submission and approval dates. The work isn't gathering new information; it's surfacing what already exists in a form that flags a problem before it becomes one, rather than leaving it buried in individual worker files that only get reviewed when something's already gone wrong.

How often these numbers should actually be reviewed

A monthly compliance report is common, and largely useless for the categories above — by the time a monthly report flags a missed onboarding step or an overdue timesheet, the practical damage is usually already done. These are the kind of indicators that need a much shorter review cycle: daily or near-daily for onboarding gaps and overdue timesheets, weekly for AWR threshold approaches, since two weeks of lead time only stays useful if it's actually being checked with some regularity rather than once a month.

The trap of tracking too many things

It's tempting, once a manager starts building out a KPI dashboard, to keep adding metrics that seem useful in isolation. The risk is that a long list of tracked numbers becomes as easy to ignore as no dashboard at all — if everything is flagged, nothing stands out as urgent. The four categories in this post are deliberately narrow: they're the ones with a direct line to a compliance or pay obligation, not a broader measure of desk performance. Layering on additional metrics is fine, but it's worth keeping the ones with real regulatory or financial consequences visually distinct from general performance tracking, so they don't get lost in the noise of everything else a manager might want to watch.

A simple test for whether a KPI is actually working

Ask, honestly, whether the last time one of these categories flagged a real issue, someone acted on it before it became a problem — or whether it was noticed only after a hirer or worker raised it independently. If it's consistently the latter, the KPI exists on paper but isn't functioning as an early warning system in practice, and it's worth treating that as seriously as not having the KPI at all.