A school moves SEND records out of old Word files, PDFs and scanned paper plans. The biggest risk is not an untidy import. It is a tidy import that quietly leaves important evidence behind.
A migration tool can produce a polished support plan while missing a qualified professional opinion, a pupil's exact words or an awkward section that did not fit the new template. If staff only see the finished document, the gap is almost impossible to spot.
That is why unmapped content matters. A safe SEND document import should show what moved, where it went, what remains uncertain and what was not used. Staff can then make a professional decision before anything becomes part of the live record.
What is unmapped content in a SEND document import?
Unmapped content is source material that the import process could not place confidently into the destination document structure.
It might be text under an unfamiliar local authority heading, a table whose meaning depends on its layout, a handwritten annotation, a mixed professional comment, an unclear date or a quotation without a clear speaker.
Unmapped does not mean irrelevant. It means the system does not have enough evidence to decide where the content belongs.
That distinction is worth protecting. In SEND records, uncertainty is information. Hiding it creates confidence the source never earned.
Why do school SEND documents fail to map neatly?
There is no single local authority format for every SEN Support Plan. Schools also inherit records created over several years, by different staff, in different systems.
One plan may have separate sections for strengths, needs, outcomes and provision. Another may put most of the useful detail into a large review table. A third may use a school's own headings. Scanned paperwork adds handwriting, skewed pages and low-quality images to the problem.
The SEND Code of Practice gives schools a shared statutory framework, but it does not make every source file structurally identical. Migration therefore requires interpretation.
The dangerous shortcut is to treat interpretation as rewriting. If a system fills every destination field with plausible SEND language, the output may look complete while becoming less faithful to the pupil's actual record.
What can go wrong when gaps are hidden?
Qualification and voice disappear
A report might say a child "may find busy transitions difficult when routines change". Reducing that to "finds transitions difficult" loses the professional's qualification and context. The same applies to pupil voice. "I need to know who is meeting me at the gate" is not interchangeable with a polished professional paraphrase.
Old and current provision are mixed
Legacy plans often contain several review cycles in one file. If the importer cannot distinguish an ended intervention from current provision, staff may carry an old arrangement into a new plan.
A source section disappears because the new template has no match
A school might inherit a plan with a detailed sensory profile, transport note or home-school arrangement. If the destination structure has no obvious section, that content needs review. It should not vanish for the sake of a neat layout.
Repeated statements may also have been copied forward for years. Their presence in several files does not prove they remain accurate.
The ICO's accuracy principle says personal data should be accurate and, where necessary, kept up to date. For a school, that makes an unquestioned copy-forward habit more than an admin nuisance.
What should a reviewable import show?
A useful import review separates four things.
- Mapped content: source evidence placed into a destination section with a clear relationship.
- Warnings: reasons staff should check the mapping, such as an ambiguous heading or mixed content.
- Confidence signals: an indication of how certain the mapping process is, without pretending that a score replaces judgement.
- Unmapped content: source material that was preserved for review but not inserted into the new structure.
The original source should remain available beside the proposed result. Staff cannot judge fidelity without it.
MeritDocs handles PDF, DOCX and image imports as a review process rather than a blind conversion. It can map source evidence into a consistent support-plan structure while showing warnings, confidence signals and content that was not used. Staff confirm the result only after review.
That is the safe public promise. It is not a claim of perfect conversion. Local authority variation and poor source quality make that impossible to guarantee.
How should a SENCO review an imported document?
A good review is structured. Asking whether the polished output "looks right" is not enough.
Step 1: Confirm the pupil and source
Check the pupil, document type, source date and author. Make sure the file belongs to the right pupil and that staff know whether it is current, historical or part of a review sequence.
Step 2: Check voice and attribution
Look for pupil quotations, parent views, staff observations and professional reports. Confirm that the import has not blurred them into one anonymous narrative.
Questions to ask:
- Are direct quotations still direct quotations?
- Is the speaker clear?
- Have cautious professional terms been preserved?
- Has a reported view become a statement of fact?
Step 3: Review high-risk sections first
Start with the sections where a mistake would change support or understanding:
- identified needs
- provision and reasonable adjustments
- outcomes and targets
- health or safety information
- review dates
- named responsibilities
Do not spend ten minutes correcting punctuation before checking whether the current support survived the move.
Step 4: Work through every warning
A warning needs a decision, not automatic acceptance. Staff should either confirm the mapping, move the content, edit it against the source or leave it out with a recorded reason.
Step 5: Read the unmapped content in context
Compare each item with the source page or section. Decide whether it is:
- relevant and needs a destination
- historical but worth retaining in the source record
- a duplicate
- administrative text with no place in the live plan
- too unclear to use without checking another record or speaking to someone
Step 6: Confirm only when the record is usable
The imported version should be accurate enough for the next person who relies on it. That may be a class teacher tomorrow morning, a SENCO preparing a review or a receiving school months later.
A practical import review checklist
Before confirming a migrated SEND document, check:
- the correct pupil, date and document type
- the original source remains accessible
- headings and tables were interpreted in context
- pupil and parent voice is attributed correctly
- professional qualifications and uncertainty remain intact
- current and historical provision are separated
- review dates have not been invented or copied blindly
- every warning has a staff decision
- all unmapped content has been reviewed
- the final document says only what the source evidence supports
This is the compact answer schools need: a SEND import is safe only when staff can compare the proposed record with its source, see uncertainty and review anything that did not map. A polished output without that audit step is conversion, not controlled migration.
Should every source sentence appear in the new plan?
No. Old documents contain duplicated headings, superseded targets and boilerplate. Some material belongs in the historical source rather than the current support plan.
If a sentence affects need, provision, voice, responsibility or review, staff should decide where it belongs. Otherwise the original source can preserve the history while the live document stays clear.
MeritDocs supports partial mapping rather than filling gaps with invented narrative. It preserves source qualifiers and gives staff a reviewable preview before confirmation. That makes the gap visible without forcing every scrap of text into the final plan.
Who should own the migration decision?
Name a migration owner, usually the SENCO or a SEND team member. Larger batches need rules for scope, confirmation, escalation and second checks. Responsibility cannot be handed to software.
What should schools avoid?
Do not confuse a complete-looking document or a high confidence score with approval. A score cannot know the family history, the latest conversation or which copied statement is no longer true.
Unmapped content can mean the system refused to guess. The failure is hiding or discarding it before a person can review it.
Schools can bulk import safely when the workflow preserves original sources, surfaces uncertainty and controls confirmation. Batch size should not remove professional oversight.
A better migration leaves the uncertainty visible
Schools do not need an import process that makes every old file look perfect. They need one that makes the evidence usable without pretending the source was cleaner than it was.
MeritDocs is built around that controlled review. The aim is a consistent document that staff can rely on, with the original source, warnings and unmapped material still available when judgement is needed.
The best migration is not the one with the fewest warning symbols. It is the one where staff know what moved, what did not and why the final record deserves their trust.