The PATHS Act amends the Homeland Security Act of 2002 to extend the Department of Homeland Security’s research and development pilot that uses other transaction authority (OTA) through September 30, 2028, and it adds a new oversight step specifically for OTA actions involving artificial intelligence. When DHS uses or extends an OTA that involves AI, the Secretary must notify four key congressional committees and offer a briefing explaining the decision within 72 hours.
Separately, the bill changes statutory procurement language in the FY2023 NDAA by lowering a monetary cutoff in section 7113(d)(1) from $4,000,000 to $1,000,000. That numeric change alters which awards fall under the referenced “covered contract” rule and will change how many and which transactions are subject to the related statutory regime.
For program managers, vendors, and committee staff, the bill tightens near‑term oversight on AI OTAs while keeping OTA flexibility in place for three more years.
At a Glance
What It Does
Extends DHS’s OTA R&D pilot to September 30, 2028, and requires the Secretary to notify the Appropriations and Homeland Security committees of both chambers and offer a briefing within 72 hours whenever an OTA involving artificial intelligence is used or extended. It also amends FY2023 NDAA language to replace a $4,000,000 threshold with $1,000,000 in a covered‑award provision.
Who It Affects
DHS acquisition and program offices that use OTAs, AI technology vendors and defense/dual‑use startups that pursue OTA awards, and congressional staff on the House and Senate Appropriations and Homeland Security committees who will receive rapid notices and briefings.
Why It Matters
The bill preserves OTA flexibility for DHS while grafting near‑immediate congressional oversight onto AI‑related transactions and expanding the universe of transactions captured by a statutory monetary threshold change—shifting implementation and compliance burdens across agencies, vendors, and committee offices.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
Other transaction authority (OTA) lets agencies contract outside the Federal Acquisition Regulation to move faster and use nontraditional partners. The PATHS Act keeps that pathway available to DHS for R&D work by pushing the pilot’s expiration out to September 30, 2028.
It does not rewrite the underlying OTA mechanics; it simply prolongs the pilot window during which DHS may execute OTAs for prototyping and development work.
What is new is a targeted oversight hook for AI: whenever DHS uses or extends an OTA that involves artificial intelligence technology, the Secretary must notify four committees—the Senate Appropriations Committee, the Senate Committee on Homeland Security and Governmental Affairs, the House Appropriations Committee, and the House Committee on Homeland Security—and offer a briefing explaining why the OTA was used or extended. That notice must occur within 72 hours of the use or extension, creating a near‑real‑time reporting obligation that aims to give Congress prompt visibility into AI buys without eliminating the OTA option.The bill also reaches back to an FY2023 statutory provision (section 7113(d)(1) of the James M.
Inhofe NDAA) and reduces a dollar threshold from $4,000,000 to $1,000,000. The text replaces the numeric figure, which changes which awards are treated as “covered” under that statutory paragraph; practitioners should map that change to the substantive rules attached to the covered‑award label in the NDAA text to understand practical effects.
Combined, the extension plus the notification requirement and the lowered monetary cutoff subtly reshape the oversight landscape: DHS retains access to non‑FAR contracting but must move faster on internal clearances and prepare to brief Congress quickly on AI transactions, and a broader set of lower‑value awards will fall under the referenced statutory umbrella.The PATHS Act leaves several operational details undefined in the statute—most notably any working definition of “artificial intelligence” for triggering the 72‑hour notice, and the form and scope of the required briefing. Those omissions will be the locus of guidance and policy decisions at DHS and will determine how disruptive the new reporting obligations prove in practice.
The Five Things You Need to Know
The bill extends the DHS R&D OTA pilot (section 831 of the Homeland Security Act of 2002) through September 30, 2028.
It adds a new requirement that the Secretary notify the Senate and House Appropriations and Homeland Security committees and offer a briefing within 72 hours after using or extending an OTA that involves artificial intelligence.
The 72‑hour requirement applies both to initial uses of OTA authority and to extensions of existing OTA transactions.
The act amends section 7113(d)(1) of the FY2023 NDAA by replacing the $4,000,000 covered‑award threshold with $1,000,000.
The statute does not define “artificial intelligence” or specify the briefing’s format, leaving operational specifics to DHS guidance and internal process changes.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title — PATHS Act
Establishes the Act’s short title: Producing Advanced Technologies for Homeland Security Act (PATHS Act). This is a formal naming provision with no programmatic effect, but it’s how the statute will be cited in subsequent guidance and legal references.
Extend the R&D OTA pilot and add AI notification requirement
Modifies subsection (a) of section 831 by extending the pilot’s sunset from September 30, 2024 to September 30, 2028. The amendment also inserts a new paragraph establishing a specific oversight duty: if the Secretary uses or extends other transaction authority in a matter involving artificial intelligence, DHS must notify four congressional committees and offer a briefing explaining the rationale within 72 hours. Practically, program offices will need a rapid internal clearance and notification workflow for AI‑related OTAs and must be prepared to explain why an OTA—rather than a FAR‑based contract—was appropriate.
Adjusts internal statutory cross‑references for the extended pilot
Edits in subsection (a) also update a cross‑reference from subsection (d) to subsection (c) where the prior text referred to procedural rules tied to the pilot. That change aligns the statutory text with the new subsection numbering produced by the amendment; acquisition counsel should confirm that any regulatory or internal DHS policy citations mirror the updated structure to avoid compliance gaps.
Lower covered‑award dollar threshold in FY2023 NDAA text
Alters subparagraph (A) of section 7113(d)(1) of the James M. Inhofe NDAA for FY2023 by striking “$4,000,000” and inserting “$1,000,000.” The amendment is a pure numeric substitution in existing statutory language; it changes which procurements meet the statutory criteria tied to that provision. Practitioners need to cross‑reference the NDAA provision to determine what compliance steps flow from being a “covered” award under that paragraph, because the PATHS Act does not itself attach new procedural requirements to the lower threshold.
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
- DHS program offices running R&D and prototyping efforts — They keep OTA flexibility through 2028, preserving a rapid procurement path for experiments and engagements with nontraditional vendors.
- Nontraditional tech vendors and startups (especially AI firms) — OTAs remain an accessible contracting vehicle; lowering the covered‑award threshold can make smaller awards and pilot contracts more viable under the OTA framework.
- Program managers seeking rapid AI capability acquisition — The statutory extension avoids the administrative disruption of a pilot lapse, keeping channels open for iterative prototyping and public‑private collaboration.
Who Bears the Cost
- DHS acquisition and legal staff — They must build a 72‑hour notification and briefing process for AI OTAs, increasing near‑term workload and requiring faster pre‑award coordination with program and legal teams.
- Congressional committee staff (Appropriations and Homeland Security) — Committees receive near‑immediate notices and will be offered briefings that consume staff time and may create downstream oversight activity.
- Prime contractors and incumbent vendors — Increased oversight and a lower threshold may expand competition from smaller firms and subject more transactions to scrutiny, potentially increasing proposal and compliance costs.
Key Issues
The Core Tension
The central dilemma is speed versus scrutiny: the bill preserves OTA flexibility to accelerate technology acquisition while imposing rapid congressional visibility on AI transactions and lowering a monetary threshold that alters which awards are treated specially—measures that increase accountability but risk slowing down the very acquisitions OTA was meant to expedite.
The PATHS Act attaches near‑real‑time oversight to a procurement vehicle designed for speed. That creates a classic operational tension: program offices must reconcile the need to act fast (a core OTA justification) with a statutory requirement to notify and brief Congress within 72 hours.
The statute provides no template for what the briefing must contain, who exactly in DHS prepares it, or whether classified details can be excluded or redacted; those decisions will shape whether the notice obligation is a quick administrative tick box or a material hurdle to rapid acquisition.
Another ambiguity is the trigger: the statute requires notices for OTAs “involving artificial intelligence,” but it offers no statutory definition of AI or scope guidance. Without a clear threshold, DHS will have to decide how broadly to interpret the phrase—potentially sweeping in many peripheral algorithmic tools—or narrow it and risk disagreements with committee staff.
The numerical change in the NDAA text—dropping a $4M figure to $1M—also has second‑order effects. Because the PATHS Act edits only the number, not the policy tied to the “covered” label, the practical outcome depends on how the NDAA’s covered‑award rules operate; the change could expand the set of awards that trigger separate requirements, or it could simply reclassify award amounts without immediate procedural consequences, depending on the cross‑referenced statutory mechanics.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.