IEP Meeting Prep
AI-built prep sheet for an IEP-style meeting, pulling your tracked behaviors and sensory profile into the asks automatically.
When to use this
Use IEP Meeting Prep the week before a school meeting. Pick the meeting type, the concerns you're walking in with, and Beacon builds a one-page prep sheet: top 3 asks, opening statement, data-backed concern cards (with behavior counts pulled from your logs), questions to ask the team, and a 'if they say no' script. Different from IEP Translator: this preps you for the meeting; Translator parses the document the school sends you.
How it works
Pick the meeting type
Six meeting types: Initial IEP, Annual review, Triennial re-eval, Amendment meeting, 504 plan, Manifestation determination. Each one shapes the legal framing and the questions Beacon includes.
Pick your concerns
Multi-select 10 concern chips: sensory, behavior, academic, communication, social-emotional, related services, placement/LRE, transition, aide/1:1, goals not met. Each becomes its own card in the prep sheet.
Add the specifics
Free-text for the things that aren't on chips. 'They want to move him to self-contained. We disagree. Last eval was 2 years ago.' Beacon uses this to shape the asks, not just add a footer.
Beacon pulls your data automatically
Behind the scenes: behavior counts from the last 30 days + your sensory profile non-neutral channels get woven into the concern cards. The amber note above the Build button reminds you this is happening.
What Beacon stores when you use it
generator_uses: Shared with all Workshop tools. tool_type = 'iep-prep'. content holds the structured prep sheet. Behavior + sensory data are READ at generation time, not stored on the row.
| Column | Type | Example |
|---|---|---|
| id | UUID | 8b3c... Auto-generated. |
| user_id | UUID | your-user-id RLS-locked. |
| tool_type | text | iep-prep Fixed. |
| inputs_json | jsonb | { "meetingType": "Annual review", "concerns": ["Sensory accommodations","Aide or 1:1 support"], "extraContext": "..." } Replayable inputs only. Behavior + sensory data is re-pulled each time you Discuss. |
| content | jsonb | { "title": "...", "cards": [{ heading, body, whyItWorks }], "plainText": "..." } Print-ready prep sheet. |
| used_at | timestamp | 2026-05-16T16:30:00Z Quota counter. |
A real example
Maya's annual review for 6yo Avery on Tuesday. Concerns: sensory accommodations, behavioral supports, aide/1:1. Tracked data: meltdown 12x/30d, stimming 47x/30d. Sensory: vestibular-seeking, auditory-avoidant.
| Card | Body |
|---|---|
| Top 3 asks | 1. Sensory break passes (3/day, parent + child request). 2. Trained 1:1 aide for unstructured times. 3. Noise-cancelling headphones in the IEP, not 'as available'. |
| Open with this | Thank you for meeting. Avery is making progress with the team, AND we have specific data showing where supports aren't matching. I want us to leave today with 3 concrete additions. |
| Sensory accommodations | Data: 47 stims/30d in our home logs, vestibular-seek + auditory-avoid profile. Ask: scheduled vestibular break every 90 min + noise-cancelling headphones written into accommodations, not 'as available'. Hook: IDEA requires accommodations be implemented as written. |
| Behavioral supports | Data: 12 meltdowns logged/30d, all in afternoon transitions. Ask: written transition protocol + sensory tools available at the moment of transition, not in the SPED room down the hall. |
| Aide or 1:1 | Data: meltdowns cluster in unstructured time (recess, lunch). Ask: trained 1:1 aide for unstructured periods specifically. |
| Questions to ask | 1. What FBA data do you have? 2. Who is responsible for implementing each accommodation? 3. How is fidelity tracked? 4. What is the escalation if the IEP isn't being followed? |
| If they say no | Script: 'I'm noting that we discussed [accommodation] and the team's position is [no]. Can we add this to the IEP notes? I want a written record of what was considered.' Then ask for it in writing. |
What Beacon auto-knows
- Every prep sheet you've generated + the meeting type + concerns each one targeted.
- Your child's behaviors logged in the last 30 days (count + emoji label).
- Your child's sensory profile non-neutral channels (the ones with strong seek/avoid patterns).
- Your child's name, age, motivator, regulator, communication style.
What Discuss with Beacon adds
- Discuss attaches the prep sheet. 'Make this firmer, this is our 3rd meeting' or 'add a CFR cite to card 3'.
- Or chain: 'Write the email I send to the team 24hrs before the meeting attaching this sheet.'
Try these with Beacon
“Reword this to be less confrontational. We need this team to like us.”
Reads the sheet. Rewrites the open + 'if they say no' card with collaborative framing ('I'm hoping we can partner on...'). Keeps the asks identical, softens the delivery.
“Add a 504 cite to back up card 2.”
Adds 34 CFR 104.33 (FAPE under Section 504) or 300.324(a)(2)(i) (behavior consideration under IDEA, depending on the meeting type) to card 2 with a 1-line plain-language paraphrase.
“We have 30 minutes only. Trim this sheet so I can use it.”
Returns a 1-page condensed version: top 3 asks, 2 questions, 1 'if they say no' line. Drops the lower-priority concern cards. Notes which were dropped so the parent can decide if any are non-negotiable.
“Write me the follow-up email to send after the meeting summarizing what we agreed.”
Drafts a polite-but-paper-trail follow-up: 'Thanks for the meeting yesterday. To confirm what we agreed: [list]. Please reply if I've misrepresented anything.' Sets up a written record.