Training budgets that survive the finance review

A training request usually reaches finance as a course name, a headcount and a number. Framed that way it is indistinguishable from a discretionary expense, and discretionary expenses are what a review exists to remove.

The requests that survive are framed as the cost of a problem that already exists. Rework because a procedure is misapplied. Findings that recur every audit cycle. Overtime absorbed because one person is the only one who can do something. Attrition in a role that takes nine months to replace. Put the number on that first, then the cost of fixing it, and the conversation stops being about whether training is nice to have.

Timing matters more than people expect. A request that lands after the budget is set is competing against nothing and loses by default. One that lands during planning, attached to a named risk, is a line item.

Group your requests. Five separate submissions for one delegate each look like five people wanting days out. One submission for a team, with a stated capability outcome, looks like a plan. It is also usually cheaper, because past roughly six delegates in-house beats public course pricing.

Be specific about what is excluded. Fees quoted excluding VAT, travel and accommodation are normal in this industry, and a request that has not accounted for them comes back. So does one where the delegate count is optimistic about who can actually be released that week.

And put the follow up in the request. What will be different, who will check, and when. A request that includes its own measure is much harder to decline than one that ends at the invoice.