Skip to content
Back to the blog
9 min read August 25, 2026

The blank-page problem: how to use a SEN support plan generator in UK schools

A SEN support plan generator should reduce blank-page work, not invent evidence. This guide shows UK schools how to move from recorded information to an approved, reviewable plan.

Call it the blank-page problem: a school already holds useful evidence, but the special educational needs (SEN) support plan still starts in an empty document. A SEN support plan generator should reduce that repeated work without deciding what a pupil needs, turning missing evidence into facts, or approving its own output.

The safe workflow is simple: gather the evidence, keep different voices clear, agree the outcomes and provision, review the draft, then keep the approved plan current.

What should a SEN support plan generator actually do?

A SEN support plan generator is a tool that helps staff organise recorded pupil information into a support-plan structure. Depending on the product, it may help with sections such as pupil strengths, barriers to learning, pupil and family views, areas of need, outcomes, provision and review arrangements.

That description matters because the word "generator" can imply more automation than a school should accept. A fluent paragraph is not evidence. A suggested target is not an agreed outcome. A document that looks complete is not necessarily ready to share.

In England, the special educational needs and disabilities (SEND) Code of Practice provides the framework for the graduated approach. The plan should help staff assess, plan, do and review support with the pupil and their parents or carers involved. A generator can support the document workflow, but it cannot make those decisions for the school.

1. Start with the evidence the school already holds

Do not begin by asking a tool to write a plan from a diagnosis or a broad description such as "struggles with attention". Begin with the information that helps another adult understand what happens in the setting.

Useful source material may include:

  • the pupil's strengths and interests;
  • current barriers to learning or participation;
  • examples of what happens in a defined context;
  • strategies already tried and what happened next;
  • the pupil's own words;
  • parent or carer views;
  • relevant professional advice;
  • the previous approved plan and its review evidence.

The source does not need to be perfect before you start. It does need to be honest. If the school has not yet observed how a strategy works, record that as something to test. Do not turn it into a confident statement because the form has an empty box.

A good first question is: what does another member of staff need to know to support this pupil tomorrow?

2. Keep different voices and evidence types separate

A pupil quotation, a parent report, a teacher observation and a specialist recommendation do different jobs. A support plan becomes less trustworthy when they are blended into one polished paragraph.

Keep track of:

  • who provided the information;
  • when it was recorded;
  • the context in which it applies;
  • whether it is confirmed, reported or still being tested;
  • what decision the school has made from it.

For example, "I find the dining hall too noisy" is the pupil's voice. "The pupil leaves the dining hall before eating" is an observation. "Offer a quieter lunch space" is a proposed adjustment. They may belong in the same plan, but they are not the same statement.

This distinction is especially important when artificial intelligence (AI) is involved. The Department for Education says schools need to consider accuracy, appropriateness and data protection when using generative AI in education. The person approving the final plan remains responsible for the record.

3. Turn evidence into a small number of useful outcomes

A plan does not become stronger because it contains more targets. Choose the changes that matter most for the pupil and the setting.

A useful outcome should make clear:

  • what the pupil will be able to do;
  • in which context;
  • by when;
  • how staff will recognise progress;
  • what support will be available while the pupil is working towards it.

Avoid targets such as "will improve confidence" or "will develop communication skills" unless the plan explains what those changes will look like in practice.

A stronger example might be:

By the six-week review, the pupil will begin the first step of an independent writing task within three minutes in four of five observed English lessons, using the agreed visual prompt.

The measure should fit the need. A percentage is not automatically better than a frequency, a work sample, a short observation or the pupil's own account. The test is whether the review will have enough information to decide what to continue, change, stop or investigate.

4. Review the generated draft before anyone relies on it

A generator should give staff something useful to work with, not something they are expected to accept because it sounds professional.

Before approval, check every section against the source material. Look for:

  • claims that are more certain than the evidence;
  • strategies presented as though they have already worked;
  • pupil or parent views that have been paraphrased beyond recognition;
  • targets with no baseline or review method;
  • provision with no named owner or agreed frequency;
  • advice that belongs in a healthcare plan, risk assessment or professional document instead;
  • review dates that do not match the school's agreed process.

The landing-page workflow shows this review stage directly. The wizard groups pupil information, pupil and family views, areas of need, and outcomes and provision before the plan is generated. The draft then sits in a visible document state where staff can review it before approval.

The point is not that every generated sentence is correct. The point is that the workflow makes the source sections and the approval decision visible.

5. Treat imported records as evidence to review, not text to trust blindly

Many schools will start with existing Word documents, Portable Document Format files (PDFs), scans or photographs of paper plans. A useful generator should help staff bring that information into a workable structure without pretending that every local format means the same thing.

Review the import before it becomes part of the live record. Ask:

  • What mapped into the new structure?
  • Which sections need checking?
  • What content did not map cleanly?
  • Is the original source still available?
  • Are warnings and uncertainty visible to the person approving the result?

The import screen below shows the kind of information a school needs before confirmation: warnings, unmapped content and a coverage signal. Those numbers are not a judgement about the pupil or the quality of the original plan. They are a prompt for a member of staff to inspect what happened.

MeritDocs supports best-fit mapping from PDFs, Word files and photographs of paper plans. Because SEND documents vary between local authorities and settings, imported content still needs professional review. A system that hides the unmapped material is making the wrong kind of promise.

6. Keep the approved plan useful after it is written

The first draft is only one moment in the plan's life. Staff need to find the current version, understand what has changed and know when the next review is due.

After approval, check that the plan has:

  • a clear current version;
  • a named review owner;
  • a real review date;
  • the agreed provision and outcome;
  • the evidence that will be collected;
  • a clear route to the previous version and review decision;
  • access for the adults who need the information;
  • an export route when the school needs to share or retain a copy.

A short pupil-facing or staff-facing summary can also help, but it should not replace the full record. It should point adults towards the current support and make the next action clear.

The passport view is useful because it turns reviewed information into a concise guide for adults supporting the pupil. It should remain linked to the wider record and be updated when the evidence or agreed support changes.

Can a SEN support plan generator write a plan without a diagnosis?

A school should respond to a pupil's identified needs and barriers rather than waiting for a diagnosis before offering appropriate support. The plan should describe the evidence the school has, the support being tried, the pupil and family views, and how the school will review its impact.

For more detail, see how to write a SEN Support Plan without waiting for a diagnosis.

Can it replace the special educational needs coordinator (SENCO)'s judgement?

No. A generator can help structure information, suggest wording and reduce repeated document work. The SENCO and relevant school staff still need to check the evidence, agree the plan, involve the pupil and family, and decide what happens at review.

The safest description is AI-assisted drafting with professional approval. It is not automatic decision-making.

What should a school ask before choosing one?

Before adopting a SEN support plan generator, ask the supplier to demonstrate a realistic pupil journey rather than a polished blank-screen demo.

Check whether the product can:

  • work from recorded evidence rather than a generic prompt;
  • keep pupil, parent, staff and professional voices distinct;
  • show what is missing or uncertain;
  • support the document structures the school actually uses;
  • let staff edit, reject and approve proposed wording;
  • show what happens during import from a PDF or scan;
  • keep current and previous versions visible;
  • make review arrangements clear;
  • protect sensitive pupil data and explain the AI processing;
  • export the record if the school needs to move or share it.

MeritDocs is a lean AI-enhanced SEND platform for school plans, pupil passports, provision mapping, reviews and reporting. Its Document Wizard helps staff create structured SEN Support Plans and profound and multiple learning difficulties (PMLD) plans from recorded information, while the Documents Hub keeps SEND documents findable, reviewable and exportable. Staff remain responsible for checking and approving the final document.

The practical test

Read the generated plan as if you were covering the class tomorrow. Can you tell what the pupil needs, what staff should do, what evidence matters, who owns the next step and when the plan will be reviewed?

If the answer is yes, the generator has helped with the right job. If the document is polished but the evidence, uncertainty or next action is unclear, the school has gained prose rather than a dependable support plan.

Sources