This source did not publish a separate summary. Review SKILL.md before using the skill.
SKILL.md
IEP 504 Meeting Kit Skill
Special-education meetings seat one amateur at a table of professionals who hold these meetings weekly — and hand that amateur the most important vote. Preparation is the equalizer: knowing the process shape, arriving with a written parent statement that enters the record, testing every proposed goal for measurability, and disagreeing — when it's time — in the specific procedural register that keeps options open. This skill builds that kit. It explains process in general terms (the specifics vary by jurisdiction and district — verify locally) and never diagnoses; the child's needs are established by evaluations, and the parent's power is making the plan match them.
What This Skill Produces
The process map — evaluation → eligibility → plan → services → review, in plain language, with where parents have formal moves (consent, disagreement, independent evaluations) — flagged as verify-your-jurisdiction
The parent-input statement — one page, written before the meeting, entered into the record
The goal-quality checklist — the tests that separate measurable goals from wishes
The meeting scripts — asking, clarifying, disagreeing-without-burning, and the don't-sign-today option
The paper-trail habits — the email-recap discipline that makes promises durable
Required Inputs
Ask for these if not provided:
Where in the process — requesting evaluation, first eligibility meeting, annual review, or a plan-isn't-working meeting; the kit differs sharply by stage
The child, as the parent sees them — strengths first (they anchor the input statement), struggles with concrete examples, what helps at home, what the child says
The documents in hand — evaluations, the current/draft plan, report cards, teacher emails, outside assessments; the kit works from what exists and lists what to request in writing
The relationship temperature — collaborative so far, or strained; the scripts calibrate, though the register stays professional either way
Framework: The Equalizer Rules
Write the parent statement before the meeting: one page — strengths, concerns with dated examples, what the parent wants addressed — submitted for the record. Spoken concerns evaporate; written ones must be responded to. It also front-loads the meeting with the parent's agenda instead of leaving them to react to the school's.
Goals must be measurable or they're wishes: every proposed goal gets the checklist — measured how? from what baseline? by when? reviewed how often? "Will improve reading fluency" fails; "from 60 to 90 words-correct-per-minute by March, progress-monitored biweekly with reports home" passes. The parent who asks "how will we measure that?" four times changes the document.
Accommodations need owners and mechanisms: "extended time" written down is not extended time delivered — ask who tells each teacher, who checks, and what happens when a substitute doesn't know. The implementation question is the difference between a plan and a PDF.
Disagree procedurally, not personally: the register is "I don't agree yet, and I'd like that noted — what are our options from here?" Parents can typically decline to sign on the spot, take the draft home, request the data behind a recommendation, and pursue independent evaluations or dispute processes — presented as flagged categories (rights vary by jurisdiction; verify the local version, and parent advocacy organizations exist for exactly this).
The paper trail is love, formalized: after every meeting and call, the two-line recap email — "Thanks — confirming we agreed X and Y, with Z to be checked by [date]." It's collegial, it's fast, and it converts goodwill into record. Between reviews, progress reports get calendared and actually read; a plan that isn't monitored quietly becomes decoration.
The Process Map (where you are, what's next, your formal moves)
[Plain-language map with the parent-decision points marked · verify-locally flag]
Parent-Input Statement (submit for the record)
[Drafted: strengths · concerns with dated examples · what we're asking the team to address]
Goal & Accommodation Review
Proposed item
Measurable/owned?
The question to ask
Meeting Scripts
Clarify: "How will we measure that, and from what baseline?" · Implementation: "Who ensures each teacher knows, and who checks?" · Disagree: "[the noted-disagreement line + options ask]" · Pace: "I'd like to review this at home before signing — what's the timeline for that?"
After the Meeting
[The recap email template · the progress-report calendar · the plan-isn't-working trigger and next step]
Special-education processes, timelines, and parent rights vary by jurisdiction and district — verify the local specifics (parent advocacy organizations and the district's own procedural-safeguards document are the standard sources). This kit organizes advocacy; it does not diagnose or give legal advice.
Quality Checks
The parent statement exists in writing before the meeting and enters the record
Every goal is tested for baseline, measurement, deadline, and review cadence
Every accommodation has an implementation owner and a check mechanism
Disagreement scripts keep procedural options open and the tone professional
Rights and timelines appear as verify-locally categories, never asserted specifics
Anti-Patterns
Do not diagnose or assert what services the child clinically needs — anchor asks in evaluations and observed data
Do not sign under time pressure — taking the draft home is a normal, script-supported move
Do not let strengths get skipped — they open the statement because the team plans better for a child than for a deficit list
Do not go adversarial by default — most teams want the plan to work; the kit's power is precision, not combat
Do not let the plan go unmonitored — an unread progress report is consent to drift