Call it the record-layer gap: special educational needs and disabilities (SEND) management software should not merely list interventions. It should connect costed provision, recorded evidence, SEN Support Plans, pupil passports, reviews, reporting, staff access and exports while keeping professional decisions with school staff.
The phrase "SEND management software" can mean different things. Some products focus on provision mapping. Others sit inside a wider management information system. Others are really document stores with a search box. Those differences matter when a special educational needs coordinator (SENCO) is trying to find the current plan, explain what support is being delivered, or show how a review changed the next step.
What are schools actually trying to manage?
The software question usually starts with a workflow problem, not a feature list. A school may be dealing with:
- evidence spread across Word files, Portable Document Format files (PDFs), email and shared folders;
- SEN Support Plans that are hard to keep current;
- provision that is recorded in one place and reviewed in another;
- pupil passports that continue circulating after they have been updated;
- review dates that depend on one person remembering them;
- staff who need the current support information without opening every historical document;
- a new SENCO who has inherited records with no clear history;
- a school or trust that needs to move away from spreadsheets or an existing platform.
These are connected problems. A plan is based on evidence. Provision should relate to the plan and its outcomes. A review should explain what changed. The current pupil passport should reflect the information staff are expected to use. If each part sits in a separate workflow, the school spends time copying information and checking which version is safe to rely on.
Where does provision mapping fit?
Provision mapping software has a clear job. It should help a school see what support is planned, which pupils or groups it applies to, who is responsible, when it runs, and how the school will review its impact.
That view is useful, but it is not the whole SEND record. A provision map does not automatically explain the evidence behind a pupil's needs, preserve the wording of a pupil or parent, create a complete support plan, or show the history of approved versions. Schools need to decide which information belongs in the map, which belongs in the plan, and which should remain in the supporting record.
A useful platform makes those boundaries clear. It does not turn every document into one long note just because putting everything in one place sounds simple.
For a practical guide to the map itself, see how to build a SEND provision map that staff actually use. The next question is how the map connects to the rest of the workflow.
What is the difference between storing documents and managing them?
SEND document management software should do more than store files in a folder. It should give staff enough structure to answer ordinary questions quickly:
- Which document is current?
- Who owns the next action?
- When was the record last reviewed?
- What changed since the previous version?
- Which evidence supports the wording?
- Can the right member of staff access it?
- Can the school export it if a meeting, handover or contract change requires it?
That does not mean every school needs a complicated records system. It means the system should support the decisions people already make. A searchable folder can find a file. A managed workflow helps a team understand whether that file is the one they should use.
Six jobs good SEND management software should handle
1. Turn evidence into a workable starting document
Staff should not have to start every support plan from a blank page when the school already holds useful information. At the same time, software should not turn missing information into confident-sounding text.
The useful middle ground is structured assistance. The system can help organise recorded information into the sections the school uses, while showing where staff need to check, add or correct something. Pupil voice, parent views, professional advice and staff observations should not be flattened into one anonymous paragraph.
The final document remains the school's responsibility. The software should make the review easier, not make the decision on the school's behalf.
2. Connect provision to the pupil's plan and review
A list of interventions is not enough. Staff need to understand who is receiving support, what the support is intended to do, who is delivering it, and what evidence will inform the next review.
This is where provision mapping and SEND management software should work together. The map gives the wider view. The pupil record gives the context. The review brings the two back together and records what should happen next.
Schools should test whether the platform can follow that path without asking staff to re-enter the same facts in several places.
3. Keep the pupil passport current
A pupil passport is only useful if staff can trust it. If an old PDF is still attached to an email or sitting in a classroom folder, a beautifully designed template has not solved the operational problem.
Look for draft and published states, clear ownership, approval dates, review dates and version history. Staff should be able to see which passport is current and what happened to the previous version.
The guide how to keep a pupil passport current covers this in more detail.
4. Make reviews and history visible
A review should not create another isolated document with no connection to the previous one. Staff need to see the baseline, the evidence considered, the changes agreed and the next review point.
The product does not need to make every school use the same timetable. It does need to make ownership and timing visible. A SENCO, teacher or senior leader should not have to search across calendars, spreadsheets and folders to work out what is open.
5. Handle the records a school already has
Few schools begin with a clean archive. Existing records may include Word documents, PDFs, scans, photographs of paper plans, local authority templates and duplicated versions.
Migration should therefore be treated as a reviewable process, not a promise that one button will make every document perfect. Schools should ask to see:
- how the source files are retained;
- how documents are mapped into the new structure;
- what happens when a section does not fit;
- whether warnings and unmapped information are shown;
- how staff correct a proposed mapping;
- how the original and new versions are connected;
- what can be exported if the school leaves later.
For more detail, see switching SEND software: how UK schools can migrate without starting again.
6. Give each person the information they need
A SENCO, class teacher, teaching assistant, headteacher and data protection lead will not all use the system in the same way. Access should reflect the work each person is allowed to do, without making the current record impossible to find.
A school should also ask how the platform handles exports, deletion, audit history and changes in staff. These are not afterthoughts. They are part of deciding whether the system can be trusted with an important record over time.
What should a school test in a demonstration?
Ask the supplier to show one complete pupil journey rather than a tour of every menu. A useful test might include:
- Start with an existing document containing clear evidence and one unresolved gap.
- Create or update a SEN Support Plan without losing the source wording.
- Set out the provision, responsible staff and review arrangement.
- Update the pupil passport and publish a new version.
- Ask a teacher to find the current support information.
- Complete a review against the previous baseline.
- Check the history and export the resulting record.
Then ask what the system does when the evidence is incomplete, the document does not map cleanly, a staff member changes role, or the school decides to leave. Those answers tell you more than a polished sample document.
Where MeritDocs fits
MeritDocs is built as a whole SEND provision-management platform for schools and multi-academy trusts. It brings costed provision mapping, pupil passports, SEN Support Plans, profound and multiple learning difficulties (PMLD) plans, individualised education plans (IEPs), reviews, reporting, migration and controlled records into one workflow.
The Document Wizard helps staff create structured plans from recorded information using UK SEND terminology and grounded source material. Staff remain responsible for checking and approving the result. The wider platform keeps costed provision, pupil passports, current versions, review context and reports connected, while the Documents Hub groups records by pupil and supports controlled access and export.
For schools with existing records, MeritDocs supports best-fit mapping from PDFs, Word files and images. It shows warnings and unmapped content before staff confirm the imported material. That matters because SEND documents vary between schools and local authorities. A migration should preserve uncertainty rather than hide it behind a clean-looking rewrite.
The point is not to add another place for staff to upload files. It is to reduce the repeated work between evidence, plans, provision, reviews and the current record.
A simple buying test
Before choosing SEND software for schools, ask whether the product can pass these five tests:
- A SENCO can find the current record without asking the same colleague every time.
- A teacher can understand the relevant support without reading the entire history.
- A review shows what changed and what needs to happen next.
- An imported document shows what mapped and what still needs checking.
- The school can export its records in a usable form if the arrangement ends.
If a platform handles those jobs well, the feature list becomes easier to judge. If it cannot, a long list of dashboards and artificial intelligence (AI) options will not fix the underlying workflow.
Sources and related reading
The SEND Code of Practice: 0 to 25 years provides the national framework for SEND practice in England. It does not make every school's documents identical, so schools should check how a platform fits their local process.
Related MeritDocs guides:
- How SENCO software should reduce paperwork without losing accuracy
- How to build a SEND provision map that staff actually use
Costed provision map for an Education, Health and Care Plan (EHCP)
- How to keep a pupil passport current
- Switching SEND software: how UK schools can migrate without starting again