Home/Blog/How to Draft a 504 Plan Accommodation Menu
Blog

How to Draft a 504 Plan Accommodation Menu

P
promptstudio
How to Draft a 504 Plan Accommodation Menu

504 menus fail when they look like a diagnosis and a legal memo. The model invents an evaluation score, a student name, and a guarantee that the school must do X. You paste it into a meeting. Counsel flinches. The job is a de-identified menu of accommodations drawn only from the notes you have, with a not-legal-advice banner, and no minted PII.

The matching generator is the 504 Plan Accommodation Menu (No PII, Not Legal Advice) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled menu survives a PII and claims check, share the version you actually use (Share a prompt).

De-identify first. Then organize.

Document type is a 504 accommodation menu, not a plan the school has adopted. Notes paste: needs the family or team already described, current classroom facts, and any accommodations already in use, with names stripped. Setting: school type only if you named it, not a fake district. De-identify rules: no student name, no DOB, no school name if it identifies, no parent emails, no medical record numbers. Banner: not legal advice, not medical advice, not a determination of eligibility. Audience: family prep, teacher brainstorm, or advocate notes, as you stated.

The first block is a scrub list: what was removed. If the generator still prints a first name, the run failed.

The menu is a list of candidate accommodations that match the needs in Notes. Each item: the need as stated, a possible classroom move, what it would take to try, and what is unknown. It is not "the school shall." It is not a diagnosis.

No invented eligibility, scores, or mandates

Eligibility, impairment labels, and evaluation scores may appear only if they are in Notes. Do not add ADHD, anxiety, or a percentile. Do not add an IEP if the notes say 504. Do not convert a parent concern into a medical claim.

Accommodations: only those that follow from stated needs, labeled as options to discuss, not as entitlements. If Notes say extra time is already used, it can appear as current. If Notes do not mention a scribe, do not add a scribe because it is common. Common is not in Inputs.

Times, frequencies, and staff roles: only if in Notes. Do not invent a 50% extra time. Do not invent a 1:1 aide. Do not name a counselor who is not in Notes.

If jurisdiction is missing, write unknown. Do not cite a statute. Do not quote OCR guidance from memory. This card is a menu, not a brief.

Banner, open questions, and a meeting packet that does not leak

Not-advice banner belongs at the top and stays there. Open questions: missing current plan, missing teacher input, missing what was already tried, missing whether this is 504 or something else the notes did not specify. Gaps: missing setting, missing language access, missing whether the student is named in attached PDFs you should not paste.

De-identify attached text. If you pasted an evaluation excerpt, strip identifiers before the model sees them when you can. If you cannot, the scrub list must catch them.

Banned words: best, guaranteed, #1, must, entitled, unless those words are in a quote you are flagging to cut. The compliance pass should quote leaks.

If Notes include a Friday meeting, that date can appear as a meeting date. It cannot appear as a legal deadline the model invented. Budget not approved for a private eval stays a fact. It does not become "the district will pay."

A worked pass: needs list, no PII, no quotes

Say Notes have three functional needs (extended time already tried, noise, written instructions), a Friday meeting, and no medical quotes. The menu can group options under those three needs. It cannot add a student name. It cannot add a diagnosis. It cannot add a guarantee.

If a later official plan lists current accommodations, paste the de-identified list and rerun so current vs. candidate is clear. Do not keep invented aide language from the first run.

Watch copy-paste into portals. The output should be easy to re-identify locally by the user if they choose, but the generated file should stay generic (Student, Grade band if given, School type if given).

Secondary structure: a one-page menu and a question list for the meeting. The question list is questions, not demands.

Fill the card, then run

Paste de-identified notes, the banner requirement, and the audience. Leave names out.

Document type: [Type]
Facts / notes paste: [Notes]
Jurisdiction or setting if any: [Setting]
De-identify rules: [DeID]
Not-advice banner required: [Banner]
Audience: [Audience]

A 504 menu is a discussion list. When a run keeps a diagnosis off the page because Notes never named one, share that filled card.