Inclusion Radar: Using AI to Scan Policies, Plans and Paperwork for Red Flags

A lot of exclusion happens quietly, inside documents — school policies that sound neutral but block access, service agreements that shift responsibility onto you, and codes of conduct that punish disability or trauma responses. Inclusion Radar helps you scan for red flags, highlight barriers, and ask sharper questions — supporting your own judgment instead of replacing it.

Variable Time
High Insight

Policies, plans and official documents can quietly shape who gets access, who bears risk, and who gets blamed. Reading and challenging them can be exhausting, especially if you’re already navigating disability, trauma or complex support needs. This guide explains how to use Inclusion Radar gently and safely, as a companion for advocacy work — not a substitute for human help.

What Inclusion Radar Is (and What It Isn’t)

Inclusion Radar is an AI helper built to review documents through a disability- and inclusion-aware lens — from school and uni policies to service agreements, workplace rules, or “information packs.” It helps you spot language that excludes or shifts burden, and suggests questions that protect your rights and options. But it’s not a lawyer, not a replacement for human advocates or unions, and not a guarantee that a policy is safe. Think of it as a highlighter and conversation starter.

When and How to Use Inclusion Radar

1

When to Use It

Use Inclusion Radar when you’re asked to sign or follow new policies — school behaviour rules, service agreements, updated codes of conduct, workplace standards, or health service terms. You can also use it before signing, to test whether a policy is equitable, or during systemic advocacy to show where inclusion is missing.

2

Prepare Documents Safely

You don’t have to paste in full documents. Remove names or IDs, focus on the policy wording, and work in sections. Add a short context line like “This is from a disability service agreement” so the AI can focus on relevant issues. That way, you protect privacy and get more accurate readings.

Key Questions Inclusion Radar Explores

When you give it a document, Inclusion Radar looks through a disability and inclusion lens. It asks questions like:

  • Does this policy assume everyone is non-disabled, resourced, and regulated?
  • Are reasonable adjustments, flexibility or support clearly stated?
  • Where are complaint pathways and rights mentioned — or missing?
  • Does it shift responsibility from the system to the individual?
  • Is there language that stigmatizes or pathologizes disability or trauma?

You can simply ask: “Please review this text for access and inclusion issues. Show me red flags, missing protections, and questions I should ask.”

Example Workflows

Workflow 1: School Behaviour Policy

Paste sections about suspension, attendance, or behaviour. Ask Inclusion Radar to identify missing adjustments and red-flag wording. It might highlight automatic punishments, vague terms like “persistent disruption,” or lack of review processes. Use that output to write questions for the school or share with an advocate.

Workflow 2: Disability Service Agreement

Focus on clauses about cancellations, privacy, fees, or complaints. Ask it to translate the text into plain language, show risks or power imbalances, and generate questions to ask before signing. It might help you ask, “What happens if you cancel?” or “How can I end this agreement safely?”

Workflow 3: Workplace Policy

Provide sections about conduct, leave, or performance. Ask Inclusion Radar to check for fairness, adjustments, and supportive options. It might reveal unfair clauses or vague expectations. Bring results to your union, HR contact, or advocate for next steps.

Helpful Prompt Patterns

Try these reusable prompts:

  • Spot the red flags: “List any red flags for disabled, neurodivergent or marginalised people. Explain why each matters.”
  • What’s missing? “What rights or protections seem to be missing for disabled or caring people?”
  • Turn this into advocacy questions: “Write questions I could send to clarify rights and adjustments.”
  • Translate into plain language: “Explain what this policy actually means, and what happens if someone can’t comply.”

Limits and Safety Notes

Inclusion Radar is still an AI tool. It can miss nuance, misunderstand law, or overstate risk. Use it as a first pass, not a verdict — a way to prepare before consulting humans. Protect privacy by removing names or identifiers and avoid using it on unsafe work devices or networks.

Using Inclusion Radar Alongside Other Tools

Inclusion Radar fits into a broader advocacy toolkit. Use it to spot issues, then apply tools like EduLinked’s NDIS Navigator or EduPsyched AI for planning and follow-up. Human advocates, unions, and legal services should always lead strategy and risk decisions. AI supports your language; humans bring ethics, context, and care.

A Gentle Way to Start

Start with a low-stakes policy — like a school info sheet. Copy one section and ask: “Scan this for inclusion issues, what might be a problem or missing, and what questions I could ask.” See if it notices patterns or language you missed. Gradually use it for more complex documents as you build confidence.

Policies are where inequity often hides. You shouldn’t have to decode them alone, especially while managing fatigue or systemic barriers. Inclusion Radar can’t make systems fair, but it can stand beside you — highlighting risks, missing rights, and unfair clauses — so you enter every policy conversation with more information, more language, and more power.