pa readiness
Damages & Work
Costs & Estimates
Insurance & DOB
Compliance Controls
FEMA Reform
Resource Hub
Organize FEMA Public Assistance records, invoices, force account documentation, photos, proof of payment, RFIs, audit files, and closeout support needed to defend project funding.
FEMA Public Assistance closeout is the final reconciliation point for eligible work, eligible costs, compliance conditions, insurance, duplication of benefits, procurement, Environmental and Historic Preservation requirements, and audit-ready records. A strong closeout file should not be built at the end of the project. It should be assembled throughout the grant lifecycle so the applicant, recipient, and FEMA can verify that the approved scope of work was completed, costs were properly supported, funds were reconciled, and all award conditions were satisfied.
Covers the closeout mindset applicants should use from the beginning of the disaster. The grant file should preserve the award record, approved scope of work, cost basis, supporting source documentation, procurement records, insurance records, EHP conditions, correspondence, amendments, payment records, and final reconciliation documents needed to support project closeout, subrecipient closeout, award closeout, monitoring, appeals, and audit.
Covers the certification that the approved scope of work was completed, the work was performed in compliance with the FEMA-State, Territorial, or Tribal agreement, eligible costs were incurred for approved work, and required payments were made according to federal grant requirements. This certification is the practical trigger for project-level reconciliation and closeout review.
Covers simplified closeout for small projects, which are generally funded based on estimates rather than final accounting. The applicant and recipient should confirm that all approved small project scopes of work were completed, payments were issued, and no conditions exist that require adjustment, such as scope changes, hidden damage, duplication of benefits, insurance changes, errors, omissions, noncompliance, fraud, waste, or abuse.
Covers requests for additional funding when the combined actual cost of all small projects exceeds the total amount obligated for all small projects. Applicants should preserve actual cost documentation for all approved small projects, track completion dates, and coordinate appeal timing because net small project overrun requests are handled through the appeal process.
Covers reconciliation of actual documented costs for large projects. With limited exceptions for capped projects, the final eligible amount for a large project is based on the actual documented cost incurred to complete the approved scope of work. The file should connect the final inspection, completed scope, quantities, invoices, timesheets, work orders, contracts, change orders, payment records, and compliance documentation to the eligible FEMA-funded work.
Covers the closeout summary records used to organize final expenditures by cost category, including force account labor, force account equipment, materials, rented equipment, contract work, mutual aid, and other eligible project costs. These summaries help reviewers trace total claimed costs back to detailed source documentation and payment records.
Covers employee time records, payroll registers, fringe benefit calculations, labor policies, equipment logs, FEMA equipment rates, material invoices, proof of payment, stock records, usage dates, and calculations showing the quantity of materials actually used for eligible disaster work. The file should show who performed the work, when the work occurred, what equipment was used, and how each cost was calculated.
Covers the contract documentation needed for closeout, including procurement policies, solicitations, advertisements, requests for quotes, invitations for bids, requests for proposals, bid responses, bidder lists, bid tabulations, independent cost estimates, cost or price analyses, contractor selection records, contracts, amendments, change orders, invoices, proof of payment, and required federal contract provisions.
Covers final financial reporting and payment reconciliation, including the final Federal Financial Report, SF-425, final reimbursement requests, expenditure summaries, federal share, non-federal match, local cost share, de-obligations, advances, reimbursements, proof of payment, and confirmation that funds were passed through and liquidated according to the award terms.
Covers the final performance progress report, closeout narrative, project status, accomplishments, final work completed, performance outcomes, milestone completion, and explanation of the impact of the completed work over the period of performance. This helps connect the financial record to the actual recovery outcome.
Covers insurance policies, statements of loss, adjuster reports, settlement offers, insurance reimbursements, final claim determinations, duplication-of-benefits review, other federal funding, donations, responsible-party recoveries, and any funding that may duplicate FEMA assistance. The closeout file should show how all actual or anticipated recoveries were accounted for before final FEMA funding is closed.
Covers Environmental and Historic Preservation records, permits, waivers, regulatory correspondence, agency approvals, floodplain and wetland conditions, historic preservation documentation, debris disposal records, environmental compliance conditions, and final evidence showing that completed work satisfied all EHP and permitting requirements attached to the FEMA award.
Covers documentation for codes and standards incorporated into the scope of work, approved hazard mitigation measures, change orders, improved project features, alternate or capped project decisions, hidden damage, scope amendments, underruns, overruns, and any FEMA-approved changes that affect final funding, eligibility, or compliance.
Covers real property, equipment, supplies, and tangible personal property records that may require additional reporting or disposition instructions. Closeout may require information for forms such as SF-428 or SF-429, as well as documentation showing custody, use, disposition, or continuing federal interest in property acquired or improved with federal funds.
Covers the separate responsibilities of the subrecipient, recipient, and FEMA. The subrecipient certifies project completion and submits supporting documentation to the recipient. The recipient reviews, reconciles, certifies, and submits closeout packages to FEMA. FEMA verifies eligibility, compliance, funding adjustments, and final closeout status before issuing written closeout confirmation.
Covers unresolved matters that may delay closeout, including appeals, arbitration, audits, monitoring findings, corrective action plans, compliance notices, questioned costs, procurement findings, insurance issues, EHP conditions, and other unresolved funding or compliance matters. These issues should be tracked early so they do not prevent project, subrecipient, or award closeout.
Covers continuous validation of documentation before final closeout. Applicants should organize records throughout the project lifecycle so FEMA, the recipient, or reviewers can sample documentation, validate actual costs, confirm completed work, and resolve issues before the final closeout package is submitted.
Covers final closeout of the Public Assistance award after all projects and subrecipients are closed, all eligible funding is obligated, all appeals are resolved, the recipient has submitted its final SF-425 and written closeout request, funds have been passed through appropriately, and FEMA and the recipient have completed all administrative actions.
Covers retention of financial, programmatic, procurement, property, performance, and source documentation after closeout. FEMA PA records generally must be retained for at least three years from the applicable final expenditure report or final SF-425 date, but longer retention may apply for real property, equipment, audits, litigation, state law, unresolved claims, or other exceptions. The audit file should be secure, indexed, and cross-referenced to the final closeout package.
```