PlaysbyMoat8
Back to the library
The workflow guideHR

Draft a structured interview scorecard

Organize interview evidence against job-specific criteria so a hiring team can review a consistent draft assessment.

5 implementation stepsIntermediate

How this works

Organize interview evidence against job-specific criteria so a hiring team can review a consistent draft assessment. Use this after an interview to organize what was actually observed against the agreed role criteria. The draft should make missing evidence easy to see and leave evaluation and selection with the interviewer and hiring team.

Map timestamped statements and examples to the role-specific rubric, draft concise explanations and flag contradictions. If ratings are requested, use only the supplied definitions and retain a human-confirmation state. Do not infer personality, protected traits or ability from absent notes.

Before you start

Role scorecard

Obtain the criteria and any approved rating definitions.

Permitted interview evidence

Use the transcript or notes for this interview stage.

Interviewer review

Identify who confirms the evidence and final assessment.

Prepare the inputs

interview_record
Required

speaker-labeled notes with references

Mark uncertain transcription and incomplete sections.

role_criteria
Required

job-related definitions and expected evidence

Exclude criteria not approved for the role.

rating_scale
Required

optional explicit anchors

Do not invent numerical scores when no scale exists.

stage_scope
Required

competencies covered and deferred

Separate unasked topics from insufficient answers.

Implementation, step by step

  1. Prepare the evidence map

    • Read the full record and attach relevant excerpts to each criterion.
    • Keep interviewer comments separate from candidate statements.

    Checkpoint: The scorecard has traceable evidence.

  2. Check coverage

    • Identify criteria with examples, partial evidence or no discussion.
    • Preserve contradictions and uncertain attribution.

    Checkpoint: Gaps are explicit.

  3. Draft explanations

    • Write concise factual summaries explaining how evidence relates to the criterion.
    • Avoid unsupported adjectives and invented outcomes.

    Checkpoint: Each criterion has a reviewable rationale.

  4. Apply supplied anchors

    • If ratings are requested, propose them only against the approved definitions.
    • Mark ambiguous cases for the interviewer rather than forcing a score.

    Checkpoint: Ratings remain provisional.

  5. Review and finalize

    • Ask the interviewer to correct facts and confirm the assessment.
    • Retain the draft and approved versions separately.

    Checkpoint: The hiring team receives an accountable record.

Decisions along the way

No evidence for a criterion

Mark not assessed or insufficient evidence according to the rubric.

Team achievement lacks personal contribution

State the reported team result and ask for clarification.

Evidence supports several anchors

Explain the ambiguity and leave the decision to the interviewer.

What you will produce

interview-scorecard-draft.md

Markdown

A consistent draft for interviewer review.

Include: criterion · evidence · rationale · provisional_rating · gap

scorecard-review-log.csv

CSV

A record of human-confirmed changes.

Include: criterion · correction · confirmed_by · status

Check the result

  • Verify every factual statement against the interview record.
  • Check rating anchors match the supplied rubric.
  • Confirm missing evidence is not automatically scored negatively.
  • Remove irrelevant personal details and protected-trait inferences.

When something goes wrong

Transcript attribution is uncertain

Verify the segment before using it as evidence.

Rubric changes after the interview

Flag unassessed criteria rather than retrofit evidence.

Draft overstates an outcome

Return to the exact statement and qualify it.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Synthetic: draft a planning scorecard.

Inputs

Rubric asks for prioritizing competing deadlines. Candidate describes delaying one task after consulting two teams but does not state the outcome.

Expected result

Synthetic result: summarize the prioritization action and mark outcome evidence missing. Do not write 'successfully delivered every project' or issue a hiring recommendation.

Run a small pilot

Start small

Draft scorecards for one stage with interviewer confirmation.

Record the baseline

Record preparation time and factual corrections.

Agree success criteria

Agree evidence accuracy and rubric consistency before broader use.

Stop or revise

Stop automated drafting if it becomes an unreviewed selection decision.

Keep the scope clear

  • The scorecard supports qualified hiring review rather than selecting candidates.
  • Use only job-related evidence within the authorized recruiting process.

Check before using

Check evidence and bias; the hiring team remains responsible for decisions.

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 transcript · Role requirements · Candidate-provided experience · Defined scoring rubric

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 ↗