When case managers cannot approve what you need
Your case manager is not the wall. Your case manager is standing in front of the wall, absorbing your frustration for a system she did not design. Three walls actually govern every no: budget caps, policy limits, and risk rules. Learn which one you’re hitting and the ask changes completely.
Make her name it. Not “it’s complicated” or “there are a lot of factors.” A specific budget ceiling, a specific policy manual section, or a specific risk finding. Once it has a name, you can appeal it, cite it, or work around it. While it stays vague, you’re fighting fog.
Budget caps
Waiver spending is capped per person, per year, set by legislative appropriation. Some caps are hard. Some have exception processes nobody mentions.
Policy limits
Manuals cap service hours, provider types, and eligible ages by written rule, whether or not the rule fits your situation.
Risk aversion
A case manager who denies something unusual rarely gets disciplined. One who approves something unusual and it goes wrong can lose her job. The incentive runs toward no.
The specific ask
“More support” is unanswerable. “Six hours a week of community habilitation, service code H2015, starting next month” is a yes or a citable no.
Reasonable response window
Give a specific written request ten business days for a written answer before you escalate. Long enough to be fair, short enough to hold the line.
Get the denial in writing
A verbal no protects nobody and starts no appeal clock. A written denial citing the policy section is the document that opens the door upward.
Questions that force clarity
“What is the annual budget ceiling for this waiver line, and how close to it are we?”
“What manual section or policy number governs this decision?”
“What specific risk finding would need to change for this to be approved?”
“Who above you has the authority to approve an exception?”
“By what date will I have a written answer?”
Dwayne spent four months asking his son’s case manager for “more hours” and getting nowhere. He was furious at her by name until a friend suggested he ask what, specifically, was stopping approval. The answer surprised him: the county’s risk committee required a documented safety incident before approving overnight support, a rule buried in an internal memo he’d never seen. He requested the memo in writing, submitted his own incident log to satisfy the criteria, and had approval three weeks later. His anger, redirected at the actual rule instead of the person reading it to him, got faster results than four months of asking nicely.
When the wall has a name and the answer is still no, here is the ladder
Escalation ladder
- 1Ask which wall (budget, policy, or risk) is the reason, in writing.
- 2Submit the specific ask with a service code, hour count, and deadline.
- 3Request the written denial citing the policy or budget section.
- 4Escalate to the supervisor, citing the specific rule you were given.
- 5Escalate to the regional or state office if the supervisor cannot move it.
- 6File for a Medicaid fair hearing if the service is waiver-funded and denied.
Have ready
- The three-wall question, asked in writing
- A specific request with service code and hours
- A written denial with the policy citation
- Your state’s fair hearing request form
- Contact information for the supervisor and regional office
- A ten-business-day response deadline stated in your letter
The case manager who says no is usually reading you a rule she didn’t write. Aim at the rule.
Dwayne spent four months calling his son’s case manager, escalating in tone if not in strategy, convinced she was the problem. She wasn’t returning his calls fast enough. She kept saying “I hear you” without saying yes. He was furious at a person for four months before a friend, another parent further down this road, asked him a question he hadn’t thought to ask: what specifically is stopping the approval. This is the post about that question, and about the three walls that stand behind almost every case manager who tells you no.
The case manager is not the wall
Let me be absolutely clear about what I’m saying: I am not asking you to feel sorry for the system that fails your family. I am asking you to aim your fight at the part of the system that can actually move. Case managers, in my experience and in the experience of the hundreds of families I’ve talked to, are rarely the reason a service gets denied. They are the messenger standing closest to you when the message arrives, and messengers make an easy target because they’re the only part of the bureaucracy with a face and a phone number.
Three structural constraints govern almost every denial, whatever language shows up in the letter. Budget caps set by legislative appropriation and divided across waiver lines. Policy limits written into a manual that predates your specific situation. Risk rules built by agencies terrified of a bad outcome making the news, which push every ambiguous decision toward no because no rarely gets anyone fired.
Budget caps: the ceiling nobody mentions until you hit it
Every HCBS waiver has an appropriated budget, set by the state legislature, and divided across every enrolled participant according to a formula that is public record but rarely explained. When your case manager says “there’s no money for that,” she is usually telling the truth about her authority, even if the underlying appropriation itself is a political choice your legislature made and could unmake.
What most families don’t know: many states have exception or supplemental funding processes for documented safety needs that exceed the standard cap. These exceptions exist precisely because caps are blunt instruments that don’t fit every situation. Ask directly whether an exception process exists. Case managers rarely volunteer this information, not out of malice, but because exception requests are extra work and extra risk for them too.
Policy limits: the manual section that governs your no
Somewhere in a policy manual is a specific section limiting the service, provider type, or age range you’re asking about. That section has a number. Ask for it. A case manager who cannot or will not cite the specific policy section behind a denial is either unfamiliar with the actual rule or applying an informal practice that isn’t really policy at all, and both of those situations are worth surfacing at the supervisor level.
Dwayne’s answer, when he finally asked, was a risk-committee memo requiring a documented safety incident before approving overnight support. It wasn’t in the public-facing waiver handbook. It was an internal practice, applied consistently but never disclosed to families who asked for overnight hours cold. Once he had the actual rule, he could meet it, by submitting his own documented incident log. The wall had a door. He just hadn’t been shown where it was.
Risk rules: the incentive that runs toward no
Here’s the uncomfortable part. A case manager who denies an unusual request almost never faces consequences for the denial, even when it’s clearly wrong. A case manager who approves an unusual request that later goes badly can face real professional consequences, sometimes career-ending ones. That asymmetry means the safe move, from inside the system, is always no. This isn’t a conspiracy. It’s an incentive structure, and incentive structures predict behavior better than good intentions do.
None of this was inevitable. Agencies could build risk frameworks that reward good clinical judgment instead of just penalizing visible failure. Some states have. Michigan, at various points, has not been one of them. That’s a policy choice, made by people with names, and it’s reversible.
The specific ask beats the vague plea every time
“We need more support” is not a request anyone can approve, because it doesn’t specify what would satisfy it. “We are requesting six hours per week of community habilitation, service code H2015, effective the first of next month, based on the attached functional assessment” is a request that has to get a yes or a citable no. Vagueness protects the agency. Specificity protects you.
This is where the paper trail habits from documentation work double duty. A specific ask, tied to a cited assessment, with a stated deadline, converts a conversation into a decision point. Decision points create appeal rights. Conversations do not.
Climbing the ladder without burning the relationship
Once the wall has a name, escalation is not an act of war. It’s the normal, designed mechanism for resolving disagreements the front line can’t resolve. Supervisor, then regional or state office, then a formal fair hearing if the service is waiver-funded. Climb one rung at a time. Document each rung. Give each rung a reasonable window, roughly ten business days for a routine request, far less for anything safety-related, before moving up.
Dwayne kept his relationship with his son’s case manager intact through all of this, because he stopped treating her as the obstacle once he understood she wasn’t one. He still sends her a holiday card. She still returns his calls the same day. That relationship, preserved instead of scorched, has made every subsequent request faster. None of this was inevitable, and none of it required him to stay angry at the wrong target. It required him to ask one good question and aim the fight where it belonged.
Jim Palasty is the founder of OASIS for Autism and a single father of an adult autistic daughter in Michigan.