Vendor evaluation guide to exams, gradebooks, and report cards

1. Prepare a fair evaluation

Define subjects, cohorts, campuses, grading periods, assessment types, users, reports, integrations, current problems, desired outcomes, constraints, and decision owner before inviting demonstrations.

Publish scenarios, hard gates, weighted criteria, evidence standard, conflict-of-interest process, acceptance test, review date, and what the school will not infer from a demonstration.

2. Test the assessment workflow

Require assessment creation, component and attempt setup, scale, rubric, mark entry, feedback, missing submission, late work, absent learner, moderation, approval, publication, report, correction, resit, special consideration, withdrawal, and transfer.

Record expected result, observed result, manual work, role, permission, calculation, history, evidence, limitation, support route, response time, and report effect. Ask the same questions of every vendor.

3. Verify calculations and history

Test weighting, rounding, boundaries, missing values, duplicate entries, amended marks, moderated results, grading-period changes, report version, and finalisation. Require the vendor to explain each output in plain language.

The U.S. Department of Education data-quality guidance connects dependable information with definitions, rules, validation, infrastructure, and professional learning. Ask how the school owns and changes calculation definitions after implementation.

4. Verify access and experience

Check view, create, mark, review, moderate, approve, publish, export, correct, archive, and delete by role, subject, cohort, campus, learner, family, supplier, and support user.

Test accessibility, device, connectivity, identity recovery, readable status and scale labels, errors, alternative formats, language, family or learner access, and support during assessment and reporting windows.

5. Verify reporting and integrations

Check report source, population, period, refresh, calculation, missing values, correction, version, finalisation, export, communication, accessibility, and reconciliation to authoritative gradebook records.

For integrations, test identity, subject, cohort, assessment, component, mark, grade, status, event time, effective time, retry, duplicate, rejection, conflict, replay, failure, audit, and ownership.

6. Verify governance and support

The U.S. Department of Education data governance checklist covers quality, access, security, lifecycle, sharing, disposal, and monitoring. Ask about permissions, supplier access, backup, restoration, retention, disposal, incidents, audit, support, and data return.

GOV.UK guidance emphasises accountable handling of school data. Apply qualified local privacy, safeguarding, security, records, accessibility, assessment, and legal review; a vendor answer is evidence to assess, not automatic approval.

7. Verify delivery and total cost

Include assessment design, data cleanup, migration, calculation setup, configuration, integration, testing, moderation, training, support, reports, storage, security, privacy, accessibility, upgrades, internal time, incidents, renewal, and exit.

Ask who maintains scales, assessments, components, calculations, permissions, reports, integrations, documentation, backups, retention, corrections, support, and family or learner communications after launch.

8. Make and review the recommendation

Publish gates, scores, scenarios, evidence, assumptions, limitations, unresolved risks, owners, acceptance conditions, review dates, and conflicts of interest. Ask an independent reviewer to challenge the recommendation.

At 30, 60, and 90 days, compare completeness, calculation differences, moderation, corrections, report confidence, staff effort, support demand, access exceptions, continuity, cost, and outcome. Decide expand, repair, consolidate, narrow, or hold.

Turn the guidance into an accountable decision

Apply this guidance to one bounded part of vendor evaluation guide to 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, family, 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.