A 504 accommodation almost always gets written for the classroom it was drafted in. "Preferential seating." "Breaks as needed." "Extended passing time." Those phrases make sense to you, in your room, on a normal day. They fall apart the moment the student is in the hallway during a fire drill, in a substitute's class, or in the gym with a teacher who's never read the plan. An accommodation nobody outside your room can execute isn't really an accommodation - it's a private agreement between you and the student that happens to be on file.
The test: could a sub run this cold?
Before finalizing any accommodation language, run it through one question: if a substitute picked up this plan with zero context, could they carry it out today, correctly, on the first try? If the answer requires "well, normally I just..." - the accommodation isn't written specifically enough yet.
Take "extended passing time." That phrase means nothing to someone who's never covered your class. Extended by how much? Starting from where? Does the student need a pass, an early-release signal, or a specific alternate route? A hallway monitor stopping a student five minutes after the bell has no way to know this student is following their plan unless the plan told them how to recognize it.
Rewriting for portability, not just compliance
A useful reframe: write every accommodation as if it has to survive being read by someone with 30 seconds and no background. That means naming:
1. The trigger - what specifically prompts the accommodation (a fire alarm, a loud transition, a test day)
2. The action - exactly what happens, described concretely enough to act on immediately
3. Who executes it - the classroom teacher, any adult present, or specifically the case manager
4. What it looks like from the outside - so an unfamiliar adult can recognize the accommodation is already in progress, not assume the student is wandering the hall
A quick before/after
Before: "Student may take breaks as needed."
After: "Student may leave the room for up to 5 minutes using a hall pass kept at the classroom door, no verbal permission required, and does not need to explain the reason to any adult who stops them - show the pass."
The second version works for a substitute, a hallway monitor doing a sweep, and the student themselves, who now has language to use if questioned.
Drafting portable language with AI
Once you know what needs naming, a model is useful for turning a vague accommodation into the specific, executable version - as long as you supply the real trigger and action, not just the category. Try:
- "Here's a 504 accommodation: [paste current wording]. Rewrite it so a substitute teacher or hallway supervisor with no prior context could execute it correctly on the first read. Name the trigger, the exact action, and what it should look like from the outside."
Build the final version inside the [504 plan tool](/504-plan) so it's stored in the same format as the rest of the student's plan, and cross-reference it against your [classroom management tool](/classroom-management) routines to make sure the accommodation doesn't quietly contradict a whole-class procedure a substitute would otherwise default to.
What still needs your judgment
- Brief actual substitutes, not just the file. A well-written accommodation still benefits from a one-line note in your sub plan flagging it exists.
- Check it against non-classroom staff. Cafeteria monitors, bus drivers, and specials teachers often aren't looped into 504 plans at all - decide with your case manager which accommodations genuinely need to travel that far.
- Revisit after an incident. If an accommodation gets missed by someone outside your room, that's a signal the language wasn't portable enough yet, not that the adult failed to care.
