The FEMA Accountability Act requires the FEMA Administrator to submit a monthly report to specified Congressional committees detailing the status of all projects and activities funded from the Disaster Relief Fund (DRF). The first report is due within 60 days of enactment, and FEMA must make each monthly report publicly available on its website within 10 days of sending it to Congress.
Each report must cover the preceding month and include the DRF unobligated balance, total obligations and disbursements, a per-declaration breakdown (including affected jurisdictions and percent of obligations disbursed), lists of submitted, approved, and disbursed public assistance projects, projects with obligation decisions pending more than 180 days, and any withheld, deferred, or reprogrammed funds with reasons and estimated timelines. FEMA must also adopt a uniform reporting template consistent with Federal open data standards within 90 days of enactment.
The bill tightens fiscal transparency around disaster spending but creates implementation demands for FEMA and its grantees.
At a Glance
What It Does
The bill directs FEMA to produce and transmit monthly status reports on all DRF-funded projects and activities to designated House and Senate committees, and to post those reports publicly within 10 days. It requires a standardized, open-data reporting template to be developed within 90 days and mandates that reports cover the prior month's unobligated balance, obligations, disbursements, per-declaration breakdowns, and lists of projects by approval and disbursement status.
Who It Affects
FEMA headquarters and regional offices must collect and publish the data and create the standard template; Congressional appropriations and oversight staff will receive monthly feeds; state, territorial, and tribal grantees and subgrantees will see their project statuses surfaced publicly. Journalists, watchdogs, and the public gain ongoing visibility into DRF flows.
Why It Matters
This creates the most frequent statutory reporting cadence for Disaster Relief Fund activity and pushes FEMA to deliver machine-readable, standardized data. That changes how oversight is done (moving from episodic audits and hearings to continuous monitoring) and will influence internal FEMA processes, IT investment, and communications about spending progress.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill creates a simple, repeatable reporting duty: within 60 days of enactment FEMA must begin submitting monthly reports to specific House and Senate committees and post the same information online. Each monthly packet covers the preceding month’s numbers and project statuses rather than forward-looking forecasts.
That means the report is a retrospective ledger: unobligated balances, how much has been obligated and disbursed, and how those totals divide across individual disaster declarations.
The required content is granular. For each declaration FEMA must identify the declaration name and date, the states/territories/tribal areas affected, cumulative obligations and disbursements, and the percentage of obligated funds already paid out.
The bill also demands operational lists: projects submitted for approval, projects approved for obligation, projects for which funds have been disbursed, and those stuck waiting for obligation decisions for more than 180 days. Finally, FEMA must explain any funds that are withheld, deferred, or reprogrammed and provide an estimated timeline for disbursement.To make the monthly flow usable, FEMA must design a uniform reporting template within 90 days and align it with Federal open data standards.
That pushes the agency toward machine-readable publication and monthly updates. The statute defines key terms for clarity — it ties “Disaster Relief Fund” to the Stafford Act and defines “obligation” as a legally binding commitment — but leaves some operational definitions and enforcement mechanisms to FEMA’s implementation.
Practically, the bill forces changes in data collection, cross-office coordination, and public-facing communications at a monthly cadence rather than the ad hoc or quarterly schedules many programs use today.Because reports must be posted publicly within 10 days of being sent to Congress, FEMA will need procedures to scrub sensitive information, resolve data quality issues quickly, and coordinate with regional offices and grantees so the published lists match internal records. The combination of retrospective accounting, per-declaration granularity, and a machine-readable standard is designed to make DRF flows auditable in near real time — but it also creates a tight operational timetable for producing accurate, explainable figures each month.
The Five Things You Need to Know
The Administrator must deliver the first report no later than 60 days after enactment and continue monthly thereafter, with each report covering the prior month.
Reports must state the DRF unobligated balance and cumulative DRF obligations and disbursements, broken out by disaster declaration with affected jurisdictions identified.
FEMA must list projects by status: submitted for approval, approved for obligation, disbursed, and those pending obligation decisions for more than 180 days.
Any funds withheld, deferred, or reprogrammed must be identified with an explanation and an estimated disbursement timeline.
FEMA must publish each report on its website within 10 days of submission to Congress and adopt a uniform, open-data reporting template within 90 days of enactment.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Declares the Act’s short title, 'FEMA Accountability Act.' This is the statutory label; it carries no operational effect but signals Congressional intent toward transparency and accountability for DRF spending.
Monthly reporting requirement to Congress
Requires FEMA to submit a monthly status report on all DRF-funded projects and activities to specified House and Senate committees, beginning no later than 60 days after the law takes effect. The provision fixes a recurring statutory reporting cadence that agencies will need to operationalize across program offices and regional staff.
Detailed contents of each monthly report
Specifies the required data fields for each monthly report: unobligated balance, totals obligated and disbursed, and a per-declaration breakdown including name, date, affected jurisdictions, cumulative obligations and disbursements, and percent of obligations disbursed. It also requires enumerated lists of project statuses (submitted, approved, disbursed) and identification of projects pending obligation decisions over 180 days, plus disclosure and explanation for any withheld, deferred, or reprogrammed funds. That level of granularity will force reconciliation between financial systems and program tracking logs.
Public posting deadline
Mandates that FEMA make each monthly report publicly available on its website within 10 days after submission to Congress. This creates near-real-time public visibility and requires FEMA to resolve sensitive-data, privacy, or security concerns quickly before posting.
Standardized template and definitions
Requires FEMA to develop a uniform reporting template consistent with Federal open data standards within 90 days and supplies statutory definitions for 'Disaster Relief Fund,' 'obligation,' and the 'appropriate committees of Congress.' The template requirement moves the agency toward machine-readable publication but leaves significant implementation detail (field formats, attachments, and PII redaction rules) to agency design.
This bill is one of many.
Codify tracks hundreds of bills on Government across all five countries.
Explore Government in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Congressional appropriations and oversight committees: receive routine, standardized data to monitor DRF obligations and disbursements and to identify bottlenecks or reprogramming without waiting for ad hoc briefings or audits.
- State, territorial, and tribal emergency managers: gain transparent, centralized visibility into the status of obligations and disbursements tied to their declarations, which helps with local planning and communicating timelines to constituents.
- Journalists, watchdogs, and the public: gain near-real-time access to machine-readable DRF data, improving the ability to track spending, surface delays, and compare declarations and outcomes across disasters.
Who Bears the Cost
- FEMA (headquarters and regions): must build or adapt financial and program-tracking systems to produce monthly, reconciled reports, design and maintain the open-data template, and staff more frequent data reviews and public communications.
- State, territorial, and tribal grantees and subgrantees: may face increased documentation and follow-up requests to ensure their project statuses and disbursement records align with the publicly reported lists.
- FEMA oversight and IT budgets: the statute imposes no dedicated funding, so existing appropriations must absorb the costs of system upgrades, data standardization, and additional personnel time, potentially competing with other priorities.
Key Issues
The Core Tension
The bill balances two legitimate aims—faster, more granular transparency to aid oversight, and the operational realities of federal disaster management that require time, coordination, and sometimes confidentiality; increasing public visibility improves accountability but raises data-quality, privacy, and resource-allocation trade-offs that FEMA and Congress must resolve.
The bill prioritizes transparency but leaves important implementation choices unresolved. The requirement to publish within 10 days forces FEMA to decide how to treat sensitive or pre-decisional information, how to redact personally identifiable or security-sensitive details, and how to reconcile data from disparate legacy systems on a tight monthly cycle.
The statute defines 'obligation' but does not define 'disbursed' or set rules for when a project is considered 'submitted' versus 'approved for obligation,' leaving room for inconsistent reporting unless FEMA issues narrow operational guidance.
The open-data template requirement is practical but unfunded: creating machine-readable exports and retrofitting financial and project-tracking systems can be costly and time-consuming. There is also risk that monthly retrospective snapshots will be interpreted as immediate operational failure (for example, large obligations with low disbursement percentages during early recovery), which could politicize otherwise normal administrative lags.
Finally, listing withheld, deferred, or reprogrammed funds with estimated timelines increases accountability but could also trigger political pressure around funding choices that are contingent on policy, legal, or intergovernmental conditions.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.