Stakeholder interview guide for exams, gradebooks, and report cards

1. Prepare the interview set

Interview teachers, department leads, assessment staff, administrators, records, leaders, learners, families, IT, support, procurement, finance, privacy, safeguarding, accessibility, security, and legal owners.

Share purpose, scope, time, confidentiality, decision boundary, and evidence standard. Avoid asking stakeholders to design a product before the current assessment work and constraints are understood.

2. Ask about the work

What triggers assessment setup, marking, moderation, reporting, or correction? Which record is used? What decision follows? Where do you wait, copy, reconcile, correct, escalate, or rely on memory?

Ask about missing submission, late work, absent learner, amended mark, moderation adjustment, resit, special consideration, withdrawal, transfer, duplicate, report correction, access failure, and outage. Request a dated example within scope.

3. Ask about meaning and evidence

How are assessment, component, attempt, submission, mark, grade, scale, weighting, rounding, boundary, missing, absent, late, exempt, pending, moderated, approved, published, and corrected defined?

The U.S. Department of Education data-quality guidance connects quality with definitions, rules, validation, infrastructure, and professional learning. Ask how errors are found, corrected, communicated, and prevented.

4. Ask about control and experience

Who can view, mark, moderate, approve, publish, export, correct, archive, and delete? How are leavers, substitutes, support users, suppliers, integrations, backup, restoration, retention, accessibility, privacy, safeguarding, records, and security handled?

Ask what a good marking cycle looks like, what a disputed result looks like, how much work is duplicated, which report is trusted, and what support is needed during assessment or reporting deadlines.

5. Reconcile the interviews

Separate observed facts, repeated patterns, individual preferences, policy constraints, supplier claims, and unresolved assumptions. Keep speaker role, date, record, evidence, and limitation with each note.

Do not average away an assessment-integrity, privacy, safeguarding, accessibility, or records concern because another role has not seen it. Define the smallest test that can resolve uncertainty.

6. Turn insight into requirements

Convert validated needs into scenarios, acceptance tests, definitions, calculations, permissions, support routes, data-quality rules, training tasks, implementation owners, and review measures.

The U.S. Department of Education governance checklist covers quality, access, security, lifecycle, sharing, disposal, and monitoring. Apply qualified local review before turning an interview statement into policy.

7. Close the loop

Send a concise summary for correction, state what changed, record what remains disputed, and name decision owner and date. An interview is not complete until participants recognise the work they described.

Review the resulting decision at 30, 60, and 90 days using completeness, corrections, moderation, report confidence, staff effort, support demand, access exceptions, and outcome evidence.

Turn the guidance into an assessment decision

Apply this guidance to one bounded part of stakeholder interview guide for school exam and gradebook software. Define the assessment or reporting decision, authoritative record, accountable owner, permitted users, correction route, evidence, and review date.

Test an ordinary assessment and meaningful exceptions such as a missing submission, late work, absent learner, moderation change, amended result, withdrawn learner, duplicate mark, grading-period change, report correction, access failure, or outage.

Keep supplier capability, school responsibility, professional judgement, local policy, legal advice, and measured outcome separate. If evidence is incomplete, narrow the claim and pilot the smallest safe change.

Review at 30, 60, and 90 days. Check completeness, timeliness, consistency, moderation, corrections, access exceptions, staff effort, support demand, reporting confidence, and the original outcome. Decide whether to expand, repair, consolidate, narrow, or hold.

Before approval, ask a reviewer who was not involved in the design to challenge the strongest assumption. Replace broad language with the exact evidence, population, date, and limitation the school can verify.

Document what was tested and what was not. A successful demonstration with a simple gradebook does not establish readiness for moderation, resits, special consideration, changed grading periods, multiple campuses, or a changed assessment policy.

Keep evidence beside the decision record so a later reviewer can distinguish observed behaviour from an assumption, estimate, or supplier statement. Name the next test where evidence remains incomplete.

Revisit the boundary when the school adds a subject, year group, campus, grading scale, role, integration, reporting period, or policy. A small change can alter permissions, definitions, calculation, timing, retention, or support demand.

Set the next review date and owner. A dependable exams and gradebook operation is maintained through clear definitions, controlled change, professional judgement, and visible accountability rather than a one-time setup.

Make the handoff readable to a teacher, administrator, leader, learner, and reviewer. State what passed, what remains manual, which records are authoritative, who owns unresolved conflicts, and how a correction is communicated without creating an uncontrolled copy.

Keep approved definitions beside calculation rules, moderation notes, training, support routes, and change history. New subjects, scales, integrations, or reporting windows can change the risk even when field names stay the same.