Getting a Conference Approved: The Business Case That Works

Conference requests are declined for a predictable reason: they ask for permission to attend something rather than proposing to solve something. The approver has no way to evaluate the first and a straightforward way to evaluate the second.

For a related workplace-management perspective, Monitask discusses accountability and responsibility in the workplace.

Current HR learning formats can be reviewed through SHRM events and education resources.

What the approver is actually deciding

Not whether the conference is good. Three other things:

Is the cost justified by a specific return? Registration is the small part. Three days of your time is the large part, and they are pricing that whether they say so or not.

Who covers the work? A request with no answer to this creates a problem for them.

Is this development, or is it a trip? Both can be legitimate. Ambiguity is what gets declined.

Answer all three unprompted and most of the objection disappears.

The structure that works

Half a page. Longer is worse.

1. The problem or decision it addresses.

"We're selecting a timekeeping system this year and need to understand multi-state configuration before we shortlist."

Not "professional development."

2. Why this event specifically.

Name two or three sessions and why they matter. This demonstrates you read the programme, which is itself a signal — most requests do not.

"Three sessions cover multi-state configuration, including one from a company that did this across 14 states after an audit."

3. What you will bring back.

The part that converts a request into a proposal. Be concrete and small:

"A written summary of the vendor landscape and a one-page recommendation on shortlisting, within a week of returning."

4. The cost, fully stated.

Registration, travel, accommodation, meals. Stating the total yourself is more credible than making them assemble it, and it signals that you have considered it.

5. Coverage.

Who handles what while you are away, agreed in advance. Removes the objection before it is raised.

6. Alternatives considered.

One line. "The sessions aren't recorded, and the vendor comparison isn't available elsewhere." Shows you did not default to the expensive option.

What weakens a request

"Great networking opportunity." True and unmeasurable.

"Industry-leading speakers." Marketing copy, and the approver can see that.

No deliverable.

No coverage plan.

Sent late. A request three weeks before an event with early-bird pricing gone reads as an afterthought.

Framed as something you are owed. Even where true, it invites a different conversation than the one you want.

Timing

Ask early. Before early-bird pricing expires — you are then also saving money, which helps.

Ask in the budget cycle if there is one. A request that fits a planned line is easier than one that creates an exception.

If you present or contribute, mention it early. Registration is frequently free or discounted for speakers, which changes the arithmetic substantially.

If the answer is no

Ask what would change it — budget, timing, level, deliverable — and get the answer. A no with conditions is a path; a no without them is information about the budget rather than about the request.

Then propose the smaller version:

Registration only, no travel, where there is a virtual option.

One day instead of three.

A cheaper regional event covering the same ground.

Recorded sessions afterwards.

Split the request — you attend this year, a colleague next year.

Ask for the deliverable to be funded differently. If the real need is a vendor comparison, a few structured calls may deliver it for a fraction of the cost. That is a good outcome even though it is not the one you asked for.

After it is approved

The part that determines whether the next request succeeds.

Pick sessions in advance, and leave any that are not working.

Take notes against your stated question, not general notes.

Book the debrief before you leave. Thirty minutes, in the calendar, within a week.

Deliver what you promised, in writing, even briefly.

Say what was not worth it. An honest assessment — including "the vendor sessions were sales pitches and I'd skip them next time" — makes you a credible requester next year. A report claiming everything was excellent does the opposite.

The one line that decides it

Every approval request is answering the same question, whether or not it is asked:

"What will be true afterwards that is not true now?"

If your request answers that in a sentence, it will usually be approved. If it cannot, the request is for a trip — which may still be reasonable, and should be asked for on those terms.