FEMA requires timely and complete project-level information from a recipient as work is completed to facilitate efficient and effective closeout of the recipient's prime award. To initiate project-level closeout, subrecipients must inform the recipient that their project is complete and provide the exact date the work was finalized.
Under simplified procedures, FEMA bases awards for small projects on cost estimates rather than final accounting, reducing the administrative burden typically associated with large projects. Once a small project is obligated, FEMA does not adjust the funding amount unless specific exception criteria are met.
FEMA will adjust a closed small project's funding level only under the following specific conditions:
To close small projects, recipients must submit a small project completion certification confirming that:
Subrecipients can request additional funding if the combined actual cost of all their small projects exceeds the total amount obligated for all their small projects. This is termed a Net Small Project Overrun (NSPO) appeal request.
Timing Mandate: Subrecipients must submit an NSPO request through the formal appeal process within 60 days of the latest work completion date of all its small projects. If all small projects are not yet obligated at that time, the subrecipient has 60 days from the date FEMA obligates its final small project to submit the appeal. The appeal must include actual cost documentation for all approved small projects.
If a subrecipient is not requesting an NSPO, they must submit a certification of completion for all small projects to the recipient within 90 days of the last small project completion date, or the last approved completion deadline, whichever is sooner. If work on the last small project was completed prior to obligation, the 90-day timeline begins exactly on the date of obligation. Recipients closing their own small projects face the same 90-day structural cutoff.
With the exception of capped projects, the final eligible amount for a large project is the actual documented cost incurred to complete the approved SOW.
At a minimum, large project closeout packages must include all applicable documentation to support the work and costs, structured around the following fields:
Prior to closing large projects, FEMA executes a systematic audit to verify that:
Streamlining Provision: If the work was 100 percent complete at the time the project was obligated based on actual costs, FEMA completes these compliance reviews prior to obligation. Therefore, reviews for deadlines, procurement, cost reasonableness, code upgrades, and EHP requirements do not need to be repeated during closeout.
For projects with post-obligation funding changes, FEMA prepares a project amendment to obligate additional funds or reduce funding based on actual costs. FEMA does not re-evaluate the cost-effectiveness of 406 mitigation based on final actual costs. If a subrecipient fails to complete the approved mitigation SOW, FEMA designates the project as an improved project and caps funding strictly at the repair/restoration SOW.
Recipients request that FEMA close each subrecipient once all of its respective projects have been completed and closed for the disaster. The request should include a project completion certification report listing all of the subrecipient's projects. If all projects are closed and there are no outstanding audits, FEMA closes the subrecipient and notifies the recipient in writing.
Stafford Act Section 705 imposes a strict 3-year limit on FEMA's authority to recover payments made to SLTT government recipients and subrecipients unless there is explicit evidence of fraud.
FEMA must provide a formal notice of intent to recover payments within 3 years from the date the recipient submitted the certification of project completion to FEMA.
Statutory Limit Exception: The 3-year statute of limitations on payment recovery under Section 705 applies exclusively to SLTT government entities; it does not apply to private nonprofits (PNPs).
A recipient must submit its final Federal Financial Report (SF-425) with a written request to close the overall PA award. The PA award is programmatically closed when FEMA ensures that all projects awarded for the incident met statutory and regulatory requirements.
For FEMA to formally close the overarching PA award, the following six conditions must be met:
Liquidation Cutoff: Recipients must liquidate all obligations within 120 days of the end of the prime award period of performance. FEMA extends this deadline only if the recipient submits a written time extension providing a reasonable justification for the delay.
Subrecipients must maintain all source documentation for each project for a minimum of 3 years after the date of transmission of the final expenditure report for project completion as certified by the recipient.
A recipient must keep all financial and program documentation for a minimum of 3 years after the date it submits the final SF-425 report.
Retention Notice: Several exceptions may require longer retention periods beyond the 3-year baseline, including requirements relating to real property and equipment disposition, active audits, or ongoing litigation. SLTT government laws may also mandate longer retention windows.
Compliance CTA: Establish the declaration file for Hazard Mitigation Plan early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.
Compliance CTA: Establish the declaration file for Public Assistance Administrative Plan early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.
Compliance CTA: Establish the declaration file for Payment Management System early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.
Compliance CTA: Establish the declaration file for FEMA-State/Tribal Nation Agreement early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.
Compliance CTA: Establish the declaration file for Application for Federal Assistance early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.
Compliance CTA: Establish the declaration file for Recipient Administrative Requirements early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.
Compliance CTA: Establish the declaration file for Declaration-Related Appeals early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.
Compliance CTA: Establish the declaration file for Federal Cost Share early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.
Compliance CTA: Establish the declaration file for Types of Assistance early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.
Compliance CTA: Establish the declaration file for Designated Areas early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.
Compliance CTA: Establish the declaration file for Incident Period early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.
Compliance CTA: Establish the declaration file for Incident Type early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.
Compliance CTA: Establish the declaration file for Declaration Determinations . early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.
Compliance CTA: Establish the declaration file for Tribal Nations early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.
Compliance CTA: Establish the declaration file for State and Territorial Governments early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.
Compliance CTA: Establish the declaration file for Declaration Evaluation early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.
Compliance CTA: Establish the declaration file for Declaration Request early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.
Compliance CTA: Establish the declaration file for Damage Assessments early. Validate incident dates, affected jurisdictions, eligible categories of assistance, cost-share assumptions, insurance information, and preliminary damage estimates before submitting or relying on the request. Keep the PDA, SLTT certifications, maps, photos, estimate support, and correspondence in the project record so later eligibility and appeal positions trace back to the declaration record.