Digital SEND pupil passport for international schools: what must travel

Digital special educational needs and disabilities (SEND) pupil passport for international schools: what must travel with the child

A family moves from Saudi Arabia to the UK. A pupil leaves a British-curriculum school in Qatar for a school in France. A parent carries a folder of reports, old support plans and email attachments, while the new special educational needs coordinator (SENCO) tries to work out which information is current.

For international schools, mobility can expose a records problem that is easy to miss while a pupil stays in one setting.

In brief: a planned digital SEND pupil passport could give a family a controlled, reviewable record of the pupil's current needs, voice, support and review history. It would not make the record legally recognised in another country, and it would not let sensitive information be sent to a school without checks. The receiving school would still need to verify the record, agree access and apply its own local requirements.

Product direction: MeritDocs currently supports pupil passport workflows with document versioning, controlled access, imports and exports inside its school workflow. A parent-held, portable digital passport account that can be carried between countries is a planned direction, not a live MeritDocs feature.

Why international mobility exposes the weakness in SEND records

A school may manage a pupil record well while the pupil stays in one setting. The weakness appears when the family, school or staff team moves.

An expatriate family may change country because of a new posting, a contract ending, a family decision or a change in schooling. The pupil may move from a school using a British curriculum to another school that uses the same broad language but a different support structure. Even inside one education group, the schools may be separate legal entities with different staff, systems and privacy notices.

The result is familiar:

the parent has several versions of the same report;
the old school knows the history but has no simple current summary;
the new school receives a large folder instead of a usable working record;
staff spend time checking whether a strategy is current;
the pupil has to explain the same needs again;
support starts slowly while adults reconstruct what has already been tried.

The problem is not that a school needs to preserve every note forever in the daily record. It is that the current picture is difficult to identify, verify and move.

What could a digital SEND pupil passport do?

The useful version would not be a giant digital file containing every assessment, email and historic observation. It would be a maintained summary connected to the supporting record.

A future digital passport could contain:

the pupil's preferred name, communication preferences and relevant identity details;
strengths, interests and what helps the pupil participate;
current barriers or areas where support is needed;
the pupil's own words, where appropriate;
parent or carer views, clearly attributed;
current reasonable adjustments and classroom strategies;
what has been tried and what appears to have helped;
the current plan, review date and named owner;
links or references to supporting reports, rather than an uncontrolled archive;
a visible version, approval date and change history;
permissions showing who can view, edit, approve or receive the record.

The record should also show what is not known. A missing assessment, tentative observation or unconfirmed report should not quietly become a permanent fact because a template expects an answer.

That distinction matters especially when the record crosses borders. A new school needs a reliable starting point, not a polished document that hides uncertainty.

Why the parent should be able to carry the record, but not control it alone

The parent is often the constant in an international move. Staff change. Campuses change. School systems change. Giving families a usable copy of the current record could reduce the chance of important information being lost between settings.

But "parent-held" should not mean "uncontrolled personal data account".

A safer model would give the parent meaningful access to a current, approved passport and a secure way to request or authorise a transfer. It would also preserve the school's responsibilities around accuracy, safeguarding, confidentiality, retention and access decisions.

The child matters here too. Under UK data-protection guidance, a child's information rights belong to the child. A parent may be able to act on the child's behalf, but that depends on the child's competence, parental responsibility and the circumstances. A future passport would need to reflect those distinctions rather than treating parental access as an unrestricted ownership right.

The transfer should therefore work more like a controlled handover than a public download link:

the current school reviews and publishes the record;
the parent or authorised adult requests a copy or starts a transfer;
the school checks identity, authority and the scope of the information;
the parent chooses the named receiving school or group entity;
the receiving school accepts the transfer and applies its own access rules;
the record is marked as received, reviewed and either adopted, amended or held pending further assessment.

This is slower than sending a link to anyone. It is also much more defensible for sensitive information about a child.

Portability is useful, but it is not a magic legal right to move the whole record

The Information Commissioner's Office (ICO)'s guidance on data portability describes a right to receive certain personal data in a structured, commonly used and machine-readable format, and in some circumstances to ask for it to be transmitted to another controller.

That right is narrower than the phrase "take the whole school record anywhere" suggests. It applies only in particular circumstances, including where the lawful basis is consent or contract and the processing is automated. It applies to personal data provided to the controller, not automatically to every professional judgement, derived assessment or third-party record held by a school.

A digital pupil passport should therefore be designed as a practical continuity tool, not marketed as proof that every part of a school record is portable by default.

The legal route for a transfer may instead involve a school's normal record-sharing process, a parent-authorised disclosure, a group-wide data-sharing arrangement, a subject access request, or a combination of these. The correct route depends on the organisations, the purpose, the information and the law that applies in each country.

That is why a credible product should make the scope of every transfer visible. The system should show what is being shared, who approved it, when it was sent, where it went and what happened afterwards.

A common standard can work across countries without pretending that SEND law is identical

A school group operating across the UK, Qatar and France may want a common record language. That is sensible. It does not mean the group can impose one country's legal framework on every campus.

The useful distinction is between a common operational structure and a common legal claim.

A group might standardise the questions it asks about current support:

What does the pupil need adults to understand first?
Which adjustments are current?
What does the pupil say helps?
What has changed since the last review?
Who owns the next action?
What evidence supports the current statement?

It could then map those fields to the local requirements, curriculum and terminology of each school. A UK school may work with SEN Support Plans or Education, Health and Care Plan (EHCP)-related records. A French school will have its own educational and legal context. A Qatar-based international school may work within local licensing, privacy and inclusion requirements alongside its chosen curriculum.

The common passport should make the pupil easier to understand. It should not claim that a British template is automatically valid everywhere.

What a multinational school group should require from the system

A group considering a cross-border SEND record should ask more than whether the supplier has a parent portal or a Portable Document Format (PDF) export.

1. Can the current record be distinguished from the archive?

The system should separate draft, approved, published and archived states. Staff in a new setting should not have to guess which of five attachments is current.

2. Is the record evidence-linked?

A summary should preserve the source and the voice behind important statements. It should not turn a parent report into a staff observation or infer a diagnosis that was never recorded.

3. Can the group set permissions by person, school and organisation?

A UK central team may need a different level of access from a campus SENCO. A receiving school may need access to the current passport without automatically receiving every historic document.

4. Is there a real export and exit route?

A school should be able to take its records out in a usable format, understand what is included and delete data when the retention period or contract requires it. A supplier that talks about portability but makes exit unclear has missed the point.

5. Can the buyer map the data flows?

The group should know which legal entities are involved, where the data is stored, which suppliers process it, what happens when a record is shared with another country and which transfer safeguards apply.

6. Does the supplier support a Data Protection Impact Assessment (DPIA) and a proper data-processing contract?

The ICO describes a DPIA as a way to identify and minimise data-protection risks before or while a project is designed. The buyer should expect a clear controller and processor model, a written data-processing agreement, sub-processor information, retention terms, deletion arrangements and incident processes.

7. Does the workflow preserve professional responsibility?

artificial intelligence (AI) may help organise evidence or draft a document. It should not decide what a pupil needs, approve a support plan or replace the judgement of the SENCO and relevant professionals.

Where MeritDocs fits today

MeritDocs is already built around the underlying record problem.

Its current workflow supports:

structured pupil passports with draft and published states;
version history, publishing, archiving and print output;
a Documents Hub that groups records by pupil and makes documents searchable and filterable;
document assignments, review context and lifecycle controls;
structured needs information that can preserve pupil and parent voice while avoiding unsupported diagnosis inference;
imports of existing plans and pupil data, with school staff reviewing and approving what is adopted;
Word, plain-text and print-ready PDF exports;
encryption before storage, access controls, two-factor authentication and recorded activity;
data stored and processed in the UK and European Union (EU), with AI drafting in the EU under zero-retention terms and pupil data not used to train models;
full deletion of customer data on exit, subject to the agreed contract and retention requirements.

The public security page also sets out the current security summary. That is useful evidence for procurement, but it is not a substitute for a school or group completing its own data-protection assessment. A supplier's blanket statement that an arrangement is compliant is not a meaningful answer on its own. The buyer needs to understand the actual data flow, roles, safeguards and contract.

A parent-controlled, cross-border passport account would be a further product direction. It would need careful design around identity, child rights, consent and authority, recipient verification, country-specific processing, record correction, revocation, expiry and the difference between a parent-held copy and a school's official working record.

That is exactly the kind of capability that should be co-designed with a serious international school group rather than invented in a sales deck.

A sensible pilot for a UK, Qatar and France group

A school group does not need to solve every country and every document type on day one.

A practical pilot could use one British-curriculum school in each of three settings and define a narrow passport containing:

pupil voice and parent voice;
current strengths, barriers and support strategies;
the current plan and next review date;
the owner responsible for keeping the record current;
a short list of supporting documents;
version, approval and transfer history;
permissions and a named receiving school.

The group should then test a real pupil journey:

create and approve the passport in the first school;
give the parent a controlled view;
initiate a move to the next school;
verify the recipient and the legal entity;
export or transfer the agreed record;
let the receiving SENCO review and accept it;
record what was amended after local assessment;
close or update the old access route.

Measure the boring things. How long did the handover take? Could the receiving SENCO identify the current support in two minutes? Did the parent understand what was being shared? Could the group explain where the data went? Were any fields misleading outside the original school's context?

Those answers are more useful than a glossy claim that the pupil has a passport.

The takeaway for international school leaders

A portable SEND record is a credible product direction because the underlying problem is real. International families move, schools change and support histories get fragmented. A current, versioned passport could reduce the amount of important information that disappears during the move.

But the passport must be designed as governed continuity, not unrestricted data ownership. Parents need meaningful access. Schools need professional control. Children need rights. Receiving schools need to verify the information. Every country involved needs its own legal and operational assessment.

MeritDocs already provides the document, passport, version and governance layer on which that direction could be built. For a UK-linked international school group, the opportunity is to develop a common record that makes SEND support more portable without pretending that every campus operates under the same law.

Review MeritDocs security and data controls or contact MeritDocs about a group pilot.

Frequently asked questions

Is the MeritDocs digital pupil passport available now?

Not in the proposed parent-held, cross-border form. MeritDocs currently supports pupil passport workflows, document storage, versioning, access controls, reviewed imports and exports. The portable account described here is a planned product direction.

This is a product direction we want to test with people who actually face the problem. If your school group, SEN team or family is dealing with a real cross-border SEND handover, email contact@meritdocs.com to receive development updates or help us test the workflow against a realistic scenario. Please share high-level, non-identifying details only at this stage, not pupil records.

Can a parent transfer the record to a new school?

Not automatically. A future workflow should let an authorised parent request or carry a current record, but the receiving school would need to be named, verified and willing to accept it. Local law, school policy, child rights and third-party confidentiality would still apply.

Would a digital passport replace an EHCP or local support plan?

No. It would be a continuity summary and a controlled route into the receiving school's assessment and support process. It would not replace an EHCP, a local statutory document, a professional report or the receiving school's own duties.

Does hosting data in the UK or EU settle the data-protection question?

No. Hosting location is one part of the assessment. The group still needs to understand controller and processor roles, lawful basis, special-category information, access, retention, deletion, sub-processors, international transfers and the relevant local law.

Sources and scope

This article is a product and operational perspective, not legal advice. The cross-border design would need review by the relevant data-protection leads and advisers in every country involved.