Troubleshooting guide for exams, gradebooks, and report cards

Classify the symptom

Start a troubleshooting case with the user, role, campus, subject, assessment, learner population, date, environment, version, exact symptom, expected result, observed result, and urgency. Avoid placing unnecessary learner data in a ticket.

Classify the issue as definition, calculation, permission, identity, calendar, integration, interface, accessibility, notification, performance, report, backup, privacy, safeguarding, security, records, training, or support process.

Check the authoritative record

Compare the assessment definition, gradebook, approved result, report, family view, export, integration, and audit history. Identify where the value first differs and who owns that source.

Check assessment, component, attempt, submission, mark, grade, scale, weighting, rounding, missing, absent, late, moderated, approved, published, and corrected meanings before changing data. A display problem and a calculation problem require different remedies.

Use a controlled response

For missing submission, late work, absence, amended mark, moderation, resit, special consideration, withdrawal, transfer, duplicate, report correction, or outage, record the permitted action, evidence, approver, communication, rollback, and review.

Do not repair an official result by editing multiple copies. If a temporary workaround is unavoidable, label it, restrict access, set an expiry, reconcile it to the authoritative record, and assign an owner.

Escalate safely

Escalate immediately when the issue risks privacy, safeguarding, security, records integrity, assessment integrity, widespread incorrect reporting, or loss of recoverable data. Keep the escalation factual and proportionate.

The U.S. Department of Education data governance checklist covers quality, access, security, lifecycle, sharing, disposal, and monitoring. Use those areas in incident review, alongside qualified local legal and policy advice.

Close with evidence

A case is not closed merely because a screen works. Re-test ordinary and exceptional cases, compare expected and observed result, check affected reports and permissions, communicate the correction, and document what remains unresolved.

At 30, 60, and 90 days, review repeat incidents, resolution time, support demand, staff effort, correction quality, and the original outcome. Update training, validation, documentation, or change control where the root cause requires it.

Turn the guidance into an assessment decision

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

Test an ordinary case and meaningful exceptions such as missing work, late work, absence, moderation, amended result, withdrawal, duplicate, 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.

Before approval, ask a reviewer who was not involved in the design to challenge the strongest assumption. Record what was tested, what remains manual, and the next test where evidence is 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, calculations, timing, retention, or support demand.

Keep approved definitions beside calculations, training, support routes, change history, and evidence. Set the next review date and owner so the operation is maintained rather than treated as a one-time setup.

Make the handoff readable to teachers, administrators, leaders, learners, families, and reviewers. State what passed, which result remains manual, who owns unresolved conflicts, and how a correction is communicated.

Do not use a successful demo, low support volume, or high report-view count as proof of quality by itself. Pair activity with observed accuracy, completeness, safe access, correction, staff effort, and the original outcome.