A useful debrief gives the recruiter three things, in this order: the verdict, the evidence behind it, and a dated next step. The verdict lets the recruiter manage the candidate honestly. The evidence lets them brief the next one. The date is the first thing the candidate asks about. Send it quickly, or name the day it will land.
Here is an example of what I mean. A hiring manager interviews a strong BDM on the Thursday. Good interview. Both sides come out of it positive. On the Friday the feedback lands: "Yeah, he was good. We'll be in touch."
There is nothing in that I can use. It is not a decision. I do not know whether he is through, whether someone else is ahead of him, or when anyone will decide. So when the candidate rings that afternoon wanting to know how it went, the honest answer is that I do not know either.
That debrief leaves the recruiter without a decision.
What does a useful debrief give the recruiter?
Three things, in this order: the verdict, the evidence behind it, and a dated next step. Each one lets the recruiter do something specific, and a debrief missing any one of them stops the process in a different way.
The verdict. Yes, no, or a genuine maybe with a reason. This is what lets the recruiter manage the candidate honestly. A yes means I can build momentum and get the next stage in the diary while the interview is fresh. A no means I can close it cleanly and keep the relationship intact. A maybe is workable, but only when it comes with what the maybe depends on.
The evidence. What the candidate demonstrated, against what the role needs. "Strong on specification, thinner on merchant channel than we expected" is evidence. I can take that back to the candidate and use it to brief the next one. "Good cultural fit" gives me nothing to relay. Evidence is also what makes a rejection defensible, because it points at the role rather than the person.
The dated next step. A date, and what happens on it. "Second stage with the national manager, week beginning the 18th, we'll confirm Tuesday." That is the first thing the candidate asks me about once the interview is done.
Where a recruiter is running the process, that hand-off works in both directions. The candidate rings me with their read straight after the interview, before the thank-you email goes anywhere. I get your read and I get theirs, and I can put the two side by side quickly. If they line up, I can move the process on. If they do not, we find out early. The candidate side of this is on the paired page.
How fast does feedback need to be?
Give feedback as quickly as you can, or give a clear date when it will be available. The second half is the one I ask for most, because it is the one that lets me hold a candidate steady.
I am deliberately not going to give you a number of hours here. I have not counted my own processes properly, so I am not going to dress a preference up as a benchmark, and I would be sceptical of anyone in this industry who quotes you one. The WA Government's Hiring Managers' Toolkit, chapter 11 on giving feedback to applicants (last updated 30 June 2026) says applicant feedback should be prompt, factual and evidence-based. It does not put a number on prompt. Business.gov.au's interview and recruit employees page (accessed August 2026) covers letting unsuccessful candidates know, and no more than that.
The practical reason for moving is simple enough. Plan on an active candidate having other options, and give the recruiter a date they can communicate.
So a hiring manager who says "I can't get the two of them in a room until Thursday, I'll come back to you Friday" has given me something real to work with. A stated date lets me explain the wait and tell the candidate when to expect an update.
Which debrief failures do I run into?
Four: waiting to see more candidates, an absent decision-maker or approval, an unplanned extra stage, and positive feedback carrying no verdict. These are patterns from my own processes. They are observations, not a ranked list of what Australian employers do.
1. Waiting to see more candidates. Seeing others is reasonable. The failure is leaving the first one with no status and no date while you do it. Tell the recruiter where the candidate sits and when the comparison closes, and they can wait with some confidence instead of assuming they have been passed over.
There is a harder version of this worth saying out loud. If someone clears the brief, decide whether seeing more people changes a named risk before extending the process.
2. The decision-maker or the approval is not available. The interview happens, then it turns out the person who signs off is on leave, or the headcount needs an approval nobody flagged. That is a planning problem, and it is fixable before the first interview by asking who says yes and whether they are around.
3. An unplanned extra stage. A third conversation for a senior hire can be completely legitimate. It becomes a failure when it was not in the process the candidate agreed to, has no new assessment purpose, and has no close date.
The fix is to consolidate. If there is someone else who needs to meet the candidate, line them up alongside the second interview. Same people, same assessment, one less gap for the candidate to sit in.
4. Positive feedback with no verdict and no next step. The one in the opening. It reads as good news, it contains no decision, and it leaves the candidate in limbo. They hear enthusiasm, and I have nothing to attach it to.
How should negative feedback be handled?
Send it through the recruiter, keep it specific and job-relevant, and tie it to evidence from the interview or the criteria you agreed at brief. That is the whole guardrail.
A useful rejection sounds like this: "The technical knowledge was there, but we needed someone who has run a specification pipeline end to end and that came across as thin against the two we are progressing." A candidate can do something with that.
Leave out personal commentary, anything about how someone presented that has nothing to do with the job, and anything you would not want repeated. It is unusable, and it puts you somewhere you do not need to be. If you have a concern you cannot articulate against the criteria, tell me it is a concern and let me probe it.
A rejection handled well can leave the door open. It is a small industry, and a specific rejection can preserve the relationship for a later role.
What does a good debrief actually change?
It gives the recruiter a verdict, evidence and a dated next step after the interview. Sourcing, screening and interviewing have already happened, so the debrief should close the loop clearly.
Three sentences do it. Verdict, evidence, date. If you are running a hire and you want a second read on how your process looks from the candidate's side, here is how I work with hiring managers. The rest of the hiring sequence sits in the building products sales hiring guide.