Structured Feedback Forms That Beat Freeform Notes
On this page
You finish a full interview loop — four interviewers, one candidate. The notes come back: "Great communicator," "seemed a bit nervous," "solid on the technical side I think," and "I liked her a lot." Four people, eight hours of interview time, and you have nothing you can compare. You can't tell whether all four were evaluating the same things, let alone how she stacks up against the next candidate in the pipeline.
Freeform notes aren't a knowledge problem. They're a structure problem. Feedback forms fix it.
TL;DR: Structured post-interview feedback forms with role-scoped fields replace unreliable freeform notes with comparable, field-by-field evaluations. Every tier of Intervy includes them — no upgrade required. Define your fields once, assign them per pipeline phase, and every interviewer fills in the same form.
Why Freeform Notes Fail at Scale
Ask three interviewers to write "their thoughts" on a candidate and you'll get three different documents shaped by three different mental models. One person writes bullet points. Another writes a paragraph. A third sends a single sentence from their phone.
The real problem isn't format — it's that freeform notes aren't comparable. When you try to make a hiring decision across a four-person panel, you're forced to reconcile summaries that were never designed to be reconciled. You end up relying on whoever wrote the most, or whoever spoke loudest in the debrief.
Here's what that costs you:
- Inconsistency across interviewers. "Strong communicator" means something different to every person who writes it.
- Bias amplification. Interviewers who liked a candidate write more, which gives their impression more weight in the debrief.
- No audit trail. Freeform notes can be revised or forgotten. There's no record of what was actually evaluated.
- Zero comparability across candidates. When two finalists both got "great energy" and "solid experience," you have nothing to distinguish them.
The core issue: Freeform notes capture impressions. Structured feedback forms capture evaluations. Only one of those is decision-ready.
A structured interview tool doesn't constrain interviewers — it gives everyone the same lens so you can actually compare what they see.
What Structured Feedback Forms Actually Look Like
A structured post-interview evaluation form is a set of fields defined once and filled in consistently by every interviewer. The fields map to what actually matters for the role, not whatever the interviewer happened to think about.
Intervy's feedback form data model supports four field types — rating, text, select, and multi-select — each suited to a different kind of evaluation signal:
In practice, these translate to:
- Rating fields. Numeric scores with configurable max and optional per-value labels — ideal for competency assessments like "Problem Solving (1–5)."
- Select fields. Single-choice dropdowns with custom options and optional color coding — useful for hire/no-hire recommendations or experience tier classification.
- Multi-select fields. Multiple-choice variants of select — good for tagging observed behaviors or flagging multiple concern areas at once.
- Text fields. Open-ended, with an optional markdown mode — for qualitative elaboration that supplements the structured fields, not replaces them.
Fields marked as recommendation or concerns surface directly in the candidate review summary, so hiring managers can see the signal without reading every response in full.
Design principle: Structured forms don't eliminate qualitative feedback — they give it a place. A text field for "What stood out?" still captures nuance, but every interviewer answers the same question in the same context.
Role-Scoped Fields — The Key to Comparable Evaluations
The failure mode of many feedback templates is building one generic form and using it for every role. A backend engineer interview and a customer success manager interview should not use the same evaluation criteria.
Intervy handles this through a clone-and-publish model. You create a base form, publish it as the org-wide default, then clone it per role and add the fields specific to that function. The clone carries all the base fields forward and lets you add, reorder, or remove fields without touching the original.
Forms go through a draft-then-published lifecycle. Published forms are immutable — if you need to update a form, you create a new version rather than editing in place. When a new version is published, any pipeline phase using the old version is automatically migrated, so nothing falls through the cracks mid-pipeline.
This version history matters for another reason: it makes your hiring process auditable. You always know exactly which version of which form an interviewer filled in for any given interview.
Here's how a typical role-scoped setup looks:
- Org default form — shared fields that apply to every role: overall recommendation, key concerns, communication assessment
- Engineering variant — adds system design depth, code quality rating, and a "would you work with this person?" select
- Customer success variant — adds empathy rating, product knowledge select, and a multi-select for flagged concerns like "unclear on pricing" or "struggled with scenario"
Each phase in a job pipeline can reference a different published form, so an initial phone screen uses a lightweight version while a final panel uses the full role-specific one.
Practical tip: Set one form as the org default so new pipelines always start with something reasonable. Override at the phase level only when the role genuinely needs different criteria.
Draft, Validate, Submit — How the Data Stays Clean
A feedback form is only as useful as the data in it. Intervy's submission model has two layers that protect data quality.
Incremental draft saving. Interviewers can save responses as a draft while filling in the form. If they get interrupted or want to revisit a field, their progress is preserved. Drafts can be updated any number of times — but once submitted, the feedback is locked. There's no way to revise a submitted form after the fact.
Field validation on submit. Every response is validated against the live form before being saved, so stale or injected fields are rejected. This means you can trust that every submitted response maps to a real field in the form the interviewer was assigned.
These two properties together — draft persistence plus strict validation — mean the feedback you read in the debrief is what the interviewer actually filled in on the form they were given. No gaps, no phantom fields, no retroactive edits.
Why this matters: The integrity of structured evaluation depends on the data being trustworthy. An interview scoring tool that lets users edit or backfill after the debrief has started defeats the purpose of structured forms.
Feedback Forms vs Scorecards — Know the Difference
Intervy has two distinct post-interview evaluation tools and it's worth being clear on what each one does.
Feedback forms are available on every tier — there's no feature gate or paywall. You can build, publish, and assign custom role-scoped feedback forms from day one.
Scorecards are a Growth and Scale feature. Scorecards aggregate competency ratings from an interview into a per-candidate summary view, pulling together scores across all interviewers in a structured hiring panel. They're the analytics layer on top of feedback.
The distinction matters when you're deciding what to build first. If you want structured, comparable post-interview evaluations right now — feedback forms are the tool, and they're available immediately. Scorecards are what you layer on when you're ready to aggregate across a panel and see candidate comparisons at a glance.
For a deeper look at how rating scales and per-competency scoring fit together, see How to Score Candidates Fairly.
Getting Started With Feedback Forms
You don't need to overhaul your hiring process to get value from structured feedback forms. Start with one role and one form.
Pick your highest-volume role. List the three to five things that actually predict success in it — not the job description bullets, the things you've seen separate good hires from bad ones. Build a form with one field per criterion: a rating field for each competency, a select for the hire recommendation, and a text field for anything that doesn't fit a structured field.
Publish it. Assign it to the interview phase where you currently get the most signal. Run it for two hiring cycles.
After two cycles, you'll have something you've never had before: structured, field-by-field evaluations from every interviewer on every candidate, filled in on the same form, in the same format, against the same criteria. Your debrief meetings will get shorter. Your hiring decisions will get sharper.
See how structured interview evaluation works in Intervy — or explore the structured technical interviews guide for the question side of the same process.