| Audience: | CIO đźž„ CTO đźž„ VP IT Operations |
| Primary sectors: | Government/Public Sector đźž„ Higher Education |
| Decision horizon: | Next funding approval or contract renewal |
Executive Summary
A replacement system can cost less to operate without releasing the money expected to fund the next initiative. Migration costs, continuing obligations and reinvestment can absorb the difference.
Approve savings-dependent spending only against usable net savings or an explicitly authorized financing arrangement. Stage work that is funded and useful independently; defer binding commitments with an uncovered shortfall. Name the responsible budget holder. Necessary modernization can proceed on its service, security or resilience case.
Our Analysis
Modernization approval establishes the investment case. Funding the next initiative requires a separate calculation: what remains available, to whom, and by which payment date.
The Narrative vs The Reality
The attractive proposition is straightforward: replace an expensive system, reduce its running costs, and use the difference to fund another priority. That sequence works only when the claimed savings survive transition costs, continuing obligations and prior funding commitments.
- Operating reductions can disappear in the total project economics. In its July 2026 Technology Modernization Fund review, GAO reported that HUD officials saw annual cost reductions after migrating to a UNISYS mainframe environment. Higher migration and transition costs prevented the anticipated overall savings. Labor’s modernization project was on track for its savings target, with further savings expected through 2029.1
- Useful modernization can leave expenditure broadly unchanged. GAO’s August 2026 telecommunications review reported that Transportation’s spending remained approximately comparable to its legacy contract costs because efficiencies were reinvested in bandwidth and upgraded capabilities.2
- Cost avoidance and better unit economics are not automatically funding. Cost avoidance releases funding when an approved budget provision is reduced and reassigned; avoiding an unbudgeted expense creates no spending authority. Improved unit economics can deliver more service for the same expenditure without funding another commitment.
- Application cost and removable expenditure are different measures. Technology Business Management (TBM) includes labour, infrastructure, licensing and shared-service allocations in application TCO.3 Trace those costs to the underlying expenditure. Moving an allocation to another service releases no funding. Released staff time increases capacity; it becomes available funding only where expenditure or an approved spending provision can actually be reduced.
- Technical changes do not automatically change payment obligations. FinOps Foundation guidance identifies continuing commitments and double-counted benefits across usage and rate optimization, including cloud, SaaS and licensing.4 Verify cancellation, renewal and minimum-payment terms against the forecast.
The Signal in the Noise
The next project needs funding that the first project has not already consumed or committed elsewhere.
What Changes the Decision
Approve a savings-dependent commitment only when Finance confirms that funding will be available by its payment dates, is authorized for the proposed use, and remains sufficient after transition costs, continuing obligations and prior claims. A savings forecast alone does not establish that funding.
A contingency reserve underwrites a shortfall. Bridge funding advances money against identified later savings, with financing costs and repayment dates included. Permanent alternative funding replaces the savings-based funding case. If no funded, independently useful stage or authorized funding for the gap exists, defer the binding commitment.
Why This Matters Now
Before the next binding order or renewal, establish who has first claim on expected savings. For US federal TMF projects, repayment terms are set in written agreements and reimbursement is not contingent on achieving savings; account for repayments before assigning funds to the next initiative.1 If the proposed use crosses appropriations, establish transfer authority; within an appropriation, check applicable purpose and reprogramming requirements.5 Across sectors, a one-time balance requires an identified funding source for later recurring payments. Higher-education CIOs must also establish who controls retained funds: the University of Arizona’s policy limits approved carryforward to one-time strategic initiatives.6
What to Watch for Next
In government, compare repayment dates with the next initiative’s payment dates. In higher education, check whether central or unit-level budget rules permit the proposed reuse.
Recommended Actions
Do This
- Produce a dated funding schedule before purchase approval. Finance verifies the baseline and service scope, net amount, prior claims and spending authority; Procurement confirms contractual release dates; the service owner supplies transition assumptions. Begin with expenditure expected to change. Where an existing TBM model is available, use it to trace shared costs; otherwise trace the relevant expenditure through contracts, invoices and staffing records. Verify which obligations disappear. A spreadsheet records that evidence.
- Apply the funding rule within existing approval. The CIO and authorized budget holder approve funded commitments, stage funded work that delivers independently, or defer uncovered binding commitments. Compare delay costs with reserve or bridge-financing costs. Record the financing source and budget holder accepting the exposure; permanent replacement funding needs its own approval.
- Reopen approval when its funding conditions fail. The budget holder and Finance must revise approval before the next binding order if a renewal, repayment or transition change creates an uncovered payment. Finance reconciles actual savings against the agreed baseline and service scope, separating scope or volume changes, reinvestment and capacity gains. Benefit tracking alone does not fund a gap.
Illustrative Funding Schedule
Assumptions:
- A $50,000 payment is due on 1 October, with no opening funding or advance budget reallocation.
- Forecast gross operating-payment reductions are $40,000 monthly, but $20,000 remains payable under continuing contracts.
- A one-time transition payment of $20,000 is due on 31 October; a one-time modernization repayment of $10,000 is due on 31 December.
- Operating flows occur at month-end. The $20,000 monthly net reduction continues through February, and Finance permits its reuse after each month-end throughout the period.
- The table assumes an authorized bridge funds the October payment. It shows principal only; financing costs require additional funding.
Date Net funding released in period Cumulative net funding Bridge principal outstanding 1 October $0 $0 $50,000 31 October $0 $0 $50,000 30 November $20,000 $20,000 $30,000 31 December $10,000 $30,000 $20,000 31 January $20,000 $50,000 $0 The base case clears bridge principal on 31 January. Approval through that date also requires a separately funded provision for financing costs; otherwise the repayment schedule must extend. If repayment is required by 31 December, $20,000 remains to be funded from another authorized source. Compare the quoted financing cost and accepted shortfall exposure with the cost of delay. Without authorized financing, defer the full commitment or schedule funded, independently useful stages after funds become available.
Illustrative Sensitivity
A $10,000 transition overrun in October raises the peak bridge principal to $60,000. The balance is then $30,000 at December-end and $10,000 at January-end; principal repayment extends to February-end. A $50,000 facility ending in January would therefore be insufficient in both amount and duration. The budget holder must authorize funding for that exposure before committing.
Avoid This
- Spending the same benefit twice. Finance should reconcile overlapping usage, rate and licensing claims before accepting them as funding; a smaller allocation to one application does not establish an enterprise reduction.
- Turning the funding gate into a modernization veto. Approve necessary continuity, security or service improvements on their own rationale and measures. Apply the savings test to the commitment that relies on those savings.
Bottom Line
Modernization can improve service without releasing money for another initiative. Approve against usable net savings or a named, authorized financing source. Stage funded work that delivers independently; defer uncovered binding commitments.
Evidence and Sources
- US Government Accountability Office. 2026. Technology Modernization Fund: Small Savings Achieved So Far, but Substantial Future Savings Expected. GAO-26-107737. July 23. Agency-reported HUD and Labor outcomes; TMF repayment requirements. The report distinguishes planned future savings from realized savings.
- US Government Accountability Office. 2026. Telecommunications: GSA Should Assess Agencies’ Effectiveness at Preventing Service Disruptions. GAO-26-107919. August 31.
- TBM Council. n.d. TBM Modeling—KPIs & Metrics. Application/solution TCO section. Accessed October 13, 2026.
- FinOps Foundation. n.d. Rate Optimization. Accessed October 13, 2026.
- US Government Accountability Office. 2016. Principles of Federal Appropriations Law: Fourth Edition, Chapter 2—The Legal Framework. GAO-16-464SP. March. Transfer and reprogramming discussion, pages 2-38–2-46.
- University of Arizona. 2012. FPM 4.1 University Budget, Fund Balance, and Reserve Policy. Effective July 20, 2012; revised April 29, 2026. Institution-specific spending and carryforward provisions.