A complaint is what you file when you have raised a concern and working it out with the school and the matter has not moved. It is a response to stalled process.

You do not need to exhaust yourself before you have the right to escalate. If you have clearly explained the issue, given the school a reasonable chance to respond, and the situation is unchanged, you have already done enough to consider a complaint. The threshold is lower than most families are led to believe — and the belief that it is higher is itself part of what keeps families struggling.

This page is here to help you decide three things: whether a complaint makes sense right now, what it will and will not do, and how to use it without losing sight of what is actually happening to your child.

When a complaint makes sense

A complaint is usually the right next step when:

• you have raised the issue and there has been no meaningful change
• support is missing, inconsistent, or not actually implemented
• your child’s access to education is being reduced or denied
• meetings and communication are not producing action
• you are being asked to wait, but nothing is improving

You do not need dozens of meetings, months of delay, or a perfect evidence binder. Those are thresholds the system benefits from, not thresholds the process actually requires.

What a complaint does

A complaint creates a formal written record. It requires a response. It moves the issue beyond the immediate school. It can trigger review or investigation.

Sometimes it produces change. Sometimes it does not. It always produces a record — and that record can matter later, in ways that are difficult to see from inside the current moment.

What a complaint does not do

A complaint does not guarantee quick resolution, the outcome you want, immediate improvement for your child, or protection from delay. The process can be active, responsive, and entirely sincere on the school’s side while your child’s situation remains exactly as it was.

This is not a reason to avoid filing. It is a reason to file with your eyes open.

Deciding whether to file now

The question is not have I tried hard enough. That framing belongs to the system, and it has no upper limit.

The question is will filing a complaint help my child right now.

Sometimes the answer is yes, because you need a record, because the school is not responding, or because escalation may shift how the situation is handled. Sometimes the answer is to file and also take other steps in parallel, or to try one more direct conversation first while preparing to file if it fails.

This is a strategic decision, not a moral one. You are not being judged on how long you waited.

%%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#fbfaf3', 'primaryBorderColor': '#e69632', 'lineColor': '#000000'}}}%%

flowchart TD
    Start([Something is wrong at school<br/>and you are considering<br/>a formal complaint]) --> Q1{Have you raised<br/>the issue directly<br/>with the school?}

    Q1 -->|No| Raise[Raise it in writing first.<br/>A complaint without<br/>a prior ask is weaker<br/>and easier to deflect.]
    Raise --> Q2

    Q1 -->|Yes| Q2{Did the school have<br/>a reasonable chance<br/>to respond?}

    Q2 -->|No, still within window| Wait[Wait the baseline window.<br/>Keep dated records<br/>of what you asked<br/>and when.]
    Wait --> Q2

    Q2 -->|Yes| Q3{Has the situation<br/>materially improved?}

    Q3 -->|Yes| Monitor[No complaint needed now.<br/>Keep records in case<br/>the issue recurs.]

    Q3 -->|No| Urgent{Is harm continuing<br/>right now?<br/><br/>Safety risk, exclusion,<br/>denied access, or<br/>discrimination.}

    Urgent -->|Yes| FileNow[File now.<br/>Urgency lowers the<br/>threshold, and the record<br/>itself may shift the response.]

    Urgent -->|No| Purpose{What do you<br/>most need from<br/>this step?}

    Purpose -->|A formal record| FileRecord[File.<br/>The record is the point.<br/>Outcome is secondary<br/>but welcome.]

    Purpose -->|A response the school<br/>has refused to give| FileResponse[File.<br/>A complaint forces<br/>a written reply where<br/>informal asks have not.]

    Purpose -->|Movement on a<br/>stalled matter| FileMove[File.<br/>Escalation can shift<br/>how the situation is<br/>handled, even when<br/>outcome is uncertain.]

    Purpose -->|Mainly to be heard<br/>or acknowledged| Pause[A complaint may not<br/>deliver this.<br/>Consider advocacy,<br/>peer support, or a<br/>direct conversation first.]

    Purpose -->|Not sure yet| Clarify[Name the specific change<br/>you want for your child.<br/>Then return to this question.]
    Clarify --> Purpose

    FileNow --> Parallel{Is filing enough<br/>on its own?}
    FileRecord --> Parallel
    FileResponse --> Parallel
    FileMove --> Parallel

    Parallel -->|Yes| FileOnly[File the complaint.<br/>Keep focus on what<br/>changes for your child<br/>while it is reviewed.]

    Parallel -->|No, child's access<br/>is still at risk| FilePlus[File the complaint<br/>and take parallel steps:<br/>safety measures,<br/>external supports,<br/>or a separate escalation track.]

    Pause --> Revisit[Revisit this decision<br/>in days, not weeks,<br/>if the situation<br/>does not improve.]

Keep your focus on the child

Once a complaint is underway, the process can quietly become the thing you are managing, rather than the situation it was meant to address. That drift is one of the most common and most costly features of formal complaint work.

Keep asking: what has changed for my child, what has not, and what is happening to them right now while this is being reviewed? A complaint is useful when it contributes to change. It is not sufficient on its own, and it is never the point.

What to read next

• Complaint types — which pathway fits your situation

Closing insight

You do not need permission to escalate. You already have it.

The question is how to use that step in a way that still centres your child, rather than the process you are being asked to participate in.