RETURN TO PREVIOUS PAGE
Scoping, Costing, and Final Reviews for Federal Disaster Assistance

Every funded activity must be directly linked to eligible disaster damage—this 'Absolute Grounding' requirement is essential for FEMA projects. The Scope of Work (SOW) must align precisely with your Damage Description. Key requirements include: - SOW specifications: length, width, depth, capacity, materials - Classification and reconciliation rules for Large vs. Small projects - 50% federal share within 60 days for expedited funding in Categories A-B - Eight-point criteria for FEMA-approved cost estimates - Strategic Funds Management for permanent work over $1 million Large projects require 'actual cost' documentation at closeout. Ensure comprehensive scoping now.

Scoping, Costing, and Final Reviews for Federal Disaster Assistance

Chapter 9 serves as the strategic bridge between the identification of disaster-related impacts and the formal obligation of federal funding. This document is the authoritative regulatory guide for establishing a Scope of Work (SOW) and determining cost eligibility. All project applications must meet the "Absolute Grounding" requirement: every funded activity must be anchored directly to eligible disaster-related damage recorded in the Damage Description and Dimensions (DDD).

Failure to align the SOW with the DDD results in the immediate denial of funding for those elements. Establish the evidentiary record now to ensure all project applications survive federal audit and reconciliation.

I. Scope of Work Development

The SOW must provide a complete description of the method of repair, corresponding directly to the disaster-related cause of damage. All repair descriptions must be defined in quantifiable terms—specifically length, width, depth, and capacity—and utilize descriptive terminology such as brick, wood, asphalt, or timber.

To develop a compliant SOW, provide the percentage of work completed, identify the performing party (force account, contract, or mutual aid), and include all technical studies, reports, and identified consensus-based codes and standards.The compliance path for Tribal Nations requires a specialized approach to recognize cultural and historical integrity.

For traditional structures—constructed of adobe, mud, earth, clay, rock, or wood—standard national infrastructure benchmarks are often inapplicable. FEMA mandates the acceptance of a Tribal Nation’s certified damage assessment, SOW, and cost estimates for these traditional residences and ceremonial buildings. Compliance officers must integrate tribal-adopted codes and cost-effective mitigation measures into the restoration scope to preserve these unique facilities while building back stronger for future disasters.

II. Cost Development

Financial eligibility is governed by the minimum project threshold, adjusted annually based on the Consumer Price Index. A project application totaling less than this minimum is ineligible for FEMA funding. Be advised that FEMA strictly prohibits combining work among several sites into a single project application for the sole purpose of reaching the minimum threshold.

Use this classification strategically:

Large projects (at or above the threshold) are reconciled to actual incurred costs at closeout, whereas Small projects (below the threshold) are generally funded based on estimates and are not adjusted unless a net small project overrun is successfully appealed.

For immediate cash flow needs, applicants may request expedited funding for Category A (Debris Removal) or Category B (Emergency Protective Measures) that meet the Large project threshold. This mechanism provides 50% of the federal share based on estimated costs, provided the request is submitted within 60 days of the recovery scoping meeting. To trigger this funding, the application must include itemized estimates for labor (budgeted, unbudgeted, and mutual aid), equipment usage and rates, supplies (purchased or from stock), and contract documentation. FEMA aims to obligate these funds within 90 days of receipt, though payment remains limited to actual, immediate cash requirements.The verification process for completed work depends on project size and documentation rigor.

For Large projects that are 100% complete, funding is strictly based on actual costs supported by verifiable documentation. FEMA will issue a Request for Information (RFI) if documentation is insufficient; failure to provide the requested data by the deadline will result in a Determination Memorandum (DM) denying assistance for those costs.

For Small projects, FEMA may accept a certification of completion in lieu of full documentation, provided the SOW is sufficiently defined and Environmental and Historic Preservation (EHP) conditions are met.Estimating emergency work involves unique challenges as these activities often lack established unit pricing or a fixed scope. If an applicant fails to provide sufficient data to support an estimate, FEMA will default to average historical pricing. This may lead to lower funding obligations than actual expenditures. To avoid this, provide a clear description of the immediate threat and detailed work activities to justify all estimated costs.For permanent work not yet completed,

FEMA determines funding based on the estimated cost to restore the facility to its pre-disaster design, function, and eligible codes. These estimates may include reasonable anticipated "soft costs" such as engineering and design services, which FEMA will fund upon request.To be accepted by FEMA, an applicant-submitted cost estimate must adhere to the following eight-point criteria:

  1. Prepared by a licensed professional engineer (PE), architect, or certified professional cost estimator.
  2. Includes a certification that the estimated cost corresponds directly to the agreed-upon repair.
  3. Based on unit costs for each SOW component (no lump sum amounts).
  4. Contains detail sufficient for FEMA to validate all components against the SOW.
  5. Reflects the current phase of design or construction.
  6. Includes actual costs for any work already completed at the time of the estimate.
  7. Demonstrates overall cost reasonableness.
  8. Includes foreseeable contingencies such as security and staging.When FEMA develops estimates for Large projects that are less than 90% complete, it utilizes the Cost Estimating Format (CEF). The use of contingency factors is strictly regulated; only FEMA Headquarters may approve factors exceeding standard ranges. For "capped" projects—such as improved or alternate projects—FEMA restricts the CEF contingency factor solely to the "Applicant Reserve for Change Orders" and prohibits additional factors or risk premiums.All estimates must be reduced by the amount of actual or anticipated insurance proceeds. This is a non-negotiable regulatory requirement to prevent the duplication of benefits. FEMA will calculate these reductions based on the applicant's insurance policy if actual proceeds are unknown at the time of the estimate.

III. Compliance Reviews

Before obligation, every project must pass through a mandatory series of quality assurance and regulatory gates. These include insurance requirement reviews, PA hazard mitigation eligibility, and EHP compliance. FEMA utilizes "Appendix L: Validation of Applicant-Provided Cost Estimates" as the primary checklist for cost estimate reviews. Failure to satisfy EHP conditions or meet insurance requirements will halt the funding process and may lead to the total de-obligation of funds if the work has already commenced.

IV. Obligation

Obligation transitions the responsibility for funds from FEMA to the Recipient. The project application then becomes the official record of the approved SOW. Recipients (States, Tribal Nations, or Territories) are mandated to account for these federal awards under their own laws and procedures. FEMA's authority to provide Small project funding as a lump sum does not require Recipients to distribute it in the same manner.For permanent work projects exceeding $1 million where funds are not required for more than 180 days,

FEMA implements Strategic Funds Management (SOP 9570.24). This aligns the obligation of federal capital with the applicant’s actual execution schedule. The Recipient is legally responsible for notifying the applicant of fund availability and ensuring the timely pass-through of obligated funds to subrecipients.

Key Findings / Arguments

Compliance success is predicated on the quantifiable link between disaster damage and the repair scope. The "Absolute Grounding" principle dictates that if a repair element cannot be traced to the DDD, it is ineligible. Applicants bear the ultimate legal burden of documenting all costs; FEMA’s role is to validate the evidentiary record using standardized tools like Appendix L. While Small projects prioritize administrative finality, Large projects remain subject to rigorous "actual cost" reconciliation at closeout.

Critical Data Points or Evidence

  • Timelines:  60 days from recovery scoping meeting for expedited funding requests; 90-day FEMA obligation target for expedited projects.
  • Thresholds:  $1 million triggers Strategic Funds Management (SOP 9570.24).
  • Citations:  44 C.F.R. § 206.202 (expedited), 206.203 (thresholds), 206.205 (payment/reconciliation).
  • SOW Metrics:  Must include length, width, depth, and capacity for all damaged elements.
  • SFM Trigger:  180-day execution window for projects over $1 million.

Notable Risks, Gaps, or Assumptions

  • Documentation Risk:  Large projects face total funding denial if actual cost documentation is absent during final reconciliation.
  • Pricing Gaps:  If applicants do not provide sufficient data, FEMA’s default use of "historical pricing" may underfund current market costs.
  • Tribal Material Gap:  Standard PA processes do not account for adobe or clay; the "certified damage assessment" is the only mechanism to prevent improper denials for traditional structures.
  • Capped Project Limitation:  CEF contingencies are severely restricted for improved/alternate projects, covering only change order reserves.

MACRO-SYNTHESIS FOR LEADERSHIP REVIEW

Top 5–10 Actionable Insights

Leadership must treat compliance as a front-end activity to protect the bottom line. Ensure the DDD is precise—using quantifiable metrics like capacity—to prevent SOW reductions during review. For Tribal Nations, immediately utilize the "certified damage assessment" allowance to bypass inappropriate infrastructure benchmarks. Manage all Large projects with the understanding that every dollar is subject to "actual cost" reconciliation; estimates are only placeholders. Leverage expedited funding within the 60-day window for Categories A and B to maintain liquidity, and utilize Strategic Funds Management for projects over $1 million to align federal payouts with actual construction milestones.

Major Risks or Red Flags

The primary risk to funding retention is the Duplication of Benefits; failure to subtract insurance proceeds will trigger immediate de-obligation. Leadership is cautioned that FEMA will not combine multiple sites to meet the minimum project threshold; each project must stand on its own merits. For Large projects, the "actual cost" requirement is a hard barrier—FEMA will deny all assistance for costs not supported by verifiable documentation at closeout.

Opportunities or Strategic Implications

Strategic Funds Management allows for the efficient deployment of capital for large-scale infrastructure without overwhelming accounting systems. Additionally, the expedited project mechanism provides a vital cash-flow tool during the first 90 days of recovery, provided itemized estimates and proof of immediate threat are submitted on time.

What Leadership Should Care About Most

Federal funding is a highly regulated grant, not a guaranteed reimbursement. It is only finalized when the SOW matches the disaster-related DDD and survives the validation of Appendix L. The Recipient holds the ultimate legal burden for fund accounting. If documentation fails to meet the eight-point criteria for estimates or the "actual cost" reconciliation for Large projects, the financial burden of the disaster will shift from the federal government back to the local level.

Chapter 9: Scoping, Costing, and Final Reviews

Chapter #
Citation Details
CTA Compliance Requirement
Citation URL
Chapter 9
44 CFR § 206.203(c)
Project Thresholds
Establishes the calculation protocol separating small projects from large projects using fiscal year indexing. Dictates that small project funding remains locked to baseline estimates, while large projects are dynamically adjusted at closeout to mirror actual documented costs.
Official Reference Document

PAPPG Chapter Asset

Open Document

Adobe Navigation Tip:
When this PDF opens in a NEW TAB in your browser, click the Document Outline or Bookmarks icon in the top toolbar. This opens a clickable index of all document headings so you can jump directly to specific legal compliance benchmarks instantly.

You can use the Adobe download or print options at the top as desired. There are also Adobe view options in top Adobe bar. Use the previous tab to navigate by to GovStar.

BACK TO TOP