An ADA Coordinator’s first 90 days should establish authority, reduce legal risk, and create a repeatable system for accessibility across programs, services, digital assets, facilities, and public communication. In practice, that means far more than answering accommodation requests. The coordinator becomes the central organizer for compliance and implementation, connecting policy, operations, grievance handling, facilities planning, procurement, and staff training. For public entities covered by Title II and many larger organizations subject to related accessibility obligations, the role is both strategic and deeply operational. When I have helped organizations stand up this function, the most successful first quarter always focused on the same outcome: build a clear baseline, assign responsibilities, and publish a realistic transition plan.
Before mapping those first 90 days, it helps to define the core terms. An ADA Coordinator is the designated employee responsible for coordinating efforts to comply with disability nondiscrimination requirements, especially under the Americans with Disabilities Act and Section 504 where applicable. A transition plan is the formal document that identifies structural barriers, sets methods for removal, assigns schedules, and names responsible officials. Program access means people with disabilities must be able to participate in services, activities, and benefits when viewed in their entirety, even if every building is not fully altered at once. Effective communication covers auxiliary aids and services such as interpreters, captioning, accessible documents, and alternative formats. Reasonable modification refers to policy or practice changes needed to avoid discrimination unless a fundamental alteration or undue burden applies.
Why does this matter so much in the first 90 days? Because accessibility failures usually are not caused by one bad policy alone. They happen when no one owns intake, no one tracks barriers, facilities and IT work separately, and leadership sees ADA obligations only as individual accommodation requests. Early decisions shape whether the coordinator becomes a reactive complaint manager or a credible compliance leader. The first three months are the window to create governance, document current conditions, and show staff that accessibility is a standard operating requirement. That foundation also supports every later article in the ADA Coordinators and Transition Plans subtopic, from self-evaluation methods and grievance procedures to digital accessibility, capital planning, and public notice requirements.
A strong first 90-day plan should answer the questions executives, department heads, and community members will ask immediately. Who is responsible for ADA compliance? How do people request accommodations or report barriers? What facilities, websites, forms, kiosks, and public meetings create the highest risk? Do current policies match Department of Justice expectations? Is there an existing self-evaluation or transition plan, and if so, is it current enough to rely on? The coordinator does not need to solve every issue in one quarter. The coordinator does need to create a defensible process, identify high-priority barriers, and demonstrate that the organization is moving from ad hoc response to documented implementation.
Days 1 to 30: Establish authority, gather records, and create intake channels
The first month is about control of information and clarity of role. Start by obtaining the designation record, job description, reporting line, and any board, council, or executive documents that assign ADA responsibility. If the role exists only informally, correct that quickly. Public-facing designation matters because people need to know where to direct requests and complaints. Review whether the organization already publishes the coordinator’s contact information, a nondiscrimination notice, and grievance procedure. Many entities have outdated notices buried three clicks deep on a website or missing from printed program materials. That is an easy, high-value fix in the first weeks.
Next, collect every compliance-related document you can find: prior self-evaluations, transition plans, settlement agreements, audit reports, accommodation logs, capital improvement lists, website remediation reports, procurement templates, emergency plans, and staff training materials. In several organizations I have worked with, the most useful records were not in legal or HR files but in facilities spreadsheets and email chains maintained by project managers. Build a document inventory that identifies date, owner, scope, and reliability. If a transition plan is ten years old and excludes digital services, pedestrian routes, or leased space, note that gap explicitly rather than treating the document as current.
Intake channels must also be stabilized early. People should have more than one way to request accommodations or report barriers: web form, email, phone, relay-accessible number, in-person contact, and paper option. Make sure the web form itself is accessible and does not require inaccessible CAPTCHA, timed sessions, or mouse-only actions. Standardize confirmation messages, response timelines, escalation paths, and case notes. A basic tracking system in Microsoft Lists, Airtable, Smartsheet, or another controlled platform is better than scattered emails. The objective is simple: every request enters one system, receives a status, and can be reported to leadership without manual reconstruction.
Days 31 to 60: Complete a practical baseline across facilities, programs, and digital services
Once intake and records are in order, the coordinator needs a current baseline. This is where many organizations overcomplicate the work. The goal is not a perfect enterprise audit in thirty days. The goal is a practical self-evaluation that identifies where barriers exist, who owns them, and which ones affect access most directly. Divide the review into at least five domains: facilities, public right-of-way elements under organizational control, digital assets, policies and procedures, and communication access. Use a standard template so departments answer the same questions and evidence can be compared.
For facilities, start with high-use locations and high-impact paths of travel: parking, passenger loading, entrances, service counters, restrooms, meeting rooms, and emergency egress procedures. Use the 2010 ADA Standards for Accessible Design as the technical reference for measurements where applicable. If your organization operates older buildings, note safe harbor issues, altered areas, and locations where program access may be achievable without immediate structural changes by relocating services. Still, avoid using relocation as a permanent substitute where barrier removal is feasible and planned. The baseline should distinguish temporary operational workarounds from capital fixes.
Digital services deserve equal attention because they generate daily barriers at scale. Review the public website, online forms, PDFs, third-party platforms, kiosks, and video content. A good screening approach combines automated testing with manual checks using keyboard navigation, screen readers, color contrast review, and caption verification. Tools such as WAVE, axe, Siteimprove, and Adobe Acrobat’s accessibility checker are useful, but they do not replace manual testing. The current operational benchmark most organizations use is WCAG 2.1 AA, and the coordinator should know where internal teams or vendors are falling short on headings, form labels, error identification, focus order, and document structure.
Programmatic barriers are often less visible than physical ones and more common. Review registration deadlines, service animal rules, companion policies, meeting participation procedures, emergency shelter protocols, procurement requirements, and event planning checklists. Ask whether staff know when to provide sign language interpreters, CART captioning, accessible seating, alternative formats, or modified policies. If departments answer these questions differently, that inconsistency is itself a compliance finding.
| Priority area | Typical first-90-day finding | Immediate action | Longer-term transition plan item |
|---|---|---|---|
| Public website | Inaccessible PDFs and unlabeled forms | Post accessible HTML alternatives and fix high-traffic forms | Set document standards, vendor requirements, and remediation schedule |
| Public meetings | No standard process for interpreters or captions | Publish accommodation request instructions on every notice | Create event accessibility protocol and staff training calendar |
| Facilities | Parking and restroom deficiencies at main service site | Install temporary signage and relocate services if needed | Budget alterations in capital plan with target dates |
| Grievance process | Outdated form and no tracking standard | Issue revised form and centralized log | Quarterly trend review and policy updates |
Days 61 to 90: Build the transition plan, governance structure, and reporting rhythm
By the third month, the coordinator should have enough information to draft a transition plan that leadership can approve and departments can execute. A credible plan includes more than a barrier list. It identifies obstacles, references the applicable standard or policy gap, assigns an owner, sets a priority level, estimates cost where possible, and gives a target completion date. For structural changes, include the official responsible for implementation as regulations contemplate. For digital and programmatic items, name the department that controls the workflow, not just the coordinator’s office. Ownership drives progress.
Prioritization should be risk-based and service-based. High priority items are barriers that block access to core services, safety functions, complaint channels, elections, emergency communications, public meetings, or high-volume digital transactions. Medium priority items may affect convenience or secondary functions but still require scheduled correction. Low priority does not mean optional; it means sequenced after more urgent barriers. Tie these priorities to budget cycles. If facilities staff submit capital requests in September and IT finalizes vendor renewals in October, the coordinator must align transition plan deadlines with those operational realities or the plan will sit on a shelf.
Governance is equally important. Establish an accessibility working group with representatives from facilities, IT, procurement, communications, HR, legal, emergency management, and major service departments. Give the group a charter, meeting cadence, and decision log. In my experience, monthly meetings with a standing dashboard work far better than ad hoc discussions after complaints arrive. The dashboard should show open requests, grievances, high-risk barriers, training completion, capital items, and digital remediation status. Leaders do not need every technical detail, but they do need trend lines and unresolved risks.
Training should begin before the 90-day mark, even if the full curriculum comes later. Front-line staff need scripts for receiving accommodation requests. Managers need decision rules for effective communication, reasonable modifications, and confidentiality. Web editors need document and content standards. Procurement staff need accessible purchasing language for software, kiosks, and public-facing technology, including conformance documentation such as VPATs, while understanding that a VPAT is only a vendor claim and not proof of usability. Facilities and project teams need to know how accessibility requirements intersect with renovations, maintenance, and temporary disruptions.
Common mistakes, legal exposure, and what good execution looks like
The most common first-90-day mistake is treating the ADA Coordinator as a single-point fixer instead of a system owner. Coordinators cannot personally remediate every PDF, inspect every doorway, or negotiate every accommodation. Their job is to create accountable processes and make sure departments perform. Another frequent mistake is focusing only on physical access. Many complaints now arise from inaccessible websites, online payments, virtual meetings, and digital documents because those barriers affect people every day and leave clear evidence. A third mistake is failing to document rationale. If an organization decides that a barrier will be addressed through program relocation, phased alteration, or alternative format production, record why, for how long, and who approved it.
Good execution looks measurable. By day 90, the organization should have a published coordinator designation and contact pathway, an updated notice and grievance process, a centralized intake log, a cross-functional working group, a current barrier inventory, and a draft or updated transition plan with priorities and owners. It should also have several visible wins: captions on posted videos, accessible meeting notices, corrected website forms, or an interim service relocation that genuinely improves access. Those early actions build trust internally and externally because they show the organization is not waiting for a complaint or demand letter to act.
The first 90 days set the tone for every later phase of ADA compliance and implementation. A strong ADA Coordinator does not begin with abstract policy language; they begin by establishing authority, finding the facts, and turning scattered obligations into a managed program. From there, the transition plan becomes the operational bridge between today’s barriers and tomorrow’s accessible facilities, services, and digital experiences. If you are stepping into this role, start with intake, baseline, and ownership. Then convert findings into a realistic plan that leadership can fund and staff can follow. That disciplined start is the fastest path to durable accessibility, lower risk, and better service for everyone.
Frequently Asked Questions
What should an ADA Coordinator prioritize in the first 90 days?
In the first 90 days, an ADA Coordinator should focus on building a clear, credible foundation for compliance rather than trying to fix every accessibility issue at once. The most important priorities are understanding the organization’s legal obligations, confirming executive support, identifying existing risks, and creating a practical system for ongoing implementation. That starts with learning how accessibility currently works across the organization, including who handles accommodation requests, who manages grievances, who oversees websites and digital documents, who controls facilities planning, and who makes procurement decisions. In many organizations, these responsibilities are spread across departments, which is exactly why the ADA Coordinator’s role is so important.
Early priorities should include reviewing existing ADA-related policies, public notices, grievance procedures, transition plans if applicable, accommodation workflows, contracts, and training materials. The coordinator should also identify whether the organization has a current ADA self-evaluation, whether complaints have been filed in the past, and where the biggest exposure areas exist. That may include inaccessible online forms, public meetings without an effective auxiliary aids process, incomplete facility access reviews, or inconsistent handling of program access requests. The goal is to quickly determine where legal risk is highest and where operational gaps are most likely to affect members of the public or employees.
Just as important, the first 90 days should produce a repeatable structure. That means establishing points of contact in key departments, creating an intake and tracking process for requests and complaints, setting expectations for response times, and beginning a prioritized action plan. A strong ADA Coordinator does not spend the first three months acting only as a reactive troubleshooter. Instead, they position the organization to become more proactive, organized, and defensible. By the end of the first 90 days, leadership should understand the accessibility roadmap, staff should know where ADA issues are routed, and the organization should have a clearer system for reducing risk across programs, services, digital assets, facilities, and public communication.
Why is the ADA Coordinator role broader than handling accommodation requests?
Many organizations initially assume the ADA Coordinator’s job is mainly to respond to individual accommodation requests, but that is only one part of the role. In practice, the ADA Coordinator serves as the central organizer for accessibility compliance and implementation across the entire organization. That includes helping ensure that programs, services, and activities are accessible; that facilities are evaluated for barriers; that websites, forms, PDFs, and digital tools are usable by people with disabilities; that grievance procedures are in place and functioning; and that staff understand how to communicate effectively with members of the public who have disabilities. The role is operational, strategic, and risk-focused all at once.
For public entities and other covered organizations, ADA compliance is not limited to case-by-case adjustments. It also involves systemic responsibilities such as policy review, public notice, reasonable modification practices, effective communication, vendor oversight, and facility planning. If accessibility is treated only as an accommodations function, the organization can miss larger patterns that create repeated barriers. For example, if a website continually publishes inaccessible documents, or if procurement teams keep purchasing software without accessibility review, the organization will face the same problems over and over. The ADA Coordinator helps stop that cycle by connecting departments and embedding accessibility into standard operations.
This broader role also matters because legal risk often comes from fragmented processes. One department may be doing a good job responding to requests, while another is creating inaccessible public communications or maintaining a complaint process that is hard to use. The ADA Coordinator brings those issues together under a consistent framework. That is why the first 90 days should be spent not only answering immediate requests, but also mapping systems, identifying recurring failures, and creating accountability across teams. When the role is structured correctly, the ADA Coordinator becomes the organization’s hub for compliance, planning, education, and continuous improvement.
What documents, policies, and systems should an ADA Coordinator review first?
At the beginning of the role, the ADA Coordinator should review the documents and systems that reveal how accessibility is currently managed and where exposure exists. That typically includes ADA and nondiscrimination policies, grievance procedures, reasonable modification procedures, effective communication processes, accommodation request forms, website accessibility statements, emergency communication protocols, procurement standards, employee training materials, and any prior self-evaluations or transition plans. If the organization has received complaints, demand letters, audit findings, or government inquiries, those materials should be reviewed early as well because they often point directly to unresolved weaknesses.
Digital systems should be part of this initial review, not an afterthought. The coordinator should look at public-facing websites, online forms, PDF documents, video content, registration systems, mobile tools, and third-party platforms that members of the public must use to access programs or services. If accessibility language is missing from contracts or purchasing procedures, that is a major issue because inaccessible technology can create long-term compliance problems that are expensive to unwind. Reviewing these systems early helps the coordinator identify whether accessibility is being addressed before purchase and publication, or only after complaints occur.
Facilities-related records are also essential. The coordinator should understand whether there has been a recent assessment of physical access barriers, how maintenance requests involving accessibility features are handled, and whether capital planning accounts for ADA-related improvements. Public meeting procedures deserve attention too, especially how the organization handles requests for interpreters, captioning, alternate formats, and other auxiliary aids and services. Together, these reviews help the coordinator move from assumptions to facts. Instead of relying on informal descriptions of what “usually happens,” the coordinator can document what policies exist, what systems are missing, and what needs to be standardized. That documentation becomes the basis for the first 90-day action plan and provides leadership with a clear picture of current compliance maturity.
How can an ADA Coordinator reduce legal risk quickly in the first three months?
The fastest way to reduce legal risk is to identify and stabilize the organization’s most visible and high-impact accessibility gaps. In the first three months, an ADA Coordinator should focus on issues that affect public access, generate recurring complaints, or show a clear lack of process. That often includes making sure there is a clear public point of contact for ADA issues, confirming that the grievance procedure is available and usable, standardizing how accommodation and modification requests are received and tracked, and addressing obvious digital barriers in high-traffic content such as applications, notices, agendas, forms, and service portals. These actions will not solve every problem, but they can significantly improve the organization’s position very quickly.
Another major risk-reduction step is establishing documentation and accountability. Legal exposure tends to increase when requests are handled inconsistently, decisions are not documented, deadlines are unclear, or staff members improvise their own accessibility practices. The ADA Coordinator should implement a basic tracking system for requests, complaints, resolutions, and follow-up actions. They should also clarify who is responsible for responding in each area, including human resources, facilities, IT, communications, and program leadership. Even a simple, well-defined workflow is better than scattered email chains and undocumented verbal decisions.
Training is another early opportunity to reduce risk. Front-line staff, managers, web teams, public meeting organizers, and procurement personnel all need at least foundational guidance on what to do when accessibility issues arise. The coordinator does not need to create a perfect enterprise-wide training academy in the first 90 days, but they should begin targeted education in the areas most likely to create problems. Finally, the coordinator should communicate regularly with leadership about priorities, barriers, and resource needs. Legal risk is not reduced by identifying problems alone; it is reduced when leadership understands what actions must be taken, in what order, and why. A strong first 90 days creates that structure and demonstrates that the organization is moving from reactive compliance to managed implementation.
What should success look like by the end of the ADA Coordinator’s first 90 days?
Success at the 90-day mark should look like meaningful organizational progress, not perfection. A successful ADA Coordinator will have established visibility, authority, and a workable structure for accessibility management. Leadership should know who the coordinator is, what the organization’s major accessibility risks are, and what the plan is for addressing them. Staff should understand where to send ADA-related requests and questions. Core departments should have identified points of contact. The organization should also have a clearer picture of its current strengths, weaknesses, and compliance obligations across programs, services, digital assets, facilities, and communications.
From a practical standpoint, success usually includes several concrete outcomes. There should be an initial assessment or inventory of major accessibility issues, a review of key policies and procedures, a functioning intake and tracking process for requests and complaints, and a prioritized action plan that distinguishes urgent fixes from longer-term projects. The coordinator should have started collaboration with teams such as IT, communications, facilities, procurement, human resources, legal, and program leadership. If there were immediate high-risk issues, such as inaccessible public forms or unclear grievance access, there should be evidence that those issues were addressed or are actively being remediated.
Equally important, success means the organization is no longer depending on informal, inconsistent decision-making. The ADA Coordinator should have begun creating a repeatable system that can endure beyond one person’s effort. That includes documented workflows, clearer responsibilities, stronger internal coordination, and early staff education. In other words, the first 90 days should move the organization from uncertainty and fragmentation toward structure and accountability. A good ADA Coordinator leaves the first three months with more than a list of problems. They leave with a roadmap
