School Data Collection Audit: Keep, Streamline or Stop?

Choose one collection and find its decision purpose

To review school data workload, start with one repeated collection and ask what decision it supports. Identify the person using it, the information they need and when they need it. Then trace the work from the first entry to the final report. A collection that looks quick to its recipient may create several rounds of entry, checking and explanation for staff.

HSE’s school talking toolkit recommends explaining why data is collected and how it helps teaching, discussing anticipated workloads and considering the workload of new initiatives. DfE’s current England service provides a staff discussion about why data is collected and which collections could be streamlined or stopped. These support a review with staff and the people responsible for the requirements.

Sources: [1] [2] [3]

This is an original work-planning audit. It does not decide which school records are legally required or give an individual permission to stop supplying information. Verify requirements with the appropriate school or trust owner. The HSE publication dates from November 2021; this guide does not treat its historical inspection comments as current Ofsted rules.

Inventory entry, checking and downstream use

Choose a real collection with a clear boundary: for example, a term progress dashboard for one department. Record the data fields, source, frequency, deadline, recipient and intended decision. Ask what the recipient actually does with the result. “Leadership wants it” identifies a recipient but leaves the use unclear.

Follow the same information through each step. A teacher may enter a result once in the approved system, copy it to a spreadsheet, add a narrative and answer a reconciliation query. Record each operation rather than counting every file as a separate educational need. Also note work that is easy to miss: locating the current template, correcting an export or explaining a mismatch.

Keep collection, checking and interpretation distinct. Removing a duplicate entry may be possible while retaining a necessary quality check. Two reports can use the same source but require different definitions; matching column names alone does not establish equivalence.

Use ordinary task labels in a shared audit. Keep actual pupil records, health information and identifiers in their approved systems. The discussion normally needs to understand the process, not circulate individual pupil data.

Read a fictional collection audit

Fictional example: a department reviews a term progress collection. These entries demonstrate questions and proposals, not an actual school’s systems or a recommendation to abolish its records.

On a small screen, swipe inside this table. Keyboard users can focus it and use the arrow keys.

Each row ends with a condition. The export proposal depends on a suitable output and someone able to produce it. The commentary proposal depends on the recipient’s real need. Neither becomes an agreed change because the audit facilitator writes “streamline” beside it.

Ask the affected staff whether the table describes their work. Include administrative staff, data managers and other receiving teams where relevant. A change that removes teacher entry may create a new preparation or checking task elsewhere.

Compare work without inventing savings

Use the same collection window and distinguish effort estimates from observations. Include setup, correction and checking as well as routine entry. Do not multiply one estimated saving by every class and every week when the frequency or work differs.

Fictional calculation: the current process has 45 minutes of source preparation, 30 minutes of duplicate entry and 15 minutes of checking: 45 + 30 + 15 = 90 minutes. An approved export might remove the duplicate entry while retaining preparation and checking: 45 + 15 = 60 minutes for the original worker. That is a proposed 30-minute local reduction under stated assumptions.

Now suppose the export requires another worker to spend 15 minutes preparing and checking it. The proposed total is 60 + 15 = 75 minutes across both workers, a 15-minute difference from the original 90. This remains hypothetical. An incompatible export, added correction work or a different required report could remove that difference.

The arithmetic is not evidence that the proposal will save time or improve pupil learning. Check the same required output, real work and receiving-team effort after implementation. For a fuller operational comparison, use the workload-change review.

Agree the change and protect required information

Give the proposal an actual decision owner, implementation owner and review point. Specify what will remain, what will change and how the required output is preserved. If an external, trust or school requirement is uncertain, resolve it before assuming it can be removed.

An original decision draft is: “We propose replacing the duplicate dashboard entry with an approved export for this collection. [Owner] will confirm the fields, definitions and access. [Implementer] will arrange the export. The existing checking task remains. We will review the actual output and staff effort after the next relevant collection.” Keep it labelled proposed until those decisions are confirmed.

Check that recipients can make the intended decision from the revised output. Ask whether data is complete enough, understandable and available at the right time, and whether corrections or follow-up have grown. A smaller spreadsheet alone is not a successful review.

Download the original collection audit record (TXT). Use it for process facts and open decisions. Needed personal health or safety support should proceed through its appropriate route alongside the workload review.

Check three audit decisions

These fictional checks test purpose, authority and the scope of an effort comparison.