School attendance systems: reliable records and follow-up

Start with the school's attendance process

Map the journey from a teacher taking the register to the office resolving unexplained absence and the attendance lead reviewing patterns. Identify who acts at each point, which information they need and how they know that a task has been completed. The system should support this process rather than leave staff to infer it from a coloured dashboard.

Keep safeguarding escalation separate from routine reporting. A missing or unexpected registration entry may require prompt action under the school's procedures. The software can surface an exception, but staff still need a clear route for checking circumstances and making decisions.

Apply the correct national guidance

Attendance requirements differ across the UK. For England, the Department for Education publishes statutory guidance titled Working together to improve school attendance. Its scope includes schools, trusts and local authorities, and it addresses registration, support and responsibilities. Schools should use the current guidance for their setting when defining system requirements.

A separate DfE daily-data guidance sets out the information and submission requirements for the schools it covers in England. Do not infer that every school type across the UK has the same reporting duty. Confirm the applicable requirements, current codes and submission arrangements with the responsible school lead and supplier.

Make register-taking dependable

Test how teachers identify the correct session, class and date. Check what happens when a pupil joins, leaves, changes class or attends a different approved activity. The interface should make incomplete registration visible without encouraging staff to select a convenient code merely to clear an alert.

Have an agreed fallback if the service, device or connection is unavailable. Staff need a secure way to record the session and a defined person to enter the information later. A fallback should preserve who took the register and when, and should not create two conflicting final versions.

Separate parent reports from authorised records

An absence message from a parent provides information for the school to assess and record. It should not automatically be treated as an authorised attendance decision simply because it arrived through the parent app. Configure the workflow so that the appropriate staff can review, follow up and apply the relevant code.

Make duplicate reports easy to identify. A parent might submit a form and then telephone the office when they are unsure it arrived. The record should support a clear acknowledgement without allowing repeated messages to overwrite earlier staff decisions unexpectedly.

Control corrections and retain an audit trail

Attendance records may need legitimate correction when new information arrives or an entry was made in error. Restrict changes to authorised roles and preserve appropriate evidence of what changed, who made the change and when. Staff should understand which corrections require additional review.

Test effective dates and reporting consequences. A correction to an earlier session should appear in relevant reports and any required downstream submission according to the system's process. Agree who checks that the correction reached the destination and how a rejected submission is handled.

Define reports before comparing figures

A percentage needs a clear denominator, period and inclusion rule. Different enrolment dates, session counts or filters can produce different figures without either report being technically broken. Ask the supplier to explain how each important measure is calculated and test it against fictional records with known outcomes.

Reporting question	What to verify
Which pupils are included?	Enrolment dates, status and selected groups
Which sessions count?	Period boundaries and applicable recording rules
Have corrections been included?	Refresh timing and historical updates
Who can see detailed reasons?	Role permissions and appropriate need
What requires follow-up?	Clear task ownership rather than an unexplained alert

Use reports to support informed conversations and action. Avoid treating a single automated label as a complete explanation of a pupil's circumstances.

Test integration and daily oversight

Where attendance information moves between systems, document the fields, frequency, expected completion time and error route. Check that pupil identifiers remain consistent and that missing records do not silently disappear from the school's view. Give staff a way to confirm successful transfer without downloading unnecessary personal data.

Assign a daily operational check and a periodic review of data quality. Track incomplete registers, unresolved exceptions, rejected submissions and recurring training issues. Review access to attendance details alongside other pupil information, including exports used in meetings.

A dependable attendance system gives the school an accurate account of each session and a manageable follow-up process. For related work, see the MIS buying guide and school parent communication.