If you want interview feedback faster, stop asking hiring managers to write it from memory. Instead, give them a pre-drafted summary to approve within minutes of the interview. That single change fixes both problems at once, because feedback speed and feedback quality collapse together as memory decays. The manager who edits a draft in two minutes gives you better detail than the same manager writing an essay from a blank page three days later.
Everything below is about making that flip real: why feedback is slow, the structural fixes that help, the highest-leverage move, and copy-paste templates and examples you can use today.
Why is interview feedback always so slow?
It is rarely because the manager does not care. It is because the task, as usually framed, is genuinely unpleasant and easy to postpone.
Four things stack up.
The blank-page problem. "Send me your feedback" asks the manager to compose something from nothing. Writing from scratch is real cognitive work, and work with friction gets deferred.
Memory decay. Detail fades quickly after a conversation. The specific answer a candidate gave, the exact phrasing, the small hesitation, all of it blurs within hours. So the manager who waits until tomorrow is not just slower, they have less to work with. The task gets harder the longer it sits, which makes them avoid it more.
No deadline. "Whenever you get a chance" is not a deadline. Feedback with no due date loses every time to work that has one.
Low priority. Hiring is important but rarely urgent for the manager. Their calendar is full of things with owners and dates. Your feedback request has neither, so it sinks.
Notice that three of these four are structural, not personal. You can fix structure.
How do I fix the process so feedback comes in on time?
Three structural changes remove most of the delay. None of them require the manager to try harder.
Set a tight service level agreement (SLA). Make the rule explicit and shared: feedback is due before the candidate advances, ideally same day. When feedback becomes a gate rather than a favor, it moves up the priority list. "No feedback, no next step" is a rule everyone understands.
Use a structured scorecard, not a blank box. A blank comment field invites a one-line shrug. A short structured form tells the manager exactly what to fill in: recommendation, confidence, the specific competencies you are testing, and evidence for each. Structure does two jobs at once. It lowers the effort (fewer decisions about what to write) and it raises the quality (it forces specifics).
Tie the deadline to the next meeting, not to the calendar. "Feedback due before the debrief on Thursday" beats "feedback due within 48 hours" because it attaches your ask to something the manager already has to show up for. The deadline borrows urgency from an event that already exists.
These fixes help a lot. But they still leave the manager staring at a form. The biggest lever removes even that.
What is the single highest-leverage move?
Draft the feedback for the manager, so they edit and approve instead of composing from scratch.
This flips the default. Today the default is "recruiter chases, manager writes." The new default is "manager approves a draft." Approving is fast and low-friction. Writing is slow and high-friction. When you change what the manager is asked to do, you change how quickly they do it.
Here is the workflow. Right after the interview, you send a short first-pass summary built from what was actually discussed: the candidate's relevant experience, how they handled each competency, any concerns, and a suggested recommendation left open for the manager to set. The manager reads it, corrects what is wrong, sharpens what is vague, sets the recommendation, and hits send. Two minutes, done, while it is still fresh.
The draft also fixes the memory problem. Because it is grounded in the actual conversation rather than the manager's fading recollection, the details are still intact when they review it. They are confirming and correcting real content, not reconstructing a blur.
Where does the draft come from? If you take structured notes live, you can write it yourself. More often, this is where an AI meeting assistant earns its place. A tool like Numi records, transcribes, and summarizes the interview and surfaces the decisions and action items right after the call, so the first-pass draft is waiting before the manager has left the room. To be clear about what it does and does not do: it produces the summary and extracts action items and decisions. It does not score or rank candidates. The hiring judgment stays with your team. The tool just removes the blank page and the memory decay, which are the two things actually slowing you down. (It is EU-hosted and does not train on your data, so you can put real interviews through it.)
What nudge templates actually get a reply?
When you do need to chase, make the ask tiny and specific. A good nudge names a deadline, points at a form, and makes it clear the task is small. Here are copy-paste versions.
Same-day Slack nudge, sent right after the interview:
Hi [Manager], thanks for interviewing [Candidate] just now.
Draft feedback is in the scorecard here: [link]
Can you edit + confirm it before you switch tasks? Takes ~2 min while it's fresh.
We need it before the [Thursday debrief] to keep [Candidate] moving.
Gentle next-morning reminder:
Morning [Manager], quick one. [Candidate]'s feedback is the only thing
holding up their next step. The draft's already written, so it's just a
review + a recommendation (advance / reject / hold): [link]
2 minutes and we're unblocked. Thank you!
Deadline-is-today email:
Subject: 2-min review, [Candidate] feedback due today
Hi [Manager],
[Candidate]'s scorecard is pre-filled and waiting for your review: [link]
All I need from you:
1. Correct anything that's off
2. Set the recommendation
3. Hit submit
If it's not in by [4pm], [Candidate] slips to next week's batch, which we'd
rather avoid. Ping me if anything's unclear.
Thanks,
[Your name]
Escalation nudge when feedback is genuinely blocking a decision:
Hi [Manager], flagging that [Candidate] has now been waiting [X days] on
feedback and a competing offer is a risk. The draft is ready to approve
here: [link]. Can you get to it today? Happy to jump on a 5-min call and
capture it live if that's faster for you.
Keep the tone light and the ask small. You are not asking for an essay. You are asking for a review.
What does good feedback look like versus vague feedback?
The difference is evidence. Vague feedback gives you an adjective. Good feedback gives you what the candidate actually said or did, tied to the competency you care about. Here are three worked contrasts.
Example 1, technical competency.
Vague:
Strong technically. Knows their stuff. Advance.
Specific:
Recommendation: Advance. Confidence: High.
System design: Walked through their redesign of a payments retry queue.
Explained the idempotency-key approach and why they chose it over locking.
Concern: Lighter on observability; couldn't describe how they'd monitor it.
Worth probing in the next round.
The second one tells the next interviewer exactly where to push and gives you a decision you could defend if challenged.
Example 2, a rejection.
Vague:
Not a fit. Something felt off. Pass.
Specific:
Recommendation: Reject. Confidence: Medium.
Stakeholder management: Asked for an example of handling a disagreement with
a senior stakeholder. Answer stayed abstract ("communication is key"); no
concrete example even after a follow-up. This role needs someone who can
push back on the VP, so this is a real gap, not a nerves issue.
"Something felt off" cannot be acted on and cannot be defended. The specific version names the competency, the evidence, and why it matters for this role.
Example 3, a genuine maybe.
Vague:
On the fence. Could go either way.
Specific:
Recommendation: Hold. Confidence: Low.
Strong on [core skill]: gave a clear example of cutting onboarding time in
half at [prior company]. Open question: only two years in a lead role, and
this job carries a bigger team. Suggest the next round focus on
scaling-a-team examples before we decide.
A structured "hold" with a clear open question is useful. It tells the next interviewer what to resolve. A shrug does not.
Across all three, the specific version follows the same shape: recommendation, confidence, competency, evidence, open question. That is what your scorecard should ask for, and it is exactly what a good interview draft should pre-fill.
Putting it together
Getting feedback faster is not about nagging managers harder. It is about changing the task. Set a same-day SLA so feedback is a gate, not a favor. Replace the blank box with a structured scorecard that asks for evidence. And most of all, hand the manager a pre-drafted summary to approve instead of a blank page to fill, so the work becomes a two-minute review while the conversation is still fresh.
Do that, and the default flips from "recruiter chases" to "manager approves." Both your speed and your feedback quality go up together, because you stopped fighting memory decay and started working with it.