Short answer: A one-hour recruitment process audit checks one thing: what your hiring process actually knew about each requirement when it decided. For one role, write the requirements in a supervisor's words, record the evidence level each one reached at the moment of decision, then fix the heaviest requirement with the weakest evidence. It needs no software.
Most hiring reviews ask whether a new hire worked out. This audit asks a different question: what did the process actually know about each requirement when the decision was made?
You can answer it for one role in about an hour. You need no software, no consultant and no new budget. You need a supervisor, a recruiter and the records from your last ten hires.
The result is a short record and a count. It describes your process, not your people.
Key takeaways
- The audit takes about an hour for one role, with a recruiter and a supervisor.
- It records, for each requirement, the evidence level reached at the moment of decision.
- Three patterns show what to fix: weight without evidence, evidence without weight, and requirement without signal.
- The result is a record and a count, not a score or a benchmark.
- Repeat it quarterly to see whether the gap is closing.
On this page: What is a recruitment process audit? · Why audit one role? · What do you need before a hiring process audit? · Step 1 · Step 2: What should the audit record? · Step 3 · Worked example: hotel housekeeper · Ten questions to test your answers · What do you do with the results? A four-week plan · Common mistakes · FAQ
What is a recruitment process audit?
A recruitment process audit reviews how your hiring decisions are made. This version checks one thing: what your process actually knew about each requirement when it decided. For one role, you list the requirements, record the evidence level behind each, and fix the biggest gap first.
The Signal Gap, a term Radius Hire introduced in The Radius Papers 01 (2026), is the distance between what a hiring decision rests on and what predicts the outcome. This audit makes it visible for one role. Two processes can take the same time and produce the same number of hires, yet rest on very different evidence. The audit shows which one you have.
Why audit one role, not the whole process?
Start small on purpose. A full process review tends to become a discussion about everything at once. One role gives you something concrete. You see real requirements, real decisions and real gaps.
Pick a role that is:
- hired often, so the findings matter
- important to operations, so the supervisor cares
- stable, so the requirements are clear
A warehouse operative, reach-truck driver, picker, production operator or hotel housekeeper are typical choices.
What do you need before a hiring process audit?
Three things:
- The job advertisement for the role.
- The supervisor's own list of requirements. Ask them: "What decides whether a new person in this role works out?"
- The records behind your last ten hiring decisions: CVs, call notes, interview notes, and when each check was done.
Who should be in the room: the recruiter who runs the process and the supervisor who manages the hires. For a staffing agency, that means the consultant who screens for the client and, ideally, the client's site contact.
How to spend the hour:
- 0 to 10 minutes: agree the requirements with the supervisor.
- 10 to 35 minutes: record the evidence for each requirement. Use the ten hiring records to check what actually happened, not what the policy says.
- 35 to 50 minutes: read the patterns.
- 50 to 60 minutes: pick one fix and name an owner.
Step 1: Write down what the role really requires
Write the requirements in plain language, the way a supervisor would say them. Do not copy the job advertisement. Advertisements are written to attract people. Requirements should describe what the job actually demands.
The real list is usually short and specific. For a hotel housekeeper, it might be:
- cleans a room to the hotel's standard
- keeps up the pace across a full shift
- starts reliably at 07:00
- uses cleaning products safely, following instructions
- works the real weekend rota
Keep it to the handful that decide whether a hire works out. Treat the list as a working hypothesis. It gets stronger when it is based on a careful look at the job, and when it is later checked against how hires actually perform and how long they stay.
Step 2: What should the audit record?
For each requirement, write down four things:
- What the current process tells you. For example: "Candidate says two years in hotels."
- Where that information comes from. The CV, a phone call, a document, a practical task.
- How much weight it carried in the decision. High, medium or low is enough.
- Which evidence level it reached at the moment of decision.
The paper records evidence at five levels: verified, demonstrated, structured, claimed and not covered.
- Verified: checked against a document or a third party before the decision.
- Demonstrated: observed or tested during the process.
- Structured: asked of every candidate and recorded against criteria written in advance.
- Claimed: the candidate's own statement only, on the CV or in an unstructured conversation.
- Not covered: nothing collected before the decision.
A structured interview asks every candidate the same job-related questions and rates each answer against a standard written in advance. The definition follows Campion, Palmer and Campion (1997). For what the research shows about structured interviews, and what it does not, see Structured vs Unstructured Interviews: What the Research Shows, and What It Does Not.
The key rule: record what the process actually does, not what the policy says. If certificates are "supposed to" be checked early but in practice are checked after the offer, record "claimed".
Use one row per requirement. Copy this table:
| Requirement | What the process knows | Source | Weight (high, medium, low) | Evidence level at decision |
|---|---|---|---|---|
Step 3: Read the patterns
Three patterns tend to appear. Each has a different fix.
Pattern 1: Weight without evidence.
A requirement carries heavy weight but reaches only the claimed level. This is often experience, reliability or pace.
Fix: verify or demonstrate earlier in the process.
Pattern 2: Evidence without weight.
The process collects something reliably, but it does not affect the decision, because nobody records it against a standard.
Fix: write the criteria down before the process starts.
Pattern 3: Requirement without signal.
Everyone agrees it matters, but the process never asks. Commute, shift expectations and physical demands often sit here.
Fix: ask every candidate, in the same way, early. Ask about the job's demands and the candidate's experience of similar work, never about health or medical conditions.
Start with the requirement that carries the most weight and has the weakest evidence.
A worked example: hotel housekeeper
Illustration built for this article, not client data.
| Requirement | What the process knows | Source | Weight | Evidence level at decision |
|---|---|---|---|---|
| Cleans a room to the hotel's standard | "Two years in hotels" | CV and a short phone call | High | Claimed |
| Keeps up the pace across a full shift | Nothing | Not asked | High | Not covered |
| Starts reliably at 07:00 | Nothing | Not asked | High | Not covered |
| Uses cleaning products safely, following instructions | Nothing | Not asked | Medium | Not covered |
| Works the real weekend rota | A tick in the "weekends" box | Application form, never compared with the rota | Low | Claimed |
The count: two requirements claimed, three not covered, none verified, demonstrated or structured.
What the patterns suggest:
- Weight without evidence (pattern 1): cleaning to the hotel's standard carries heavy weight but is only claimed. It could be demonstrated, where that is safe and proportionate.
- Evidence without weight (pattern 2): every candidate answers the weekend question, but nobody compares the answer with the real rota, so it never affects the decision. Write down what the rota needs before the process starts.
- Requirement without signal (pattern 3): pace, the 07:00 start and safe use of cleaning products are never asked. They could be asked of every candidate against a written standard.
None of this criticises the people involved. The finding is about the process. For a warehouse version of this example, with a reach-truck certificate and right to work, see What Is the Signal Gap?
Ten questions to test your answers
Use these to challenge the audit. Answer about what the process actually does, not what the policy says.
- Are the requirements for this role written down, in the words a supervisor would use?
- How many of those requirements are supported at the moment of decision by something other than the candidate's own claim?
- Does every candidate for this role get asked the same questions?
- Are the criteria for a good answer written down before the first candidate is seen?
- Would two managers screening the same twenty applications produce the same shortlist?
- When are identity, right to work and required certificates actually checked, compared with the offer?
- Which requirements are never asked about before the offer?
- How long does the process take from application to decision, and how many candidates drop out along the way?
- Who made the decision, and could you reconstruct six months later what it was based on?
- What do you record about the people you hired, and does anything from the screen predict it?
A role where questions 1, 3, 4 and 6 produce uncomfortable answers has a large Signal Gap. That can be addressed without changing anything about the people running the process.
What do you do with the results? A four-week plan
Spread the work over four weeks: the audit with the supervisor, then questions and rating standards, then one verification step moved earlier, then outcome records.
- Week 1: Run the audit with the supervisor. Output: a requirement list with evidence levels.
- Week 2: Write one question and one short rating standard for each requirement that is claimed or not covered and that no document can prove. Leave document checks, such as certificates, for Week 3. Output: a question set and written criteria.
- Week 3: Move one verification step, such as the certificate check, before the offer, where lawful. Check with legal counsel first. Write a short explanation of the process for candidates. Output: an updated process and candidate information text.
- Week 4: Start recording outcomes for new hires: attendance, early leaving and a supervisor rating at a fixed point. Output: a baseline to measure against.
Then repeat the audit every quarter and compare the count. That shows whether the gap is closing.
Common mistakes
- Auditing the policy instead of the practice. The audit is only useful if it records what really happens.
- Turning the count into a score. There is no validated scale for the Signal Gap. The count describes one process for one role. Do not compare it across sites or employers as a benchmark.
- Blaming individuals. A requirement at the claimed level is a process finding, not a recruiter failure.
- Buying a tool before the audit. Count your gaps first. Then judge any method or tool by which requirements it would move up the evidence levels.
FAQ
How do you audit a hiring process?
Pick one role, write its real requirements, record the evidence your process holds for each at the moment of decision, count the requirements at each evidence level, and fix the heaviest gap first.
How long does a recruitment process audit take?
About an hour for one role, if you bring the job advertisement, the supervisor's requirement list and the records from your last ten hires.
Who should be in the room?
The recruiter who runs the process and the supervisor who manages the hires. For a staffing agency, the consultant who screens for the client and, ideally, the client's site contact.
How often should you repeat the audit?
Every quarter. Compare the count of requirements at each evidence level with the last one to see whether the gap is closing.
Can staffing agencies use this audit?
Yes. For an agency, the same evidence problem sits inside its own screening, where a poor match costs margin, recruiter time and client trust. Run it on a role you screen for a client, ideally with the client's site contact.
What if the requirements are not written down anywhere?
That is your first finding. Writing them down with the supervisor is step one, and every other improvement depends on it.
Sources
- Radius Hire (2026). The Radius Papers 01: A New Standard for Frontline Hiring. Sections 1.1, 2.1 to 2.5, 4.9, 5.3, Appendix A and Conclusion.
- Campion, M. A., Palmer, D. K., and Campion, J. E. (1997). A review of structure in the selection interview. Personnel Psychology, 50(3), 655 to 702.