The DHS Grants Accountability Act edits multiple statutory grant programs to impose uniform deadlines, minimum applicant windows, and longer periods of performance. It amends the Homeland Security Act of 2002, the Implementing Recommendations of the 9/11 Commission Act of 2007, and 46 U.S.C. 70107 to require timely publication of notices of funding opportunity (NOFOs), at least 30 days for applications, and a minimum 54‑month period for use of awarded funds.
The bill also tightens allocation language and increases pre‑NOFO reporting to congressional committees.
For compliance teams and grant managers, the bill converts several long‑standing administrative practices into statutory obligations: publishing NOFOs within set deadlines (or within 60 days if appropriations don’t set one), preserving a 30‑day application window, and allowing projects more time to spend awards. It also requires administrators to notify specific congressional committees annually before issuing NOFOs and replaces discretionary allocation language with mandatory allocation on enumerated bases—changes that increase oversight and reduce agency discretion in prioritizing grant funds.
At a Glance
What It Does
The bill requires agencies that administer DHS preparedness, transit, railroad, bus, and port security grants to publish NOFOs by specified deadlines (or within 60 days of appropriations enactment), give applicants at least 30 days to apply, and make awarded funds available for at least 54 months. It also modifies allocation language to mandate allocations be made on stated bases and requires annual notifications to two congressional committees before issuing NOFOs.
Who It Affects
State and local homeland security offices, transit agencies, railroad operators, intercity bus operators, port authorities, and the federal offices that manage these grants (DHS components and other departments named in the underlying statutes). Grant program offices and legal/compliance teams that draft NOFOs will carry new procedural duties.
Why It Matters
By statute-izing timelines and committee notice, the bill reduces administrative variability between grant cycles and strengthens congressional oversight. That changes how agencies schedule competitions, how applicants budget and plan projects, and how watchdogs review allocations—and raises operational questions about staffing, audit timing, and how rigidly agencies must adhere to the new criteria.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill stitches together a set of procedural rules and transparency requirements across several federal grant programs that support preparedness and transportation security. First, it turns previously discretionary timing and prioritization language into mandatory duties: agencies must publish NOFOs within deadlines tied to appropriations acts (or within 60 days if the appropriations act is silent), and they must give eligible applicants at least 30 days from publication to submit applications.
Those rules apply to grants administered under specific Homeland Security Act sections and to multiple transportation security programs (public transit, railroad, intercity bus, and port security).
Second, the act sets a uniform minimum period of performance for awarded funds: once a grantee receives an award under the listed programs, the recipient will have at least 54 months to obligate or use those funds. That lengthens the typical federal grant lifecycle and affects project phasing, drawdown schedules, and audit timing.
The bill also requires that allocations to States or areas be made “on the basis of” the statutory criteria instead of merely being “considered,” which constrains how administrators document and justify distribution decisions.Third, the bill tightens pre‑award oversight by adding a requirement that the Administration provide an annual notification to the House Committee on Homeland Security and the Senate Committee on Homeland Security and Governmental Affairs before issuing the relevant NOFO. Related statutory tweaks include moving or renumbering subsections and deleting obsolete provisions so the new deadlines and definitions operate cleanly.
The package is procedural rather than substantive funding reform: it leaves eligibility rules, eligible activities, and formula/statutory funding shares intact while changing the timing, publication, and transparency framework around competitions.Operationally, agencies will need new internal calendars, publication checklists, and reporting templates to meet the 60‑/30‑/54‑month sequence. Applicants and subrecipients will need to adjust proposal timelines and cash‑flow planning to fit the new minimum application window and extended performance period.
Finally, because the bill names which statutory sections are “specified” for the new 2021 rules, the changes do not automatically sweep into every DHS grant program—only those sections listed in the bill and the enumerated transportation security statutes are covered.
The Five Things You Need to Know
The bill requires a minimum 54‑month period of performance for awarded funds under the enumerated DHS preparedness and transit/port grant programs.
Agencies must publish NOFOs in accordance with any deadlines in the applicable appropriations act, or if no deadline exists, within 60 days of enactment of that appropriations act.
Every NOFO covered by the bill must allow eligible recipients at least 30 days from publication to submit applications.
Section 2007(a) language is changed from requiring administrators to “consider” criteria to directing them to “allocate such funds…on the basis of” the statutory criteria, legally tightening allocation obligations.
Before issuing a relevant NOFO, the Administrator must submit an annual notification to the House Committee on Homeland Security and the Senate Committee on Homeland Security and Governmental Affairs.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Make discretion into a minimum frequency requirement
This change replaces a permissive verb with a mandatory timing floor: where the underlying statute previously used a verb that allowed agencies to act irregularly, the bill requires action at least annually. Practically, agencies that previously issued NOFOs or made allocations sporadically will have to establish annual cycles or document why a statutory action occurred each year. That creates a predictable cadence for applicants and for congressional oversight but gives agencies less flexibility to consolidate multiple years into a single competition.
Tighter allocation language and pre‑NOFO committee notice
By changing the statutory phrasing from “consider” to “allocate…on the basis of,” the bill raises the evidentiary bar for allocation decisions: agencies must tie distributions to the enumerated factors and will face a harder legal or oversight burden to justify deviations. The insertion of an annual notification requirement requires the Administrator to brief congressional homeland security committees before the NOFO hits the street—this moves a degree of program design and prioritization into a formal pre‑award reporting step to Congress.
NOFO publication deadlines, minimum application window, and 54‑month performance period
The bill adds a three‑part administrative regimen: publish notices by appropriations deadlines or within 60 days if none exist; allow at least 30 days for applications; and set a 54‑month minimum period to use award funds. It also defines which grant statutes are covered (see 'specified section'), so the new timing rules apply to particular preparedness grants (sections 2003, 2004, and 2009). Agencies will need to update internal procedures, IT publication schedules, and award documentation to reflect these minimums.
Risk assessment inputs must precede NOFOs by 30 days
The amendment requires that the information underpinning risk assessments (used to prioritize or justify allocation) be provided at least 30 days before any NOFO or program guidance. That creates a fixed sequencing: key risk inputs must be finalized early enough to inform a NOFO, which reduces last‑minute changes but requires earlier interagency coordination and possibly faster data collection cycles.
Same publication/application/performance rules extended to transport and port grants
The bill inserts the 60‑/30‑/54‑month rules into multiple transportation security grant statutes: public transit (sec. 1406), railroad security (sec. 1513), over‑the‑road bus (sec. 1532), and port security (46 U.S.C. 70107). Note that the operative word in those statutes is “Secretary,” which means the head of the department defined by each underlying statute (for example, Transportation for some sections and Homeland Security for port security); implementing agencies will need to coordinate across departmental lines to harmonize procedures and reporting.
Housekeeping to align numbering and cross‑references
The bill removes an outdated subsection and renumbers adjacent subsections so internal cross‑references and the new ‘specified section’ definition work correctly. While procedural, these edits are necessary to prevent inconsistencies where the new timing and transparency rules interact with existing program text.
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
- State and local homeland security offices — gain predictable NOFO schedules and a 54‑month performance period that smooths planning, project phasing, and cash‑flow management for large capital or multi‑phase projects.
- Transit agencies, rail operators, intercity bus operators, and port authorities — benefit from clearer competition timelines and longer award windows that reduce pressure to obligate funds quickly and support multi‑year procurements.
- Grant applicants with limited proposal capacity (smaller jurisdictions and non‑profits) — benefit from the statutory minimum 30‑day application window, which provides a guaranteed baseline preparation period.
- Congressional oversight offices and appropriations staff — benefit from formalized pre‑NOFO notifications and clearer statutory bases for allocations, improving oversight and legislative engagement.
Who Bears the Cost
- DHS program offices and other administering agencies — must add administrative capacity to meet publication deadlines, produce annual committee notifications, and manage longer performance tracking and closeouts.
- Grant managers and auditors at state/local governments — will need to revise grant calendars, monitor multi‑year performance, and track funds across a longer duration, potentially increasing compliance workload.
- Applicants expecting faster competitions — may face compressed internal review cycles if agencies cluster multiple NOFOs into a short period despite the statutory minimums; meeting the new documentation standards for allocation may increase proposal complexity.
- Federal program legal teams — will face more frequent inquiries and possible challenges because allocation decisions must now be demonstrably tied to statutory criteria rather than merely considered.
Key Issues
The Core Tension
The central dilemma is predictability versus flexibility: the bill forces predictable, transparent grant cycles and stronger congressional visibility—helpful for planning and oversight—but in doing so constrains agency discretion and may shorten the practical time available for complex proposal preparation or extend federal monitoring burdens across a longer performance period. Reasonable administrators may prefer flexibility to tailor competitions to evolving threats, while applicants and Congress prefer standardized rules that limit opaque decisionmaking.
The bill standardizes timelines and transparency but leaves several practical and legal questions open. First, the interaction with appropriations language is ambiguous: the statute defers to any deadline in the appropriations act and otherwise imposes a 60‑day publication rule, but appropriations riders already vary across programs and years.
Agencies will need to reconcile differing appropriations directives with the new fallback rule, and disputes could arise about whether an appropriations deadline is a statutory mandate or a funding condition.
Second, the 30‑day minimum application window and the requirement to allocate “on the basis of” statutory criteria trade flexibility for predictability. Complex grant competitions (multi‑tiered proposals, large capital projects requiring environmental review, or cost‑share calculations) often need more than 30 days for robust, compliant submissions.
Conversely, a guaranteed minimum could be gamed by agencies that issue abbreviated NOFOs and rely on pre‑application outreach to shift substantive work outside the formal window. Finally, the extension to a 54‑month performance period reduces pressure to obligate quickly but also extends federal oversight horizons, potentially complicating audits and requiring sustained program monitoring resources.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.