How to get your employer to pay for a conference

A conference funding request gets approved or refused on four things: what problem it solves for the business, what the whole trip costs, how many working days you'll be away, and what you bring back afterwards. Leave one of those out and a manager who wants to approve the spend still can't, because they don't have enough to defend the decision if their own manager asks about it.

The business case comes before the ticket

Most requests open with the event itself: the name, the programme, the reason it looks worth attending. A manager reads that as a personal preference, and personal preferences are the first thing cut from a tight budget. The stronger opening names the gap at work the conference closes, whether that's a skill the team is short on, a decision that needs outside input, or a shift in the field the sessions will explain before it turns into a problem. If you're still deciding whether a specific event earns that case, Is This Conference Worth Going To? sets out how to check before you ask.

The cost is the whole cost.

The ticket price is the number everyone quotes, and usually the smallest part of what attending actually costs the business. Travel, accommodation, meals and the working days lost, both attending and recovering, belong in the same total, because that's the figure your manager is weighing against the budget line. A request that puts the full number up front reads as more credible than one that lets the real cost surface later in an expenses claim.

Time away is a cost even when someone else pays

Two or three days out of the office carries a cost regardless of who covers the ticket: meetings move, work waits, colleagues pick up the slack. Naming the dates and who covers what while you're away answers a question your manager is asking before they've finished reading the rest of the request.

What comes back closes the loop

Approval is easier to give when there's something to point to afterwards, whether that's a short write-up circulated to the team, a session run internally on what was learned, or a list of contacts worth following up. It doesn't need to be elaborate, but naming it before you go, rather than promising something vague, is what turns the spend from a personal trip into something the team can see the value of. How to Actually Get Value From a Conference covers what's realistic to commit to and how to follow through on it.

The sections below cover how to write the request itself, how to build the full cost figure, what to offer in return, and a worked example of a short proposal that puts all four elements in one message. If you want the finished structure, Worked Examples and Templates has a version you can adapt.

The number your manager sees first is the ticket price, and that is often the number that gets a yes. The number they remember afterwards is the total, once travel, the hotel, meals and the days you were not at your desk have all landed on the same invoice or expense claim. Building the full total before you ask makes the conversation easier.

The ticket price is the smallest number

Check whether the ticket includes meals, the evening event, or workshop access, since a cheaper ticket that excludes lunch and a hotel-adjacent add-on can end up costing more once those are bought separately. If early-bird pricing is available, note the deadline in your request: asking after it has passed and paying the higher rate is an easy way to lose your manager's confidence in the rest of the figures.

Travel and accommodation

Rail fares move sharply with how far ahead you book, so get a quote at the time you submit the request. If the conference runs over two days, work out whether an overnight stay is cheaper than two days of early starts and late trains, both in cash terms and in how fit you will be for the second day. Book the hotel through the conference's own rate if one exists: organisers often negotiate a block rate with a nearby hotel, and it is usually lower than booking independently.

Meals and the costs that do not show up on a ticket

Some conferences include lunch and refreshments in the ticket price; others leave you buying food in a venue where a sandwich costs more than it would on the high street. Check the programme or the event's own FAQ for what is and is not covered, and put a modest daily allowance into your total for the gaps. Evening meals on a trip of more than one day belong in the figure too, particularly if the alternative is expensing them separately later and looking like the request undercounted.

The working days lost

A day at a conference is a day you are not doing your usual job, and if travel adds a half day either side, that is the real time cost. This matters because your manager is approving your absence, and someone else covering, or your work simply waiting, is a cost even though no invoice arrives for it. Naming this plainly is usually what gets a request approved quickly.

Adding it up without surprises

Put ticket, travel, accommodation, meals and any workshop or add-on fees into one figure before you send the request, and say what assumptions sit behind it, such as advance rail booking or a shared hotel rate. A request that states the full cost up front, with the reasoning for each line, is easier to approve than one that arrives looking small and grows after the fact. For the structure of the request itself, see How to Get Your Employer to Pay for a Conference, and for a template with the numbers laid out, check the Worked Examples and Templates page.

A funding request that only states a cost gives a manager nothing to point to afterwards. Naming a specific deliverable, something the business can see, read or attend, turns a one-off spend into something the team gets some return on, and makes the same request easier to approve a second time.

A short write-up

A one or two page note naming three or four things that changed how you'd approach a live problem, each with a specific action attached, is more useful than a list of every talk you sat through. A summary with no recommendation reads as proof of attendance, and it won't do much work in next year's funding request.

An internal session

Offering to run a short session for the team, 20 to 30 minutes, within a few weeks of getting back, turns the write-up into something spoken and open to questions. It also gives your manager a second thing to point to: that you passed it on to people who didn't go.

A list of contacts made

Naming who you spoke to and why it's useful, a supplier worth a second look, a peer at a comparable organisation, someone whose approach solves a problem your team already has, turns networking from a vague line in the proposal into something the business can actually follow up.

Matching the offer to the size of the ask

A half-day event costing a few hundred pounds probably only needs a short note. A multi-day conference with travel, accommodation and two working days lost justifies a session and a named list of follow-ups, because the spend is bigger and the case for repeating it needs to be stronger. Promising more than you'll actually deliver is worse than offering nothing, so pick something you know you'll do.

Worked Examples and Templates includes a sample structure for this kind of note. How to Actually Get Value From a Conference covers what to do while you're there so the write-up has something worth writing.

A funding proposal that gets approved quickly is short and specific, and it answers the two questions a manager actually has: what does this cost, and what comes back to the team. The example built into this guide runs to about half a page, structured so it can be read in the time it takes to open an email and approved without a follow-up question.

The structure that makes it easy to say yes

The proposal states the ask in the first line. A short paragraph follows naming the conference, the dates and the reason it's relevant to the role. Then comes a costed breakdown covering the ticket, travel, accommodation and the working days away, so the manager sees the full picture once. It closes with what comes back: a write-up, a short internal session, or a specific list of contacts or suppliers worth following up.

Why the tone matters as much as the layout

A request written as a business case reads differently from one written as a favour. It doesn't apologise for the ask, and it doesn't pad the case with enthusiasm about the speakers or the venue. It treats attendance as a decision with a cost and a return, and leaves the manager to weigh it as one.

The full wording for each section, along with the costing worksheet referenced elsewhere in this guide, sits in the worked examples and templates page.