pa readiness
Damages & Work
Costs & Estimates
Insurance & DOB
Compliance Controls
FEMA Reform
Resource Hub
Build defensible scopes of work and cost estimates using quantities, unit costs, assumptions, contingencies, CEF support, and update protocols for FEMA Public Assistance projects.
FEMA Public Assistance cost estimating begins with a defensible connection between disaster-caused damage, the approved scope of work, measured quantities, cost sources, and the funding record. This page organizes the key estimating issues applicants must manage when developing scopes, supporting costs, using CEF, applying RSMeans or other industry-standard cost data, and defending estimates through FEMA validation, insurance review, closeout, and audit.
Connects the agreed damage description and dimensions to the proposed or completed scope of work. The estimate should not begin with a budget target; it should begin with eligible disaster-related damage, the method of repair, measured dimensions, and a clear explanation of how the work restores the facility or addresses emergency impacts.
Covers the repair method, completed or proposed work, work locations, dimensions, percent complete, labor source, contract status, technical studies, engineering reports, hazard mitigation measures, and codes or standards that affect the scope. The scope should be specific enough for FEMA to validate what work is eligible and what costs directly correspond to that work.
Covers estimates prepared by the applicant, engineer, architect, cost estimator, public works staff, or consultant. The estimate should be prepared using recognized industry standards, itemized unit costs, measurable quantities, documented assumptions, and sufficient detail for FEMA to validate that each component corresponds to the agreed scope of work.
Covers the base construction estimate for eligible work. Part A is the foundation of the FEMA Cost Estimating Format because later CEF factors are applied to the base estimate. A strong Part A should trace each dollar from damage, to eligible scope, to measured quantity, to unit cost source, to location adjustment, to spreadsheet line item, to project cost. Lump-sum estimates should be avoided because they weaken validation and audit defense.
Covers general requirements, general conditions, contingencies, contractor overhead and profit, escalation, plan review and permit fees, applicant reserve, design, inspection, and project management costs. These factors should support the eligible scope and must not duplicate costs already included in Part A, contractor bids, FEMA cost codes, or actual completed work.
Covers use of RSMeans square-foot models for rapid building damage magnitude estimates, declaration support, budget planning, asset registry valuation, and early FEMA project formulation. For buildings, RSMeans can help translate facility type, square footage, story height, perimeter, location, and building system damage into a faster, more defensible preliminary estimate before detailed design quantities are available.
Organizes building estimates by functional systems instead of isolated trade guesses. UNIFORMAT II supports conceptual and early-stage estimates by grouping costs into systems such as substructure, shell, interiors, services, equipment, special construction, demolition, and building site work. This is especially useful when the facility is damaged and exact material selections are not yet known.
Covers measurements, sketches, drawings, photographs, field notes, GIS records, dimensions, quantities, units of measure, local cost history, contractor quotes, FEMA cost codes, RSMeans, BNi, Marshall & Swift, and other recognized estimating sources. The estimate should be reproducible by another competent reviewer using the project file.
Covers the basis for determining whether costs are reasonable, including local market conditions, historical pricing, competitively procured costs, city cost indexes, labor rates, material availability, equipment rates, escalation, location factors, and disaster-specific pricing pressures. Applicants should document why the selected pricing source fits the project location, timing, and scope.
Separates actual documented costs from estimated costs for work still to be completed. This distinction is critical because completed work should be supported by invoices, force account records, contracts, proof of payment, and other actual cost records, while uncompleted work must be estimated using a clear method, current assumptions, and documented update protocols.
Separates base repair costs from insurance recoveries, duplication-of-benefits reductions, code and standard upgrades, Section 406 hazard mitigation, improved project features, alternate project costs, and ineligible betterments. This cost segregation helps prevent insurance conflicts, audit findings, and disputes over whether a cost restores the pre-disaster facility or funds a separate improvement.
Covers the estimate documentation needed to withstand FEMA validation, Requests for Information, recipient review, closeout reconciliation, appeals, and audit. The file should explain the damage basis, scope basis, quantity basis, cost basis, assumptions, exclusions, estimate date, pricing source, location adjustment, contingency logic, and changes made as design or construction information improves.
```