Back to the blog
8 min read July 18, 2026

How to build a SEND parent communication plan that does not depend on memory

A clear parent communication plan helps schools keep promises, record decisions and prevent small misunderstandings becoming larger SEND disputes.

How to build a SEND parent communication plan that does not depend on memory

Most problems with SEND parent communication do not begin with one terrible conversation. They begin with a promise that was not written down, a follow-up that had no owner or an update that stayed in one person's inbox.

When the SENCO is covering absence, the class teacher changes or a meeting gets moved, the gaps become visible. The parent remembers what was agreed. The school remembers part of it. The pupil is left waiting for the next step.

A good communication plan is simple: **record what the family needs to know, what the school has agreed to do, who owns it and when the next contact will happen.** It should support a relationship, not turn every conversation into a form-filling exercise.

Why a communication plan helps

SEND communication is often spread across email, phone logs, meeting notes and the pupil's support record. Each channel has a place, but the school still needs one dependable account of the decision that matters.

Without that, staff can make three common mistakes:

  • asking a parent to repeat information they have already provided
  • giving different answers because the latest decision is not visible
  • assuming someone else will make the promised follow-up contact

These mistakes waste time and damage trust. They also make it harder to understand whether the school has acted on what was agreed.

A communication plan does not mean contacting families constantly. It means making contact purposeful and making the next step clear.

Start with the points that need a planned conversation

Do not begin by creating a log for every message. Identify the moments where communication has the greatest effect on support:

  • a new concern or referral
  • the start of SEN Support
  • a review of provision or outcomes
  • a change to an adjustment or intervention
  • a transition between classes, phases or schools
  • a parent request for information
  • a complaint or disagreement about what has happened

For each point, agree the minimum information staff should capture. This might be the date, the people involved, the main issue, the decision, the action owner and the next contact date.

The record should be factual. It should distinguish what the parent said, what the school explained and what was agreed. Do not turn it into a judgement about the family.

Use a clear contact structure

A useful entry can fit into six short parts:

  1. **Reason for contact:** why the conversation happened.
  2. **Information shared:** the relevant facts or update.
  3. **Parent or pupil view:** what they asked, disagreed with or wanted considered.
  4. **Decision:** what was agreed, including anything that was not agreed.
  5. **Owner:** the named person responsible for the next action.
  6. **Next contact:** when and how the school will update the family.

This structure stops the record becoming a transcript. It captures the part that another member of staff needs if they take over tomorrow.

For example, "spoke to mum, discussed attendance" tells the next person almost nothing. "Parent reported that noisy lunch arrangements are increasing morning anxiety. SENCO to speak with pastoral lead by Friday. School to call parent on 24 September with the agreed adjustment and review date" gives the conversation a usable outcome.

Make promises visible

The most important part of a communication record is often the least formal: what the school said it would do.

Create a short action list alongside the contact record. Every action should have:

  • one owner
  • one due date or review point
  • a status
  • a link to the relevant pupil document or decision

Avoid assigning an action to a team. "SEN team to follow up" sounds collaborative but hides responsibility. One person can own the action while other staff contribute.

If the school cannot meet the promised date, record the new date and tell the family. Silence is what turns a delay into a trust problem.

Keep the pupil's voice in the record

Parent communication is not only about adults. The child's or young person's view should be included where relevant, using their own words when possible.

Do not convert a pupil's comment into a polished summary that changes its meaning. Record the quote, explain the context and show how it affected the decision. A pupil who says, "I cannot think when everyone talks at once," has provided useful information about a barrier. That is more actionable than a vague note that the pupil struggles with busy environments.

The same applies to parent concerns. A record should not flatten disagreement into "parent unhappy". State what the concern was and what the school did with it.

Decide what belongs in the live SEND record

Not every email needs to become a permanent part of the pupil record. The test is whether the contact changes, explains or evidences the support decision.

Keep information that helps staff understand:

  • the current need or barrier
  • an important change in circumstances
  • the provision being considered or delivered
  • the parent's or pupil's view
  • a decision and its reason
  • an action or follow-up commitment

Do not copy long email chains into the record without extracting the decision. A large pile of messages can make the important point harder to find.

Schools also need to handle personal data carefully. Use the school's approved systems, restrict access to people who need it and follow the retention arrangements that apply to the record. A communication log is not a reason to create uncontrolled copies in personal inboxes or local spreadsheets.

Build the plan around the school calendar

Communication becomes easier when it is planned at the points families already need information. For example:

**Before a new term:** confirm any changes to staff, timetable, access arrangements or key routines.

**After the first few weeks:** check whether the agreed support is happening as intended and whether the pupil has identified a problem.

**Before a review:** tell the family what evidence will be considered and invite their view in enough time to use it.

**After a review:** send a clear summary of what changed, who is doing what and when the next review will be.

**Before a transition:** confirm what information is being shared, who the receiving staff are and how the family can raise a concern.

This is better than waiting for communication to become urgent. It also helps staff separate routine updates from decisions that need a formal review.

What to do when communication breaks down

When a parent says the school has not followed through, do not start by defending the record. Start by checking it.

Look for four things:

  1. What did the school say it would do?
  2. Was a person named to do it?
  3. Was a date agreed?
  4. Is there evidence that the action happened or was explained if delayed?

If the answer is no, say so plainly and repair the process. A defensible record is not one that makes the school look perfect. It is one that shows what happened, what was missed and how the school responded.

MeritDocs keeps SEND documents in one searchable hub, so staff can see the current support record and export the document they need without reconstructing the history from separate emails. That makes it easier to prepare for a difficult conversation and harder for a key decision to disappear when staffing changes.

A short weekly check for SENCOs

A weekly 20-minute review can keep the plan alive. Check:

  • contacts promised for the next seven days
  • actions that are overdue
  • reviews that need a parent contribution
  • recent changes not yet reflected in the current record
  • families waiting for a response
  • pupils whose views have not been captured recently

Do not turn this into a meeting for its own sake. The output should be a small list of actions with owners and dates.

If the school has to maintain the list by comparing four spreadsheets and several inboxes, the workflow is already costing too much. A live record should reduce checking, not create another administrative ritual.

FAQs

Does every phone call with a parent need a formal record?

No. Record contact when it contains information, a concern, a decision or an action relevant to the pupil's support. Keep the entry concise and factual.

Should parents receive a copy of every communication log entry?

Not necessarily. Follow the school's information governance and access procedures. Families should receive the information and decisions they need, while the school should keep an accurate internal record of the contact and follow-up.

How can a school avoid sounding defensive in its records?

Separate fact from interpretation. Record what was said, what was agreed and what happened next. Avoid labels such as "difficult parent" or "refused to engage" unless there is a precise, relevant fact behind the description.

The standard worth aiming for

A parent should not have to restart the story every time they speak to the school. A teacher should not have to guess whether an adjustment is current. A SENCO should not have to search an inbox to find the action that was promised last week.

The answer is a communication plan linked to the live SEND record. MeritDocs gives schools a practical way to keep current documents findable, filterable and exportable, while the school's own process determines what should be recorded and who acts on it.

The gain is not more paperwork. It is fewer broken promises and a clearer path from what a family says to what the school does next.

Sources