IASC Guidelines on Inclusion of Persons with Disabilities in Humanitarian Action

IASC Guidelines on Inclusion of Persons with Disabilities in Humanitarian Action

1. What Is IASC Guidelines on Inclusion of Persons with Disabilities in Humanitarian Action?

The IASC Guidelines on Inclusion of Persons with Disabilities in Humanitarian Action provide an operational framework for making humanitarian assistance and protection inclusive. IASC stands for Inter-Agency Standing Committee. The guidelines help humanitarian actors address the rights, requirements, and participation of persons with disabilities when designing and delivering a response.

For NGOs and multilaterals, the executive question is concrete: can people with different disabilities influence the response, register for assistance, receive services, and raise concerns safely? Consultants can use the guidelines to structure an operational assessment, but the objective is better access and protection—not simply a completed checklist.

2. Origin and Background

The guidelines were developed by an IASC task team co-chaired by UNICEF, Humanity & Inclusion, and the International Disability Alliance. Their development followed commitments associated with the Charter on Inclusion of Persons with Disabilities in Humanitarian Action, launched at the 2016 World Humanitarian Summit. IASC endorsed the guidelines in October 2019. Persons with disabilities and their representative organizations participated in their development.

The original purpose was to translate inclusion commitments into practical humanitarian action. This remains distinct from corporate workforce diversity initiatives. Subsequent implementation resources, including UNICEF’s toolkit, provide checklists, training, budgeting guidance, and accountability tools to support operational application.

3. How IASC Guidelines on Inclusion of Persons with Disabilities in Humanitarian Action Works

The starting point is the interaction between a person’s functioning and their environment. An inaccessible registration process, communication channel, or distribution location can prevent participation. In practical terms, teams should investigate barriers rather than infer requirements from a diagnosis or visible impairment.

The guidelines use a twin-track approach: make mainstream humanitarian programs inclusive while providing targeted support for disability-related requirements. Accessible distribution arrangements belong to the first track; individualized transport assistance or assistive products may belong to the second. Neither track substitutes for the other.

The four “must-do” actions

ActionOperational interpretation
Promote meaningful participationEnable persons with disabilities and organizations of persons with disabilities, or OPDs, to influence assessment, design, delivery, and evaluation.
Remove barriersAddress environmental, institutional, and attitudinal obstacles that prevent access to assistance and participation.
Empower persons with disabilities and strengthen capacitiesSupport their knowledge, skills, and leadership while building humanitarian staff capabilities for inclusive action.
Disaggregate data for monitoring inclusionUse disability-disaggregated information, alongside evidence about barriers and risks, to identify exclusion and improve the response.

These are continuing responsibilities across sectors and phases of humanitarian action, not four sequential stages completed once.

Useful assessment units include a registration pathway, cash-transfer mechanism, shelter site, referral service, or complaints channel. Examine each from the participant’s perspective: successful enrollment does not establish that assistance was accessible, usable, or safely received. UNICEF’s implementation resources similarly connect assessment, planning, delivery, and monitoring.

4. When to Use IASC Guidelines on Inclusion of Persons with Disabilities in Humanitarian Action

Use the guidelines when preparing contingency plans, designing a humanitarian grant, selecting delivery arrangements, reviewing partner performance, or investigating unequal access. They are particularly useful when several organizations control different parts of a response and disability inclusion risks becoming everybody’s aspiration but nobody’s responsibility. Interagency planning guidance treats inclusion as cross-sectoral rather than the responsibility of protection teams alone.

Priority questions include:

  • Does registration exclude people who cannot travel, use a phone, or navigate complex forms?
  • Can participants reach and use payment agents, distribution points, shelters, and sanitation facilities?
  • Can people report misconduct without relying on an intermediary who may compromise confidentiality?

Inputs should combine service-use records, accessibility observations, participant interviews, partner procedures, and information about functioning and barriers. Quantitative counts alone cannot explain exclusion. Reliable information on both affected persons and the obstacles they face is important for response planning.

The guidelines are not a forecasting model or a substitute for technical sector standards. Conclusions will be misleading if teams assess only existing recipients, assume one consultation represents every disability, or treat documented procedures as proof of practical access.

5. How to Apply IASC Guidelines on Inclusion of Persons with Disabilities in Humanitarian Action: Step-by-Step

The following is a practical implementation sequence, not an additional official IASC framework.

  1. Clarify the decision and scope.

    Specify what must change: for example, cash delivery across three districts during the next response phase. Define the services, implementing partners, geographic boundaries, and decisions the sponsor can authorize.

  2. Gather evidence safely.

    Review assistance records, unsuccessful registrations, accessibility conditions, complaints arrangements, and participant experiences. Use accessible consent processes and collect only information necessary for the decision. UNICEF’s checklist emphasizes informed consent and disability-inclusive data ethics.

  3. Define the units of analysis.

    Assess specific service pathways by site, channel, and participant group. Do not average away differences between physical, sensory, intellectual, and psychosocial disabilities. Include people who never entered the program.

  4. Build an inclusion action register.

    Create a working table covering each pathway, the four actions, observed barriers, supporting evidence, proposed changes, accountable owners, costs, and deadlines. This is an implementation aid—not an official IASC scoring system.

  5. Interpret findings with participants.

    Validate apparent barriers with persons with disabilities and relevant OPDs. Distinguish a genuinely inaccessible service from missing data or an unrelated delivery failure. Record uncertainties instead of manufacturing numerical precision.

  6. Authorize and fund changes.

    Combine mainstream improvements with individualized support. Cost communication formats, transport, accommodations, staff preparation, and OPD contributions explicitly. Incorporate these requirements into partner budgets and response funding requests.

  7. Test alternative operating conditions.

    Check whether the approach survives displacement, payment-agent closure, disrupted communications, or reduced transport availability. Ask who becomes excluded under each scenario and prepare accessible alternatives.

  8. Align owners and iterate.

    Bring program, safeguarding, logistics, finance, monitoring, and partner leaders together with OPDs. Agree escalation routes and review actual access after implementation. Revise arrangements when participant feedback contradicts the original assessment.

For a multi-partner rollout, program management support can help convert the register into coordinated workplans, decision logs, and follow-up routines. The sponsor should retain responsibility for resolving unfunded actions and cross-partner dependencies.

6. Example: IASC Guidelines on Inclusion of Persons with Disabilities in Humanitarian Action in Action

Fictional example: Harbor Aid, a humanitarian nonprofit, supports flood-displaced households through food distributions and cash assistance. Its dashboard shows strong registration, but field teams report uncollected transfers and repeated requests for relatives to collect assistance.

The program director selects the guidelines to examine registration, payment collection, distribution, and complaints pathways across three sites. Harbor Aid partners with local OPDs and arranges accessible consultations with people who use services and people who have been missed.

The assessment identifies SMS-only notices, distant payment agents, and complaints routinely routed through family members. The team recognizes that changing distribution locations alone would leave communication and confidentiality problems unresolved.

Harbor Aid introduces multiple notice formats, revises collection arrangements with its payment partner, and offers individually agreed assistance for people unable to travel. Persons with disabilities help test the changes. OPD representatives receive orientation on humanitarian coordination, while staff receive practical inclusion training.

The monitoring team compares successful assistance receipt across participant groups and collects confidential feedback about remaining barriers. The director commissions service delivery transformation to embed the revised pathways in partner procedures. The success criterion is usable, safely received assistance—not training attendance or registration totals alone.

7. Strengths and Limitations

Strengths

  • Connects rights with operations. Participation, accessibility, capacity, and monitoring become explicit responsibilities rather than an isolated inclusion project.
  • Supports cross-functional action. The twin-track approach connects mainstream service improvements with targeted support.
  • Creates a useful diagnostic lens. Teams can examine where people encounter obstacles and distinguish nominal coverage from meaningful access.

Limitations

  • Does not provide an automatic ranking. Leaders still need to judge urgency, protection implications, feasibility, and resource requirements.
  • Depends on implementation capacity. Identifying a barrier does not secure transport, interpretation, accessible facilities, or funding. Inclusion requires deliberately allocated resources.
  • Data tools have boundaries. The Washington Group Short Set does not identify every person with a disability and can underrepresent psychosocial difficulties. Supplement it with appropriate qualitative evidence and other tools.

Use the guidelines to structure decisions, not to declare a program inclusive on the strength of a policy or aggregate score.

8. Common Pitfalls and How to Avoid Them

  • Reducing accessibility to ramps. Physical changes leave communication and procedural barriers untouched. Review the entire service pathway, including information and feedback channels.
  • Consulting without sharing influence. Attendance is not meaningful participation. Involve persons with disabilities before decisions close and explain how their input changed the design.
  • Using recipients as the denominator. Recipient-only analysis overlooks people unable to register. Examine unsuccessful applications and outreach evidence alongside service records.
  • Turning data into an eligibility gate. Functioning questions support statistical analysis; they are not medical diagnoses or a complete assessment of individual assistance requirements. Do not make access depend mechanically on a survey classification.
  • Creating unsafe reporting arrangements. A complaints channel can be accessible but still compromise privacy. Offer safe, appropriate alternatives and test them with intended users.
  • Leaving inclusion unfunded. General commitments do not pay for accommodations or OPD contributions. Assign costed actions and named budget owners before implementation.

9. How IASC Guidelines on Inclusion of Persons with Disabilities in Humanitarian Action Relates to Other Frameworks

Theory of Change—before or alongside. A Theory of Change explains how activities are expected to produce outcomes and makes assumptions explicit. Use it to define the intended result; then use the IASC guidelines to test whether people with disabilities can participate in and benefit from that pathway. Training is an activity, not evidence of improved access.

Sphere standards—alongside. Sphere provides minimum humanitarian standards for areas such as water and sanitation, food security, shelter, and health. Prefer those standards for technical service requirements; combine them with the IASC guidelines when assessing who can actually access the service. Neither replaces the other.

Core Humanitarian Standard—alongside and during implementation. The CHS addresses organization-wide quality and accountability, including participation, accessible communication, safe complaints, and coordinated support. It complements disability-specific analysis by helping embed the resulting changes in organizational systems. The revised CHS was launched in March 2024.

10. Key Takeaways

  • Assess participation and usable access—not simply reported coverage.
  • Combine inclusive mainstream services with targeted support.
  • Work with persons with disabilities, not only on their behalf.
  • Translate findings into funded actions with accountable owners.
  • Use disaggregated data carefully and validate conclusions through participant experience.

11. FAQs About IASC Guidelines on Inclusion of Persons with Disabilities in Humanitarian Action

Are these guidelines relevant to every social-sector organization?

Their direct purpose is humanitarian action. They are especially relevant to emergency-response NGOs, humanitarian funders, and implementing partners. Other nonprofits can draw on their participation and accessibility principles, while adapting the operational guidance to their own services.

Can smaller NGOs apply the guidelines?

Yes. Start with one critical service pathway, engage persons with disabilities, identify immediate barriers, and maintain a short action register. Scale the assessment to available resources without treating limited capacity as a reason to postpone obvious improvements.

What disability data tools should teams use?

Select tools appropriate to the population and purpose. Washington Group functioning questions support disaggregation; child-focused work should consider the UNICEF/Washington Group Child Functioning Module. These tools do not replace questions about barriers, safety, or individual support requirements.

How long does application take?

There is no useful universal timeline. A workshop can establish scope and ownership, but credible assessment requires accessible consultation and operational evidence. Security, geographic reach, partner readiness, and the complexity of proposed changes determine the effort. Treat inclusion as an ongoing management responsibility rather than a one-time study.

How to get started

1

arrow-down-blue

Tell us about your project

2

arrow-down-blue

Interview candidates

(We’ll provide bios within 48 hours on average)

3

Select your consultant and start work

Find a Consultant

or email us at: [email protected]