Title II of the Americans with Disabilities Act requires state and local governments to provide equal access to programs, services, and activities, but it also recognizes a narrow limit: a public entity does not have to take an action that would impose an undue financial and administrative burden. Because that exception can be misused, the regulation assigns the decision to a specific level of authority and requires a written explanation. For agencies, schools, courts, police departments, transit systems, and other public entities, understanding who must make the decision is essential to lawful ADA compliance and defensible operations.
In practical terms, Title II applies to public entities, meaning any state or local government and any department, agency, special purpose district, or other instrumentality of those governments. The core rule is broad nondiscrimination. People with disabilities must have an equal opportunity to participate in and benefit from government offerings, whether the service is in person, by phone, online, or through a contractor. The undue financial and administrative burden standard most often arises in effective communication cases, especially around auxiliary aids and services such as sign language interpreters, CART captioning, accessible documents, and qualified readers.
The controlling language appears in the Department of Justice Title II regulation at 28 C.F.R. 35.164. It states that the decision that compliance would result in such a burden must be made by the head of the public entity or that person’s designee after considering all resources available for use in the funding and operation of the service, program, or activity. The decision must be accompanied by a written statement of reasons. That sentence answers the headline question directly, but agencies still need context because the rule works together with program access, effective communication, reasonable modification, and the direct threat and fundamental alteration standards.
I have worked with public sector ADA coordinators and department leaders long enough to know where confusion usually starts. Frontline staff often think they can deny a request because it seems expensive, inconvenient, or unfamiliar. They cannot. Title II sets a high bar for denying a requested aid or service on burden grounds, and the analysis is entity wide for the specific service, program, or activity, not a quick judgment by a supervisor at the counter. Just as important, even when a requested action would create an undue burden, the public entity must still take any other action that would not result in such a burden but would nevertheless ensure, to the maximum extent possible, that people with disabilities receive the benefits or services provided.
Who Must Make the Decision Under Title II
The decision maker must be the head of the public entity or a properly designated official. In a city, that may be the city manager, mayor, or agency head, depending on the structure. In a public university, it may be the president or an authorized senior administrator. In a county court system, it may be the chief administrative officer if formally delegated. The regulation does not allow an intake worker, teacher, dispatcher, clinic receptionist, or line manager to make a final undue burden determination. Those employees can elevate the request, gather facts, and propose alternatives, but they should not issue the denial as if they hold the authority themselves.
The written statement matters as much as the title of the signer. A valid determination should identify the specific requested action, the service or program involved, the resources considered, the operational impact, and why the action would create an undue financial and administrative burden. Boilerplate language is risky. A one line note saying the request is too expensive will not satisfy the regulation or impress a court. Public entities should document actual costs, timing, staffing constraints, procurement issues, and why lower burden alternatives were explored or offered.
Consider a common example: a deaf parent requests a qualified American Sign Language interpreter for an Individualized Education Program meeting at a public school. A school secretary cannot deny the request because a staff member can pass written notes. The district must assess the communication context, the complexity of the discussion, and the parent’s usual method of communication. If the district believes the specific request would impose an undue burden, the determination must be made by the proper senior official, in writing, after considering available resources for that school program or district function. In many districts, the facts will not support a burden defense at all, especially for a scheduled meeting of high importance.
What Counts as an Undue Financial and Administrative Burden
Undue burden is not the same as annoyance, ordinary expense, or administrative preference. The term means significant difficulty or expense when evaluated against the resources available for the funding and operation of the service, program, or activity. Agencies should look at the actual cost of the aid or service, the budget and staffing available, the frequency of the need, procurement timelines, existing contracts, and whether the entity can spread the cost across the relevant operation. The analysis is contextual. A small rural district and a large state agency may face different facts, but both must show a real, evidence based hardship.
Because Title II covers public services broadly, the standard often appears in effective communication disputes. The Department of Justice has repeatedly emphasized that public entities must furnish appropriate auxiliary aids and services where necessary to afford an individual with a disability an equal opportunity to participate. Appropriate does not always mean the person’s preferred aid in every instance, but primary consideration must be given to the requests of individuals with disabilities in many communication contexts, particularly for state and local government communications with members of the public. Denying a requested interpreter because staff believe lipreading should be enough is a classic compliance failure.
Administrative burden deserves separate attention. Some entities focus only on price and ignore logistics. Yet the rule also recognizes extraordinary operational disruption. For example, a last minute request for a rare language tactile interpreter in a remote area may present procurement and scheduling barriers that are real. Even then, the entity cannot stop at no. It must ask what can be done now to ensure maximum possible access, perhaps by rescheduling promptly, using interim remote services if effective, or arranging an equally effective alternative communication method while a qualified provider is secured.
| Scenario | Likely analysis | Compliant response |
|---|---|---|
| Deaf resident requests ASL interpreter for city council hearing scheduled next week | Routine civic meeting; cost usually modest relative to city resources | Provide qualified interpreter unless specific facts show extreme hardship |
| Blind applicant requests accessible digital tax notice instead of scanned image PDF | Low cost, high feasibility with existing document tools | Remediate and send accessible format promptly |
| Rural jail receives immediate request for tactile interpreter at 2 a.m. | Urgent, complex, limited vendor availability may affect timing | Escalate to authorized official, document efforts, provide best available effective alternative and secure full service as fast as possible |
How the Decision Fits Within the Broader Title II Framework
Title II undue burden analysis is only one part of the compliance picture. Public entities also have obligations around program access, reasonable modifications to policies, practices, or procedures, and accessible communications. Program access under 28 C.F.R. 35.150 is about whether existing services, when viewed in their entirety, are readily accessible to and usable by individuals with disabilities. A city might not have to make every old building accessible if it can provide access to the program another way, but it cannot leave the program inaccessible overall. That concept is different from denying a specific auxiliary aid as an undue burden under 35.164.
Another related concept is fundamental alteration. A public entity does not have to make a modification that would fundamentally alter the nature of a service, program, or activity. This defense is distinct from undue burden, although the two are sometimes analyzed together. For example, waiving all academic requirements for a public licensing course could fundamentally alter the program, while hiring an interpreter for lectures usually would not. Agencies should be careful to use the right standard, because courts and the Department of Justice do not treat these defenses as interchangeable labels.
The Rehabilitation Act also matters. Section 504 applies to recipients of federal financial assistance and often overlaps with Title II. Many public schools, colleges, transit authorities, and health departments must comply with both. In practice, the standards are often interpreted consistently, and failures under one framework frequently signal problems under the other. Agencies should also remember the 2024 DOJ rule updating web and mobile app accessibility requirements for state and local governments by incorporating WCAG 2.1 Level AA. Digital access requests may therefore be easier to solve through proactive design than through case by case burden analysis.
Process, Documentation, and Real World Risk Management
A defensible Title II process starts before any dispute. Every public entity should designate at least one ADA coordinator if it has fifty or more employees, publish grievance procedures, train frontline staff on how to recognize accommodation and communication requests, and create an escalation path to the authorized decision maker. In my experience, the biggest mistakes are procedural: requests are lost, staff debate disability status instead of access needs, and nobody asks procurement or finance for real numbers before declaring a burden. Those failures make later written statements look manufactured.
Good documentation should answer five questions. What exactly did the person request. Why is it needed for equal access in this program or activity. What options were evaluated, including the requested one. What resources were considered for funding and operation. What alternative, if any, will the entity provide to ensure access to the maximum extent possible. This structure helps the entity comply with the regulation and gives courts, investigators, and complainants a clear record. It also promotes better service because the conversation shifts from whether to help to how to help effectively.
Risk management also means understanding when the burden defense is unlikely to succeed. Scheduled appointments, hearings, parent teacher conferences, benefit interviews, and court dates rarely justify denial of common aids such as qualified interpreters, captioning, large print, accessible electronic documents, or screen reader compatible forms. Costs for these services are generally predictable and can be budgeted. By contrast, genuinely unusual requests, emergency timing, vendor scarcity, or requests that would require rebuilding an entire system overnight may present a closer question. Even then, agencies should expect scrutiny and should document every alternative explored.
Public entities that contract out services remain responsible for ADA compliance. A county cannot avoid Title II duties because a private medical vendor operates the jail clinic, and a city cannot blame a software vendor for an inaccessible payment portal. Contracts should require accessibility, indemnification where appropriate, testing standards, and prompt remediation obligations. Internal links across an ADA Titles Explained hub should point readers to deeper pages on effective communication, program access, web accessibility, law enforcement interactions, and transportation, because Title II compliance is operational, not abstract. When departments understand that structure, undue burden becomes the rare exception the regulation intended.
Key Takeaways for Public Entities and ADA Coordinators
The answer to who must make the Title II undue financial and administrative burden decision is straightforward: the head of the public entity or a designee with that authority, after considering all resources available for the funding and operation of the service, program, or activity, and with a written statement of reasons. Everyone else in the organization should treat the issue as an escalation question, not a personal judgment call. That single governance point protects disabled residents from arbitrary denials and protects agencies from inconsistent, poorly supported decisions.
The broader lesson is that Title II public entities should build systems that make burden determinations uncommon. Budget for interpreters and captioning. Buy accessible software and documents from the start. Train staff to recognize requests quickly. Keep vendor lists current. Use grievance procedures to catch problems early. Most important, remember that even if one requested action would be an undue burden, the duty to provide access does not disappear. The entity must still find another effective way, to the maximum extent possible, to deliver the benefit or service.
For an ADA Titles Explained hub, this topic is foundational because it shows how Title II balances civil rights with operational reality without allowing convenience to override access. If you manage a public program, review your delegation documents, written procedures, and communication access workflow now. A clear decision maker, a documented analysis, and a habit of offering effective alternatives will put your agency in a far stronger compliance position before the next request arrives.
Frequently Asked Questions
Who is allowed to decide that a requested accommodation or modification would be an undue financial and administrative burden under Title II?
Under Title II of the Americans with Disabilities Act, that decision cannot be made casually or delegated to front-line staff. The regulation requires the determination to be made by the head of the public entity or by a designee who has been given proper authority to act on behalf of the entity. In practical terms, that means a clerk, teacher, dispatcher, receptionist, caseworker, patrol officer, or other individual employee does not get to simply say that an accommodation is too expensive, too difficult, or too inconvenient. The rule is designed to prevent ad hoc denials and to ensure that the decision is made at a high enough level to reflect the resources and responsibilities of the entire public entity.
This matters because Title II applies broadly to state and local governments and to the programs, services, and activities they operate. A request for effective communication, program access, auxiliary aids and services, policy modification, or another accessibility-related measure must be evaluated through the lens of the public entity as a whole, not just the budget or staffing of one office, classroom, courthouse division, police shift, or transportation route. By assigning the decision to the head of the entity or an authorized designee, the ADA makes clear that an undue burden finding is an exception of last resort, not an easy way to avoid compliance.
Why does Title II require a high-level official to make the undue burden decision?
Title II places the decision with the head of the public entity or an authorized designee because the undue financial and administrative burden defense is supposed to be narrow and carefully controlled. If lower-level employees could deny requests on their own, there would be a much greater risk of inconsistent decisions, misunderstandings of the law, and denials based on inconvenience rather than actual burden. A high-level decision-maker is more likely to understand the entity’s full legal obligations, overall resources, operational structure, and the importance of avoiding discrimination against people with disabilities.
The requirement also promotes accountability. When a decision must come from leadership, the entity has to treat the matter seriously and assess it based on real facts rather than assumptions. That means looking beyond a single department’s immediate discomfort or budget preference and considering whether the requested action is truly too costly or administratively disruptive in light of the entire public entity’s resources. For agencies, schools, courts, police departments, and transit systems, this structure helps prevent misuse of the exception and reinforces the ADA’s central rule: access is the norm, and denial is the rare exception that must be justified.
Does the public entity have to put an undue burden decision in writing?
Yes. Title II regulations require that an undue financial and administrative burden determination be accompanied by a written statement of the reasons for reaching that conclusion. This written explanation is not a technicality. It serves several important purposes. First, it forces the entity to articulate the actual basis for the decision rather than relying on vague claims that something is too hard or too expensive. Second, it creates a record showing that the issue was considered by the proper level of authority. Third, it provides transparency to the individual who requested the accommodation or modification and to anyone later reviewing the decision, including agency counsel, oversight bodies, investigators, or courts.
A proper written explanation should do more than simply repeat the words “undue burden.” It should identify the requested action, describe the reasons the entity believes the action would create significant financial or administrative strain, and reflect a genuine evaluation of the entity’s available resources and operational circumstances. A conclusory email, an oral refusal, or a blanket policy statement often will not reflect the kind of individualized, documented assessment the ADA expects. In practice, the writing requirement helps distinguish lawful, evidence-based determinations from unsupported denials that may violate Title II.
If a public entity decides a particular request would be an undue burden, can it simply deny the request and stop there?
No. Even when a public entity determines that a specific requested action would impose an undue financial and administrative burden, that does not usually end the analysis. Title II still requires the entity to take other steps, to the maximum extent possible, to ensure that the person with a disability receives the benefits of the service, program, or activity. In other words, the entity cannot treat an undue burden finding as permission to walk away. It must consider whether there is an alternative accommodation, auxiliary aid, modification, or method of access that would be effective without creating the same level of burden.
For example, if a particular requested measure is unusually costly or operationally difficult, the entity may still need to provide a different effective option. In a school setting, that could mean identifying another way to ensure communication access or participation. In a court, it could mean arranging a workable alternative that still preserves meaningful access to proceedings. In policing, corrections, or transit, it may require a different operational adjustment that avoids discrimination while addressing legitimate resource constraints. The key point is that Title II focuses on equal access. A lawful undue burden determination relates to a specific requested action, not to the broader obligation to provide access wherever it can reasonably be achieved.
How should agencies, schools, courts, police departments, and transit systems handle these decisions to stay compliant with Title II?
Public entities should approach undue burden issues through a structured, documented process rather than informal judgment calls. That starts with training staff to recognize accommodation and access requests and to understand that they should not deny such requests on their own authority by claiming the request is too difficult or too expensive. Staff should know when to escalate the issue, who has decision-making authority, and what information needs to be gathered for a proper assessment. Policies should identify the head of the entity or the authorized designee who can make the determination and should require a written explanation whenever the entity concludes that a requested action would create an undue financial and administrative burden.
Just as important, the entity should evaluate each request individually. Blanket assumptions are risky. A school district should not assume a communication aid is always too costly. A court should not rely on a routine practice of refusing modifications without a fact-specific review. A police department should not reject an accessibility-related request because a single shift commander views it as inconvenient. A transit agency should not focus only on one route, office, or unit if the relevant resources are broader. Sound compliance means examining the actual request, the actual burden, the entity’s overall resources, and the availability of effective alternatives. When public entities follow that process, they reduce legal exposure, strengthen public trust, and better fulfill the ADA’s purpose of ensuring people with disabilities have equal access to government programs, services, and activities.
