A disability action plan is a practical document for identifying barriers and setting out who will remove them, by when, and how progress will be checked. Use the printable template below to create an organization-wide accessibility plan; adapt its goals and actions to the people, places, services, or activities it covers.
What a Disability Action Plan Covers
The phrase “disability action plan” can describe different things. In this article, it means a plan used by an organization, group, or service to improve access and inclusion for disabled people. It may cover a workplace, school, community program, public-facing service, event, building, website, or a combination of these. It is not a personal medical or rehabilitation plan, and it should not be used to make decisions about an individual without their participation.
A useful plan turns a broad commitment into specific work. For example, “improve communication” is an intention, not an actionable task. A stronger action might be to provide event information in accessible digital formats, identify who prepares those materials, set a date for updating the process, and decide how attendees can request another format.
Plans vary in scope and form. Some are required or encouraged by local rules, funding conditions, or organizational policy; others are voluntary improvement tools. Requirements differ by location and sector, so a general template cannot establish whether a particular organization has met its obligations. The central purpose is consistent: identify barriers, consult affected people, assign actions, and review whether changes actually improve access.
Decide the Scope Before You Write
Set a clear boundary so the plan is manageable and people know what it covers. A small community group might focus on its meeting venue, event communications, and registration process for the next year. A larger organization may need separate workstreams for facilities, employment, digital services, procurement, and customer support. If the scope is too broad, actions can become vague; if it is too narrow, significant barriers may be missed.
Record who is responsible for approving and maintaining the plan, which teams or locations are included, and when it will be reviewed. If the plan applies to a service, describe the service and the people who use it. If it covers a workplace, include relevant stages such as recruitment, onboarding, daily work, and progression, while protecting individual privacy.
- Define the locations, programs, services, or processes included.
- Set a planning period and a realistic review date.
- Name a coordinator and identify who can approve resources or changes.
- Explain how people can contribute or raise an access concern.
Printable Disability Action Plan Template
Copy or print the table and add rows as needed. Use plain language, name a responsible role rather than leaving ownership implicit, and make deadlines specific. The fields are deliberately general so they can be used by a workplace, nonprofit, school, service provider, or event team.
DISABILITY ACTION PLAN
| Plan details | Complete here |
|---|---|
| Organization or team | ________________________________________ |
| Scope and locations | ________________________________________ |
| Plan period | ________________________________________ |
| Coordinator and approval role | ________________________________________ |
| People consulted and consultation method | ________________________________________ |
| Plan review date | ________________________________________ |
| Barrier or opportunity | Intended outcome | Action and steps | Owner | Due date | Resources or dependencies | How progress will be checked | Status and review notes |
|---|---|---|---|---|---|---|---|
| ________________ | ________________ | ________________ | ____________ | __________ | ____________ | ____________ | ____________ |
| ________________ | ________________ | ________________ | ____________ | __________ | ____________ | ____________ | ____________ |
| ________________ | ________________ | ________________ | ____________ | __________ | ____________ | ____________ | ____________ |
| ________________ | ________________ | ________________ | ____________ | __________ | ____________ | ____________ | ____________ |
Sample — fictional details: Barrier: event registration asks attendees to call to request access arrangements. Intended outcome: attendees can make requests privately using a clear, accessible contact option. Action: add an accessible email request route and explain how information will be used. Owner: Events Coordinator. Due date: 30 September. Check: review the registration page and ask for feedback after the next two events. Status: In progress.
How to Turn the Template into a Working Plan
Start with evidence about the experience of accessing the organization, rather than guessing what people need. Review the full journey: finding information, making contact, entering a building or online service, taking part, asking for help, and giving feedback. Existing complaints, service questions, accessibility requests, staff feedback, and routine process reviews can reveal patterns. Treat these sources carefully; an absence of complaints does not prove there are no barriers.
For each issue, describe the barrier in observable terms. “People cannot participate” is too broad to guide a response. “The online form cannot be completed using only a keyboard” gives a team something specific to investigate. Then state the outcome in terms of improved access, not merely completion of a task. Installing a feature is an output; whether people can use the service more easily is the outcome to check.
- List barriers and opportunities within the plan’s scope.
- Consult people affected and refine the descriptions.
- Choose a practical action and break complex work into steps.
- Assign one accountable owner, a due date, and any dependencies.
- Agree on evidence of completion and a way to assess the result.
- Review progress, record changes, and revise actions when needed.
For example, if visitors cannot tell whether a venue has a step-free entrance, actions might include checking the route, publishing accurate arrival information, and assigning someone to keep it current. Simply adding a sentence to a webpage is not enough if the information is inaccurate or the route itself remains unusable. The plan should distinguish an information fix from a physical access improvement.
Consultation, Respect, and Privacy
Disabled people are not a single group with identical requirements. Access needs can differ between people and can change with context. Some barriers relate to mobility, vision, hearing, communication, cognition, energy, sensory environments, or more than one of these. Consultation helps reveal practical details that a team may overlook, but no one person should be expected to speak for everyone.
Offer more than one way to contribute where possible, such as a conversation, an accessible form, or written comments. Explain the purpose, how feedback will be used, and whether it will be shared. Make participation itself accessible: provide information in advance, allow time to respond, and ask what format or arrangements would help. If participants need support to take part, plan for it rather than treating it as an unexpected extra.
Do not collect diagnoses or personal details simply because a plan concerns disability. Record the barrier and the action needed at an appropriate level of detail, and restrict access to any sensitive information that is genuinely necessary. A public-facing plan can describe an improvement without identifying the person who raised the issue. Consultation should inform decisions, not become a request for personal medical evidence.
Priorities, Owners, and Resources
Not every action can happen at once. Prioritize issues by considering how strongly they limit participation, how many people or processes may be affected, whether an immediate workaround is needed, and whether one action enables other improvements. A low-cost change can be important, but cost alone should not decide priority. Likewise, a technically complicated action may need staged work rather than being left off the plan.
Make ownership explicit. A department name can be useful, but one role or named coordinator should be responsible for following up. The owner may need other teams to contribute; list dependencies such as approval, procurement, specialist assessment, or a scheduled website update. Set a due date that reflects those dependencies and revisit it if circumstances change. Repeatedly carrying an overdue item forward without a reason or revised path makes the plan less credible.
Resources can include staff time, training, accessible communication formats, equipment, maintenance, or outside expertise. A plan should not promise work that has no approval or resources. If funding is uncertain, record the decision needed, who will seek approval, and the date for reconsideration. Cost estimates and purchasing decisions depend on the specific setting; this template does not provide financial-planning advice.
Measures and Regular Review
Choose a check that matches the action. For a process change, evidence might include a revised procedure and confirmation that relevant staff know how to use it. For an event improvement, the team might check whether access information was available in advance and invite feedback about the experience. For a physical or digital change, a completion check can be paired with feedback from people who use it. No single measure captures every person’s experience, so use more than one kind of evidence when practical.
Review the plan on a stated schedule and after meaningful changes, such as moving premises, introducing a new service, or changing a key process. At review, mark actions as complete, in progress, delayed, or no longer relevant, and explain the reason. For completed actions, ask whether the intended outcome occurred. If it did not, revise the action rather than treating the checkbox as success.
Share progress in a format people can access, while respecting privacy. A brief update can identify completed work, upcoming priorities, and obstacles requiring a decision. A plan is a living management tool, not a one-time declaration: new barriers may emerge, and effective actions may need maintenance.
Common Problems and How to Avoid Them
- Vague promises: Replace “be more inclusive” with a specific action, accountable owner, and target date.
- Consultation after decisions are made: Seek input while options are still open, and report what changed as a result.
- Focusing only on buildings: Consider communication, digital access, policies, events, customer service, and workplace practices too.
- Assuming one solution fits everyone: Offer ways to request adjustments and review whether the approach works for different users.
- Counting activity instead of impact: Record that training happened, but also check whether the relevant process or experience improved.
- Letting the document go stale: Assign a coordinator, schedule reviews, and update the plan when services or circumstances change.
A related misconception is that publishing a plan itself makes an organization accessible. Publication can make commitments visible, but it does not remove a barrier. The plan is useful only when actions are resourced, carried out, and checked with attention to the people affected.
Frequently Asked Questions
What should a disability action plan include?
A practical plan typically identifies its scope, the barriers or opportunities found, intended outcomes, actions, responsible owners, due dates, resources or dependencies, measures, and a review schedule. It should also explain how disabled people can contribute and how feedback will be handled.
Who should write a disability action plan?
An organization should involve the people who can make and carry out decisions, including staff responsible for relevant services or facilities. Disabled people affected by the plan should have meaningful opportunities to shape it. A coordinator can maintain the document, but responsibility should not rest on one person without decision-making support.
Is a disability action plan legally required?
That depends on the country, local rules, organization type, and circumstances. A general template cannot determine legal duties or certify compliance. Check the rules that apply in your location or ask a qualified professional if you need legal advice.
How often should the plan be reviewed?
Set a regular review date that suits the scope and pace of change, and review sooner when a major service, location, or process changes. The key is to check both whether actions were completed and whether they improved access, then update owners, dates, or priorities as necessary.
Is this template for an individual’s personal support plan?
No. It is designed for an organization or group improving access across a service, workplace, event, or similar setting. An individual support plan has a different purpose and should be developed with that person and the relevant qualified support team, according to their circumstances.
If a situation calls for legal, medical, or financial-planning advice, ask a qualified professional who can consider the specific circumstances.