Welcome to Agentic ADA & 504 Accommodations thatroutes a new request with the documentation already gathered.
Approving an accommodation is a legal determination, and the institution makes it. Risely's agents do the work around that decision: route the request, gather the documentation, carry the approved plan onto new sections, and confirm the delivery.
Approved plan · new term
carrying forward
Determined by the institution
·Section A
lecture · extended time set
instructor letter sent
·Section B
seminar · notes shared
instructor letter sent
·Section C
lecture · extended time set
instructor letter sent
·Section D
lab · bench setup outstanding
instructor letter sent
Lab bench setup outstanding
drafting the request
The coordinator reviews the request and sends it. Nothing closes on its own.
The request reaches the coordinator with the file already built.
Risely's agents collect the documentation, pull the prior plan and this term's course formats, and hand over a complete case. The determination stays where the law puts it, with the institution.
Case file
gathering
Held for the coordinator
Approving an accommodation is a legal determination, and the institution makes it.
An approved plan follows the student into the next term.
Every active plan maps onto the sections a student actually registered for, and each instructor gets the letter for their own section. Nobody re-requests what the institution already approved.
Term start, in one view
Nobody re-requested what the institution already approved, and the handful that did not land have owners.
An accommodation is real once the setting exists.
Risely's agents check extended time in the course site, the shared notes, and the assigned seat. Whatever did not land comes back as a named gap rather than an assumption.
Delivery check
An accommodation exists once the setting exists. Risely's agents check the setting and raise what is missing.
The interactive process keeps its own record.
Each request, each document, each determination and each delivery check lands on one file, with the role that acted attached. That file is the one an inquiry reads.
Interactive process, as logged
Student
requested an accommodation
Risely's agents
gathered the documentation and opened the case
Coordinator
made the determination and signed the plan
Risely's agents
sent the letters and checked delivery
Coordinator
routed the one outstanding setup
One complete file per case, current on the day anyone official asks for it.
One section changes. The plan follows.
A late add, a swapped section, a course that moves to a lab. Any of them changes where a plan has to land, and every one runs the same way.
A student adds a lab section
a swap made during add and drop
Risely's agents map the plan to it
the approved terms do not change
The instructor gets the letter
with what the plan means in a lab
Delivery comes back short
the bench needs a physical setup
The coordinator routes the request
facilities owns it the same day
Agentic ADA & 504 Accommodations never works alone.
What changes, and how it runs.
Every approved plan travels with the student
New sections inherit it without a fresh request.
Delivery gets checked, never assumed
A gap surfaces as a routed task with an owner.
One complete file sits behind every case
The interactive process logs itself as it happens.
The technical read
Connects read-only to your SIS, LMS, and case system to start
The institution makes every accommodation determination
Every action lands on an append-only log
Runs alongside what you have. Nothing rips out.