PlaysbyMoat8
Back to the library
The workflow guideHR

Review the quality of interview notes

Help interviewers write specific feedback by comparing their notes with the role rubric and strong examples.

5 implementation stepsSimple

How this works

Help interviewers write specific feedback by comparing their notes with the role rubric and strong examples. Use this to improve how interviewers document evidence, not to evaluate the candidate again. The useful result is specific coaching on vague, unsupported or incomplete notes against the agreed rubric.

Compare the written scorecard with documentation standards and examples of strong evidence. Identify missing behavioral detail, unsupported ratings and contradictions while preserving the interviewer's original text. Ask for clarification instead of inventing what the candidate said.

Before you start

Role rubric

Obtain competencies and the expected evidence for this interview stage.

Documentation standards

Define what counts as a specific observation, supported rating and unresolved gap.

Reviewed examples

Use anonymized strong and weak notes to illustrate quality, not candidate suitability.

Prepare the inputs

scorecard
Required

criterion, rating, notes and interviewer

Preserve the original version before proposing edits.

rubric
Required

job-related criteria and rating definitions

Do not substitute a generic personality assessment.

evidence_policy
Required

documentation quality rules

Separate note quality from hiring recommendations.

optional_transcript
Required

permitted timestamped interview text

Use only to verify quoted evidence, not infer protected traits.

Implementation, step by step

  1. Map notes to criteria

    • Associate each note and rating with the relevant rubric item.
    • Identify blank fields and comments unrelated to the role.

    Checkpoint: A completeness map exists.

  2. Inspect evidence quality

    • Find claims lacking examples, outcomes or observable behavior.
    • Distinguish an absent note from evidence that the candidate lacks a skill.

    Checkpoint: The review lists specific documentation gaps.

  3. Check rating support

    • Compare each rating with the rubric definition and written evidence.
    • Flag contradictions and unsupported certainty without assigning a replacement hiring score.

    Checkpoint: Each concern references the original text.

  4. Draft coaching feedback

    • Suggest a precise clarification question or evidence-based rewrite structure.
    • Do not fabricate details to make a weak note sound complete.

    Checkpoint: The interviewer receives actionable edits.

  5. Prepare the corrected record

    • Let the interviewer confirm facts and revise the scorecard.
    • Retain the original and corrections so quality review cannot silently alter interview evidence.

    Checkpoint: The final notes have an accountable author.

Decisions along the way

Note says only 'strong candidate'

Ask which observed behavior supports which rubric criterion.

Rating is high but evidence is mixed

Flag the mismatch and request the interviewer's explanation.

Transcript contradicts a note

Present the timestamped discrepancy for correction without deciding candidate suitability.

What you will produce

scorecard-quality-review.md

Markdown

Coaching on documentation quality only.

Include: criterion · issue · evidence · clarification · suggested_structure

scorecard-corrections.csv

CSV

A record of interviewer-confirmed changes.

Include: field · original · proposed · confirmed_by · status

Check the result

  • Ensure feedback targets note quality rather than candidate selection.
  • Verify all quoted interview evidence against the permitted source.
  • Check that missing evidence is not described as a negative finding.
  • Confirm no invented examples enter the revised scorecard.

When something goes wrong

Rubric unavailable

Review basic clarity only and mark rating support unassessed.

Notes contain sensitive irrelevant details

Exclude them from coaching artifacts and ask the owner to handle the record appropriately.

Interviewer cannot recall evidence

Leave the criterion insufficiently documented rather than reconstructing an answer.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Synthetic: review a collaboration scorecard.

Inputs

Rubric asks for a concrete example of resolving disagreement. Note says 'Good communicator, 5/5' with no example; another field records 'did not discuss conflict.'

Expected result

Synthetic result: flag unsupported rating and conflicting coverage. Ask the interviewer whether a relevant example was discussed; do not invent a conflict-resolution story or lower the candidate's score automatically.

Run a small pilot

Start small

Review anonymized scorecards from one interview stage.

Record the baseline

Record reviewer time and the share of notes requiring factual clarification.

Agree success criteria

Agree documentation completeness and coaching usefulness criteria with recruiters.

Stop or revise

Stop if the review begins producing selection or rejection recommendations.

Keep the scope clear

  • Documentation quality is not a proxy for candidate ability.
  • Hiring decisions remain with qualified reviewers using job-related evidence.

Check before using

Make sure the review assesses documentation quality; a person makes the hiring decision.

Business activities

  • Hire and assess candidates

Editorially adapted workflow; not independently tested.

FROM A RECIPE TO YOUR WORKFLOW

Bring the company context together.

This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.

For this recipe: Interview rubric · Feedback examples · Interviewer notes

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗