Section 313 Explained: FEMA's New Public Assistance Transparency Dashboard — and What It Means for Counties

A Reporting Mandate, Not a Reform Proposal

Most of the FEMA news this spring has been about what might change. Section 313 is about what already has. It is not a recommendation, a council report, or a bill working its way toward the House floor. It is law — enacted April 30, 2026 as part of the Homeland Security and Further Additional Continuing Appropriations Act of 2026 (H.R. 7147), and announced as a county win by the National Association of Counties on May 4.

Section 313 forces FEMA to publish a publicly accessible, interactive dashboard tracking every reimbursement request under the Public Assistance Program. For county emergency managers and the finance officers who chase PA dollars after a declared disaster, this is the first federal transparency requirement that operates at the project level rather than the program level.

What Section 313 Actually Requires

The mandate is specific. FEMA must post, for each PA reimbursement request:

• Applicant identifiers, submission dates, and project descriptions
• Cost estimates and federal/non-federal cost-share breakdowns
• The status and timeline of FEMA's review — approval and grant issuance dates included
• Project-level progress updates
• Plain-language explanations for any cost estimate not approved, or any grant delayed beyond statutory timelines, together with the corrective actions taken

Individual Assistance request data is in scope as well, so the dashboard is not limited to the public-infrastructure side of recovery.

Two clocks govern publication. FEMA must post a request's data no more than 90 days after receiving it, and within 60 days of a project entering final review at the Department of Homeland Security. For an applicant who has historically had no visibility into where a project sat in the queue, a hard 90-day posting requirement is a structural change in the information balance.

The Plain-Language Explanation Is the Part With Teeth

Dashboards full of dates and dollar figures are easy to publish and easy to ignore. The provision that changes behavior is the requirement that FEMA explain — in plain language, on a public page — why a cost estimate was not approved or why a grant slipped past its statutory deadline, and what is being done about it.

That requirement runs in one direction in the statute: it constrains FEMA. But it has an immediate practical consequence for applicants. A public, plain-language denial reason is only contestable if the applicant can answer it with evidence. When the dashboard says a Category B cost estimate was reduced for inadequate documentation, the county's rebuttal is its own contemporaneous record — or it is nothing.

Accountability Cuts Both Ways

The reflexive read of Section 313 is that it puts FEMA under a microscope. It does. But the dashboard is a two-sided ledger, and counties should plan for the side that faces them.

Every figure FEMA posts about a county's project is a figure the county should be able to independently produce and reconcile. If the dashboard shows a submission date, the applicant should know the operational records behind that submission down to the Operational Period. If it shows a cost-share breakdown, the applicant should be able to tie every federal dollar to a documented resource and assignment. If it shows a reduction, the applicant should be able to walk the line items back to ICS 214 activity logs, ICS 211 check-in records, and ICS 204 work assignments captured while the incident was running.

A federal transparency dashboard does not generate any of that. It exposes whether it exists. Counties that run operations on paper and reconstruct PA packages months later will find the dashboard publishes the gap between what they claimed and what they can prove — on a page their county commission and local press can read. The same transparency that pressures FEMA also makes weak local documentation legible to everyone.

What Counties Should Do Before the Dashboard Goes Live

The statute sets posting deadlines for FEMA, not an implementation date the agency has announced, so the practical window is now and not predictable. NACo's Intergovernmental Disaster Reform Task Force has said it will monitor the rollout; counties should treat the interval before the dashboard is live as preparation time, not waiting time.

The preparation is not legal or political. It is operational. A county positioned to use Section 313 to its advantage is one whose cost-recovery records are a byproduct of how it runs incidents — resource lifecycle tracked from check-in through demobilization, costs accumulating by Operational Period as operations unfold, documentation packages already aligned to PA categories before a request is ever submitted. This is the approach platforms built on the ICS data model take: the audit-ready file exists because operations were run correctly, not because someone rebuilt it for the dashboard.

Section 313 gives counties a public instrument to hold FEMA to its timelines. Whether that instrument cuts in a county's favor depends entirely on whether its own numbers hold up next to FEMA's. The agencies that can answer the dashboard line for line are the ones that were already documenting like it existed.

See how NIMS Logic produces PA-aligned documentation as a byproduct of operations →