Supporting a pupil with a medical condition is not just a safeguarding task.
It is a workflow task.
If the school knows what the condition is, what medication is needed, who is trained, and where the current plan lives, the pupil is much safer and staff are much calmer.
The Department for Education’s statutory guidance says schools should support pupils with medical conditions and use clear templates for things like individual healthcare plans, parental agreement for medicine, medicine logs, and staff training records. Read the guidance on GOV.UK.
The best medical condition record is the one any trained adult can find quickly, understand immediately, and trust in a hurry.
That sounds obvious.
It is also where many schools fall down.
A care plan lives in one folder.
A medicine log lives somewhere else.
A training record is held by someone in admin.
A parent email about a change is in an inbox.
Then, when a supply teacher arrives or a trip is due, nobody is fully sure which version is current.
What the guidance expects
The DfE guidance is not asking schools to invent a complicated system.
It is asking for a sensible one.
The templates on GOV.UK are there to help schools: see the supporting resources.
create and invite parents to contribute to a child’s individual healthcare plan
ask for parental agreement for administering medicine
keep a record of medicine administered to children
keep a record of staff training in administering medicines
That is a good model because it turns a vague duty into a few specific records.
For most schools, the challenge is not the first plan.
The challenge is keeping the plan live.
What a useful record should contain
At a minimum, a school should be able to find the following without hunting around.
1. The current health plan
This should say what the condition is, what support is needed, what signs of concern to watch for, and what to do in an emergency.
If the pupil has asthma, epilepsy, diabetes, allergies, or another condition that can change quickly, the plan needs to be practical rather than long.
Short is fine.
Clear is essential.
2. The medicines agreement
If a school administers medicine, there needs to be a clear record of what was agreed with parents and what staff are allowed to do.
That protects the pupil and the school.
3. The medicine log
If medicine is given, the record should show what was given, when it was given, and by whom.
That is basic traceability.
4. Staff training records
If a pupil needs a specific medicine or procedure, staff training should be recorded and kept current.
If the school cannot show who has been trained, it is relying on memory rather than process.
5. The handover note
Trips, cover lessons, timetable changes, and new staff all create risk.
The record should make handover easier, not harder.
Where schools usually go wrong
The problems are familiar.
The plan is there, but nobody can find it
This is common in schools where the record is technically written down but practically invisible.
The medicine is tracked, but the staff training is not
That leaves a gap between the policy and the real world.
The parent update never reaches the live plan
A change happens, but it stays in email.
By the time it matters, the old instruction is still the one people see.
The same pupil has several versions floating around
One document in a shared drive.
One in a paper file.
One on a team inbox.
That is how people end up making decisions from the wrong copy.
MeritDocs keeps SEND documents in one searchable hub, so staff can filter by pupil, see what is current, and export when needed. That matters for medical conditions too, because the school should not have to reconstruct the support record from scattered fragments when a pupil needs help quickly.
A simple school workflow that works
A good process does not need to be fancy.
It needs to be repeatable.
When the condition is first identified
gather the parent information
agree what the school needs to know
write the healthcare plan
record any medicine requirements
identify the staff who need training
Before the pupil needs support in practice
check the plan is current
confirm the medicine log is ready
confirm who is trained
make sure cover staff know where to look
During the school day
keep the live record accessible
log anything administered straight away
note any change in symptoms or support needed
After a change
update the plan
tell the relevant staff
archive the old version if it is no longer current
That last step matters more than people think.
If the old version is still floating around, the system is not safe enough yet.
Why this matters beyond compliance
Pupils with medical conditions do better when adults are not improvising.
They need consistency.
Parents need to know the school has the right plan.
Staff need to know what to do without second guessing.
Leaders need to know the record can stand up if there is a concern later.
This is also where medical support and SEND support often overlap.
Some pupils have a medical condition and SEND.
Some have a health need that affects learning, attendance, behaviour, or access.
The school does not need separate worlds for each piece of information.
It needs one dependable picture.
That is why MeritDocs is useful here. Schools can keep current SEND documents in one place, with review dates visible and exports straightforward, so the live support record stays connected to the child instead of drifting into separate silos.
How to make the record usable in an emergency
Ask the simplest test.
If the usual class teacher was absent, could another trained adult answer these questions in under a minute?
What is the condition?
What medicine or action is required?
Who should be contacted?
Where is the current plan?
What is the warning sign that means escalation?
If the answer is no, the record is too hard to use.
A good plan is not the longest plan.
It is the one that can be found and understood fast.
A quick checklist for leaders and SENCOs
Before term starts, check that every pupil with a medical condition has:
a current plan
parent agreement if medicine is given
a medicine log where needed
staff training recorded
a named owner for updates
a simple handover route for trips and cover
If one of those pieces is missing, fix it before the next busy week.
What not to do
Do not rely on one person remembering everything
If the school can only run the process when one adult is in work, it is fragile.
Do not mix up current and historical records
The old version can matter for evidence, but it should not be the default working copy.
Do not make staff search inboxes in an emergency
That is not a system.
That is a delay.
Do not treat the plan as a formality
The record exists to protect the pupil and help staff act.
It is not there for decoration.
MeritDocs helps schools run this properly by keeping SEND documents in one place, with current information easier to find, review dates visible, and exports straightforward. The real gain is not just speed. It is a record people can actually rely on when a child’s support has to be checked in the moment.
FAQ
Do all medical conditions need the same level of paperwork?
No. The detail should match the risk and the support needed. But every pupil with a condition that affects school life should have a clear record.
Who should write the plan?
Usually school staff will lead it with parents, and other professionals where needed.
What if the condition changes during the year?
Update the live record at once and make sure staff know the current version is the one to use.
Is this only for primary schools?
No. Any school that supports pupils with medical conditions needs a clear process.
The takeaway
Pupils with medical conditions need more than goodwill.
They need a live record that is clear, current, and easy to hand over.
When the plan, medicine log, and training record are all in one dependable system, staff can do the right thing without delay.
That is better for safety, better for confidence, and better for the pupil’s day.
MeritDocs gives schools one searchable hub for current support records, so the medical condition process stays visible instead of being lost in inboxes and folders.