How to ask management to fund external event support
You know the team cannot carry this conference alone, but management sees only a fee and wants to know why.
The short answer
Ask in the language management uses: the problem in terms of risk and capacity, the options compared, what you are asking to approve, and how you will know it worked. Do not lead with the fee or with how stretched the team feels.
A short request that shows three options, including doing nothing, is easier to approve than a long plea for one.
What management is actually deciding
The approver is choosing between spending money, spending staff time or accepting risk. If the request only talks about workload, management may hear a staffing complaint rather than a business decision.
Frame the request around what the event needs to achieve for the organisation, what currently threatens that, and what each option costs in money and in internal time.
The structure of a one-page request
- Purpose: what the event is for and why it matters this year, in two sentences.
- Situation: the date, current stage, who is working on it and what is not owned.
- Gap: the specific tasks without capacity, with an estimate of weekly hours in the remaining months.
- Options: do nothing, add internal time, or appoint outside support, each with cost, benefit and risk.
- Recommendation and ask: the option you propose, the amount or range for approval, and the decision date.
- Control: what stays with the organiser, how progress will be reported and how scope will be limited.
Compare options on the same terms
| Option | Money cost | Internal time | Main risk |
|---|---|---|---|
| Do nothing | None now | Heavy, unplanned, in the last weeks | Decisions late, rework, member-facing mistakes |
| Add internal time | Possible backfill or overtime | Taken from other member services or projects | Other work slips; no cover for absence |
| Appoint outside support for defined workstreams | A scoped fee, to be quoted | Reduced to approving and answering | Scope drift if the brief is vague |
| Smaller event or later date | Lower spend | Lower | Member expectations and committee consensus |
Questions management is likely to ask
- Why can the team not absorb this? Show the task list and weekly-hours estimate.
- What exactly will we get for the fee? Show scope, deliverables and who decides what.
- How will we know it is working? Offer a simple status report and dates for review.
- What if the scope grows? Describe the change-approval route.
- Is there a cheaper way? Show the option table and the costs of each.
Tone and timing
Make the request early enough that approval does not itself become the bottleneck. A request made in the final six weeks tends to be a rescue request, which is harder to scope and to approve.
Bring the responsibility matrix as evidence. It shows the gap in a form that is hard to dispute.
Worked example · Fictional example
A communications head asks the CEO
Fictional organisation and figures, for illustration only.
The communications head of a fictional property developers' association prepares a one-page request for the CEO. The matrix shows supplier coordination, speaker logistics and registration follow-up unowned, estimated at about eight hours a week for the final three months. Three options are compared, and the request recommends outside support for those three workstreams only.
The CEO asks for a quotation range and a status-report sample, approves the principle subject to the finance director agreeing the figure, and sets a date. Programme, budget and speaker choices stay with the committee.
Use this yourself
One-page request to management
Copy into a memo. Keep it to one page and attach the responsibility matrix.
- Event, date, and what it must achieve for the organisation:
- Current stage and who is working on it:
- Tasks without capacity, and estimated weekly hours by month:
- Option A: do nothing (consequences):
- Option B: add internal time (who, from what, cost, risk):
- Option C: appoint outside support (scope, cost to be quoted, risk):
- Recommendation and the approval requested (amount or range, decision date):
- What stays with the organiser, and who approves changes:
- How progress will be reported, and review dates:
Handle it in-house, or bring in help?
Your team can usually handle this when
- The gap is small enough to close with protected time from one person.
- Management has already approved similar support in the past.
- You can quantify the gap from a clear task list.
Outside planning help earns its fee when
- Management sees external support as a luxury and needs a structured case.
- Several teams are involved and nobody can describe the whole gap.
- The request needs an independent view of scope and cost, which a planning review can supply.
Need the case and scope prepared?
A conference project lead or an Event Blueprint can help turn the gap into a defined scope: what outside support would take on, what stays with your committee, and the deliverables you would review. That gives management something specific to approve and to quote against.
Questions organisers ask
Should I name a supplier in the request?
Usually not at first. Ask for approval of a scope and a budget range, then obtain quotations. Naming a supplier too early can complicate procurement.
What if management says no?
Ask what would change the answer: a smaller scope, a later phase, or evidence of risk. Then document the decision and the consequences accepted.
Can I ask for a small first step?
Yes. A bounded review or planning pack can show the gap and the options with limited spend before a larger decision.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.