An eight-stage recruitment pipeline, operated end to end without human routing.

Problem

UK education recruitment runs under the heaviest compliance load in the staffing industry. DBS enhanced checks, Child Workforce clearances, safeguarding training verification, regulated-activity references. Nothing is skippable. Every candidate, every time.

The per-candidate cost was concrete. 65 to 120 minutes of manual work, across CV review, initial screening, document verification, reference collection, interview scheduling, and profile generation. At thousands of candidates a year, that is a full team running the same sequence on loop. Existing tools could screen CVs, answer candidate questions, or schedule interviews. None of them ran the pipeline end to end.

First principles

Recruitment is a state machine. A candidate moves from sourced, to screened, to compliance-verified, to interviewed, to documented, to placed. Each transition is gated on a small number of facts. The facts are observable. Most of them can be collected in conversation.

A pipeline failure mode is not the missing fact. It is the gap between stages, where a candidate sits with the team chasing the next step and the candidate forgetting which step they were on. The work that compounds is closing those gaps automatically, not improving the quality of any single step.

WhatsApp is the candidate's native channel. The pipeline operates there. Voice notes and document photos are first-class inputs, not exceptions.

Pipeline

The eight stages run autonomously. Consultants work only on placement. Every status, document, and communication syncs to the existing CRM in real time, so the consultant's tooling does not change.

Numbers

Observation

Two patterns surfaced.

Compliance gates have to live alongside the pipeline state, not on top of it. A DBS-on-update-service check that runs at outreach is too late if the screening stage already proceeded against a candidate without one. The verification step runs the same check at every stage transition. A candidate cannot advance past a missing constraint.

The 85% completion rate is the operational manifestation of an interface choice. Compliance questions in a form structure are abandoned at the rate forms are abandoned everywhere. The same questions in a chat structure are answered. The interface is part of the pipeline, not separate from it.