Plain definition
Budgetary slack is deliberate understatement of expected revenue or overstatement of expected costs, capacity, or time so that a target is easier to achieve. It differs from a transparent contingency: a contingency names a specific risk, amount, trigger, and release decision; slack conceals a cushion inside an ordinary plan.
Illustrative example
Monetary examples use Saudi riyals (SAR). The same principles apply in other currencies.
A sales manager’s account evidence supports of next-quarter revenue. To improve the chance of earning a performance bonus, the manager submits without disclosing the difference. Operations then staffs for the lower plan and finance limits inventory purchases. When orders arrive close to , the company rushes to add capacity and may lose sales or pay premium delivery cost.
By contrast, management may approve a separate contingency for a named risk—for example, a temporary supplier surcharge—with a defined trigger and a decision maker who can release or remove it. The transparent reserve can be tested; the hidden cushion cannot.
| Evidence-supported revenue | |
|---|---|
| Submitted budget revenue | |
| Undisclosed slack |
Caution is not automatically slack. Forecasts should reflect genuine uncertainty, and a downside scenario may be prudent. The problem arises when someone knowingly distorts the central estimate for a private performance advantage or to avoid challenge.
Why it matters
Hidden slack can make managers appear to meet targets while the company underinvests in a real opportunity or misstates the resources it will need. It also makes later variance analysis misleading: a favourable result may reflect a deliberately low plan rather than better execution. Trust in the planning process falls when teams believe numbers are negotiated cushions instead of evidence-based estimates.
Practical consequence
Require significant revenue and cost estimates to show their evidence, confidence, and dependencies. Challenge unexplained gaps between account detail and the submitted total, and keep contingencies in separate labelled lines with an amount, risk, trigger, owner, and approval rule. Design incentives so managers are not rewarded solely for beating an easily reduced target. Do not remove reasonable risk provisions merely because they are cautious; test whether they are explicit and proportionate to a real exposure.