One Side of A4: The Training Proposal That Actually Gets a Yes

Budget season has a smell. It is the smell of a slide deck being built at 11pm for a meeting that will last twelve minutes. Someone has asked for training. Someone else has asked what it costs. And somewhere in between, a good idea is turning into forty pages nobody will read.

Here is the alternative: one side of A4.

Not because brevity is fashionable, but because a single page forces you to say the only things a budget holder actually needs. What is broken. What you know about it. What people will do differently. What happens if you do nothing. And how you will know it worked. That is the whole argument. Everything else is decoration.

This matters more than usual right now. Teams are shaping plans for 2027, which means requests are being stacked up, compared, and quietly cut. A clear page survives that process better than a beautiful deck. It also survives the year, because the same page becomes the brief you hand the trainer and the note you check yourself against in March.

Start with the problem, not the course

The first line should not be the name of a course. It should be the thing that is going wrong.

'Quotes take four days and too many come back wrong' tells a finance director more than 'negotiation skills workshop' ever will. The course is your proposed solution. The problem is why anyone should care. Lead with the problem.

Be specific and local. Which team? Which process? How often? If it is the client onboarding desk, say so. If it is the warehouse in Leeds, say so. Vagueness reads as padding, and padding reads as risk.

Use evidence you already have

You do not need a survey. You need three things you can point at.

Look at what already exists: complaint logs, rework hours, overtime, missed deadlines, onboarding time, staff turnover, the same three questions that come up in every team meeting. Pick the two or three that best describe the problem. Note where each came from and when. 'Six complaints in September, all about the same handover step' is evidence. 'Staff seem demoralised' is not, unless you can show it.

If your numbers are thin, say that too. 'We don't measure this yet, but in the last two months three experienced staff have flagged the same gap' is honest and still persuasive. Budget holders are used to uncertainty. They are less used to people admitting it.

Describe the behaviour, not the syllabus

The question behind every training request is: what will be different on a normal Tuesday afternoon?

So answer it. 'Team leaders will run a five-minute check before quotes leave the building.' 'New starters will handle their first client call in week two instead of week six.' 'The shift handover will use one template instead of three.' That is what you are buying. The course is just how you get there.

This section also protects you. If you cannot describe the behaviour, you are not ready to ask for the money. Go back and talk to the team.

Put a number on doing nothing

Not a dramatic number. A believable one.

If the rework takes three hours a week across four people, say so. If a delayed quote loses one job a month, estimate it conservatively. If managers are spending Friday afternoons fixing errors, count the hours. Then write one line: 'At current rates, this pays for itself by the end of Q1.' Check the maths before you write it, because someone will.

The point is not to exaggerate. It is to show that the status quo has a cost, and that you have thought about it like an adult.

Name the one number you will check

This is the part most requests leave out, and it is the part that gets a yes.

Pick a single measure. Give its current level. Give a date for reviewing it. 'Quote error rate, currently around 12%, reviewed at the end of March.' Or 'time to first client call for new starters, currently 31 days, reviewed in April.'

One number, not five. Then commit to reporting back, even if the news is mixed. That commitment does two things: it makes the request feel like an investment rather than a spend, and it gives you a reason to talk to the budget holder again when the course is done.

Keep the page boring

Five headings. A few lines under each. The problem at the top, the cost and the ask at the bottom. No mission statement, no stock photo of a handshake, no paragraph about the provider's 25 years of experience.

If you need to attach a course outline, attach it as a second page and label it clearly. The first page is the argument. The second page is the detail. Do not let them swap places.

What to do when the answer is no

Ask what would make it a yes. Sometimes the answer is a smaller version: half the team, a shorter course, a pilot with one department. Sometimes it is a later date. Sometimes it is more evidence.

Take the no as information, not a verdict. A budget holder who says 'not this year, but show me the error rate in April' has just given you a plan.

The page is not just for them

Once it is approved, that single page stays useful. It is the brief you send the trainer so they know what problem they are solving. It is the note you check in the first fortnight, when everyone is back at their desks and the momentum is slipping. It is the thing you reread before the review meeting, to see whether you asked for the right thing in the first place.

Budget season rewards people who make decisions easy. One page, clearly argued, is easier than forty. Write the page first. The deck can wait, and probably should.