Turn the Budget Cut and New Deadline into Agreed Constraints

Your budget was cut and your deadline moved earlier. Before you look at options, write down exactly what changed. A constraint is a hard limit your plan has to fit inside, such as how much money you can spend or the date work must be finished.

A constraint is only useful when it is a number or a date. Compare:

• Vague: "Budget is down by roughly a fifth, and we need to deliver sooner."
• Exact: "Free spend is capped at 640,000 from 1 May to 30 September."

The vague version invites argument. One person hears 20%, another hears 25%. One person thinks "sooner" means two weeks, another thinks two months. You can't test a scenario against "roughly". You can test it against 640,000 and 30 September.

This lesson follows one example throughout. A company was running a program with an original budget of 1,200,000 and a deadline of 31 October. Today is 1 May. Finance has just announced a cut, and the main customer wants delivery a month earlier. By the end of the lesson you will have turned that news into a short statement your leadership team can confirm.

A budget cut doesn't take money from one pot. Split what is left into three parts:

• Spent: money already paid out. It is gone.
• Committed: money you are bound to pay under signed contracts or orders, even if you haven't paid yet.
• Free: money not yet spent or committed. Only this part can be moved between projects.

Treat committed money as unavailable unless a contract can be exited or changed. When one can, note the option and what it costs. You will need that note when you build scenarios later.

In the example, 210,000 has been spent and 100,000 is committed. Of the committed amount, 60,000 is an agency contract. The contract says it can be ended with 30 days' notice for a fee of 15,000. Write that down: "Agency contract, 60,000 committed, exit possible with 30 days' notice, fee 15,000." Don't decide now whether to exit. You are only recording the option and its cost.

A common mistake is to count committed money as free because the invoice hasn't arrived yet. That makes the budget look bigger than it is.

The calculation is simple subtraction:

Free budget = original budget − amount lost − amount spent − amount committed

In the example:

• Original budget: 1,200,000
• Amount lost in the cut: 250,000 (just under 21%, which people were calling "roughly a fifth")
• New total budget: 950,000
• Already spent: 210,000
• Committed under contracts: 100,000
• Free to reallocate: 640,000

So the real limit for every decision from here on is 640,000, not 950,000. Many leaders start planning from the new total and later find that a third of it was never available.

If the free figure comes out negative, your current commitments already exceed the new budget. That is useful to know early. It means some of the exit options you noted, such as the agency contract, will have to be considered.

Use the sliders to see how the free budget changes. The original budget is fixed at 1,200,000.

A shorter deadline is not just pressure. It is a second limit, separate from money, and it needs the same precision.

Do three things:

1. Count the working weeks left. In the example, 1 May to 31 October was about 26 calendar weeks. The new deadline of 30 September leaves about 21. Take out 3 weeks when most of the team is on summer leave and 1 week of public holidays. That leaves 17 working weeks instead of 22. You lost 5 working weeks, not "a month".
2. List the deliverables that must be ready by the new date. A deliverable is a specific result someone can check. Here: the online ordering portal live, the three largest customers moved onto it, and support staff trained.
3. Note the fixed points. These are dates you can't move that shape the plan: a supplier contract renewal on 31 July and a trade show launch on 10 September.

More money can't fully replace lost time. People need to be hired and trained, and suppliers have their own schedules. Keep time as its own line in your constraints.

News about cuts often arrives in loose language. Each loose phrase hides a question you need answered. Watch for:

• Approximate amounts: "about 20% less", "a few hundred thousand"
• Fuzzy periods: "sometime in Q3", "before the summer", "end of year"
• Undefined scope: "the main deliverables", "the important stuff"
• Unclear base: "20% less" than what? The original budget, the new budget, or what is left?

For each phrase, ask the person who said it for the exact figure or date. "About 20% less" became a cut of 250,000 from 1,200,000. "Sometime in Q3" became 30 September. Q3, the third quarter of the year, runs from July to September, so "sometime in Q3" could have meant any date across three months.

An AI chat tool can help with the first pass. Paste the announcement into an AI tool your company has approved for confidential information and ask: "List every vague amount, date or scope term in this text, and the question I should ask to make each one exact." Then get the answers from people, not from the AI. The tool can find vague wording, but it doesn't know your real numbers.

Pull everything into one paragraph, the constraint statement. Include what is still uncertain and who will settle it. Example:

From 1 May to 30 September, the program has 640,000 free to reallocate, on top of 210,000 already spent and 100,000 committed. Of the committed amount, 60,000 is an agency contract that can be ended with 30 days' notice for a 15,000 fee. The deadline is 30 September, which leaves 17 working weeks after leave and holidays. By then the ordering portal must be live, our three largest customers moved onto it, and support staff trained. Fixed dates: supplier renewal 31 July, trade show launch 10 September. Open question: whether a further 100,000 could be cut in Q3. The Finance Director will confirm by 9 May.

The last two sentences matter. An open question is something you don't know yet that could change the constraints. Write it down, name the person who will answer it, and give a date. Otherwise it comes back halfway through your scenario work and resets the discussion.

Before you build any scenario, send the constraint statement to the people who set the budget and the deadline and ask them to confirm or correct it. In the example, that is the Finance Director, who announced the cut, and the Head of Sales, who agreed the new date with the customer. If the CEO or the board set either limit, include them.

Ask for a clear reply, for example: "Please confirm these figures and dates are correct, or tell me what to change, by Friday." Silence is not agreement. A nod in a meeting is easy to forget. A written "confirmed" is not.

This step keeps later debates focused. Without it, people who dislike a scenario will argue the numbers again ("I thought we had 700k") instead of discussing the options. With the figures agreed, the conversation stays on what to cut, delay or reduce.

If someone corrects a figure, update the statement and send it round again. Don't build scenarios on a version that hasn't been confirmed. In the next lesson you will use the agreed constraints to separate fixed commitments from work that can move.