Back to the blog
6 min read May 8, 2026

How to build a year 11 SEND transition brief staff will actually use

A good transition brief is short, current, and easy to trust. Here is how to turn the live record into something staff can use on day one of the next placement.

How to build a year 11 SEND transition brief staff will actually use

The one-page rule

A transition brief should be short enough to read in one sitting and useful enough to guide action the same day.

That means one or two pages, not a bundle of attachments.

If a busy tutor, form teacher, or college support lead has to hunt for the point, the brief is already failing. The document should tell them what matters now, what has worked, what has not, and what to do next.

The best version is not clever. It is clear.

What the brief should answer

A good year 11 SEND transition brief answers six basic questions:

Who is the pupil now?

What support is currently in place?

What helps them learn, settle, and attend?

What makes things harder?

What has already been tried?

What should happen next?

If the brief cannot answer those questions quickly, it is too broad.

What to put in it

You do not need to include every detail from every meeting. You need the details that matter when the pupil moves on.

1. Current support

List the support that is live now, not the support that was used two terms ago.

2. Exam access arrangements and reasonable adjustments

These are often the first things a receiving setting needs to know because they affect day one planning.

3. Strengths and triggers

Keep this practical. What helps the pupil settle, focus, and recover? What tends to make things harder?

4. Attendance or timetable barriers

If attendance, anxiety, transport, or fatigue are part of the story, say so plainly.

5. Family views and pupil voice

Do not paraphrase the useful bit into something vague. If the pupil has said a particular support makes a difference, keep that visible.

6. Next actions

Always include the next action, the owner, and the date.

A quick build process that works

You can usually build a decent brief faster than people think, provided the source record is clean.

Step 1: Pull the live record

Start from the current version of the support plan, review notes, and agreed actions. Do not start from old emails.

Step 2: Cut repetition

If the same point appears in three places, keep the clearest version once.

Step 3: Rewrite in plain English

This is a school document, not a policy essay. Use short sentences. Use concrete language.

Step 4: Put the next step near the top

The recipient should not have to read the whole thing to know what happens first.

Step 5: Check whether it works for someone new

Read it as if you had never met the pupil. If it is confusing, it is not ready.

Step 6: Export and share the right version

The brief should be easy to send to the right people without rebuilding it from scratch every time.

MeritDocs keeps SEND documents in one searchable hub, so staff can filter by pupil, see what is current, and export when needed. That matters because the easiest brief to use is the one built from a live record, not a scavenger hunt.

What a good brief sounds like

Good:

"Current support is daily check-in, reduced processing load, and a quiet start to lessons."

"The pupil settles better when instructions are given once, then checked back."

"Next action: review travel anxiety with family and tutor by 15 May."

Bad:

"Supports in place as discussed."

"Continue with strategies."

"Monitor progress and follow up."

The bad version may look tidy, but it does not help anyone act.

What not to include

A brief is not the place for every historic concern.

Leave out:

old interventions that no longer matter

duplicate meeting notes

long quotations that do not change the next step

policy language that staff will skim past

anything that is already captured elsewhere and does not change use in practice

The goal is not completeness for its own sake. The goal is use.

How this helps schools in real life

A useful transition brief saves time in three places.

First, it saves SENCO time because they do not have to rebuild the story for every handover.

Second, it saves teacher time because they can see what matters before the first lesson.

Third, it saves parent time because they are not asked to explain the same support needs again and again.

That is the deeper value of proper record keeping. It reduces friction.

Patchwork systems work until they do not. Shared drives, inboxes, paper folders, and old Word documents can keep a school going, but they are poor at giving staff one dependable version of the truth.

MeritDocs helps schools run this properly by keeping SEND documents in one place, with current information easier to find, review dates visible, and exports straightforward. The real gain is not just speed. It is a record people can actually rely on when the pupil changes teacher, tutor, or setting.

A simple template you can copy

Use this structure:

Pupil name and year group

Current support in place

What works

What makes things harder

What has already been tried

Exam access arrangements or key adjustments

Parent and pupil priorities

Next action, owner, date

Review date

That is enough for most transitions.

FAQ

Should the brief go to the receiving college or sixth form?

Yes, if that is part of the normal transition process and the school has a lawful reason to share it.

Does it need to be long?

No. If it runs beyond two pages, it probably contains too much history.

Who should own it?

Usually the SENCO or the person coordinating transition, with input from tutors and support staff.

Should parents see it?

Yes, where appropriate. It should reflect a shared understanding of the pupil, not a private school-only note.

The takeaway

A year 11 SEND transition brief should make the next adult's job easier, not harder. If it is short, current, and specific, it will actually be used. If it is bloated, vague, or out of date, it will be ignored.

MeritDocs is useful here because it keeps the live record in one searchable hub, so staff can build and export a brief from something current instead of piecing it together after the meeting.