Start with the correct closeout calendar
Treasury's State and Local Fiscal Recovery Funds program describes the American Rescue Plan Act program's $350 billion allocation 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 immediate sustainment question is which approved funding source will cover them after that support ends. The transition must follow the recipient's actual fiscal calendar and funding authority.
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 arriving as an unplanned request in a later 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, closeout is an opportunity to test the original business case against actual operating costs. Procurement teams should compare the forecast with the delivered service, identify material differences and document their causes. If a program was presented as a one-time investment while essential recurring costs were omitted, the next solicitation should require a clearer account of total ownership cost.
That review should also preserve what worked: early budget coordination, an explicit operating model, usable documentation and knowledge transfer. These are useful factors for buyers to evaluate in future proposals, with evidence from the delivered work rather than broad vendor assurances. The end of temporary grant support does not end modernization; it makes the recurring funding decision harder to postpone. This is our procurement assessment, not a forecast that every state faces the same budget conditions or will make the same buying decision.
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.
Build a service-level funding decision
A useful sustainment review starts with one service, not a total portfolio figure. Consider a hypothetical grant-funded case-management platform whose implementation contract is closing while hosting, support and monitoring continue. The grants lead can confirm whether particular expenditures are allowable. The service owner still needs a separate answer about who pays for operation after those funds are exhausted.
Prepare three views for the budget decision:
- The committed bill: contracted minimums, renewal dates, termination notice periods and other obligations the agency has already accepted. Have procurement confirm the actual terms; an estimated annual subscription is not the same as an unavoidable liability.
- The expected operating bill: staffing, consumption, support and maintenance under stated workload assumptions. Identify what changes with transaction volume, data retention or coverage hours, and show the uncertainty instead of hiding it inside one estimate.
- The transition bill: migration, data export, training, parallel operation or retirement costs if the state changes providers or reduces scope. A cheaper renewal is not automatically the cheapest service once those costs are included.
These are recommended management views, not Treasury accounting categories. Keep the grant record and the forward operating forecast distinct so that a sound sustainment decision does not become an unsupported claim of grant eligibility.
Decide which capability the state can sustain
If the full operating model is not funded, present alternatives while there is still time to implement them. Continued operation at the current service level may be justified where the capability is essential and recurring funding is available. A shared service may reduce duplicated work, but it needs an agreed allocation of costs, service responsibilities and an owner for disputed priorities. A narrower service may be viable if its reduced coverage is explicit and the program can accept the consequences.
Retirement is also a legitimate option when the capability no longer meets the mission or its cost cannot be justified. That decision requires a plan for records, required retention, user transition and contractual exit. It should not happen accidentally because nobody approved an invoice.
Ask each option to answer the same practical questions: what continues, what stops, who performs the work, what the transition costs, and what service risk the agency accepts. Finance should identify the funding authority; procurement should validate commitments and exit terms; the program executive should own the service consequences. Technology staff should demonstrate that the proposed handoff or reduction is operationally feasible.
The final closeout discussion should produce a decision record with a named owner, a funding basis and the next renewal or review date. A grant ledger can balance while the operating model remains unresolved. The point of this review is to expose that difference before it interrupts a public service.
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.
