Advocacy Guide: Back It — Self‑Determination | MadlySane

Advocacy Guide: Back It — Self‑Determination

A calm, detailed guide to ask for what you need, back it with clear evidence, and protect your pace. Use only what helps, and keep your privacy intact.

What this guide does

Use this like a working folder: clarify your ask, collect proof that supports it (“Back It”), and send a simple, respectful request. Everything is optional, save locally if you prefer.

Privacy first

No required login. You can print, copy, or save drafts offline. If you choose to email someone, you decide what to share.

Quick start

Step 1 — Name your need

  • What: One sentence request (accommodation, schedule, support, clarity).
  • Why: One sentence reason tied to function, wellbeing, or fairness.
  • Outcome: What a “yes” changes in practice.
Request: I’m requesting a flexible 10‑minute buffer before meetings.
Reason: This supports my executive function and reduces shutdown risk.
Outcome: I’ll arrive regulated and prepared, improving participation and reliability.

Step 2 — Back it

Gather 2–4 small pieces that support your ask: logs, emails, policy excerpts, brief notes from a clinician or coach, performance examples.

Keep it short and relevant; you’re connecting dots, not proving your worth.

Step 3 — Send a kind, clear request

Use the email or letter template below. State the request, attach your “Back It” pieces, and suggest one simple next step.


Know your rights

Self‑determination means you choose: what to share, when to proceed, and how to define success. Depending on your context (school, workplace, healthcare), certain policies or laws protect reasonable requests for access, accommodation, and clarity.

  • Document context: School, work, healthcare, service provider, or public service.
  • Find the policy: Handbook, accommodation policy, service standards, grievance process.
  • Map fit: One sentence connecting your request to that policy or standard.

Note: Laws and processes vary by place and setting. Use official sources where possible; ask a trusted advocate if you’re unsure.


Prepare your ask

Clarity worksheet

  • Request: What exactly are you asking for?
  • Reason: How does this support your function, safety, or access?
  • Impact: What improves if the request is granted?
  • Alternatives: 1–2 acceptable options.
  • Boundaries: What’s not okay for you?

One‑paragraph script

Hi [Name], I’m requesting [request] because it supports [function/outcome]. I’ve included a brief set of notes that show where this helps in practice. My preferred start date is [date]. If that’s not workable, I can consider [alternative 1/2]. Thank you for considering this — I’m happy to answer questions.

Back It — evidence package

Choose 2–4 simple items. Label each with one sentence that ties it to your request.

Evidence menu

  • Brief log: 3–5 dated examples of when the need shows up.
  • Policy excerpt: One paragraph screenshot or quote with citation.
  • Performance example: Before/after when support was present.
  • Professional note: Short statement from clinician/coach (if you choose).
  • Email snippet: Relevant prior agreement or guidance.

2‑page “Back It” template

Page 1 — Summary
• Request: [one sentence] • Why now: [one sentence] • What changes: [one sentence] • Attachments list (2–4 items)

Page 2 — Attachments (labeled)
A. [type] — [1 sentence link to request] B. [type] — [1 sentence link to request] C. [type] — [1 sentence link to request]

Filename and email subject

Filename: 2025‑MM‑DD_Back‑It_[Your‑Name]_[Request].pdf
Subject: Request for [Request] — Back It summary attached

Meeting script

Opening

Thanks for meeting. My request is [request]. It supports [function/outcome], and I’ve prepared a brief “Back It” packet with 2–4 items. I’m asking to start on [date]. I can consider [alternative 1/2] if needed.

If pushed for personal details

I’m comfortable discussing how this affects my role and the supports that work. I prefer to keep personal health details private. The items I’ve shared show what’s needed for success.

Closing

Thank you. I’ll email a one‑paragraph summary and the “Back It” packet. If anything needs adjustment, I’m open to a small pilot and review date.

Follow‑up plan

Timeline

  • Day 0: Send request + Back It packet.
  • Day 5–7: Polite nudge if no response.
  • Week 2–3: Escalate per policy (cc supervisor/ombudsperson) if needed.
  • 30–45 days: Review outcomes; adjust or escalate.

Polite nudge email

Hi [Name], checking in on my [request] sent on [date]. I’m happy to answer questions and can start with [small pilot] if helpful. Thanks for your time.

Escalation, respectfully

Hi [Name], following up on my [request] submitted [date]. Attaching the Back It packet again. Per [policy/process], I’m cc’ing [role] to help us move forward. I appreciate your consideration.

Boundaries and safety

  • Your choice: You decide how much to share. Focus on function and outcomes.
  • Breaks: It’s okay to pause, regroup, or bring a support person.
  • Documentation: Save copies of requests, replies, and meeting notes.
  • Escalate when needed: Use the policy process; stay factual and brief.
In a crisis or if you feel unsafe, use local emergency options or trusted crisis resources. Online guides can’t replace immediate care.

Templates and copies

Email request

Subject: Request for [Request] — Back It summary attached

Hi [Name],
I’m requesting [request] to support [function/outcome]. I’ve attached a short “Back It” summary with 2–4 items showing where this helps. I’d like to start on [date]. If needed, I can begin with [small pilot] and review on [date].

Thank you for your time,
[Your Name]

Letter header

[Your Name][Role/Program][Date]
To: [Recipient, Title][Department/School/Clinic]
Re: Request for [Request] — Self‑determination and access

Meeting notes

Date/Time:
Attendees:
Request:
Agreed Next Step:
Review Date:
Open Questions:

Resources

Use official policy pages, program handbooks, and trusted advocacy organizations relevant to your setting and location. Keep links you actually use; aim for clarity, not volume.

  • Policy links: Accommodation, access, grievance, and timelines.
  • Local orgs: Advocacy centers, disability services, ombudsperson.
  • Support people: Who can attend, review, or debrief.

FAQ

Do I need to share a diagnosis?

No. You can focus on function, barriers, and supports that work. Share only what helps your request.

What if they say no?

Ask what would make a yes possible, offer a small pilot, or escalate per policy. Keep it brief and factual.

How much evidence is enough?

Two to four short, relevant items are usually sufficient. Quality over quantity.

© MadlySane. All rights reserved.