Start with the correct closeout calendar
The American Rescue Plan Act's State and Local Fiscal Recovery Funds allocated $350 billion to state, local, tribal, and territorial governments for pandemic recovery and resilient infrastructure. The obligation deadline passed December 31, 2024; unobligated funds are subject to return, so the deadline does not mean every award dollar was committed. The expenditure deadline is December 31, 2026: a little more than three months after the original publication of this article. For state CIOs and program directors who used ARPA funding to invest in technology modernization, the remaining work goes beyond accounting.
It is a test of whether they built durable capacity or rented temporary capability on the federal government's tab. Treasury identifies an earlier September 30, 2026 expenditure deadline for eligible Surface Transportation and Title I projects. Recipients should confirm the category and award conditions before treating December 31 as their own deadline.
Separate the implementation bill from the operating bill
The design of ARPA's SLFRF program created a specific challenge for technology investments. Capital acquisition and recurring operation are separate budget decisions. Roads and bridges need upkeep, and technology investments likewise carry continuing costs that a grant-funded installation does not resolve. Cloud subscriptions, software maintenance agreements, SOC analyst positions, technical support contracts, managed security services: all of these generate forward obligations that do not end when the federal grant is fully expended. A locality that used temporary revenue for continuing services needs to identify a replacement revenue source; the precise size of that exposure must come from its own budget.
Where recurring costs were grant-supported, the pain is not the loss of the investment itself — it is the operating cost structure the investment created, now looking for a general-fund home in January 2027.
Make sustainment a budget decision
A more resilient approach is to make a deliberate distinction between capital and operating expenditure when obligating technology funds. Network infrastructure upgrades, one-time system implementations with a defined go-live, data center consolidations, and application modernizations with clean transition-to-sustainment plans can create lasting capability when their operating needs are funded. An ongoing service program can be equally durable if its recurring funding and ownership are secure. An agency can draw an explicit line: federal dollars fund eligible implementation costs while its own budget identifies future operations before grant paperwork is signed. That sequencing matters because it allows the fiscal impact to be absorbed into appropriations while the federal money was still available to cushion the transition, rather than landing as a surprise line item in the FY 2027 budget cycle.
Assign an owner to every recurring cost
The harder portfolio includes programs where the operating cost profile was never cleanly resolved. Whole-of-state cybersecurity services funded through separate grants can face a similar sustainment problem, but SLCGP award periods and rules should not be inferred from the ARPA calendar. But the same dynamic appears across ARPA-funded IT: benefits eligibility modernization projects that replaced a legacy system but now run on cloud infrastructure that costs money every month, data integration platforms built to aggregate agency data that require licensed middleware, workforce training programs that created certified analysts whose positions were funded as temporary staff.
Each of these has a recurring cost that needs an owner in the next fiscal year. Finding that owner — whether a state appropriation, a cost-recovery model, an interagency agreement that distributes costs across benefiting agencies, or a formal transition to a shared service — is an operational task before closeout.
What this means for the next procurement
For vendors and integrators who worked on ARPA-funded technology programs, the close of this period can function as an operational test of the original business case. The state procurement officers who managed these contracts will remember which implementation teams accurately forecasted total cost of ownership and which did not. States that now face unexpected sustainment costs on a program that was pitched as a one-time capital investment have a legitimate grievance, and that institutional memory travels directly into the next procurement cycle.
Conversely, technology providers who helped state clients build genuinely sustainable programs — who engaged the budget and planning process early, who documented the operational model, who transferred knowledge rather than creating dependency — are well-positioned with buyers evaluating the next generation of state IT investment under tighter budget scrutiny. The end of ARPA's SLFRF does not mark the end of state technology modernization. It marks the end of the period in which that modernization was unusually well-resourced by federal money, and the beginning of a procurement environment shaped by what states learned from spending it.
Build the closeout and sustainment file
- Inventory the continuing bill. List cloud consumption, licenses, support, staffing, monitoring, backups, data retention and contract escalation clauses for each project. Separate legally obligated grant costs from future operating needs.
- Reconcile the grant file. Have the grants lead and finance team confirm eligibility, obligation evidence, category-specific deadlines and remaining allowable expenditures against Treasury guidance. A purchase order alone is not a sustainment plan.
- Choose a funded operating model. Identify the appropriation, approved cost-recovery rate, interagency agreement or shared-service arrangement that will pay each recurring bill. Record who approves a shortfall.
- Exercise the handoff. Require administrators to restore a backup, change an account and resolve a routine incident using the delivered documentation. Keep training evidence and unresolved defects with the acceptance record.
- Prepare a decision before money runs out. If recurring funding is missing, present a costed reduction, consolidation or orderly retirement option with resident-service impacts. Do not allow an unfunded renewal to become the default.
What to measure
- Funding coverage: recurring annual cost with an approved funding source, compared with total recurring annual cost.
- Operational readiness: recovery and handoff tasks completed without relying on one vendor employee.
- Unresolved exposure: renewal dates, cost increases and service commitments that have no named budget owner.
Sources and further reading
- Treasury SLFRF self-service guidance — obligation, expenditure and category-specific deadlines
Spartan X's program-execution and logistics disciplines are useful at this handoff: connecting assets, support responsibilities and recurring costs so the capability remains usable after the grant file closes.
