Sampling pupil work without turning the sample into a second register

When a school invites an outside reader, the first anxiety is often legal rather than pedagogical: will copies of exercise books leave the building, and under whose name? The answer should be boring. The school remains the keeper of identities. The reader needs enough of the piece to judge the outcome, and a code that lets faculty retrieve the original if a finding is disputed.

A workable method is a sample pack assembled by the department: photocopies or exports with names replaced by the school’s own internal codes, plus a sealed key that never leaves the office. We read the pack. If a finding must be checked against handwriting or a missing page, a teacher opens the original on site. Nothing about that process requires a new login, a shared drive we operate, or a desktop file that travels home on a personal machine.

Where schools use the optional local tracking utility associated with Releasepathbase, the same principle holds. The utility is a record-keeping aid on a machine the school already controls. It does not take custody of pupil files, does not reach into financial accounts, and does not replace the school’s register.

The sample size can stay modest. For a year group of thirty, six pieces per contested outcome usually expose whether the task could have produced the evidence the scheme claimed. The point of the sample is argument, not surveillance.

All field notes