How to set up ATS interview scorecards and feedback workflows

ATS interview scorecards should not be treated as standalone forms. They work when they are part of a repeatable feedback workflow that tells interviewers what to assess, when to submit feedback, who can see it, and how the hiring team will use it.

That matters whether you are a founder hiring your first team lead, an HR lead standardising interviews, or a recruiter trying to keep a busy panel on schedule. A tidy scorecard means little if every interviewer uses a different scale or submits notes three days after the debrief.

This guide uses Greenhouse, Ashby and Breezy HR as practical examples. Greenhouse shows the most structured approach, Ashby shows the configurable scaling-team model, and Breezy HR shows the simpler small-business route with an important plan-gating catch.

What are ATS interview scorecards?

ATS interview scorecards are structured evaluation forms used to assess candidates against agreed job criteria. They usually sit inside an interview stage, candidate profile or feedback form, rather than in a separate document.

A useful scorecard captures the evidence that matters: skills, traits, qualifications, attributes, ratings, notes and a hiring recommendation. The limit is that a scorecard cannot fix vague criteria; it only records them more neatly.

Greenhouse is the clearest structured-hiring example. Its scorecards are designed around predetermined criteria, and teams can add skills, traits, qualifications, attributes and focus attributes for specific interviews.

That structure is useful if several interviewers are involved, because each person can assess a defined area. The trade-off is setup effort: Greenhouse rewards teams that are willing to define roles, stages and interview kits properly before hiring begins.

Why do scorecards fail without a feedback workflow?

Scorecards fail when nobody owns the workflow around them. The common failure is a good-looking form that is optional, inconsistently used, or filled in after the decision has already been made.

A proper workflow covers required completion, interviewer instructions, rating labels, reusable templates, visibility controls, reminders, score comparisons and reporting. Each piece removes one common source of messy feedback, but each also adds admin overhead.

The goal is comparable evidence, not faster form completion. If interviewers cannot explain why they chose a rating, the rating is just a tidier version of instinct.

Buyers should therefore look beyond whether an ATS has scorecards. Ask whether it can make feedback timely, private until submitted, tied to a stage, reusable across jobs and visible in reporting without creating a manual spreadsheet afterwards.

How should you define hiring criteria before building a scorecard?

Start with the job, not the form. Define the must-have skills, role-specific competencies, qualifications, values and knockout criteria before opening the ATS settings page.

Separate observable evidence from vague impressions. “Can debug a production incident using logs and metrics” is useful; “strong problem-solver” is too broad unless the interviewer knows what proof to collect.

Do not ask every interviewer to assess everything. A recruiter screen might cover motivation, compensation range and logistics, while a technical interview assesses job skills and a final interview covers leadership or values.

This focus keeps interviews shorter and feedback cleaner. The downside is that it requires discipline: if the hiring manager keeps adding pet questions, the scorecard becomes a dumping ground.

How do you map scorecards to interview stages?

Map each criterion to the stage where it can be assessed properly. A recruiter screen can test motivation and logistics, a hiring-manager screen can test role fit, a technical interview can test job skills, a panel can test collaboration, and a final interview can test leadership or values.

This mapping reduces duplicate questions and makes feedback easier to compare. It also exposes gaps, such as a values criterion that nobody is actually assessing.

Ashby is a useful example for scaling teams. Its interview plans determine candidate stages, are created in admin, are assigned to jobs, and all jobs require an interview plan.

Ashby also recommends grouped interview plans when teams use multiple interview plans and want cleaner reporting across similar stages. That is valuable at scale, but it means the admin model needs to be kept tidy as hiring expands.

Stage names matter more than teams expect. If one job uses “Technical Screen”, another uses “Tech Interview” and a third uses “Skills Call”, reporting becomes harder before any data reaches the dashboard.

Which rating scale should you use?

Use the simplest rating scale your team can apply consistently. More options do not automatically create better signal, especially when interviewers are busy or poorly calibrated.

Greenhouse uses a five-point scorecard scale: Definitely Not, No, Mixed or Neutral, Yes, and Strong Yes. That gives useful nuance, but only if interviewers understand the difference between neighbouring ratings.

Breezy HR uses a simpler thumbs-up or thumbs-down model with written notes. That is easier for small teams to adopt, but it gives less gradation for borderline candidates.

Ashby is more configurable. Its feedback forms can include sections, required fields, private fields and multiple field types, including short answer, long formatted answer, multiple choice, checkboxes, yes/no, numbers, scores, currency and dates.

Configurable fields are useful if different roles need different evidence. The catch is that too much customisation can make reporting noisy, especially if each hiring manager builds their own scale.

Whatever scale you choose, add written evidence fields. A “Yes” without notes is weak evidence, while a short explanation tied to the interview question is far easier to defend in a debrief.

How do you attach scorecards to interview kits, stages or feedback forms?

Attach the scorecard to the place where the interviewer already works. If the form sits somewhere separate, completion drops and feedback arrives late.

In Greenhouse, interview kits include interview instructions, interview questions, the candidate resume and a scorecard. This is strong governance because the interviewer sees the brief and the scorecard together, but it depends on hiring teams keeping interview kits current.

In Ashby, interviews are templates that include interviewer briefing or instructions and assign the feedback form used after the interview. Feedback forms are reusable questionnaires for interviewer ratings and scores, which helps when several jobs share similar stages.

In Breezy HR, scorecards can be associated with positions or pipeline stages. That is simpler to configure than a heavier enterprise workflow, but custom scorecards are only available on Growth, Business and Pro plans.

A practical setup checklist is short. Create the template, assign it to the stage, assign the interviewer, mark required fields, check the candidate profile view, and run a test candidate through the workflow before the first real interview.

Do this before the role goes live. Editing forms mid-process is risky, and Breezy HR specifically warns that changing scorecard settings can remove existing feedback in custom sections.

How do you make feedback timely, private and comparable?

Require feedback before the debrief or before the candidate advances, where your ATS supports that workflow. Late feedback is usually less specific and more likely to be influenced by the group discussion.

Interviewers should submit their own feedback before seeing other interviewers’ scorecards. Greenhouse can prevent interviewers from seeing other interviewers’ scorecards before submitting their own feedback, which helps reduce groupthink.

That control is useful, but it is not a bias cure. It gives each interviewer a cleaner starting point, while the hiring team still needs calibration and a fair debrief process.

Asynchronous feedback also matters. Greenhouse can assign a scorecard without scheduling an interview, and Ashby supports submitting feedback without a scheduled interview and requesting feedback without scheduling.

This is useful for resume reviews, take-home tasks and hiring-manager assessments. The limitation is accountability: if feedback is requested outside a scheduled event, someone still needs to chase completion.

Greenhouse vs Ashby vs Breezy HR: which setup fits which team?

Greenhouse is the strongest example if your priority is structured scorecard governance. Scorecards are required by default for jobs, although admins can make them optional at the interview-plan level.

Greenhouse also supports focus attributes, five-point ratings, interview kits, visibility controls and AI-generated notes mapped to scorecard questions through Greenhouse Notetaker. The trade-off is cost and implementation weight; ATSLab records Greenhouse from roughly $6k, and the public pricing page says pricing is customised.

Ashby is the better example if your hiring workflow is changing quickly and reporting needs to keep up. Reusable feedback forms, private fields, required fields, many field types and grouped interview plans give scaling teams more control.

That flexibility suits teams hiring at volume, but it can become a slog if nobody owns the system design. Ashby All-In-One Foundations is publicly listed at $400 per month for companies up to 100 employees, with Plus and Enterprise listed on the public pricing page rather than at fixed public prices.

Breezy HR is the simpler small-business option if you want scorecards, written notes, overall candidate scores and side-by-side comparisons without a heavy implementation. It is ATSLab’s top-ranked tool overall, with a recorded price of $157 for its Startup plan.

The catch is important: Breezy HR custom scorecards are available on Growth, Business and Pro, not Bootstrap or Startup. If custom scorecards are central to your process, do not assume the $157 Startup plan is enough.

How much do ATS scorecard workflows cost?

Scorecard cost is usually a plan question, not a separate line item. The risk is buying an ATS because the demo showed scorecards, then finding the plan you chose does not include the controls you need.

Greenhouse lists Core, Plus and Pro plans, and says pricing is customised based on plan, hiring volume, organisational complexity and required capabilities. Its pricing page lists structured interview kits and scorecards under Core, but does not publish a self-serve dollar price.

Ashby lists All-In-One Foundations, All-In-One Plus, All-In-One Enterprise and Ashby Analytics for your existing ATS. Foundations is publicly listed at $400 per month for companies up to 100 employees, with a 10% annual-commitment discount available.

Breezy HR lists Bootstrap, Startup, Growth, Business and Pro. Startup is listed at $157 per month on annual billing and $189 per month on monthly billing, but custom scorecards require Growth or higher.

Usage-billed items can change the maths. Ashby pricing includes candidate texting limits and lists additional SMS at $90 per 1,000 messages, while Breezy Intelligence credits start at $30 per 100,000 credits.

Ask the vendor to quote the exact plan and add-ons needed for your scorecard workflow. A lower headline price is less useful if required fields, AI notes, texting, sourcing or custom scorecards sit elsewhere.

What is changing in 2026 with AI notes and interview workflows?

AI is moving into interview workflows, but buyers should treat it as a governed feature rather than a shortcut. The useful question is whether AI output maps back to the scorecard criteria your team already agreed.

Greenhouse Notetaker is listed as available on Core, Plus and Pro, and maps AI-generated notes to scorecard questions. That can save interviewer admin time, but teams still need consent rules, data access controls and review habits.

Ashby announced AI Interviewer in May 2026 after acquiring Talent Llama’s team and assets in 2025. That signals where the category is going, but availability, fit and policy approval still need checking before purchase.

Breezy Intelligence credits power tools including Applicant Insights, Resume Audit, Activity Summary, Candidate Sourcing and Help Me Write. Breezy also advertises a 14-day full-feature trial with no credit card required and 100,000 Breezy Intelligence credits included.

Before buying around AI, ask about candidate consent, recording policy, data retention, human review, admin permissions and usage costs. AI notes can improve coverage, but they should not replace interviewer judgement or a clear hiring rubric.

What should buyers check before committing to an ATS?

Ask whether structured scorecards are included in the plan being quoted. Then ask whether they can be required before advancement, debrief or offer approval.

Check whether interviewers can be blocked from seeing other people’s feedback until they submit their own. If the ATS cannot do that, set a team rule and decide who enforces it.

Ask whether templates can be reused across jobs, and whether rating scales, sections, required fields and private fields can be customised. More control is useful, but it needs one owner to prevent template sprawl.

Ask whether feedback can be submitted without a scheduled interview. This matters for resume reviews, take-home assessments, async hiring-manager feedback and agency-style candidate reviews.

Ask what happens when a live scorecard is edited after feedback has been submitted. If the answer is vague, test it in a trial or sandbox before using the workflow on a real role.

Finally, ask what reporting is available on feedback completion, average scores and stage outcomes. Good reporting depends on clean stage names, consistent scorecards and clear rating labels, not just a dashboard.