Conference Record

Making the Case

Most conference requests are a cost with a justification attached. The ones that get approved are a return with a cost attached, and the difference is how the page is ordered rather than how much is asked for. For a separate operational reference outside conference evaluation, see this resource .

Reviewed August 9, 2026. An additional independent source is Clarivate .

The five lines

One. What comes back, specifically. Not "professional development". Three sessions on the migration problem we are stuck on. The maintainers of the library we depend on will be there. I will come back with a written summary for the team.

Two. The total. Registration, travel, accommodation, meals, and the working days. State the days. Hiding them makes the request look cheaper and makes you look as though you did not count.

Three. Why this event. A named alternative and why it lost — a cheaper regional event, a recording, next year's edition. Showing you considered the alternatives is what distinguishes a request from a wish.

Four. What happens with what you learn. A written note, a session for the team, a decision that has been waiting. This is the line that converts a personal benefit into an organisational one.

Five. The deadline that matters. Early registration date, not the conference date, with the difference in money stated.

One page. Five lines. Longer requests are not more persuasive; they are harder to approve.

What weakens a request

Leading with the fee. It frames the whole thing as a cost.

Omitting the days. The approver will notice, and it costs more credibility than the days cost money.

"Networking". True, unmeasurable, and it reads as a holiday to anybody who did not attend.

And no alternative considered. A request for one specific conference with no comparison implies the conference was chosen first and the justification written afterwards — which is frequently true and does not need to be visible.

The line that helps most

"I will produce a written summary for the team within a week."

It is small, it is checkable, and it changes the category of the request. It also makes the trip more useful, because attending with an obligation to summarise changes what you pay attention to.

Then actually do it. The second request is approved on the strength of the first summary, and the person who never delivered one has spent the budget they will want next year.

If the answer is no

Ask which line failed. Cost, timing, or the case itself — the answers differ and only one of them is about money.

Propose the cheaper version. One day instead of four, online attendance if offered, or a colleague going and reporting back.

And ask about grants. Travel support exists at many conferences and applications are frequently undersubscribed, and an employer who cannot fund the whole thing will often fund the remainder.

When the honest answer is that it is not worth it

Worth naming, because a page about getting approval should say it.

Some conferences do not repay their total cost, and that is a separate question from whether they are legitimate.

If you cannot write line one — what comes back, specifically — that is the finding, and it arrives before you have spent anybody's money. A request that cannot state its return is usually a request that does not have one.

The short version