We use cookies to optimize our website and our service.
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
The technical storage or access that is used exclusively for statistical purposes.
The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
FAST – Past, Present, and Future
Leave a Comment
Updated: April 22, 2025 by June Kailes
Functional Assessment Service Teams (FAST)
Past, Present, and Future
By June Isaacson Kailes
Published: April 2025
This article explores FAST’s (Functional Assessment Service Teams) history, present status, and future opportunities and challenges.
A generic description of FAST is teams of government and community partners with disability skill sets that are deployed in a disaster to deliver needed support. These supports enable people with disabilities to be included in disaster planning, response, recovery, and mitigation to maintain health, safety, and independence.
There are many opportunities for FAST adoption and customization.
This article recommends that readers question, from the perspective of their roles and responsibilities, “Is there value in FAST?”
Below you will find:
Motivation and History
In the 1970s and 80s, decades before Hurricane Katrina, a handful of us California advocates documented the deep and dramatic lack of equal and inclusionary emergency services for people with disabilities. Examples of this discrimination included people with disabilities being turned away from shelters (wheelchair and mobility scooter users, service animal users, blind people, Deaf people, etc.). When attempting to register at a shelter, people with disabilities were sometimes separated from families and significant others, and asked to go to or sent to medical shelters or other facilities and institutions (hospitals, nursing homes, and other long-term care facilities). Rather than working to make sure people remained in their homes in the community, there was the misconception that it was better to admit people to nursing facilities. Once admitted, leaving was extremely difficult as people lost their community support, such as housing, personal attendants, etc.
The common belief was that people with disabilities were sick, needed medical care, needed protection, needed supervision, and thus needed “special shelters.” What may appear as acute, vulnerable, and fragile to the untrained and biased eye is just the everyday disability-lived experience.
People with disabilities were and continue to be confronted with the indiscriminate application of the medical model. The false belief is that most people with disabilities need medical services and medical care. This implicit bias to see people with disabilities as ‘sick’ or ‘unwell’ unnecessarily overburdened scarce emergency medical resources.
Experienced community-based disability services staff ready to help at shelters were turned away because of a “lack of proper credentials.”
In 2007, I conceived and pitched the concept of FAST to the California Department of Social Services, which contracted and worked with me to develop the FAST concept, plans, and training course. In 2010, it was accepted as a FEMA Course.
Intent and Objectives
In California, where FAST originated, the intent was to work together better and smarter by providing disability-related assistance through increasing capacity. This meant building partnerships with community-based organizations (CBOs), cities, counties, states, the American Red Cross, and other Voluntary Organizations Active in Disaster (VOAD) to develop the teams. They would be made up of government workers and community disability service staff, especially those with lived experience. This included blending government workers’ competencies and skill sets with those of community disability service providers.
By applying nimble, flexible, and scalable competencies, team members would complement and augment shelter workers to address the complexities of supporting people with disabilities in maintaining their health and safety, and surviving emergencies. Together, team members had a working knowledge of cross-disability access needs (hearing, vision, mobility, speech, and/or memory and understanding, mental health, and behavioral health). Teams may move to other shelters and return to shelters as needed or requested.
Team members would:
FAST support decreased the impact and gaps caused by the disaster disruption and degradation of critical support systems and customized environments, which typically work barring emergencies. These disruptions contributed to severe disproportionate impacts during emergencies for people with disabilities.
Team Makeup:
Eligible individuals for FAST team membership included people with the core capabilities and skills needed to work effectively with people with disabilities. These skills were not something they would acquire through FAST training, but they already had those competencies and skills.
The intent was a group of combined skills and experience working with people with varying access and functional needs, such as older people, people with chronic health, mental health and behavioral health conditions, people with intellectual and developmental disabilities, hearing loss, and vision loss. In other words, people would bring their awareness and skill sets to a team. Team members had the knowledge, skills, and ability to work in their area(s) of access and functional needs.
Present
FAST programs have evolved with customized focuses, resources, and versions depending on location. (See below “Examples of expanded FAST roles”). Some states and local governments have active FAST, while others have inactive FAST. There is no definitive data to track how many teams are in development versus how many teams have deployed, and how many are deployment-ready. There is a lot of focus on the start-up process and training, but less on deployment and sustainable teams. Some current conceptual FAST practices exhibit some “medical model” influence, undermining the principles of independence and community-based support. Much information about FAST needs to be collected and analyzed, and some critical questions are listed in the “Investigate the options” below.
The California FAST website, describes FAST eligibility as a “minimum of two years” experience working with and/or the AFN (access and functional needs) community.” At the local government’s request, a team of 2-8 trained members deploys to emergency shelters.
In California and elsewhere, unlike the original intent, many teams have morphed into government-centric teams instead of a mixed makeup of government workers and community partners.
Government-only FAST, as opposed to a preferred mixed makeup team of community and government workers, may involve some people with disabilities who happen to be government employees. There is no assurance that they bring to their role the needed lived experience or skills at applying independent living values and a social model to delivering services rooted in understanding the details, diversity, nuances, and complexity of living with a variety of access needs.
Payment and Reimbursement:
Why the transition to government-only teams? It is easier and takes less effort to train, recruit, and deploy government workers because of expense reimbursement, insurance, and liability issues. CBO participation is a sizable unresolved barrier. A significant weakness overlooked in FAST’s initial conception is the expense reimbursement, insurance, and liability issues.
Because of this, disability services staff often must volunteer with no reimbursement. The expectation that all community partners will volunteer their time does not work.
Although many community-based organizations have non-profit tax status, this does not mean volunteers do their work. Community-based organizations have contractual payroll, operating expenses, compliance, and deliverable obligations. Staff serving on teams means the CBO must cover staff salaries, overtime, travel, etc., which is sometimes impossible without additional funding.
The lesson to apply is that agreements with CBOs must include the who, what, where, when, why, how, and reimbursement details agreed on in advance.
Future
FAST was conceived in 2006 – 2007. What is slowly changing is the growing recognition of the need for disability-inclusive planning, services, processes, and training. The outdated disability implicit biases are now more frequently challenged, models are shifting, and acceptance and adoption of inclusion are increasing. The number of state and local access and functional needs coordinators in emergency management continues to grow.
Establishing or Reworking and Refining
There are many ways to institute FAST, and there is no one right way. There is much to consider and investigate regarding whether a FAST concept will work for you.
For readers interested in establishing or reworking and refining FAST, consider broadening the focus and roles, refreshing and augmenting the training, renaming FAST, defining measures of success, and investigating different FAST programs in terms of what is working and what needs to change.
Broadening the Focus
FAST’s sheltering focus is too narrow. Some local governments never or rarely open shelters. The FAST roles before, during, and after disasters should be flexible and customizable. (See “Examples of Expanded FAST Roles” below).
Expanding the Makeup of Potential Community Partners
Use the expertise of local community partners instead of only using a state team that may be disadvantaged and may not be as familiar with local resources, culture, norms, and demographics.
The responding partners should consist of and represent diversity in experiences to provide effective services. For example, in the context of privilege and ableism, it means avoiding implicit disability biases and inaccurate assumptions such as everyone having stable internet connections, money to buy emergency supplies, a usable vehicle, and the ability to walk, lift, run, see, hear, speak, remember, and understand.
Expand the definition of potential community partners to include overlooked segments such as:
Partners should include:
Examples of Expanded FAST Roles:
Training:
Many who took FAST training during blue sky times cannot apply what they learned for years, and many trained individuals are no longer available. Therefore, it is crucial to devote greater focus and resources to ongoing training and just-in-time training at the beginning of deployments. This training should consist of refresher information such as short practical, tactical steps, and using existing field operation guides (FOGs), job aids, etc.
FAST training should be reserved for people who are eligible to become team members. Since there are few courses that address access and functional needs, many take FAST training to get this information, knowing they cannot be a team member due to pre-existing disaster-related obligations.
Others take the training because they are considering what it takes to develop, maintain, and sustain a FAST program, which calls for a separate training designed for FAST program administrators.
Measuring success:
Evaluation methods typically focus only on the process versus results. For example, in training, positive participant training evaluations of content and instructors, the number of training sessions delivered, and participants who passed the post-training test are all process measures.
Success training measures should focus on impact and results. Here are a few examples:
Renaming FAST
Existing FAST also have different names. Many endorse changing “assessment” to assistance regarding a FAST name change, as assessment is not enough without follow-up assistance. Others suggest changing “service” to “support.”
Investigate the options:
Define your intent and goals, and consider investigating existing FAST programs and other options. What is working, and what needs change?
Other options exist to leverage partnerships and maximize impact from effectively working with and contracting with diverse community partners to prepare for, respond to, recover from, and mitigate the effects of disasters and emergencies. When adequately prepared, community partners with critical planning, response, and recovery capacity roles can reach and help more people than the government alone to prevent deaths and injuries. (See Return on Investments in Public Engagement).
There is a common underestimation of what it takes to develop, operationalize, maintain, and sustain FAST. Avoid iceberg planning by diligently exploring the layers of detail under the surface including:
Identify and interview local jurisdictions and states with FAST deployment experience versus those focused on the start-up activities of adapting training and recruiting teams. Even in California, the number of people trained is impressive, but the number of team deployments is small.
Questions to Ask When Starting a FAST Program
Teams and numbers of active members:
Active deployable list:
Training:
Evaluation:
Summary
There is much to consider and investigate regarding whether a FAST program or other options are right for you. Explore all the options that leverage partnerships to maximize impact from effectively working with and contracting with diverse community partners to prepare for, respond to, recover from, and mitigate the effects of disasters or emergencies. Be thoughtful, comprehensive, and diligent in exploring the details.
Resources
Community partners:
Competencies:
Site Surveys:
About the Author
June Isaacson Kailes
June owns a disability policy consulting practice and is a pioneer, leader, and innovator in health care, emergency management, aging with disability, stakeholder engagement, and hospitality. The breadth and depth of her experience in disability, accessibility, and functional needs issues are widely known and respected as a writer, trainer, researcher, policy analyst, subject matter expert, and advocate. June concentrates on replacing the ambiguous aspects of disability etiquette, sensitivity, awareness, and legal compliance with maximum impact, practices, and measurable skill sets. June works with clients to build critical disability competencies and capabilities. She translates the laws and regulations into clear, actionable, detailed, and sustainable building blocks and tools that close service gaps, prevent civil rights violations, and remove barriers, inequities, and disparities. June uses the “how, who, what, where, when, and why, to get physical, programmatic, communication, and equipment access right! June has received many honors and awards, has delivered hundreds of keynote addresses, workshops, and seminars, and has over 200 publications.
Read and find more resources on June's website here.
Category: Tags: disability, disasters, emergencies, FAST, preparedness