Keep support records relevant and private
See this course’s project requirements
Assemble a private access-support request and follow-up plan using fictional information.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- Describe a task, access barrier, desired outcome, and possible changes.
- Map the responsible process for the chosen setting.
- Draft a clear request and a placeholder-only documentation plan.
- Compare two assistive options using task evidence and privacy questions.
- Include a status log, follow-up script, and verified-route questions for unresolved access.
Review and revise
Use these criteria to check your work and choose what to improve.
- Request clarity: a specific task and barrier connect to a practical participation outcome.
- Route accuracy: employment, school, and postsecondary processes are distinguished and the responsible role is named.
- Privacy: sensitive records are replaced with placeholders and authorized channels are identified before sharing.
- Follow-through: options are compared for effectiveness and the log distinguishes request, implementation, and participation.
Want more background?
The idea in everyday life
An access request may lead to questions about supporting information. That does not mean every person involved needs your full history. A privacy plan separates an initial process inquiry, any appropriately requested documentation, and the practical arrangements others need to know. In this course, you will handle labels and placeholders, never real medical or educational files.
Share necessary information with the appropriate recipient through the appropriate channel.
One step at a time.
Use the sample or information you have permission to use. Keep your work as you go. You can pause between steps.
- 1
Draw three boxes: initial request, supporting documentation if properly requested, and implementation details. Put the mock request in the first; use a labeled placeholder rather than a real document in the second.
- 2
Check the organization’s instructions for the authorized recipient and secure channel. If a request seems broader than the access issue, ask what information is necessary and why. In the workplace guidance, documentation should relate to the disability and accommodation need where appropriate.
- 3
Write a sharing rule for your practice packet: no diagnoses or records in a public portfolio, group chat, ordinary class submission, or example screenshot. Staff who implement an arrangement may need instructions rather than your entire history.
- 4
Create a private tracking row with the date, document type, authorized recipient role, and confirmation status. If a real case involves disputed documentation or legal rights, seek the relevant office or qualified adviser; do not resolve the dispute by falsifying or broadly distributing records.
See how it works.
Fictional practice case: the mock college access office asks Lee to discuss its documentation procedure through its designated channel. Lee’s classroom project contains only a placeholder marked supporting document, not submitted. A tutor needs to know that an accessible text version should be available before discussion, but the course packet does not include a diagnosis. Lee records the request date and the office role separately from the practical arrangement. When a fictional message asks for the entire medical history in a public shared folder, Lee pauses and asks the access office to confirm what information is necessary and the authorized delivery method.
Did you cover these?
- Use placeholders instead of real records.
- Name an authorized recipient role and channel-verification step.
- Separate practical arrangements from medical history.
What to finish
A plan for who may receive which support records, plus a tracking log using placeholders instead of real private documents.
Watch for this
Uploading a whole private file because a request mentions documentation.
How can I tell I understand it?
You can distinguish process information from sensitive evidence and implementation instructions.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkTools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-09-10
Read request, documentation, effective alternatives, and response sections. The guidance is dated 2002 and expressly notes later ADA amendments; used for request-process education, not disability diagnosis, coverage, or current individual eligibility decisions.
Access: The named EEOC guidance is publicly readable without an account. Reading it does not open a complaint, obtain representation, or determine a personal legal outcome.
Reuse: This specific EEOC — Reasonable accommodation request guidance resource supports the cited lessons. Life Starter’s scenarios, calculations, scripts, and questions are original; no source worksheet, logo, or endorsement is reused. Free reading is not a general reuse license.
Source & access notes · checked 2026-09-10
Read audience, purpose, channel, and privacy examples. Original request drafts and access scenarios are used; no source activity is copied.
Access: This specific OpenStax chapter is freely readable in a browser without an account. All required exercises are supplied here; no enrollment, certificate purchase, or university affiliation is needed.
Reuse: Original Life Starter examples, questions, and lesson sequence are informed by this OpenStax chapter. No source exercises, illustrations, quizzes, or logos are reproduced; consult the source’s own license for separate reuse.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.