When a search goes wrong or a new hire struggles, you want to check your hiring process and find where it broke. A recruitment audit can cover any part of how your team hires. The one in this guide answers a narrower question you can act on: for each hiring decision your team made recently, could someone who wasn’t in the room see what the team was looking for, what each interviewer found, and why the candidate moved forward or didn’t? Each decision leaves a record: the notes from the intake meeting, the interviewers’ scorecards, the debrief, and the reason given for a rejection. If that record can’t answer the question, you can’t tell whether a search broke at the criteria, the interviews, or the decision itself.

This guide is for recruiters and recruiting leads who want to run that audit. It shows you how to pick a sample of recent decisions, trace each one through the record it left, sort the gaps by their cause, and run the same audit again next quarter.

Before you run it, you may be tempted to start with industry benchmarks on how other companies hire. Those figures come from teams with different roles, different interview stages, and different ways of counting, so they rarely tell you what to change in your own process. That’s why my advice is to audit your own decisions first, before you compare your process with anyone else’s. Your own records show you where the process breaks, and the gaps you find there are ones your team can fix.

Pick the decisions your recruitment audit will cover.

A recruitment audit works best on a sample small enough that you can read every record behind each decision. Choose the sample before you open anything, so you don’t only pick the searches you already worry about:

  1. Choose a recent period, such as the last quarter, so the records come from the process your team runs now.
  2. Pick a few roles from different teams, including at least one search that felt slow or difficult and one that felt routine.
  3. Include rejected candidates as well as hires. Take the candidates turned down after a final round, because a late rejection should leave as full a record as a hire.

Leave offer letters and work authorization checks out of this audit: they belong to a compliance review run by your human resources (HR) or legal team. This audit checks whether the decisions themselves were written down.

Once the sample is set, pick one hiring manager to read it with you, ideally one who didn’t run any of the searches you sampled, so they read the record the way someone outside the room would. You know where the records live, and a hiring manager can say whether a record gives them enough to make a hiring decision.

Check that the criteria were written down before the search began.

Every later check depends on this one. If no one wrote down what the role needed, you can’t tell whether an interviewer’s feedback was on point, or whether a candidate was turned down for a reason the team agreed on. For each role in your sample, look for a written record from the intake meeting that covers:

  • the skills and experience the role needs, with the firm requirements kept apart from the preferences
  • what evidence of each requirement would look like in an interview
  • which interview stage assesses each requirement, and who runs that stage
  • how the team will settle a disagreement between interviewers

If the criteria only exist in the hiring manager’s head, or in a job description written for candidates, note that against the role and go on to the next one. Fix the intake first for those teams, so their next search starts from written criteria.

If your intake meetings don’t produce that record yet, there’s a separate guide to the questions, agenda, and template for a recruiter intake meeting.

Trace each decision through the record it left.

Now take each candidate in your sample and follow them from their first interview to the decision. At each stage, check what should exist and whether it does. Use this table as your checklist:

Stage What the record should show What a gap looks like
Interview plan Each requirement from the intake assigned to a stage and an interviewer A requirement no stage covered, or two stages assessing the same thing
Each interview A scorecard submitted before the candidate moved to the next stage No scorecard, or one submitted after the next stage began
Each scorecard A rating with written evidence for it, tied to the role’s requirements A rating with nothing written under it, or notes that never mention the requirements
Debrief The decision, who made it, and the reasons, written down at the time A decision with no reasons, or reasons that don’t match the scorecards
Rejection The reason the candidate didn’t move forward A status change in the applicant tracking system (ATS) with no reason attached

For each candidate, finish by checking that the record explains the decision: could someone reading only the record say why the team advanced or rejected this candidate? Write down yes or no, and for every no, note the first stage where the record runs out.

Sort each gap by its cause before you fix it.

A gap can look the same in two places and have two different causes. A missing scorecard after a panel interview might mean no one was told it was theirs to write. After a final round, it might mean that stage never had a scorecard at all. Sort every gap by its cause first, because each cause has its own fix:

Cause How to spot it What to fix
No scorecard for the stage The stage has no form attached in your ATS, so no interviewer could submit one Add a scorecard to the stage, with a field for each requirement it assesses
A form that doesn’t fit Interviewers fill in the rating and leave the other fields empty, or put their notes wherever the form has room Rewrite the form so its fields match what that stage assesses
No owner The interview happened, but no one was assigned the scorecard, often on a panel or with a stand-in interviewer Name one interviewer for each stage who owns its scorecard
Late feedback The scorecard exists but went in after the candidate moved to the next stage Agree on a feedback deadline at intake, and hold the next stage until it’s met
The reasons live somewhere else The reasoning sits in a chat thread, an email, or an interviewer’s own notes Move it into the candidate’s record in your ATS, and tell the team where it belongs

Sending interviewers a reminder is the usual response to missing scorecards, but a reminder only fixes one of the causes above: late feedback. If most of your gaps sit in one stage or one form, fix the stage first, before you chase any interviewer.

For late feedback, start with the deadline you agree on at intake, then chase anyone who misses it. There’s a separate guide to getting every scorecard submitted on time.

Where Metaview fits.

Tracing a decision gets hard when the only record of an interview is what someone wrote afterward, because a missing or thin scorecard leaves you nothing to check. It gets easier when every interview leaves a record of its own.

Metaview is the Agentic Recruiting Platform, and its Notetaker keeps that record. Where consent has been given, the interview is captured by the Metaview Notetaker. It records and transcribes the interview, then turns the conversation into structured notes.

Interview notes in the Metaview Notetaker, grouped under topic headings, each heading marked with the number of sources behind it and followed by bullet points
Notes from an interview, grouped by topic. The candidate’s answers shown are sample data.

The recording captures every spoken word, so when you trace a decision and find a thin scorecard, you can read what the candidate said in that interview and see what the scorecard left out.

The Notetaker also drafts the scorecard from the conversation against your team’s template, so the interviewer starts from a draft instead of an empty form. The interviewer then reviews the draft, rates the candidate, and submits the scorecard.

While you trace a decision, the Metaview Assistant answers questions in plain language from your captured interviews, so you can ask it to recall what the candidate said about one of the role’s requirements.

When you want to look across many interviews at once, rather than one candidate at a time, Metaview Reports lets you report on your own interview data inside Metaview.

However you read a candidate’s interviews, judge each decision on all of them together. Shahriar Tajbakhsh, Metaview’s co-founder and chief technology officer, has described the standard a candidate’s interviews should meet as a set:

One interview can’t get all of the signal needed to make a hiring decision, but the collection of all interviews for any given candidate must provide the necessary information.”
Shahriar Tajbakhsh Shahriar Tajbakhsh Co-founder and Chief Technology Officer · Metaview

That’s the same test you ran on each decision in your sample. If a candidate’s interviews, read together, show everything the decision needed, someone outside the room can follow it.

Keep a record of every interview.
Book a demo to see how the Metaview Notetaker records each interview and drafts the scorecard for your interviewers to review.
See it live

Check that the fixes held at your next audit.

Once you’ve fixed the first gaps, you’ll want to know whether your process is getting better. The way to tell is to compare each audit with the one you ran the quarter before. That comparison only holds if you run the audit the same way each time. Set it up like this:

  1. Keep the same checks and the same definitions each time. If you count a scorecard as on time when it arrives before the next stage, count it that way every quarter.
  2. Sample the same kinds of decisions each time: recent hires and late-stage rejections, across a few teams.
  3. Break the results down by role, stage, and interviewer, so you can see whether a gap is spreading or staying in one place.
  4. Write down each fix you made and the gap it was meant to close, so the next audit can check it.

Run the next audit a quarter later. When you do, take these four steps to see whether last quarter’s fixes held, and where to start when one didn’t:

  1. Read the intake record for each new role in the sample. If a team you flagged last quarter has again started a role without written criteria, start there, and book the intake with the hiring manager before that team’s next search opens.
  2. Trace the stages you fixed last time. If a gap you fixed is back, ask who owns that stage now, because a fix often lapses when its owner moves on.
  3. Look for gaps in stages that were clean last time. If one appears, sort it by its cause before you change anything.
  4. For each decision, ask again whether someone reading only the record could see why the team decided as it did, and compare your answers with last quarter’s. Wherever the answer is no, start the next round of fixes at the first stage where that decision’s record runs out.

Keep running the audit each quarter. When you bring in a team you haven’t covered yet, give it a sample of its own, so you compare its results with its own earlier audits rather than with another team’s.

You’ll know the fixes have held when every decision explains itself: someone reading the record can see the reasons behind each one, in every role you sampled.

See it in action.

Read every interview behind a hiring decision.

See how the Metaview Notetaker records each interview and drafts the scorecard, so your next audit has a record to read.

Frequently asked.

How often should you run a recruitment audit?

Run it once a quarter. That’s soon enough that the records come from the process you run now, and long enough that there are new decisions to sample. Run one sooner after a big change, such as a new ATS or a new interview process.

Who should run a recruitment audit?

A recruiter or recruiting lead, with one hiring manager. The recruiter knows where the records live, and the hiring manager can say whether the record would have helped them decide.

How many decisions should the sample include?

Enough to cover a few roles, with both hires and late rejections, and few enough that you can read every record behind each one. If you can’t read them all in an afternoon, cut the sample.

Is a recruitment audit the same as a hiring compliance audit?

No. A compliance audit checks paperwork, such as offer letters, work authorization documents, and how long records are kept, and it belongs to HR or legal. A recruitment audit checks whether each hiring decision was written down well enough for someone else to follow.

Should you use industry benchmarks at all?

They can prompt a question, such as whether your process has more interview stages than it needs. Check any answer against your own records before you change anything, because a benchmark can’t show you where your process breaks.