What should a school first-aid record contain?

A school first-aid record should identify the person, incident date, time and place, injury or illness, first aid given, immediate outcome, and the first aider's name and signature. Check communication evidence and give any missing information an owner and review time. Keep an unknown answer visible until an attributed source supports it.

This checklist helps school leaders, first-aid leads, SENCos and pastoral staff in England check one record. It offers a recording aid, with no clinical approval or guarantee of legal compliance. Actual care follows the pupil's plan, trained staff, local procedures and qualified clinical advice. Don't delay an urgent response to complete a record.

Separate the recommended record from local completeness checks

DfE's non-statutory first-aid guidance strongly recommends recording incidents attended by a first aider or appointed person. Its six recommended field groups cover timing and place, the person, injury or illness, care, immediate outcome, and the first aider's name and signature. The eight prompts below split timing from location and add a local communication and missing-information check. They aren't eight new statutory requirements.

Near misses need a factual account of what nearly happened and the safety action taken; don't invent an injury to complete a form. Early-years providers should check the separate applicable EYFS framework. Notification requirements depend on the setting and circumstances; this article doesn't set one rule for every school or child.

Eight prompts for the person checking the record

1. Who was involved?

Identify the injured or ill person accurately, using the minimum identifiers needed. Distinguish pupils, staff and visitors. Check the selected person against the source; a familiar name alone may identify the wrong record.

2. When did it happen?

Record the incident date and time. Keep these separate from the time someone entered the record. If timing is approximate or reported by someone else, say so and identify that source. A default timestamp isn't confirmation of the event time.

3. Where did it happen?

Name a location another adult can recognise. Distinguish the incident location from where care was provided. An unclear location needs an explicit uncertainty entry and enquiry, rather than a guessed classroom or playground.

4. What was observed or reported?

Describe the injury, illness or near miss in plain factual language. Attribute the person's account separately from staff observations. Record relevant injury location where known. Don't turn a symptom, assumption or uncertain account into a diagnosis.

5. What first aid or safety action was actually given?

Describe the care actually provided, with its source. For a near miss, record the action taken to make the situation safe. A proposed action, equipment available nearby or a copied previous entry doesn't establish what happened on this occasion.

6. What was the immediate outcome?

Record the immediate disposition, such as return to class or collection, with relevant timing and source. Don't treat a return-to-class entry as proof of recovery or clinical safety. Later developments belong in dated additions through the school's procedures.

7. Who provided first aid, and how is it authenticated?

Identify the attending first aider and the signature recommended by DfE. Keep the person entering the record separate if someone else provided care. For an electronic process, check how the school authenticates that account. A typed staff name or recorder's login alone shouldn't be assumed equivalent to the first aider's signature.

8. What communication evidence or information gap remains?

This is an added local completeness check. Record who was told, by whom, through which route and when, where supported by evidence. Distinguish prepared, queued, sent and confirmed contact. Give an unresolved field a responsible adult and review time; don't tick notification merely because a message exists.

FA-017: a blank contact field changes the enquiry

Every person, identifier and event here is invented. Record FA-017 concerns Alex Example. It gives 21 October 2026, 10:35, the covered playground, and attending first aider Sam Example. Alex reported falling; Sam recorded an observed graze, the first aid actually provided and a return to class at 10:50. Those entries remain attributed accounts, without any claim here about treatment technique or its adequacy.

Communication method and time: not yet established. Evidence check owner: first-aid lead Jo Example. Review point: 14:00 that day. Check the approved incident record and related communication history; retain the missing state until confirmed.

Jo finds a related message in the communication record. Its status is draft, with no evidence it was sent. The question changes from whether the contact field was simply omitted to whether contact happened at all. Neither the blank field nor the draft establishes that the parent was, or wasn't, told another way.

Jo asks the responsible staff member for the source evidence and follows local contact procedures. If a phone conversation is confirmed, Jo records its attributed method, time and source through a dated correction or addition, preserving the original record. If confirmation remains unavailable, the uncertainty stays open with Jo and a further review point. This invented time illustrates ownership, without setting a notification deadline.

Access to each source needs separate authorisation. Linking the incident and communication records helps a person check evidence; it cannot establish notification, reading, understanding, diagnosis, causation or clinical safety. For wider role allocation, use the school health responsibility map.

Keep reporting, access and retention decisions separate

A first-aid record doesn't establish that an HSE report is required or has been submitted. HSE's school incident-reporting guidance explains that most school incidents aren't reportable under RIDDOR. The authorised responsible person checks that guidance and local procedures. This checklist cannot make the reporting decision.

Health information is special-category data. The ICO explains the need for an Article 6 lawful basis and an Article 9 condition; don't invent blanket consent. Its guidance is under review following the Data (Use and Access) Act 2025. Limit access and copies to the information necessary for the authorised purpose, including when checking another record. Masked identifiers or small counts don't establish anonymity or lawful sharing.

Follow the school or trust's retention schedule with its data protection officer, considering the record's purpose and any preservation obligations. DfE's record-keeping guidance supports purpose-specific retention; there isn't one retention period supplied by this checklist. Keep a route to challenge inaccuracies and preserve provenance when supported corrections are made.

Where enabled and authorised, Student Radar's First Aid workspace supports structured incident facts, attending staff, communication and follow-up records. Staff check evidence and local authentication requirements. Explore the school medical records workflow and recording guide against your school's arrangements.

Read one record with another authorised adult. If a field depends on an assumption, record what remains unknown, who will check it and when.

Sources and further reading

• DfE, First aid in schools, early years and further education: non-statutory England guidance; publication page published 15 August 2000, updated 14 February 2022. Recording and reporting section.
• HSE, Incident reporting in schools and EDIS1 Rev3: guidance on RIDDOR 2013, 2013 revision, checked 25 October 2026; Great Britain reporting framework.
• ICO, What is special category data? and What are the rules?: regulatory guidance. The definition page was updated 9 April 2024; both pages checked 25 October 2026 and under review following the Data (Use and Access) Act 2025.
• DfE, Record keeping and management: school data-protection guidance published 3 February 2023, updated 14 October 2026. Check retention against purpose and local responsibilities.