Record School Exam Version Proof

01 / CONTEXT

Define the control decision

A filename alone cannot prove that the correct exam paper remains unchanged. A compact release record should link the approved master to its subject, session, page count, marks, checksum, storage path and reviewer.

02 / PROCEDURE

Run the control sequence

1. 01

   Assign a release ID and record the approved filename.

2. 02

   Record subject, paper, session, page count and total marks.

3. 03

   Capture file size and an approved cryptographic checksum.

4. 04

   Keep the release record outside the protected master folder.

5. 05

   Repeat comparison after transfer, restore or authorized change.

03 / EVIDENCE

Preserve proof without personal data

A defensible control record identifies the exam owner, subject, paper, session, authoritative path, permitted accounts, restriction mode, release ID, page count, total marks, checksum evidence, recovery owner and next review date. It should not contain live questions, candidate data, operational answer keys or credentials. Use fictional questions and non-operational answer keys during every technical test.

Recheck the arrangement after changes to Windows, exam software, document format, print workflow, storage, Folder Protect, permissions, service accounts or school roles. Confirm both usability and recovery: an authorized operator should read the released template, an unauthorized account should not alter it, and the recovery owner should restore a separately held copy without depending on the protected folder. Preserve unexpected behavior before changing controls.

Keep the claim narrow. Local restrictions may reduce accidental writing, deletion or access on a tested Windows path, but they do not encrypt data, establish academic approval, examination authorization or secure printing, administer identities, create assessment-validity or approval evidence, provide version history or replace backup. Escalate those requirements to the platform and accountable owner designed to meet them.

Ask a second operator to follow the written procedure without verbal help. Record whether that person can identify the released final master, create a working copy, recognize the release ID, interpret denied access and find the recovery owner. This usability check reveals ambiguous paths, hidden service-account dependencies and undocumented knowledge before an exam platform, print workflow, storage or staff change. Correct the procedure, repeat the test with fabricated data and retain only minimal evidence.

04 / BOUNDARY

State what the control cannot prove

Version proof detects file differences; it does not prove question correctness, assessment validity, candidate fairness or examination authorization.

Validate the exact Windows account, exam application, print workflow, storage path and current product release. If encryption, academic approval, secure printing, immutable history, identity governance or regulated retention are required, select systems designed for those jobs rather than broadening a desktop restriction claim.

05 / SOURCES

Primary references

• UK government: Exam system contingency plan
• NIST SP 800-53 Rev. 5

References support specific controls and do not imply endorsement.