After an interview, the hiring manager often shares an impression in a chat message, a quick call or a scattered email. The recruiter then has to interpret that impression before moving the candidate on. When feedback is unstructured, decisions become hard to compare across candidates, hard to hand over to a colleague and hard to defend later. Capturing hiring-manager interview feedback as a structured record in the Applicant Tracking System turns impressions into a shared, searchable outcome. This article describes how to set that up without turning every manager into a form-filler.
The need shows up in every segment. In recruitment agencies the feedback often comes from a client contact rather than an internal manager, yet the same structure helps. Staffing and secondment teams need a clear go or no-go after a client interview before they commit a candidate to an assignment. Executive search firms capture panel feedback per round so a mandate stays consistent. In-house recruitment teams keep hiring managers aligned when several people interview the same candidate. The fields below work across those contexts.
Agree what “structured” means before the interview
Structured feedback is not a novel. It is a small set of fields that every hiring manager answers the same way: a clear recommendation (advance, hold or reject), a short reason tied to the brief, scores on the competencies that were agreed for the role, and any risks or conditions for the next step. Keep the list short so managers finish it. Link the fields to the shared scorecard agreed before the conversation and to the structured vacancy brief, so feedback is judged against the same criteria that were used to select the candidate. Where a stage has written entry criteria, the feedback should say whether those criteria were met.
Request feedback in the record, not only in chat
Create the feedback request on the candidate and vacancy in the Applicant Tracking System as soon as the interview is booked or completed. Name the hiring manager, set a reply deadline on the feedback request and keep the named scheduling owner responsible for chasing it. Chat and email can still be used as a nudge, but the authoritative answer lives in the recruitment record. That way a colleague can see what was asked and what is still outstanding without searching inboxes.
Require a written outcome before the next stage
Do not move a candidate forward on a verbal “looked fine”. Make a completed feedback record a precondition for the next pipeline stage, just as you would for a written interview outcome before the next stage. If the manager is unsure, capture that as a hold with a reason and a next action date, not as silence. When several interviewers are involved, collect each view separately and then record a single decision with the actor who made it, in line with recording who moved the candidate.
Keep notes usable for the team
Free-text comments still matter, but they should support the structured fields rather than replace them. Ask for concrete observations against the brief, not personality labels. Follow the same discipline as candidate notes the team can rely on: short, factual and free of private chatter that does not belong in a shared file. Where a rejection follows, map the reason to your standard rejection reasons so later reporting stays consistent. If the candidate no-showed, handle that through the no-show process instead of filing empty feedback.
Use the feedback in reviews and handovers
Structured feedback pays off when it is reused. Bring unanswered requests and thin scorecards into the weekly pipeline review. Include aggregated interview outcomes in the monthly recruitment report for management without exposing personal comments. When a vacancy or candidate is handed over, the new owner should find the feedback history in the record rather than reconstructing it from chat, which is part of a clean handover between recruiters. Client-facing progress updates can summarise that interviews happened and what stage followed, without pasting internal scores into a client progress report.
A practical start
- Define five to seven feedback fields tied to the brief and scorecard
- Create every feedback request on the candidate and vacancy record with an owner and deadline
- Block the next stage until a written recommendation is recorded
- Capture each interviewer’s view separately, then one clear decision with the actor
- Keep free text short, factual and mapped to standard rejection reasons when needed
- Review outstanding feedback requests in the weekly pipeline meeting
From impressions to a shared decision
Structured hiring-manager interview feedback in an Applicant Tracking System replaces fragile chat threads with a record the whole team can use. With agreed fields, a deadline on every request, a written outcome before the next stage and reuse in reviews and handovers, decisions stay comparable and candidates move for clear reasons. Explore the product or book a demo — we will show how interview feedback, scorecards and stage rules work in BoldATS for your segment.