Aggregating Interview Feedback and Scorecards
Interviewers agree to give feedback and then don't, or submit it days later once the specifics of the conversation have blurred into every other interview they did that week — and a hiring decision meeting held without complete scorecards means the group is deciding on partial information or delaying the meeting entirely while a recruiter chases down the one interviewer who hasn't submitted. Even when feedback comes in on time, a simple averaged score can hide a real split — one strong advocate and one strong objector averaging out to a flat 'maybe' that looks like consensus when it's actually significant disagreement worth surfacing before a decision.
STARTING PRICE
From €299
Standard tier · Multi-step workflow with AI extraction/decisioning and 2-3 integrations.
Get a quote →Saves roughly 3-5 hrs/week for a recruiter coordinating multiple concurrent hiring loops.
How the automation works
We remind interviewers to submit structured scorecards immediately after their interview slot ends, while the conversation is still fresh, rather than waiting for a end-of-week batch reminder. Scorecards use a consistent structure per competency so responses are genuinely comparable across interviewers, and submissions get checked for a real assessment versus a rubber-stamp rating with no supporting notes. Aggregation surfaces the actual distribution of scores and specific points of disagreement between panelists, not just an averaged number, so the hiring manager walks into the decision meeting seeing where the panel genuinely agrees and where it doesn't — and a complete scorecard set, or an explicit list of who's still missing, is ready before the meeting starts instead of during it.
Process flow
- 01
Interview slot ends trigger
Completion of a scheduled interview slot triggers an immediate feedback request to that interviewer, rather than a batched end-of-day or end-of-week reminder.
- 02
Prompt structured, competency-based scorecard ai
Interviewers submit feedback against the role's specific competency structure, keeping responses comparable across the panel instead of free-text notes.
- 03
Escalate unsubmitted feedback output
Feedback not submitted within a short window triggers a direct reminder, escalating to the recruiter if it's still outstanding close to the decision meeting.
- 04
Flag rubber-stamp submissions ai
A scorecard with a rating but no supporting notes, or a rating inconsistent with the notes given, is flagged for the recruiter to follow up before the decision meeting.
- 05
Aggregate showing real disagreement ai
Scores are compiled to show the actual distribution and specific points of disagreement between panelists, not collapsed into a single averaged number that can hide a real split.
- 06
Deliver pre-meeting summary output
A complete summary, or an explicit list of who's still missing, is ready ahead of the decision meeting rather than assembled live during it.
Inputs
- Interview panel and slot completion data
- Role-specific competency scorecard structure
- Interviewer submission history and timeliness
- Decision meeting schedule
Outputs
- Structured, competency-based scorecards per interviewer
- Aggregated scores showing distribution and disagreement
- Rubber-stamp submission flags
- Pre-meeting feedback completeness summary
Works with
Prefer a fully custom build instead of an off-the-shelf integration? We scope both options during your free consultation — most jobs like this one work fine on standard connectors, but higher-volume or non-standard systems sometimes need bespoke API work, reflected in the complex tier.
Where this goes wrong if you get it wrong
- Averaging panel scores into a single number can hide meaningful disagreement — a strong advocate and a strong objector averaging to a flat 'maybe' looks like mild consensus but is actually a split worth surfacing explicitly, and the aggregation needs to show distribution, not just a mean.
- A scorecard submitted with a numeric rating but no supporting notes gives the hiring manager nothing to evaluate the reasoning behind, and treating it the same as a fully justified rating in aggregation gives it undue weight — thin submissions need to be flagged distinctly, not silently averaged in alongside well-supported ones.
- Chasing feedback too late, after several days have passed, produces recall-degraded scorecards where interviewers reconstruct a generic impression rather than recalling specifics from that particular conversation — the request needs to go out immediately after the interview slot, not batched for end-of-week convenience.
- Feedback language that veers into subjective 'culture fit' commentary disconnected from the role's actual competencies creates legal exposure if a rejected candidate challenges the decision — the structured scorecard format needs to keep feedback anchored to defined, job-relevant competencies rather than open-ended impression notes.
Frequently asked questions
How does this handle a panel where interviewers strongly disagree?
Aggregation surfaces the actual score distribution and specific disagreement points between panelists rather than an averaged number, so the hiring manager sees where the panel is split before the decision meeting, not after.
What happens if an interviewer just gives a rating with no explanation?
Submissions with a rating but no supporting notes are flagged distinctly from well-supported feedback, prompting a follow-up rather than being averaged in with equal weight.
How quickly are interviewers reminded to submit feedback?
Reminders go out immediately after the interview slot ends, while the conversation is still fresh, rather than a generic end-of-week batch reminder that arrives after recall has degraded.
Does this keep feedback focused on job-relevant competencies?
The scorecard structure is built around the role's defined competencies, which keeps submissions anchored to job-relevant criteria rather than open-ended subjective impressions.