A district receives one-time federal relief funding and buys devices. A nonprofit receives a capital grant and replaces its network. A municipality uses an end-of-year surplus to stand up a new platform.
In each case the money was real, the purchase was reasonable, and the procurement process worked as designed. Someone compared options, checked the price, confirmed the budget and signed.
And in each case the organization acquired something that costs money every year afterwards.
Devices need management, replacement and eventually disposal. A network needs support contracts, firmware maintenance and somebody who understands it. A platform needs licenses that renew, configuration that drifts, and administration that has to happen whether or not anyone was assigned to it.
None of that was funded. It was not hidden, either. It simply was not the question being asked at the point of purchase, because the question being asked was whether the organization could afford to buy the thing.
The asymmetry
Procurement processes are built to scrutinize acquisition. Competitive bidding, price comparison, board approval, funding source verification. The controls are real and they work.
Almost none of that attention is directed at what the purchase obligates the organization to for the next five years.
This is not a criticism of the people running those processes. The rules they operate under are written around acquisition, because acquisition is where the historical risk of fraud and favoritism sits. Sustainment is a budget question, and it arrives in a different fiscal year, in a different document, usually in front of a different set of people.
So the two halves of the same decision are made separately, by different people, at different times, against different criteria. And the half that determines whether the thing survives is the half nobody owns.
What it looks like in year two
The pattern is recognizable once you have seen it a few times.
Year one, the purchase is celebrated. The equipment arrives, the platform goes live, the grant reports well.
Year two, the licenses renew and the renewal is not in the operating budget. Somebody finds the money by deferring something else.
Year three, the person who configured it has left, nobody else knows it properly, and the system is running on defaults nobody chose. Or it has quietly stopped being used, and the organization is paying for it anyway.
Year four, it is a liability. It is out of support, it cannot be updated without a project, and it is now a finding on an audit or an entry on a risk register.
The purchase was never wrong. What was wrong was treating a recurring obligation as a one-time transaction.
