How verified-release would fix the IIJA drawdown problem

The Infrastructure Investment and Jobs Act authorized roughly $1.2 trillion in federal infrastructure spending. Years into implementation, the drawdown rate — the speed at which authorized dollars actually flow to projects — has consistently lagged the authorization schedule. Part of the bottleneck is capacity. A meaningful and underdiscussed part is verification: program offices are slow to release funds because they cannot quickly verify whether the milestone being invoiced for has actually been achieved. The structural fix isn't more staff or a new statute. It's a registry-anchored release model that moves verification from forensic audit to release-time gate.

The drawdown gap, in numbers

IIJA's headline number is $1.2 trillion in total authorization across five years, with roughly $550 billion in new funding above baseline reauthorization levels. The expected year-over-year outlay schedule assumed a steady-state run-rate of roughly $100-120 billion per year of incremental outlays across the bill's lifetime.

Actual outlays have run materially below schedule. The Congressional Budget Office's tracking reports and the Department of Transportation's program-level dashboards consistently show drawdown lagging authorization by 12-24 months across most major programs. Bridge-investment programs, electric-grid resilience programs, and rural broadband deployments are particularly affected.

The political consequence is significant. IIJA was sold on a delivery timeline. The drawdown gap converts the headline authorization into a slower-than-promised reality, which becomes a political liability for the administration that enacted it and for the agencies executing it.

What's actually slow

The bottleneck has three real causes, and the proportions matter for thinking about fixes:

• Recipient capacity — state DOTs and local sub-grantees take time to design, environmentally clear, procure, and bid out projects. This is real and significant but is structural to how infrastructure procurement works. New money in 2022 doesn't translate to ground-breaking before 2024-2025 in most cases.
• NEPA + environmental review — major projects need NEPA clearance before federal dollars can flow. Permitting reform has bipartisan attention but the review cycle is still measured in years for any project requiring an Environmental Impact Statement.
• Verification bottleneck at release-to-recipient — this is the underdiscussed piece. Once a project is awarded and the recipient is invoicing, the verification work required for the federal program office to approve the release of funds against that invoice is slower than the invoicing cycle. Recipients submit invoices; program offices take weeks to verify; the funds sit obligated-but-not-outlayed.

The first two are policy questions. The third is an infrastructure question that the federal government can solve without new legislation.

Why verification is slow

A typical IIJA-funded project disbursement cycle looks like this:

1. Recipient performs work — pours foundation, installs structural steel, completes lane miles, energizes substation.
2. Recipient invoices the federal program (often through a state pass-through entity) for the milestone associated with the work performed.
3. The pass-through entity reviews the invoice against the project agreement, the work plan, and supporting documentation (photographs, inspection reports, certifications).
4. If approved at the pass-through level, the request flows to the federal program office for final approval.
5. The federal program office reviews again against statutory and regulatory requirements.
6. Funds are released to the recipient via Treasury disbursement.

Each of those review cycles is bottlenecked by the same structural problem: the reviewer is making a judgment call about whether the underlying work actually meets the milestone definition, based on documentation that the recipient themselves prepared. When the documentation is incomplete, ambiguous, or inconsistent with the project agreement, the review cycles back to the recipient for clarification — adding weeks per iteration.

When the documentation looks fine and the release goes through, the verification quality is downstream-tested at audit, sometimes years later. If the audit finds the milestone wasn't actually met as documented, the recipient faces clawback. The Inspector General reports stack up.

The fix: move verification to the moment of release

The structural fix to the IIJA drawdown bottleneck is the same structural fix that resolves the HUD CDBG-DR audit- reconstruction problem — described in detail in our earlier piece, The verified-release disbursement problem. The core idea: instead of releasing funds when the recipient submits an invoice and the program officer signs off, release is gated on a registry-verified state transition for the underlying asset.

For an IIJA-funded infrastructure project, the asset is the physical infrastructure itself: bridges, substations, broadband cabinets, transit vehicles, rail track, electric- grid hardware. Each piece of infrastructure registered into a verified-asset registry carries a passport: provenance, installation milestones, inspection records, lifecycle state.

When the recipient invoices for a milestone, the federal program office's release decision becomes:

• Does the registry show the asset's verified state matches the requested milestone? If yes, release.
• Does the remaining program budget cover the requested amount? If yes, release with rail fee.
• If either condition fails, the release is denied automatically with a structured reason — and the recipient can address the gap before re-requesting.

The release cycle shortens from weeks to hours. The verification quality moves from forensic-reconstruction-at- audit to verified-at-release. The drawdown rate accelerates because the bottleneck shifts from human judgment to deterministic registry query.

What this would look like for specific IIJA programs

Three concrete examples of how verified-release would apply to specific IIJA-funded programs:

Bridge Investment Program (BIP)

BIP funds bridge replacement and rehabilitation through FHWA. A typical project registers bridge components (girders, deck panels, expansion joints) into the verified registry with their provenance and structural inspection records. As the project progresses through milestones (foundation poured, superstructure set, deck completed, opened to traffic), the asset's lifecycle state advances and the verified-release gate opens for the corresponding disbursement.

Grid Resilience and Innovation Partnerships (GRIP)

GRIP funds electric-grid resilience hardware. Substation transformers, switchgear, and distribution-level hardware get registered with manufacturer provenance, inspection records, and installation milestones. Disbursements release on verified state transitions: hardware received, hardware installed, hardware energized.

Broadband Equity, Access, and Deployment (BEAD)

BEAD funds last-mile broadband deployment. The "asset" here is more fragmented (cabinets, fiber spans, customer premises equipment) but the verification logic is the same: registry records track provenance and installation state; release-time verification gates the disbursement.

What the federal program office gets

For the federal program officer — say, an FHWA bridge program lead or a DOE GRIP program manager — the day-to-day workflow changes very little. They still set program rules. They still handle exceptions and policy questions. What changes is the verification gate underneath their decisions: instead of reviewing recipient-prepared documentation and exercising judgment about whether the milestone was met, they're approving releases against a verified-state record they didn't have to reconstruct.

When the Inspector General eventually audits the program, the audit response is dramatically faster: every release is tied to a specific asset record, a specific verified state transition, and a specific timestamp. The reconstruction problem disappears because the verification was captured at the moment of release.

The rail-fee economics

The economics for the federal program are favorable. A basis- point rail fee on each verified release (typically 20-30 bps) is small per transaction and visible on every audit row. For a $100B IIJA program area, 25 bps on verified releases would generate $250M in infrastructure costs against multi-billion- dollar audit-defense and recipient-relationship cost savings. The fee structure is auditable, the costs are line-item visible to OMB and to congressional appropriators, and the structural benefit — faster drawdown, fewer IG findings, better recipient relationships — flows back to the program.

Why this hasn't been built inside the federal system

The structural reason is coordination. A verified-release model requires every infrastructure recipient — state DOTs, local sub-grantees, contractor primes — to register their deliverables into a shared registry. That's not a federal procurement; it's an industry coordination problem. Federal agencies are structurally bad at industry coordination across 50 state DOTs and tens of thousands of local sub-grantees.

The fix comes from a neutral infrastructure operator — the same operator structure that resolves the verification problems in modular construction, EV battery passports, and critical-minerals provenance. The federal agency doesn't have to build the registry; the agency adopts the registry that the asset producers are already registering into for their own commercial reasons (financing access, insurance pricing, downstream procurement preferences).

That's the architecture Keystone's Disbursement Rail provides — and the live demo walks through a working release attempt against a sample $5M DOE program in real-time, showing the HTTP 200 release vs HTTP 422 denial paths explicitly.

The political alignment

Verified-release disbursement is one of the rare infrastructure-policy interventions that has clean political alignment from every angle:

• Administration — faster IIJA drawdown = faster delivery of infrastructure outcomes = better political return on the bill
• Inspectors General — audit reconstruction problem evaporates; IG offices get faster, more defensible audits
• Congressional appropriators — clearer cost visibility (rail fees as line items), cleaner audit trail, defensible spending records
• State DOTs and local sub-grantees — faster reimbursement, fewer review cycles, less cash-flow friction
• Contractors — payment lag compresses, work-in-place financing terms improve
• Future administrations of either party — better cost-effectiveness, better audit defense, no statutory dependency

The IIJA drawdown problem is partly a capacity problem, partly a NEPA problem, and partly a verification problem. The verification piece is the one that doesn't require legislation to fix — and it's the one that has been ignored.