A special educational needs and disabilities (SEND) pupil passport can be clear, concise and beautifully written, then become risky the moment an old copy keeps circulating.
The problem is rarely the template. It is version control.
Staff need to know which passport is current, who approved it, what changed and what to do with the previous version. Without that workflow, an update on the special educational needs coordinator (SENCO)'s drive does not stop a printed copy in the cover folder or an attachment in an old email being used.
In brief: keep one controlled pupil passport with separate draft and published states. Give every published version an owner, approval date and review date. Replace access to the previous version when a new one is published, preserve the old version in an archive and tell the staff who use it what changed.
What is a pupil passport for?
A pupil passport is a concise staff-facing summary of the information adults need to support a pupil consistently. It may include strengths, communication preferences, current barriers, helpful adjustments and the pupil's own views.
It is not the full SEN Support Plan. It should not try to hold every assessment, target, meeting note or professional report. Its job is to make the most useful current information available at the point of practice.
That makes freshness part of quality. A polished passport with outdated communication guidance can be worse than no passport because staff trust it.
Why do pupil passports go stale?
Most stale passports are produced by a sensible action with no controlled next step.
A teacher saves a local copy for quick access. A SENCO emails an updated Portable Document Format files (PDFs). A teaching assistant prints it for a folder. The pupil changes class. A parent shares a correction. Each action makes sense on its own. Together, they create several versions with no obvious source of truth.
The warning signs are familiar: filenames such as final2, no visible review date, staff editing downloaded copies and draft wording sitting beside the approved version. The fix is not a stricter filename. It is a publishing workflow.
What is the difference between draft and published?
A draft is work in progress. Staff may be gathering pupil voice, checking details with parents, comparing source records or agreeing wording.
A published passport is the approved version staff should use.
Those states need to be visibly different. If a half-complete draft appears in the same folder and format as the live passport, somebody will use the wrong one sooner or later.
Set a simple rule:
Staff-facing access points show only the current published passport. Drafts remain in the controlled editing workflow until approval.
This protects the pupil from speculative or unconfirmed wording entering daily practice. It also gives the editor room to work without creating confusion.
A six-step pupil passport workflow
1. Start from the current published version
Open the controlled current version and create a new draft from it. Do not use memory or whichever attachment is easiest to find. Record why the update started. Typical triggers include:
- a scheduled review
- a class or phase transition
- a new communication preference
- a material change in need or provision
- pupil or parent feedback
- relevant professional advice
2. Check every statement against a source
A passport is brief, but its content still needs evidence.
Preserve the pupil's own words rather than polishing them into professional language. Attribute parent views clearly. Do not turn a tentative observation into a fixed description, or a strategy into proof of a diagnosis.
MeritDocs can use reviewed needs statements in the passport workflow, helping staff keep source voice and avoid unsupported inference. Staff still decide what is accurate, relevant and ready to publish.
3. Make the changes easy to review
The approver should be able to see what changed without placing two PDFs side by side.
Keep a short change note such as:
- updated preferred communication method following pupil review
- removed lunchtime exit card because it is no longer used
- added agreed science practical adjustment
- corrected parent contact preference
Do not write "general update". That tells nobody what to check.
4. Approve before publishing
Define who can approve a passport. In many schools this will be the SENCO or an authorised member of the SEND team, with input from the pupil, parent and relevant staff.
Approval should confirm that the content is current, voice is attributed correctly, sensitive detail is necessary, adjustments match agreed support and the next review date is set. It is a real control, not a tick added after distribution.
5. Publish one new current version
Publishing should do three things at once:
- make the approved passport the current staff-facing version
- remove the previous version from ordinary access points
- preserve the previous version in a dated archive
MeritDocs supports draft and published passport states, version history, archiving and print output. That keeps editing separate from staff-facing use and preserves earlier versions without presenting them as current.
When the passport begins with an existing EHCP, the upload route can feed the working record without staff re-entering the same history into a new-ISP wizard. See how the two ISP routes connect to the pupil passport.
If the school uses printed passports, include the version date and a clear instruction to destroy or return superseded copies. For secure digital access, link staff to the live published view rather than sending attachments that cannot be recalled.
6. Tell staff what changed and check use
A new version is not live in practice merely because it exists. Tell relevant staff what changed, why it matters and where the current passport lives. A quick check may show that adults still rely on an old routine. That is a training issue, not a reason to add more text.
When should a pupil passport be reviewed?
Set a routine review date, then define events that trigger an earlier review.
Useful triggers include:
- the pupil says the passport no longer reflects them
- a parent identifies an important change or error
- staff find that an adjustment is not working
- new professional advice changes daily support
- the pupil moves class, phase, site or setting
- attendance, distress or participation changes materially
- a safeguarding or medical update affects what staff need to know
The review date should not be invented inside free text. Keep it as controlled workflow data with an owner. MeritDocs keeps passport versions and publication states together so the current view is clear while the history remains available when staff need to understand a change.
What should happen to old pupil passports?
Archive them. Do not leave them mixed with current documents, and do not erase the history.
An earlier passport may explain a past decision and show how support changed. That history can matter during reviews, transitions or complaints.
The archive should retain the previous version, its publication and replacement dates, the approver and the reason for replacement. Ordinary staff access should still lead to the current version first. History is useful. Ambiguity is not.
A quick audit for school leaders
Choose a small sample. Can a teacher find the current published version in under a minute? Are its approval and review dates clear? Is pupil voice preserved? Can the previous version be found without being mistaken for the live one? Were printed copies addressed after the latest change?
If three staff produce three different versions, the school has a workflow problem, not a formatting problem.
The takeaway
A useful pupil passport is not a one-page template. It is a maintained publication.
Separate drafting from staff-facing use. Approve changes. Publish one current version. Archive what it replaced. Tell staff what changed. That is how a school turns a helpful summary into a record adults can trust when they need it.
Version control must cover more than the pupil passport
A pupil passport is only one part of the live SEND record. The same control is needed for the current SEN Support Plan, PMLD plan, provision summary, reasonable-adjustment record and any short handover document that staff rely on. Otherwise a school can keep one passport current while a lesson plan or support summary quietly points to an older decision.
The practical test is not whether a file has a recent date. It is whether a colleague can answer three questions without opening several folders:
- Which record is the approved current version?
- What changed since the previous version, and why?
- Who needs to act differently because of the change?
A version check for a changing support plan
Imagine that a pupil no longer needs adult prompting for every written task, but still needs a chunked instruction and a quiet start. The old plan says “continuous adult support”. The new plan narrows the adjustment. The change should be recorded as a decision, approved by the right school staff, reflected in the current plan and explained to the adults who use it. Archiving the old plan alone does not stop it being reused.
Keep a short change note beside the new version. It should name the changed provision, the evidence or review that prompted it, the date it takes effect, the owner of implementation and the next review point. That is more useful than a filename such as `final-new-v3.docx`.
What to do when two records disagree
Do not ask a teacher to choose the document that “looks newest”. Pause the handover or support decision and resolve the conflict against the latest approved source. If the school cannot establish which version was approved, record that uncertainty, ask the SENCO or named owner to decide, and update the live record before the next lesson or review.
The DfE data-protection guidance for schools treats record keeping as an active management task: schools should know what data they hold, why they hold it and when it should be reviewed or disposed of. That does not prescribe a particular SEND software product, but it is a useful standard for testing whether version control is real rather than cosmetic.
MeritDocs manages pupil passports inside a wider SEND workflow, keeping the current approved version, its history and review dates connected so staff can see what changed and what is live. Documents remain searchable and available to export. The school still decides what is approved and what the change means for practice.
Sources
Relevant guidance: Department for Education (DfE) and Department of Health and Social Care (DHSC), SEND code of practice: 0 to 25 years; Information Commissioner's Office (ICO), records management framework.