
A disaster intake form fixes that. It gives response teams one consistent way to learn who needs help, what happened, and which services apply, without turning survivors into professional form-fillers.
This template is built for nonprofits, government agencies, faith-based organizations, and emergency response teams coordinating their own assistance programs. It supports case intake and inter-agency coordination. It does not replace an official FEMA application.
Below, we'll cover every section worth including: survivor information, household needs, damage and displacement details, consent, referrals, and follow-up, plus how to design and test the form for real disaster conditions.
Key Takeaways
- Capture only what's needed for triage, service delivery, referrals, reporting, and follow-up
- Separate required fields (name, contact, urgent needs) from conditional ones like insurance or document uploads
- Build for mobile, in-person, kiosk, and assisted intake since survivors won't all reach you the same way
- Confirm current FEMA, state, local, and funder requirements before using the form in a live response
What Is a Disaster Intake Form?
A disaster intake form is an internal tool. It captures a survivor's situation, immediate needs, eligibility indicators, requested services, and next steps in one place so your team can act quickly and coordinate with partners.
It's easy to confuse with other disaster records, but each one answers a different question:
| Record | What it actually does |
|---|---|
| Disaster intake form | Connects a survivor to your organization's own services |
| Preliminary damage assessment | Measures community-wide impact to support a disaster declaration |
| FEMA Individual Assistance application | Determines federal benefit eligibility |
| Service referral form | Documents a handoff to another provider after intake |
The people who rely on this form every day aren't just survivors. These roles all need the same data to stay coordinated, especially when a case moves between hands during a surge:
- Intake staff and case managers
- Volunteers and partner agencies
- Program administrators
No single template works for every situation. A form built for a flash flood response won't look identical to one built for a multi-state wildfire recovery lasting months.
Your form should match the disaster type, response phase, service catalog, and funder requirements. CharityTracker's disaster recovery case management software supports that customization for short-term emergency response and long-term recovery in the same system.
What to Include in a Disaster Intake Form
Organize the template so intake workers move from immediate safety concerns toward household details, damage, needs, and follow-up, without overwhelming the person in front of them.
Essential Contact and Household Information
Collect the basics first, and ask them carefully:
- Name and preferred name
- Safe contact method (phone, email, or in-person only)
- Current location and mailing address
- Damaged-property address, if different from current location
- Household members, ages, and relationships
- Language preference and accessibility or communication needs
Add a safe-contact question. Someone staying in a shelter, sharing a phone, or displaced from their usual address may not be reachable through standard channels. Ask directly how and when it's safe to follow up.
Before collecting Social Security numbers or other sensitive identifiers, research what your program actually requires. FEMA's eligibility criteria for federal assistance call for SSN verification to confirm identity for a federal benefit decision — a different process with a different legal basis than your organization's intake.
If your services don't require it, don't ask for it.
Disaster, Damage, and Displacement Details
Capture the basics of what happened:
- Disaster type and date or date range
- Affected location and evacuation or displacement status
- Current housing situation and property type
- Plain-language description of damage or loss
Add conditional fields only when relevant:
- Insurance coverage and policy or claim status
- Landlord or homeowner status
- Help already received elsewhere
A photo or document upload area can support specific decisions. Always offer an alternative for people who can't upload files from a shelter or a borrowed phone.
Immediate Needs and Risk Screening
Keep this section short. National VOAD's case management guidelines define an immediate need as anything whose absence threatens health or safety — food, medication, emergency housing, and crisis counseling. Build triage questions around that standard, not property damage alone.
Cover:
- Urgent shelter, food, water, clothing, and medication
- Medical care, transportation, power, and sanitation
- Childcare, pet safety, and personal safety concerns
Include a question that can surface safeguarding risks, and give staff clear instructions to escalate emergencies immediately rather than waiting on routine review. Let trained staff assign the priority or urgency rating. Don't phrase questions so survivors feel they must prove how bad things are.

Services, Referrals, and Consent
List what your organization actually offers and let staff (or respondents) select what's needed: supplies, temporary lodging, repairs, financial assistance, legal help, benefits navigation, or case management.
For referrals, record:
- Partner organization and referral date
- Receiving agency and reason for referral
- Consent status and who owns the follow-up
Consent language should be plain, not legal boilerplate. Explain how information will be used, who might receive it, and that agreeing to a referral is optional.
CharityTracker's network requires a signed Release of Information before basic identifying data is shared across member agencies, and services are never contingent on that agreement — a useful model on any system.
Follow-Up and Documentation
Close the loop without rewriting the whole intake narrative:
- Intake date, staff or volunteer name, and case number
- Preferred follow-up method, assigned worker, and target date
- Current status and next action
Allow staff to log services delivered, unmet needs, duplicate records, and closure reason as separate updates. Before finalizing these fields, check your funder's reporting requirements — VOCA, ESG CAPER, or HMIS — and map only the fields those programs actually need.
How to Design the Form for Real Disaster Conditions
A solid field list still fails if the form slows people down mid-crisis. Start with a short first-stage form for urgent triage, then layer in conditional questions or a full case-management assessment once immediate safety and basic needs are addressed. Digital intake tools used by disaster relief teams—including platforms like CharityTracker—make that staged approach easier to run across phones, kiosks, and staff-assisted entry.

Make the Form Easy to Complete Under Pressure
Keep completion fast when stress is high:
- Use plain language and short questions
- Group related fields together
- Make touch targets large, contrast readable, and required fields obvious
- Skip jargon and unexplained program acronyms
Design for mobile phones, tablets, paper-assisted entry, and low-connectivity environments. Research accessibility requirements for your service area before launch, not after a complaint.
Offer interpreter support and a way for staff to record answers on a survivor's behalf. Self-service should never be the only path.
Use Conditional Logic and Reduce Duplication
Only show what matters in the moment:
- Insurance questions after someone indicates they have coverage
- Property questions only for homeowners or renters who need that help
- Business questions only when the respondent is reporting business impact
That alone shortens the form for most people.
Use a consistent household or case identifier to flag possible duplicate records, but never deny service on a match alone—verify first. Be explicit about which fields the survivor answers, which staff complete, and which get verified later.
Build in Trust, Privacy, and Transparency
Place a short privacy notice near sensitive questions. State plainly that providing information does not guarantee assistance or approval. Ask only for data tied to services you actually deliver.
When sensitive data is required, spell out:
- Who can access it
- How long you keep it
- How someone can request a correction
Add a review or read-back step before submission so survivors can fix errors—especially phone numbers, addresses, names, and urgent needs. That one step catches more mistakes than field validation alone.
Test the Template Before Deployment
Pilot the form with intake workers, volunteers, accessibility reviewers, and people with direct disaster recovery experience. Research applicable legal, contractual, funder, and government requirements, then document which fields are mandatory and why.
Next, run a simulated surge and confirm the form still works when you hit:
- Duplicate submissions
- Incomplete responses
- Multiple languages
- Attachment failures
- Loss of internet connectivity
If it fails in any of those conditions, fix it before the next activation—because it will fail in a real response.
From Intake Submission to Coordinated Follow-Up
A form is only the front door. What happens after submission determines whether survivors actually get help.
Post-submission workflow:
- Receive and screen urgent needs
- Verify essential details
- Assign ownership
- Coordinate services
- Document outcomes
- Follow up

Triage and Immediate Response
Define in advance which answers trigger immediate staff review, emergency escalation, or a shelter or medical referral. Keep emergency instructions visible on the form itself and on the confirmation screen, so someone in immediate danger isn't left waiting for a routine queue to catch up.
Review and Case Assignment
Set up a review queue with a designated owner, response priority, and status label for every submission. Don't promise a response time you can't consistently meet.
Train staff to tell the difference between incomplete information and actual ineligibility, and give them a way to contact applicants for clarification without forcing a restart.
A GAO review of case management after Hurricanes Katrina and Rita found that providers in Mississippi couldn't reach more than 1,000 of over 5,000 clients because contact details were outdated or inaccurate. Accurate contact data isn't a nice-to-have; it's the difference between a case getting closed and a survivor falling through the cracks.
Referrals and Partner Coordination
Record what was requested, what was provided, what was referred elsewhere, and whether the applicant consented to that sharing. Standardized service and referral categories let every participating agency read the same record the same way, which makes unmet needs easier to spot at a program level.
This is where CharityTracker's Assistance Network earns its keep. Instant referrals between member agencies, backed by consistent service categories, help prevent one household from receiving duplicate aid while another goes without.
Follow-Up and Closure
Set follow-up checkpoints based on the type of assistance provided. Track contact attempts, outcomes, remaining needs, and changed circumstances.
Closure should use consistent statuses:
- Resolved
- Referred
- Unable to contact
- Declined
- Duplicate
- Outside program scope
Keep a path open to reopen a case if needs continue; disaster recovery rarely wraps up on a single visit.
Reporting and Improvement
Track aggregate measures over time:
- Response volume
- Urgent needs identified
- Referral completion rate
- Unmet needs
- Services delivered
- Time from intake to first contact
Use de-identified trends, not individual records, to adjust staffing and resource allocation for the next event. Never publish personally identifiable survivor data in a report.
Digitize and Secure Disaster Intake Management
Paper forms and spreadsheets work fine for a handful of intakes. They fall apart fast once you're dealing with high submission volume, multiple intake locations, rotating volunteers, partner referrals, remote intake requests, and ongoing follow-up across weeks or months.
That's the gap a system like CharityTracker was built to close. It helps disaster-response teams:
- Centralize client records in one place
- Support remote and kiosk intake
- Coordinate referrals across partner agencies
- Capture digital signatures
- Produce the reports funders ask for
CharityTracker started in 2006 during Hurricane Katrina relief efforts, when community leaders in Florence, Alabama, needed a better way to coordinate assistance across overwhelmed agencies. It's a case management tool for mission-driven organizations, not a FEMA application portal or a government system.
If you're evaluating any digital intake platform, research and document:
- Access permissions and who can view or edit records
- Encryption in transit and at rest
- Backup procedures and incident response plans
- Retention periods tied to applicable federal, state, local, and program requirements
Pair whatever system you choose with a written data governance plan. Spell out who can view records, how consent is documented, how attachments are protected, how long you keep data, and how it's securely disposed of when that period ends. A platform can only enforce the rules you've written down.

Frequently Asked Questions
How do I get approved for disaster assistance?
Approval depends on the specific program's eligibility rules and verification process. An organization's intake form is not a federal application; for FEMA assistance specifically, check current requirements at DisasterAssistance.gov.
How long does it take to get approved for FEMA disaster assistance?
Timing varies by disaster, application completeness, inspection needs, insurance status, and program workload. There's no fixed national timeline, so check your application status directly in your FEMA account at DisasterAssistance.gov.
What information should a disaster intake form collect?
Core fields usually include contact details, household and housing situation, disaster impact, urgent needs, requested services, consent, referrals, and follow-up information. Avoid collecting sensitive data your services don't actually require.
Does a disaster intake form replace a FEMA application?
Generally, no. Your form helps coordinate your own organization's services, while FEMA assistance requires the official application process and current federal eligibility rules.
How can organizations protect information collected after a disaster?
Collect only what's necessary, document clear consent, and restrict access by role. Use secure transmission and storage, limit document access, set retention rules, and train staff on compliance requirements regularly.