Most schools do not lack SEND information. They lack usable SEND information.
A pupil's needs may be described in a speech and language report, an old support plan, a parent email, a review document and a scanned form from a previous school. The evidence exists. Finding the current statement, knowing who said it and using it safely in the next document is the hard part.
A structured pupil needs profile solves a different problem from file storage. It turns relevant statements from those source documents into reviewable information that staff can find and reuse, while keeping voice and uncertainty intact.
That is more useful than another summary PDF. It is also more demanding. A profile should never become a bucket of AI-generated assumptions.
What is a structured pupil needs profile?
A structured pupil needs profile is a maintained set of evidence-backed statements about a pupil's strengths, needs and experiences. Each statement should retain enough context to show what it says, who said it, where it came from and whether staff have reviewed it.
It is not the same as a pupil passport. A passport is usually a concise, staff-facing view of useful current information. The needs profile sits beneath future documents and workflows. It can hold more structured evidence without asking a teacher to read every source file.
It is not a diagnosis list either. A need should not be inferred merely because a document mentions a condition, a behaviour or a strategy.
Why is a folder of PDFs not enough?
A folder can preserve documents. It cannot tell staff which statements are current, duplicated, contradicted or superseded.
A Year 7 pupil may have one file saying they avoid written work, another describing difficulty planning extended answers, and a review showing that a writing frame helped in science but not English. Reducing that evidence to "difficulty with writing" is shorter, but much less useful.
The next support plan still depends on someone finding and interpreting the detail again. Useful evidence stays buried, different voices blur together, old statements survive and staff retype the same information.
MeritDocs approaches this as an evidence-to-document workflow. It can help staff extract sentence-sized needs statements from recorded SEND documents, distinguish different voices and present suggestions for review. Staff decide what becomes part of the structured profile.
What should the profile preserve?
Each statement needs its source, speaker, qualifications and review status. "May", "sometimes", "reported" and "not yet observed" all carry meaning. Staff should be able to trace wording back to a document, distinguish pupil voice from parent or professional evidence, and update a statement without erasing the history that explains earlier support.
A suggested statement should never become live merely because software extracted it. A member of staff must confirm, edit, reject or investigate it.
How does a structured profile improve daily SEND work?
The benefit appears when the next task begins.
It makes plan writing less repetitive
A SENCO drafting a support plan should not have to reopen eight files to recover the same pupil quotation and professional recommendation. Reviewed needs statements provide a safer starting point.
That does not mean auto-filling every section. The writer still has to decide what is relevant to this plan, this outcome and this review cycle.
It makes handovers more dependable
Receiving staff need current information and enough source context to trust it. A structured profile can show the statement itself and its voice, rather than handing over a folder with instructions to "read the latest reports".
It exposes contradictions and protects voice
Two documents may disagree. One may describe a barrier as constant while a later observation finds it only in unstructured periods. A good profile keeps that conflict visible. It also protects pupil and parent wording from being polished until the useful detail disappears.
Reviews can then ask whether a statement remains true, what evidence changed and what support followed.
A five-step workflow for building a pupil needs profile
1. Choose the source set
Start with documents that are relevant and reasonably current: support plans, review records, professional reports, pupil views and agreed parent contributions. Do not import every file merely because it exists.
Record the source date and document type. Old evidence may still matter, but staff need to know its age.
2. Extract statements without improving them
Pull out sentence-sized evidence. Preserve direct quotations and cautious wording. Do not turn a tentative observation into a fixed need, or a strategy into proof of a diagnosis.
Avoid targets, provision descriptions and review judgements unless the profile has a defined place for them. A needs profile becomes muddy when every sentence from every plan is treated as a need.
3. Classify voice and meaning
Mark whether each statement comes from the pupil, parent, school staff or a professional report. Use the school's agreed categories, but do not let classification replace the original wording.
The SEND Code of Practice places children, young people and parents at the centre of decision making. A profile that strips out who said what works against that principle even if its prose looks tidy.
4. Review suggestions against the source
For each statement, ask:
- Does the source actually support this wording?
- Is the speaker correct?
- Has any uncertainty been preserved?
- Is the statement current enough to use?
- Is it already present in another form?
- Does it describe a need or merely repeat a target, provision or opinion?
MeritDocs can suggest structured statements and compare them with existing profile content to reduce repetitive re-suggestion. It also avoids unsupported diagnosis inference. Staff remain responsible for confirming the evidence and deciding how it should be used.
5. Use the profile, then maintain it
A profile earns its keep when it supports real work: a new SEN Support Plan, a review, a pupil passport or a transition handover.
Set a review habit. When new evidence arrives, compare it with existing statements. Confirm what still applies, update what has changed and retain enough history to explain the decision.
What should schools avoid?
Do not let the profile become a second ungoverned record. Keep source attribution, protect quotations, flag contradictions and review old statements. Do not infer a complete picture of need from a diagnosis or import targets as if they were facts.
Reuse should also be selective. A transition brief, support plan and pupil passport serve different readers. They can draw from the same reviewed evidence without becoming identical documents.
A concise definition schools can use
A structured pupil needs profile is a reviewed layer between source documents and future SEND workflows. It preserves evidence, source voice and uncertainty in a form staff can find and reuse, while keeping professional approval in control.
That definition sets a useful boundary. The profile organises evidence. It does not make statutory decisions, diagnose a pupil or replace conversations with the child and family.
Frequently asked questions
Is this the same as a one-page profile?
No. A one-page profile or pupil passport is a concise output for a particular audience. The structured needs profile is the reviewed evidence layer beneath several documents and workflows.
Can AI build it automatically?
AI can identify candidate statements, but staff should compare them with the source and approve what becomes live. Review the profile when significant evidence arrives and through the normal SEND review cycle.
Build a record that gets more useful over time
A folder of PDFs grows by accumulation. A structured needs profile grows by review.
That distinction matters. Schools need to preserve original evidence, but they also need a current layer that people can use without repeatedly rebuilding the pupil's story from scratch.
MeritDocs helps connect those two jobs. Source documents remain part of the record, while reviewed needs statements can support later document workflows. The result should not be a smoother story. It should be a more traceable one.