How to Fill Out the FEMA Request for Public Assistance (w/Examples) + FAQs

The FEMA Request for Public Assistance (RPA) is the official form, now filed inside the FEMA Grants Portal, that an eligible applicant submits to ask FEMA for federal disaster recovery dollars after a Presidential major disaster or emergency declaration. You file it by logging into the Grants Portal, completing the digital RPA (the modern replacement for paper Form FF-90-49), and submitting it to your State, Tribal, or Territorial (Recipient) within 30 days of the date the area was designated under the declaration.

Missing that 30-day window is the single most common way applicants lose access to billions in Public Assistance (PA) funding, and FEMA reports that the PA program has obligated over $200 billion since 1998 to help communities rebuild under the Stafford Act. One missed click in the portal can cost a small county its entire debris removal reimbursement.

• 📝 How to complete every field of the RPA inside the Grants Portal without errors.
• ⏰ The exact deadlines, extensions, and consequences tied to the 30-day rule under 44 CFR § 206.202.
• 🏛️ Which applicants qualify, including States, locals, Tribes, and Private Nonprofits under the PAPPG V4.1.
• 💡 Real named examples, scenario tables, and the seven mistakes that get RPAs rejected.
• ⚖️ How to appeal, arbitrate, or fix a denied RPA using 2 CFR Part 200 and FEMA appeal rules.

What the FEMA Request for Public Assistance Actually Is

The Request for Public Assistance is the gateway document for the entire Public Assistance grant program. Without an approved RPA, an applicant cannot become a “subrecipient” and cannot submit a single project worksheet for reimbursement. The form is short, but it triggers the legal relationship between the applicant, the State or Tribal Recipient, and FEMA under the Robert T. Stafford Disaster Relief and Emergency Assistance Act.

The RPA is governed by 44 CFR § 206.202(c), which requires the applicant to submit it to the Recipient within 30 days after the area is designated. The plain meaning is that the clock starts on the date your county or Tribe is added to the declaration, not the date of the storm itself. The consequence of late filing is denial of eligibility, full stop, unless the Recipient grants a justified extension.

A common misconception is that filing the RPA guarantees money. It does not. It only opens the door so the applicant can begin formulating projects, attending the Recovery Scoping Meeting, and uploading damage documentation. For example, Tina Alvarez, the city manager of a small Florida city, filed her RPA on day 28 after Hurricane Milton and unlocked $4.2 million in debris and emergency protective measure reimbursements that her neighboring town lost by filing on day 33.

The Legal Backbone

The RPA sits on top of three legal layers that every applicant must respect. First is the Stafford Act §§ 403–406, which authorizes FEMA to fund emergency work and permanent work. Second is 44 CFR Part 206, which spells out eligibility, deadlines, and cost share. Third is 2 CFR Part 200, the Uniform Guidance that governs procurement, audits, and allowable costs.

The consequence of ignoring any layer is de-obligation, where FEMA claws back funds years later after a DHS Office of Inspector General audit. A real-world example is the OIG report on Puerto Rico Electric Power Authority, where hundreds of millions were questioned for procurement violations. Applicants often misunderstand that signing the RPA is also a legal certification that they will follow these federal rules.

Who Can File an RPA

Eligibility is narrower than most people assume, and FEMA only recognizes four applicant types under 44 CFR § 206.222. Filing as the wrong entity is a fast path to denial, and FEMA will not let you “switch” the applicant after the 30-day window closes. The plain meaning is that only legally distinct entities with their own taxpayer identification number and governing authority should file.

The four eligible applicant types are State agencies, Local governments (including counties, cities, special districts, and council of governments), Federally Recognized Tribal governments, and certain Private Nonprofit (PNP) organizations. Tribes also have the unique option to file as a Recipient directly with FEMA under the Sandy Recovery Improvement Act of 2013. Each category has its own evidence requirements, and the consequence of mixing them up is rejection.

A common misconception is that any 501(c)(3) qualifies. Only PNPs that own or operate an eligible facility providing a critical service or essential social service qualify under Section 102 of the Stafford Act. For example, Pastor James Whitfield of Grace Community Shelter learned that his food pantry qualified as essential social service, but only after first applying for an SBA disaster loan for non-critical facilities, as required by 44 CFR § 206.226(c).

Private Nonprofit Deep Dive

PNPs face the toughest paperwork burden when filing the RPA. They must upload an IRS tax-exempt determination letter, or a state ruling that confirms nonprofit status, plus governing documents like articles of incorporation and bylaws. The consequence of missing one document is automatic deferral until the next quarterly review, which can stall reimbursement by 90 days or more.

PNPs are split into two buckets. Critical services PNPs (education, utility, emergency, medical, and custodial care) can apply directly to FEMA. Non-critical but essential PNPs (museums, libraries, community centers, shelters, food banks) must first apply to the SBA, get a denial or partial loan, and then come back to FEMA for permanent work funding under PAPPG V4.1, Chapter 2. A common misconception is that the SBA detour blocks emergency work funding, but it does not, emergency protective measures remain directly eligible.

Tribal Nation Options

Federally Recognized Tribes can choose to be a Recipient (direct relationship with FEMA) or a Subrecipient (through the State). The Tribal Declarations Pilot Guidance explains how to elect Recipient status. The consequence of choosing wrong is administrative complexity and slower obligation.

For example, Chairwoman Linda Crow Feather of a Plains Tribe chose Recipient status after a 2025 ice storm because her Tribe wanted control of the cost-share waiver request. The decision unlocked direct coordination with the FEMA Region 8 office and saved nearly four weeks of routing time. A misconception is that small Tribes lack capacity for Recipient status, but FEMA provides direct technical assistance through the Tribal Affairs Office.

Step-by-Step: Filling Out the RPA in the FEMA Grants Portal

The modern RPA is filed inside the FEMA Grants Portal, the cloud platform that replaced legacy paper submissions for nearly all applicants. The plain process is register, log in, locate the open declaration, complete the digital RPA, and submit. The consequence of skipping registration is that the 30-day clock keeps ticking while you wait for account approval, which can take 3 to 5 business days.

Before starting, gather your SAM.gov Unique Entity ID (UEI), your DUNS legacy number if applicable, your authorized representative’s signed designation letter, and your Public Assistance Program and Policy Guide. A common misconception is that SAM.gov registration is optional for small applicants, but it is mandatory under 2 CFR § 25.205.

Step 1: Register in the Grants Portal

Go to the Grants Portal sign-up page and click Apply to be a PA Applicant. Enter your organization’s legal name exactly as it appears on your IRS or state record. Mismatches with SAM.gov cause obligation delays later.

Provide the primary contact name, email, and phone number. The system emails a verification link within minutes. The consequence of using a personal email address is loss of access if that employee leaves; always use an organizational domain. For example, Maria Lopez, finance director of a Texas county, registered with her county.gov address and kept access through three staff turnovers.

Step 2: Locate the Active Declaration

After logging in, the portal shows a list of open events. Click the correct disaster number, such as DR-4824-FL or EM-3601-NC. Selecting the wrong event is a frequent error and creates an orphaned RPA that FEMA cannot match to your declaration.

Verify that your county or Tribe is listed in the designated areas under the Designated Areas page. If your area is not yet designated, you cannot file. The consequence of premature filing is automatic system rejection, but you can monitor the FEMA disaster page daily for updates.

Step 3: Complete the Applicant Information Section

Enter the legal name, physical address, mailing address, county, congressional district, FIPS code, and EIN. The FIPS county code must match Census records. Errors here cascade into every project worksheet later, and FEMA staff have to manually correct them, slowing obligation.

Pick the correct applicant type from the dropdown: State, Local, Tribal, or PNP. For PNPs, the portal opens additional required uploads. A real example is Riverside Memorial Hospital, which mistakenly chose “Local Government” instead of “PNP,” and had to refile the entire RPA after a two-week back-and-forth with the Recipient.

Step 4: Designate the Primary and Alternate Contacts

The Primary Contact receives every notification. The Alternate Contact is the backup. List a third Authorized Representative who is legally empowered to sign grant agreements, often the mayor, county judge, tribal chair, or PNP executive director, supported by a board resolution.

The consequence of listing only one contact is a complete communication blackout when that person is on vacation or out sick. A common misconception is that the IT department should be the primary contact, but FEMA needs a programmatic contact who knows the projects, not just the system administrator.

Step 5: Identify Damage Categories and Impacts

Check every applicable category from A to G. Category A is debris removal, B is emergency protective measures, C is roads and bridges, D is water control facilities, E is buildings and equipment, F is utilities, and G is parks, recreational, and other facilities, all defined in PAPPG V4.1, Chapter 7. Under-reporting categories at the RPA stage does not bar later projects, but it slows resource assignment at the Recovery Scoping Meeting.

Provide a rough damage estimate, even if it is a placeholder. The consequence of leaving the field blank is that FEMA’s automated triage tool may assign your applicant a lower-priority queue. A common misconception is that the dollar figure is binding, but it is not; you can revise it as project worksheets develop.

Step 6: Sign and Submit

The Authorized Representative electronically signs and submits the RPA. The portal generates a tracking number and a PDF receipt. Save both. The consequence of not downloading the receipt is that you cannot prove timely filing if there is a dispute, and FEMA’s portal logs are not always accessible to applicants in real time.

After submission, the Recipient (your State Emergency Management agency) reviews and forwards to FEMA. FEMA then formally accepts the applicant and schedules the Recovery Scoping Meeting within 21 days under the new PA Delivery Model. A misconception is that filing the RPA means money is on the way, but the actual obligation happens project-by-project, often months later.

Three Real-World Filing Scenarios

Filing Action	Funding Outcome
County files RPA on Day 12 with complete data and signed designation letter	FEMA accepts within 5 days, Recovery Scoping Meeting set for Day 21, debris reimbursement obligated within 60 days
PNP files RPA on Day 25 without IRS determination letter	RPA deferred, applicant uploads letter on Day 35, FEMA accepts but emergency work obligation delayed by 6 weeks
City files RPA on Day 33 with no extension request	Recipient denies as untimely under 44 CFR § 206.202(d), city loses eligibility for $7.8 million in projects

Applicant Choice	Legal Consequence
Tribe elects Recipient status under SRIA	Direct FEMA coordination, but Tribe must manage its own subrecipient monitoring and single audit
Non-critical PNP skips SBA loan application	FEMA denies permanent work projects under 44 CFR § 206.226(c), only emergency work funded
Local government uses wrong FIPS code	Project worksheets bounce back, obligation delayed 30+ days, possible duplicate-applicant flag

Documentation Decision	Reimbursement Impact
Applicant uploads SAM.gov UEI confirmation at RPA stage	Smooth obligation, no payment hold
Applicant uses expired SAM.gov registration	Payments frozen until renewal under 2 CFR § 25.205
Applicant lists personal Gmail as primary contact	Communication breakdown when staff leaves, missed deadlines, possible de-obligation

Named Examples That Illustrate the Process

Maria Lopez, finance director of a Gulf Coast county, filed her RPA on Day 9 after a hurricane declaration. She uploaded the Designation of Applicant’s Agent form, confirmed her SAM.gov registration was active for the next 14 months, and selected Categories A, B, C, and E. Her county received its first obligation within 47 days, well below the national median.

Pastor James Whitfield of Grace Community Shelter, a non-critical PNP, filed his RPA on Day 18. He first applied to SBA disaster loans, received a partial denial letter, and then submitted that letter to FEMA under 44 CFR § 206.226(c). His shelter ultimately received $312,000 in permanent work funding for roof repairs.

Chairwoman Linda Crow Feather of a Northern Plains Tribe filed as a Recipient under the Tribal Declarations Pilot Guidance. She negotiated a cost-share adjustment directly with FEMA Region 8 and used Tribal Mitigation Plan crosswalks to fast-track Section 406 mitigation funding.

Mistakes to Avoid

• Missing the 30-day deadline under 44 CFR § 206.202, which causes complete loss of eligibility unless a written extension is granted by the Recipient with documented justification.
• Filing under the wrong applicant type, such as a hospital district filing as a city, which forces a complete refile and burns precious days off the clock.
• Letting SAM.gov registration expire, which freezes all payments under 2 CFR § 25.205 and can stall reimbursement for months.
• Forgetting to upload the Designation of Applicant’s Agent resolution, which means FEMA cannot legally accept signatures and the RPA sits in limbo.
• Listing only one contact, which creates a single point of failure and risks missed Recovery Scoping Meeting invites.
• Skipping the SBA loan step for non-critical PNPs, which under 44 CFR § 206.226(c) makes permanent work projects ineligible.
• Underreporting damage categories, which delays resource assignment and complicates project formulation later.
• Using personal email for the primary contact, which causes communication failures when employees leave and can lead to missed appeal windows.
• Submitting without saving the PDF receipt, which leaves the applicant unable to prove timely filing in any future appeal under 44 CFR § 206.206.

Do’s and Don’ts

• Do confirm your area is designated on the FEMA declarations page before filing, because premature submissions get rejected.
• Do keep your SAM.gov UEI active and renewed annually, because expired registrations halt payment.
• Do upload the signed agent designation resolution at the RPA stage, because it speeds obligation later.
• Do select every potentially impacted damage category, because adding categories later slows project worksheets.

• Do request a deadline extension in writing if needed, because 44 CFR § 206.202(d) allows it for justifiable reasons.

• Don’t wait until Day 29, because system outages and document gaps can blow the deadline.

• Don’t use a personal email, because turnover causes communication blackouts.
• Don’t ignore Recipient guidance, because the State or Tribe is your direct overseer and gatekeeper.
• Don’t assume PNP status without documentation, because FEMA requires the IRS determination letter.
• Don’t skip reading the PAPPG V4.1, because every eligibility rule sits inside it.

Pros and Cons of the Grants Portal RPA Process

• Pro: Real-time tracking and timestamped submission inside the Grants Portal eliminate disputes about timeliness.
• Pro: Document uploads are centralized, reducing lost paperwork compared to the legacy paper Form FF-90-49.
• Pro: Automated routing to the Recipient cuts manual handoffs and shortens review windows.
• Pro: Integration with project worksheet workflows allows seamless progression from RPA to obligation.

• Pro: The Portal stores historical declarations, useful for repeat applicants in disaster-prone regions.

• Con: Account approval can take 3 to 5 business days, eating into the 30-day window.

• Con: Portal outages during peak disaster activity have been reported, which can spike applicant anxiety.
• Con: PNPs face heavier upload burdens than other applicants, including IRS letters and bylaws.
• Con: The Portal’s user interface is not always intuitive for first-time small-government users.
• Con: Mistakes made at the RPA stage cascade into every later project worksheet, and corrections require Recipient intervention.

Appeals, Arbitration, and Fixing a Denied RPA

If a Recipient or FEMA denies your RPA, the applicant has the right to a first appeal within 60 days of the denial under 44 CFR § 206.206(c). The plain meaning is that you must submit a written appeal through the Recipient, with documentation explaining why the denial was wrong. The consequence of missing the 60-day window is loss of appeal rights.

A second appeal goes to the FEMA Assistant Administrator for Recovery within another 60 days. For disputes over $500,000 (or $100,000 for small impoverished communities), applicants can elect PA Arbitration before the Civilian Board of Contract Appeals. A real example is City of Arcadia v. FEMA, where the city successfully argued for a procurement-related appeal under Uniform Guidance principles.

A common misconception is that appeals are pointless because FEMA almost always wins. In reality, the GAO disaster recovery reports show that a meaningful share of appeals lead to partial or full reversals when applicants document procurement, eligibility, and cost reasonableness carefully under 2 CFR Part 200.

Key Entities You Will Work With

The Recipient is your State, Tribal, or Territorial emergency management agency, which acts as the pass-through grantee. The Subrecipient is you, the applicant. FEMA’s Joint Field Office (JFO) houses the Public Assistance Group staff who run scoping meetings. The Program Delivery Manager (PDMG) is your single point of contact at FEMA.

The Office of Inspector General audits closeout, and the Government Accountability Office reviews program-wide performance. The Small Business Administration handles non-critical PNP loan referrals. Each entity has a discrete role, and confusing them is a frequent cause of delay.

Federal vs. State Nuances

Federal law sets the floor through the Stafford Act, 44 CFR Part 206, and 2 CFR Part 200. States layer on additional rules through their emergency management agencies, such as California OES, Texas Division of Emergency Management, and Florida Division of Emergency Management.

Some states require applicants to attend a State Applicant Briefing before the RPA can be accepted. Others, like Florida, use FloridaPA.org as a parallel state portal that mirrors the FEMA Grants Portal. The consequence of ignoring state-specific portals is duplicate filings and miscommunication. A misconception is that the federal portal is enough; in many states, it is not.

FAQs

Is the FEMA RPA the same as a project worksheet?

No. The RPA only registers you as an applicant. Project worksheets come later for each individual damaged site or activity, after FEMA accepts your RPA and schedules the Recovery Scoping Meeting.

Can I file the RPA after the 30-day deadline?

Yes, but only if the Recipient grants a written extension under 44 CFR § 206.202(d) for justifiable reasons. Without an extension, the late RPA is denied.

Do private nonprofits qualify for FEMA Public Assistance?

Yes, if they own or operate an eligible facility providing critical or essential social services and hold an IRS determination letter or state nonprofit ruling.

Must I have an active SAM.gov registration to file?

Yes. Under 2 CFR § 25.205, a current SAM.gov UEI is required for any federal grant payment, and expired registrations freeze obligations.

Is the paper Form FF-90-49 still accepted?

No, in nearly all cases. FEMA has migrated RPA filings to the Grants Portal, with paper used only in rare connectivity-limited situations.

Can a Tribe file directly with FEMA without going through the State?

Yes. Federally Recognized Tribes can elect Recipient status under the Sandy Recovery Improvement Act and the Tribal Declarations Pilot Guidance.

Does filing the RPA guarantee funding?

No. It only opens applicant status. Actual funding flows project-by-project after damage documentation, eligibility review, and obligation under PAPPG V4.1.

Can I appeal a denied RPA?

Yes. Applicants get a first appeal within 60 days and a second appeal within another 60 days under 44 CFR § 206.206, plus arbitration for larger disputes.

Do I need a Designation of Applicant’s Agent resolution?

Yes. A signed Designation of Applicant’s Agent is required so FEMA knows who is legally authorized to sign grant agreements.

Are emergency protective measures eligible before the RPA is approved?

Yes. Costs for life-safety emergency protective measures incurred during the incident period are reimbursable, as long as the applicant later becomes eligible by filing a timely RPA under the Stafford Act § 403.

Can my city add damage categories after submitting the RPA?

Yes. You can update damage categories during project formulation, although early identification helps FEMA assign the right scoping resources under the new PA Delivery Model.

Does FEMA pay 100 percent of disaster costs?

No. The standard federal cost share is 75 percent, with 25 percent paid by the non-federal applicant, unless the President authorizes a higher share under Stafford Act § 403(b).