Quick answer
Practice explaining a concern and requesting a specific action. Check the governing rules and deadlines separately.
A request states what you want. A decision states what was agreed or ordered. Implementation is what actually happens. Keep all three stages separate.
What to do
Identify the problem and the rules that may apply. For a legal issue, verify current primary authority for the correct jurisdiction.
Establish the chronology: what happened, when, and how you know.
Gather the relevant records and preserve unchanged originals.
Separate documented facts from assumptions, interpretations, and disputed statements.
Identify missing information or gaps. Describe what would answer the unresolved question.
Explain why the issue matters to the goal or decision.
Request a specific remedy: an action connected to the identified problem and supported by the applicable rules.
Preserve procedural rights through the required process. A meeting or informal request does not itself preserve every deadline.
Verify implementation against the actual decision or agreement, using evidence of completed actions.
Fictional example: an unreadable timetable
A community workshop says it will provide a readable timetable. A participant receives a small image and cannot read the session details. This example concerns an ordinary service promise; it does not assume a legal violation.
The participant keeps the promise and the delivered image, records when each arrived, and explains which details are unreadable. They avoid assuming why the image was used. Their request is concrete: “Please provide the timetable as selectable text with session titles and times.”
A reply saying “I will send a text version” is an agreement to act. A new attachment is evidence of delivery. The participant then checks whether it contains readable session titles and times. Delivery and usability are separate questions.
Practice: identify the remaining gap
In the fictional example, the participant receives a new file, but two session times are missing. What should the implementation record say?
- Record what was received and the two missing times.
- Identify the relevant part of the agreement.
- Ask for the specific missing information without claiming that everything was completed or that no progress occurred.
Why that next step helps
The follow-up acknowledges the completed action and identifies the remaining gap. It makes the next request easy to understand and verify. The same distinction matters with an assessment: completion alone does not establish whether it adequately answered the question it was meant to address.
Keep the limits visible
A well-organized request does not guarantee the requested result. An official may disagree about the facts, the governing rule, the available remedy, or the proper procedure.
CAST and W3C are linked as learning and usability design background. They do not establish these organizing steps as a legal test or support a case-specific legal conclusion.
This public exercise uses fictional facts. Keep personal records in an appropriate private system, and verify filing, service, receipt, representation authority, and deadlines separately.
Your next step
Use the Evidence Organizer for one item, then use the Decision Implementation Tracker only when you have an actual agreement or decision to track. For vocational rehabilitation procedures, open the related jurisdiction-specific guide and its primary authority.
Background, examples & sources
Official information
- CAST UDL Guidelines 3.0: organization and strategy development (Design background only; an original organizing exercise)
- W3C: Making Content Usable for People with Cognitive and Learning Disabilities (Supplemental usability guidance; not legal authority for a remedy)
Last source review: 2026-10-09 · Original exercise checked for stated educational scope
Original writing exercise and fictional example, October 9, 2026; CAST and W3C cited only as design background
Your next step
Organize one evidence item — free worksheet.