The short version
A good one-page SEND profile should do one job well. It should give staff the information they need quickly, without forcing them to trawl through a long support plan or a pile of old notes.
That means it needs to be short, current, and specific.
The SEND Code of Practice is the right place to start if you want the profile to reflect ordinary SEND duties and review culture, not just a local habit: SEND Code of Practice: 0 to 25 years.
The best profiles answer a small set of questions:
- what does this pupil need
- what helps
- what makes things worse
- what should staff do next
- who owns the next review
If a profile does not answer those questions in a minute or two, staff will not use it when the room is busy.
What a one-page profile is for
A one-page profile is not a polished summary for the website.
It is a working document.
It should help with ordinary school life, such as:
- supply cover
- class changes
- transitions between year groups
- parent meetings
- annual reviews
- pastoral handovers
- quick checks before a lesson
That is why it needs to be practical rather than decorative.
If the profile reads like a brochure, it is already off course.
What to include
A one-page profile only works if it is selective. Put in the things that change decisions.
A strong template usually includes:
- pupil strengths and interests
- primary need or needs in plain English
- what helps in class
- what to avoid
- triggers and warning signs
- reasonable adjustments already agreed
- current interventions or support
- review date and owner
- a contact point for urgent questions
That is enough for most staff.
It gives them the minimum picture they need without overwhelming them.
Keep it brief and specific
This is where many profiles go wrong.
They fill the page with broad phrases such as "needs encouragement", "benefits from support", or "responds well to adult input".
Those phrases are too vague to help.
A useful profile says things like:
- use short, concrete instructions
- check understanding after each step
- offer a quiet start after break
- warn before changes in routine
- avoid open-ended questions when the pupil is dysregulated
That is the difference between a document people skim and a document people use.
What to leave out
A one-page profile is not the place for everything you know about a pupil.
Leave out:
- long chronology
- copied policy language
- old interventions that have stopped
- repeated diagnosis detail
- paragraphs of background that do not change day-to-day support
- anything the reader cannot act on quickly
If you need the full history, keep it elsewhere.
The profile should point staff to the current picture, not try to be the whole archive.
How to keep it current
A profile is only useful if it stays alive.
That sounds obvious, but in many schools the profile is written once and then quietly drifts out of date.
A simple maintenance rhythm works better:
1. Give one person the job
Someone has to own the live version.
If everybody can edit it, nobody keeps it clean.
2. Update it when something changes
If a new adjustment works, add it.
If a support strategy stops working, remove it.
If the pupil moves year group or key staff change, check the summary before the handover is complete.
3. Keep a review date on the page
If staff cannot see when it was last checked, they will not trust it for long.
4. Archive the old version rather than leaving it in circulation
There should be one current profile.
Not three nearly identical ones with slightly different wording.
MeritDocs keeps SEND documents in one searchable hub, so staff can filter by pupil, see what is current, and export when needed. That is useful here because the problem is rarely writing the profile once. The problem is keeping the same pupil picture current across ordinary school work.
Where it fits in the school workflow
The profile should not sit alone.
It should connect to the school routines that already matter.
In class
Teachers should be able to open it and see the basics without guessing.
In handovers
Cover staff and new staff need the version that is current now, not the version from last term.
In meetings
A good profile gives parents and staff something concrete to react to.
It keeps the discussion on the live picture, not vague memory.
In annual reviews
The profile should make it obvious what has changed, what is still open, and what the next step is.
That is why it works best when it is part of a wider live record, not a random file on a shared drive.
A simple structure that usually works
If you want a starting point, use this order:
- strengths and interests
- main need or needs
- what helps
- what to avoid
- current adjustments and support
- key contacts and review date
That order makes it easier for staff to scan the page quickly.
You can also add a short "what to do first" box if the pupil needs a very specific response at the start of the day or after a difficult lesson.
That box is often more useful than another paragraph of background.
Why one page is usually enough
A lot of school documents become long because people are trying to protect themselves from missing something.
That is understandable. It is also how documents become unusable.
One page forces discipline.
It asks the writer to decide what matters most for day-to-day teaching, support, and handover.
That is a good thing.
The pupil does not need every piece of history on the front page. Staff need the right page in front of them when they are trying to help.
What MeritDocs changes
This is where the workflow matters.
If the profile lives in an email chain or an old folder, it becomes one more thing staff have to hunt for.
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. Schools can pull the live profile from the record rather than rebuilding it from memory for every handover.
That sounds small. It is not.
A one-page summary is only valuable if people can trust it is the latest one.
FAQ
Is this the same as a pupil passport?
In practice, many schools use the terms differently, but the job is similar. The important thing is not the label. It is whether the document is short, current, and useful.
Who should own it?
Usually the SENCO or another named lead should own the process, but class staff need to feed in the practical detail because they see what works day to day.
How often should it be updated?
Whenever something important changes, and at least on a regular review cycle. If it is only reviewed once a year, it will drift.
Should it replace the support plan?
No. It should sit alongside the support plan and point people to the current picture quickly.
The takeaway
A one-page SEND profile works when it is built for the people who will use it.
That means plain English, real detail, and a current version that staff can find fast.
If the profile helps a teacher act sooner, helps a cover teacher avoid mistakes, or helps a parent meeting stay focused, it is doing its job.
If it is long, vague, or buried in a folder nobody checks, it is just another file.
MeritDocs gives schools a live place to keep that profile current, so the next person in the room is not guessing.