Commission and appoint the project lead
What an event management proposal should include
You are about to ask a consultant or agency to propose how they would manage your conference, and you want to receive something you can actually compare.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
A usable proposal states what will be done, by whom, in what phases, what is excluded, how decisions are made, how the fee is built and what happens when scope changes. Anything missing from that list becomes a negotiation later.
The easiest way to get it is to send your brief with the request and ask for the proposal in a stated structure.
The twelve items to ask for
| Item | What a good answer looks like |
|---|---|
| 1. Understanding of the event | Restates your purpose, audience and constraints in the proposer's own words, and lists assumptions. |
| 2. Scope of work | Named deliverables by phase, not only activity words such as manage or coordinate. |
| 3. Exclusions | What is outside scope and who is expected to do it. |
| 4. Team and time | Who does the work, their role and the time commitment, with named cover for absence. |
| 5. Decision rights | What the project lead can decide alone and what needs your approval. |
| 6. Plan and milestones | Phases with dates or date ranges and the outputs due at each. |
| 7. Supplier approach | How suppliers are shortlisted, who contracts them and how conflicts of interest are declared. |
| 8. Reporting | What you receive, how often, in what format. |
| 9. Fee structure | What the fee covers, how it is built, what is billed separately and when invoices fall. |
| 10. Change handling | How added work is requested, priced and approved, linked to scope growth. |
| 11. Event-day boundaries | Where responsibility starts and stops, see event-day limits. |
| 12. Handover and end of engagement | What documents you keep, and what happens if either side ends the work early. |
Warning signs in the proposal itself
- Scope written only as verbs with no outputs, so nobody can tell when something is done.
- A single total with no breakdown, which makes comparison impossible.
- No mention of what the client must provide and by when.
- Silence on who contracts suppliers and who is liable for them.
Contract terms are a separate question
A proposal describes the intended work. Liability, indemnity, termination, intellectual property and data handling belong in the agreement, and your organisation's legal adviser should review them.
Use the proposal to surface these topics early. Ask the proposer which terms they expect to be in the agreement and bring that list to your adviser.
Giving every proposer the same facts
- Send the same brief and the same list of items to each proposer.
- Set one deadline for questions and share each answer with everyone.
- Ask for the fee in your own table so lines can be matched, then compare with the quotation method.
- Hold a short call with each, using the same questions.
Worked example · Fictional example
A secretariat reads two proposals for a one-day forum
Fictional organisation and figures, for illustration only.
The Persatuan Fiktif Pengurus Logistik receives two proposals. One lists activities in detail but gives a single lump sum. The other prices three phases and lists exclusions, including speaker travel and printed materials.
Neither covers event-day boundaries. The secretariat sends both a short list of missing items and asks for revised proposals by the same date, so the comparison starts from equal information.
Use this yourself
Proposal request checklist
Paste this into your request so every proposer answers the same questions.
- Restate our purpose, audience and constraints, and list your assumptions.
- List deliverables by phase, with the output due at each milestone.
- List what is not included and who is expected to do it.
- Name the people doing the work, their roles, time commitment and cover arrangements.
- State what you can decide alone and what needs our approval.
- Give a phased plan with dates or ranges.
- Explain how suppliers are shortlisted, who signs their contracts, and how conflicts are declared.
- Describe reporting: content, frequency, format.
- Break down the fee, state what is billed separately and the invoice schedule.
- Describe how added work is requested, priced and approved.
- State where your responsibility on event day starts and ends.
- State handover documents and what happens if the work ends early.
Handle it in-house, or bring in help?
Your team can usually handle this when
- Your team has issued event service requests before and has a template.
- Only one or two proposers are being compared.
- The scope is small and a single phase.
Outside planning help earns its fee when
- You have not bought event management before and cannot tell a thin proposal from a full one.
- Procurement needs a documented basis for choosing.
- Proposals arrive in very different shapes and need normalising before a committee can read them.
Need the request and the comparison prepared?
A conference project lead can turn your brief into the request, answer proposers' questions with one voice, and prepare a side-by-side summary for your committee. The choice and the signature stay with your organisation.
Questions organisers ask
How long should an event management proposal be?
Length matters less than structure. A short proposal that answers all twelve items is more useful than a long one that skips scope and exclusions.
Should we ask for the fee before the scope is agreed?
Ask for an indicative fee with stated assumptions, then confirm it once scope is agreed. A fee without scope cannot be compared.
Can a proposer see our budget?
You decide. Sharing a range can help proposers fit scope to it, while withholding it can show how each one prices. Either way, state what the budget includes.
Who should read the proposals?
At least the budget owner and the person who will work daily with the appointee. Finance or procurement should read the fee and change sections.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.