Funding for a contested project is buried inside a budget nobody wants to question, such as infrastructure, compliance, or contingency, so approvers never vote on it as a separate item.
An example
Six months into the job, the new controller at a hospital system was asked to explain a variance in the cybersecurity remediation budget. The program had sailed through the board because it answered an audit finding. Inside it sat a $1.8 million line for a patient-engagement app that the chief digital officer had twice failed to get approved on its own. Elsewhere, the professional-services account carried a run of consulting invoices with no named owner, each just under the $250,000 review threshold, all reclassified by one executive who could sign alone. When the controller asked about the app line in the finance committee, the reply was that questioning it meant slowing remediation the regulator was watching. The controller asked for a line-item walkthrough of both accounts anyway, with internal audit sampling the invoices, and the app came back to the committee as its own proposal.
Why it works
Burying the item makes funding it look easier: approvers are voting for cybersecurity or compliance, and nobody has to own a vote for the contested project. It makes the alternative, pulling the item apart, look worse, because the host program's legitimacy can be invoked to make the objection seem pedantic, and costlier, because the questioner has to master a technical domain and slow a budget cycle colleagues depend on. Conditions favor it when the host category is respected or complex, approvers are short of time, the sponsor builds the budget, and no audit discipline reaches individual lines.
The thinking behind it
Richard H. Thaler Thaler's Mental Accounting and Consumer Choice (1985) shows that people sort money into separate mental accounts and judge spending against the account it falls in, so the same sum can feel trivial in one account and unacceptable in another. A contested $1.8 million project inside a cybersecurity program is judged as part of an account approvers have already accepted. Pulling it out moves it back into an account where it must stand alone.
Herbert A. Simon In Administrative Behavior (1947), Simon analyzed organizations as systems of decisions shaped by premises the organization supplies, such as goals, information, and categories. Whoever builds the budget chooses the categories approvers decide within. When the item sits under compliance, approvers reason from the premise that compliance spending is required, and the item inherits that premise without ever being argued for.
George A. Akerlof Akerlof's The Market for "Lemons": Quality Uncertainty and the Market Mechanism (1970) shows how a gap in information lets the informed side set the terms. The unit that builds a technical budget knows what each line funds, and approvers cannot check without expensive expertise. Line-item review and audit sampling work because they close the gap at its source.
Warning signs
A sub-line inside an infrastructure, compliance, or contingency budget has no separate business case. Questions about it are answered by invoking the host program's importance. Catch-all accounts such as professional services show activity with no named owner, amounts cluster just below review thresholds, and one senior signer can reclassify spending without a countersignature. A contested project that failed on its own earlier now seems to be moving without anyone having approved it.
How to defend yourself
Ask for the business case for the sub-line by name. If none exists, the question has answered itself. Expect to be told you are slowing critical work. Answer that separating the item takes a week, and leaving it hidden puts the whole program's standing at risk. Raise it before the budget locks; afterward the item has its own constituency.
- Request a line-item walkthrough of the largest technical budgets, and ask internal audit to sample them.
- Look across categories together, contingency, professional services, and capitalized costs, since each alone looks normal.
- Frame the request as protecting the host program, whose credibility suffers if a hidden item is found later.
How a leader shuts it down
Make line-level review of large technical budgets routine, and mandate it every cycle, since it is expensive and will lapse otherwise. Narrow catch-all accounts, lower materiality thresholds, give one controller visibility across them, and require a countersignature on reclassifications. A project that fails on its own should not reappear inside someone else's budget.