Proposal
What Is an Event Proposal?
Structure, Examples, and What Wins
An event proposal is not a description of an event. It is an argument that a particular event is the right way to achieve a result the reader already wants. Proposals that lead with the event lose to proposals that lead with the result.
The short answer
An event proposal is a document submitted to a client, sponsor, or internal decision-maker that sets out the objective of a proposed event, the concept that delivers it, how it will be executed, what it costs, and what the reader is being asked to approve. It is used in two situations: responding to a brief or a request for proposal, and pitching an event nobody has asked for yet. The structure is similar; the burden of proof is not.
What the document has to do
Before writing, be clear about which of two jobs you are doing, because they need different openings.
| Situation | Reader already believes | Your opening must |
|---|---|---|
| Responding to a brief or RFP | That an event should happen | Show you understood the objective better than the competition did |
| Pitching unsolicited | Nothing yet | Establish the problem and why an event is the right instrument for it |
| Internal budget request | That resources are scarce | State the ask, the return, and the cost of doing nothing |
In all three cases, the reader is deciding whether to spend money and reputation on you. Everything that does not help them make that decision is padding, and padding is how a proposal gets skimmed.
Point
Assume your reader opens the document, reads the first page, and then jumps to the budget. Write for that behaviour: the first page must carry the objective, the concept in one line, and the headline ask.
The structure
1. The objective, in the reader's words
Restate what the event is for using the language of the business, not the language of event production. 'Give three hundred existing customers a reason to renew before the end of the contract year' is an objective. 'Deliver a world-class attendee experience' is not — it names no outcome and could be said of anything.
2. The audience
Who attends, how many, what they currently think, and what you need them to think afterwards. If you cannot describe the shift you are attempting, the rest of the document has nothing to aim at.
3. The concept
One paragraph that could be read aloud. What kind of event, where, roughly when, and the single idea that makes it work. If the concept needs three pages to explain, it will need three pages to sell internally after you leave the room, and it will not survive.
4. The programme
An outline of the event itself: format, flow, the content spine, and what attendees do rather than only what they watch. Enough detail to be credible, not so much that it reads as a finished plan you will inevitably change.
5. Delivery
Who does the work, the production approach, the timeline from approval to event day, and the dependencies you need from the reader. This section is where experienced buyers look for evidence that you have done this before.
6. Investment
Costs, grouped the same way your budget is grouped, with what is included and what is explicitly excluded. Give the reader a total they can take to their own approver.
7. Measurement
How you will know whether the objective was met, defined before the event rather than after. Name the measures, who captures them, and when they will be reported.
8. The ask
Exactly what you want the reader to do, and by when. 'Approve the budget envelope and confirm the date by the 14th so that the venue hold converts' is an ask. 'We look forward to hearing from you' is not.
Note
Risks deserve a short section of their own, and including them strengthens rather than weakens a proposal. Name the two or three real exposures — a date dependency, a speaker who is not yet confirmed, a venue hold that expires — and say what you will do about each. Readers who have run events before are suspicious of documents with no risks in them.
Example wording
The difference between proposals is usually in the phrasing rather than the structure. These pairs show the same content written weakly and strongly.
| Weak | Stronger |
|---|---|
| A premium, immersive brand experience | A half-day working session where forty named accounts build their own migration plan with our engineers |
| We will drive engagement | Each attendee leaves with a written plan and a named contact; we will report how many of the forty have booked a follow-up within thirty days |
| Budget: see attached | Investment: total as below, inclusive of venue, production and catering; excluding attendee travel and any content filming |
| Timeline: approximately 3 months | From approval, eight weeks to venue contract and speaker confirmation, four weeks to content freeze, one week on site |
| We are passionate about events | We delivered three events of this format in the last year; references available on request |
An example opening paragraph
You told us renewals in the mid-market segment are decided between March and May, and that your team rarely meets those customers in person before the decision. This proposal sets out a single-day working session in April for forty of those accounts, built so that each one leaves with a written plan and a named contact. The ask is approval of the budget envelope below, and confirmation of the date by the 14th.
That paragraph does four things in four sentences: it proves the brief was understood, states the concept, states the measurable outcome, and states the ask. Everything after it is evidence.
How to present cost
Cost is where proposals are won and lost, and most of the damage is self-inflicted through vagueness.
- Group costs the way your budget is grouped so the proposal and the eventual invoice are legible as the same document.
- State exclusions prominently. The exclusions are what create disputes later, so putting them in small print is a false economy.
- Say what currency, and what tax treatment. For cross-border work, say who carries the exchange risk and whether quoted figures include applicable taxes.
- Avoid presenting a single number for a scope that is not yet fixed. Where elements are undecided, present them as separately priced options rather than burying an average in the total.
Point
Rates for venue, labour, equipment and catering depend on market and change year to year, so a proposal should price from quotes you currently hold in the city where the event will run. Never carry forward a number from a previous event in a different market as though it were a rate card.
Options rather than a single figure
Where the reader has a genuine choice, present two or three scoped options with the difference stated in one line each — typically a smaller version, the recommended version, and an extended version. State which you recommend and why. This converts a yes-or-no decision into a which-one decision, and it surfaces the reader's real constraint early.
Writing and submitting it
- 01
Confirm the brief before writing
Ask the three questions whose answers would change your approach: what the decision criteria are, who else is in the room when it is decided, and what the real deadline is. Proposals written on assumptions read like proposals written on assumptions.
- 02
Draft the one-page summary first
If you cannot write the objective, concept, ask and headline cost on one page, the thinking is not finished. Write that page, then build the document behind it.
- 03
Write the measurement section before the programme
Deciding how success will be judged usually changes the programme. Doing it last means the programme is never tested against anything.
- 04
Price from current quotes
Approach suppliers before you submit, not after you win. A proposal priced from memory is a proposal you will have to renegotiate.
- 05
Have someone outside the project read it cold
Give them five minutes and ask what is being proposed, what it costs, and what is being asked of them. If they cannot answer all three, fix the first page.
- 06
Submit, then walk it through
Where the format allows, present it rather than only sending it. A document read in silence loses to a document someone explained, and the questions you get are what you need for the next version.
Key takeaways
- Lead with the objective in the reader's language, not with a description of the event.
- The first page must carry objective, concept, headline cost and the ask — readers skim the rest.
- State exclusions prominently and price from current quotes in the city where the event will run.
- Include risks and a measurement section; their absence reads as inexperience to anyone who has delivered events.
FAQ
Frequently asked questions
A document that asks a client, sponsor or internal approver to commit to a proposed event. It sets out the objective, the audience, the concept, the programme, how it will be delivered, what it costs, how success will be measured, and precisely what decision is being requested. It is an argument for a result, not a description of an event.
Long enough to be credible and short enough to be read. A one-page summary carrying objective, concept, cost and ask, followed by the supporting sections, works for most situations. Where a formal RFP specifies a structure or page limit, follow it exactly — proposals are routinely disqualified for ignoring submission rules.
Costs grouped the same way your budget is grouped, a clear total, an explicit list of exclusions, the currency and tax treatment, and the assumptions the price depends on such as headcount bands or number of event days. Where scope is genuinely undecided, present priced options rather than hiding an average inside a single figure.
Yes. Name the two or three genuine exposures and what you will do about each. Experienced buyers treat a risk-free proposal as evidence that the writer has not delivered this kind of event before, and unnamed risks surface later as disputes rather than as decisions.
A proposal argues for a decision and is written for an approver. A plan organises the work after the decision and is written for the delivery team. Reusing a plan as a proposal buries the argument in detail; reusing a proposal as a plan leaves the team without owners, dates or dependencies.