How to get your employer to pay for a conference

A request to attend a conference is really four separate approvals folded into one email, and most requests get stuck because only one of them is written down. Your manager needs to see the business case, the full cost, the time you will be away from your usual work, and some sense of what comes back for the outlay. Leave one of these out and the request either bounces back with a question or sits in a slow, noncommittal maybe.

The business case

This is the reason the conference connects to the job you are actually paid to do. A manager is approving a line in a budget, so the case needs to name the problem the trip addresses: a skill gap, a decision the team is about to make, a market you need to understand better than you currently do. "It looks useful" is not a business case. "We are choosing a new supplier for X next quarter and this is where the people making that decision will be" is.

The full cost, not just the ticket

The ticket price is the number everyone quotes and the number that is least likely to be the whole story. A complete request itemises travel, accommodation if the event runs more than a day, meals not covered by the ticket, and the cost of the working days you will not be doing your normal job while you are there. Presenting the ticket price alone and letting the rest surface later is the single most common reason a verbal yes turns into an awkward conversation about the expense claim.

The time away

Approving a conference means approving a gap in cover, and that is a separate decision from approving the spend. Say what will not get done while you are out, who picks up anything urgent, and whether the dates clash with anything the team already has planned. A manager who has to ask "but who covers your Tuesday standing meeting" after saying yes is a manager who will hesitate longer next time.

What comes back

The spend becomes easier to defend, to you and to anyone above your manager who asks about it, if something concrete comes out the other side. A short write-up circulated to the team, a fifteen-minute internal session on what you learned, or a list of contacts made that the business can actually use are all things a manager can point to later. This does not need to be elaborate; it needs to exist and be specific enough that someone other than you can see the point of the trip.

A worked version of a request built around these four elements, with the structure and level of detail that tends to get a quick answer, is set out in the worked examples and templates. If you are still deciding whether the event is worth the case in the first place, that question is covered separately in Is This Conference Worth Going To?

The ticket price is the number a manager sees first, and it is rarely the number that matters. A funding request built on the ticket alone tends to come back with extra questions later, once travel, hotel nights and the days spent away from your desk get added on top. Working out the full cost before you ask saves that second, awkward conversation.

The ticket itself

Check what the ticket actually buys before quoting it. Some conference tickets cover the sessions only, with meals, the evening social and any workshop add-ons priced separately. A day pass and a full multi-day pass are different purchases with different implications for how many nights you need away, so match the pass to the sessions you actually plan to attend.

Travel

Travel cost depends on how far the venue is and how close to the start time you need to arrive. A conference starting at 9am on the far side of the country usually means travelling the evening before, which turns a one-day trip into a two-night one once accommodation is added. Work out the travel time first, then decide whether an early train or flight on the day is realistic or whether the extra hotel night is the honest option.

Accommodation

Work out how many nights you genuinely need. A single-day domestic conference within a couple of hours' travel may need no hotel at all. A two-day event that starts early on day one usually needs one night, sometimes two if the return journey on the final evening is impractical. Booking outside the conference hotel block is often cheaper, but check whether the block rate includes anything the alternative does not, such as breakfast.

Meals and incidentals

Lunch is usually included in the ticket price for a single-track or multi-track daytime conference; breakfast and dinner usually are not. Add a daily allowance for meals not covered, plus a smaller amount for the incidentals that always turn up: coffee before the day starts, a taxi when the last train doesn't line up, printing something at the hotel. These are small individually and easy to forget as a group.

The working days lost

This is the cost most funding requests leave out, and it is often the one your manager is actually weighing. A day at a conference is a day not spent on your usual work, and a travel day either side is often a half-lost day as well. Put a rough figure on that, using your day rate or the value of the work that will be delayed, and say what will cover it: nothing, a colleague picking up the most urgent items, or the work simply waiting until you're back. Naming this is what makes a request easy to approve, because it answers the question your manager would otherwise have to ask.

Building the realistic total

Add the ticket, travel, accommodation, meals and a working-days figure together, then add a margin for the things that move once you book: a train fare that rises closer to the date, a hotel room that isn't available at the block rate by the time you get approval. Present this as one total in the request, so the number your manager sees is the number they'll actually be asked to sign off. A worked example of how this total is built and presented sits in the worked examples and templates section, and if you haven't yet settled on which conference is worth this outlay, that decision belongs in Is This Conference Worth Going To? before the costing does.

An employer approving conference costs is buying a chance to see something come back into the business. A funding request that only describes the sessions you'll attend and the people you might meet gives your manager nothing to point to later if someone asks why the budget went there. Naming the return before you leave is what turns the request from a favour into a decision with an obvious answer.

Three things worth offering

• A write-up. One or two pages covering what you learned and where it applies to current work, circulated within a week of getting back, while it's still fresh and your manager still remembers approving the spend.
• An internal session. A twenty- to thirty-minute walkthrough at a team meeting, covering the two or three things worth repeating to colleagues who didn't go. This reaches several people at once.
• A list of contacts made. Relevant where the conference is about relationship building or supplier scouting. Attach names, roles and what each contact might be useful for, so the list is usable.

Match the offer to why you're actually going

A conference built around a specific skill or tool suits a write-up, because the return is knowledge that changes how you do the job. A conference built around sector direction or trends suits an internal session, because that content is more useful shared with several people at once than filed as one person's notes. A conference built around partnerships or sales suits the contacts list, because the return there is relationships.

Promise it before you go

Put the deliverable in the funding request itself. A line like "I'll circulate a one-page summary to the team by the following Friday" is a specific commitment your manager can hold you to, and it's often the detail that moves a hesitant approval into a yes. See How to Actually Get Value From a Conference for what to do with what you learn once the event is over.

A product manager wants to attend a two-day conference on data infrastructure, held in Manchester, eight weeks from now.

The full cost, not just the ticket

Turning the costs into a request

1. Add the direct costs together: £550 + £120 + £100 + £40 = £810.
2. Count the working days separately from the money. The trip covers the two conference days plus travel, so two days out of the office. A manager needs it to weigh against team capacity that week.
3. State both together as a single figure and a single time commitment: £810 in budget, two days' approved absence.

The proposal

Hi [manager's name],

I'd like to attend [conference name] in Manchester on [dates]. It's the main UK event for [specific topic relevant to the role], and this year's programme covers [one or two concrete session topics relevant to current work].

Full cost: £810 (ticket £550, travel £120, hotel £100, meals £40). I'd need two working days out of the office, including travel.

I'll write up the sessions relevant to [current project] and run a 20-minute session for the team the following week on what's changed in the space. I'll also come back with contacts from [specific companies or teams doing similar work] worth following up.

Can I go ahead and book?

Why this gets a yes without a reply

The manager is not being asked to find a number. £810 and two days are both stated, so there is nothing left to look up before approving. The proposal also names a return — a write-up, a team session, a set of contacts.

For the cost bands that apply to a longer or overseas trip, see How to Actually Get Value From a Conference. A blank version of this template, with the figures left for you to fill in, is in Worked Examples and Templates.