This article is for educational purposes only. It is not financial advice, not legal advice, and not tax advice. Figures vary by individual circumstances, so consult a qualified professional before acting.
Opening: That "Approved" Letter Didn't Save You, Now What?
You did everything right. You went through the disability services office. You submitted documentation. You waited, probably losing sleep over it, and you got the approval letter. It felt like a victory for about five minutes. Then the rotation site said no. Or "we need more information." Or worse, just stopped responding.
I've been there, spiraling at 2 a.m. wondering if I'm about to lose a rotation I spent months setting up. That fear is real. But here's what you need to hear right now: an approved disability letter is necessary, but it's not a magic key that unlocks every door at every site. Sites operate under their own policies, their own essential function definitions, their own logistics. Your letter gets you in the conversation, it doesn't guarantee the outcome.
The worst-case scenario you're imagining, "I lose the rotation, my whole timeline collapses, I fail out", that's the anxiety talking. Most of the time, what looks like denial is actually a gap. A formatting issue. A missing functional detail. A scheduling problem nobody caught. You can fix gaps. You can't fix what you don't understand. So let's get you understanding what went wrong and what to do about it.
How "Approved" Can Still Fail: The 6 Most Common Reasons Sites Push Back
Your disability services office approved you. That letter means something, it legally protects you and establishes your right to accommodations. But sites push back anyway, and they do it for six predictable reasons. Knowing them kills the panic because you can plan for each.
Reason mismatch. Your letter says you're approved for "extended time on exams" or "alternative scheduling." But the site expected specific wording, a particular format, or details about how that applies in their clinical environment. A letter that says "flexible scheduling" sounds great in a university office. On a clinical floor where rounds start at 6:30 a.m. and the attending needs you present, "flexible" means nothing without operational specifics. The site isn't being hostile, they literally can't implement what they don't understand.
Operational gaps. This one's maddening. Your letter is fine. The site agrees in principle. But nobody at the site knows how to make it happen. There's no accommodation liaison. The clerkship coordinator doesn't know who handles scheduling adjustments. The attending physician was never told. The letter exists in a vacuum, and clinical sites are chaotic enough without adding an undefined accommodation to the daily scramble.
Documentation scope problems. Your letter might be too vague, "Student has a disability requiring accommodations", or too detailed in the wrong ways. Sites need functional impact language: what you can and can't do, how the limitation manifests, what accommodations address it. A diagnosis-heavy letter without functional context leaves sites guessing. And guessing makes them nervous. Nervous sites default to "no."
Policy misalignment. Your school's disability policy says one thing. The rotation site's institutional policy says another. Maybe the site defines "essential functions" differently than your school does. Maybe their clerkship handbook requires physical attendance standards your letter doesn't address. You're caught between two policies that don't talk to each other.
Timing and communication failures. The letter exists. The right people just never saw it. It went to the disability office. The disability office sent it to the dean's office. The dean's office was supposed to forward it to the site. Somewhere in that chain, it stalled. Now it's two weeks before the rotation, and nobody at the site knows what you need. They're not refusing, they're uninformed.
Confidentiality and consent friction. Some sites won't implement accommodations without a signed release on file. If your letter doesn't include the right consent language, or if the site's compliance office hasn't cleared the sharing of accommodation details with clinical supervisors, they'll stall. They're protecting themselves legally, but it feels like a wall to you.
What Sites Are Actually Checking (Even When They Don't Say It Out Loud)
Sites don't tell you their internal checklist. They just delay or ask for "more information" and leave you panicking about what they're really evaluating. Let me pull back the curtain.
They're checking four things: essential functions, safety, evaluation integrity, and logistical feasibility. Essential functions means: can you still do what the rotation requires with accommodations in place? If the rotation requires drawing blood and your accommodation affects fine motor function, they need to know how that works. Safety means: does the accommodation create risk for patients, staff, or you? Evaluation integrity means: can they still fairly assess your performance? Logistical feasibility means: can they actually make it happen with the resources they have?
"Documentation quality" is site-speak for: does your letter explain the functional limitation, provide a clear accommodation rationale, and stay consistent with the rotation's learning objectives? If your letter says "student needs breaks" but doesn't specify frequency, duration, or how breaks work in a clinical setting, the site sees a problem, not a solution.
You need to separate two conversations that often get tangled. First: are the accommodations appropriate and reasonable? Second: how do we implement them without undermining core learning and evaluation? If you address these together, everything becomes a fight. If you separate them, you can agree on the principle and negotiate the logistics.
Watch for subtle signals. Delays. Vague refusals. "We'll see." Requests for "more paperwork." These all mean the site has a concern they haven't articulated. Your job is to surface it, not to wait and hope.
The Interactive Process: Your Anxiety-Relief Roadmap (Step-by-Step)
When the site pushes back, you don't argue. You don't panic. You run the interactive process. Here's exactly how.
Step 1: Identify who pushed back and what they said. Was it the clerkship coordinator? The site director? A supervising physician? The ADA office? Get the name, the role, and the exact accommodation they're questioning. "They said no" isn't enough. Who is they? What specifically did they refuse?
Step 2: Ask for a written, specific explanation of the barrier. Don't accept "because policy." Ask which policy. Ask what part of the accommodation conflicts with site requirements. Say: "I want to make sure I understand the concern so I can work with my disability services office to address it. Could you share the specific barrier in writing?" This isn't aggressive, it's the interactive process working as intended.
Step 3: Contact your disability services office immediately. Tell them what the site said. Ask for a site-ready clarification or letter addendum. Your DSO can revise the letter to address the site's specific concerns, adding functional detail, operational specifics, or language about essential functions. You shouldn't be doing this alone. That's what they're there for.
Step 4: Propose an accommodation plan that preserves essential functions. If the site worries about scheduling, offer concrete arrival times and coverage plans. If they question exam logistics, propose a format that maintains evaluation integrity. If they need assistive tools, identify exactly what and how it works in their environment. You're not asking permission, you're offering a solution.
Step 5: Request a brief implementation meeting. Get everyone in the same room or on the same call: you, the site coordinator, and whoever handles accommodations at the site. Set a timeline tied to the rotation start date. "Can we meet by [date] to finalize the implementation plan so I'm ready for the rotation start?" Puts pressure on without being hostile.
Step 6: Keep a paper trail. Every conversation. Every email. Every name and date. Because worst-case scenario, and I've seen this happen, someone says "we never agreed to that" and you have no record. Confirmation emails after every call: "Thanks for meeting today. What we agreed: [specifics]. Please confirm if I've captured this accurately." That sentence has saved people's rotations.
Common Letter/Accommodation Gaps, and How to Fix Them Without Burning Bridges
Most letter problems fall into patterns. Here's how to fix each one without making the site defensive.
If your letter is vague: Ask your DSO to rewrite it with functional descriptions phrased for implementation. Not "student has ADHD requiring accommodations." Instead: "Student experiences reduced sustained attention during extended testing; 1.5x time on written exams addresses this functional limitation." Sites need to see the connective tissue between limitation and accommodation.
If accommodations need scheduling: Don't leave it abstract. Provide a concrete plan. Arrival time. Break schedule. How you'll handle call shifts. What happens if a patient emergency overlaps with a scheduled break. Sites respect specificity because it means they don't have to figure it out themselves.
If the site asks for "more proof": Don't send your own medical records. That's a trap. Your DSO should provide consistent verification, functional confirmation, not diagnostic detail. You're not the one who should be explaining your diagnosis to a clerkship coordinator. That's a boundary. Protect it.
If essential functions are questioned: Propose "equivalent outcomes." Same learning goals, different pathway. If you can't do a physical task the traditional way, can you demonstrate competency through an alternative method? If you need a different assessment format, can it measure the same competencies? Frame it as preserving the rotation's integrity, not weakening it.
If you're worried about seeming difficult: Use collaborative language. Not "You have to accommodate me." Instead: "I want to ensure we're meeting both the accommodation requirements and the rotation's essential functions. Here's what I'm proposing." The shift from adversarial to collaborative isn't weakness, it's strategy. Sites respond to people who make their jobs easier.
The biggest mistake: Arguing on the spot. When someone says "we can't do that," your instinct is to push back. Don't. Shift to documentation and meeting requests. "I understand there's a concern. Let me work with my disability services office and come back to you with a plan that addresses it." Buys you time, keeps the door open, and prevents you from saying something you'll regret.
<chart-data-api config='{"type":"bar","title":"Most Common Reasons Approved Letters Don't Work at the Site","labels":["Documentation specificity","Site operational workflow","Essential function concerns","Timing/communication","Consent/confidentiality"],"values":[28,22,18,17,15],"yAxisLabel":"Relative frequency"}'>
Templates You Can Use Tomorrow: Emails That Ask for Clarity (Not Confrontation)
You're anxious. You don't want to sound demanding. You also don't want to sound apologetic. Here are two templates that hit the right tone, professional, specific, and solution-focused.
Email to Site Coordinator:
Subject: Accommodation Implementation for [Rotation Name], [Your Name]
"Hello [Name],
I'm reaching out regarding my approved disability accommodations for the upcoming [Rotation Name] rotation starting [date]. I understand from our recent communication that there are questions about implementing my accommodations at this site.
Could you share the specific barrier or concern in writing so I can work with my disability services office to address it? I want to ensure we meet both the accommodation requirements and the rotation's essential functions.
I'd also like to request a brief meeting to discuss an implementation plan. I'm available [two-three time windows]. Would any of these work, or is there a time that's better for you?
Thank you for your time. I'm committed to making this work smoothly for everyone involved.
[Your Name] [Your Student ID]"
Email to Disability Services Office:
Subject: Site Pushback on Approved Accommodations, Addendum Request
"Hello [Coordinator Name],
I received pushback from [Site Name] regarding my approved accommodation letter for [Rotation Name]. The specific concern they raised was: [quote or summarize what they said].
Could you provide a site-ready clarification or addendum addressing this concern? I'd like to include functional details specific to a clinical setting and any language about essential functions that might help.
I'm hoping to resolve this by [date] given the rotation starts on [date]. Please let me know if you need any additional information from me.
Thank you, [Your Name]"
When Things Still Don't Move: Escalation Paths Without Tanking Your Chances
Sometimes the site won't budge. The coordinator ignores emails. The attending flat-out refuses. You're running out of time and the rotation start date is bearing down on you. Here's how to escalate without blowing things up.
Know your escalation options. In order: your school's disability services office (they can advocate directly), the site's ADA or compliance office, the program director, the institutional ombuds, and the formal grievance process. Each step up adds pressure, but also adds people who understand accommodation law better than the clerkship coordinator does.
Escalate based on process, not emotion. Don't say "they're being unfair." Say: "I'm requesting that the interactive process be completed before the rotation start date." That's a legal framework, not a complaint. It signals you know your rights without threatening litigation.
Document deadlines. If the rotation starts in ten days, say so. If an exam date is approaching, name it. If scheduling constraints mean accommodations must be in place by a certain date to be feasible, put that in writing. Deadlines create urgency without hostility.
Request provisional implementation. If your school's policy allows it, ask for accommodations to be implemented temporarily while the review continues. "I'm requesting provisional implementation of my approved accommodations while we work through the site's concerns, to ensure I don't fall behind in the rotation." This prevents you from losing time while bureaucrats sort things out.
Handle retaliation fear. You're scared that pushing back means a bad evaluation or a ruined relationship with the site. Fair concern. Here's how to manage it: stick to written communication. Frame every request as compliance, not permission. Don't apologize for needing accommodations. Don't over-explain your disability. Keep the conversation about process and logistics, not about you. And if someone makes a retaliatory comment, document it immediately and report it to your DSO.
Closing Reminder: This Isn't a Personal Failure, It's a Process Problem You Can Fix
Here's what I need you to hear: this isn't your fault. You followed the process. You got approved. The fact that a site pushed back doesn't mean your accommodations are unreasonable or that you don't deserve them. It means the system is imperfect and sites sometimes need help understanding what they already agreed to support.
You have control here. You can ask for specifics. You can involve your disability services office. You can request a meeting. You can keep a paper trail. You can escalate if needed. The "I'm doomed" feeling is real, but it's not accurate. Most of these situations resolve with clarification, not confrontation.
Right now, today, do one thing: draft the email. Contact your DSO. Ask for the meeting. Stop the spiral and start the process. You've got this.
Key Takeaways:
- "Approved" is the starting point, sites often require specific, implementable documentation and a working operational plan.
- Ask for a specific barrier, then run the interactive process with your disability office and the site coordinator (and get it in writing).
