Sample conference planning pack
You want to see what a planning pack looks like before deciding whether you need one.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
This page shows excerpts from a planning pack for a fictional conference. Everything here is invented: the organisation, the people, the numbers and the decisions. It shows the format and level of detail, and it is not a record of any real event or client.
Take the layouts and adapt them to your own event. A pack is useful when each line has an owner, a date and a status.
How to read this sample
The fictional event is a two-day professional conference run by a fictional supply chain association. Names, figures and dates are placeholders. A real pack would use your own facts, and unknowns would stay marked as unknown.
The excerpts below follow the order of the Event Blueprint: brief, timeline, responsibilities, decisions, open questions.
Excerpt 1: project brief
| Item | Entry |
|---|---|
| Event | Annual Supply Chain Practice Conference, two days, Selangor (fictional) |
| Purpose | Share practice among members and set the association's priorities for the coming year |
| Audience | Practising members and invited guests from partner bodies |
| Planning size | 250 delegates, illustrative only, to be confirmed from last year's registration data |
| Format | Day 1 plenary and panel sessions. Day 2 two parallel tracks and a networking lunch |
| Date window | A fixed window set by the council, with two avoid-dates listed in the pack |
| Decision owners | Programme: education sub-committee chair. Budget: honorary treasurer. Suppliers: secretary with treasurer sign-off |
| Already promised | One panel seat offered to a partner body. No supplier appointed |
| Out of scope | Sponsor sales, technical production and the association's annual general meeting |
Excerpt 2: milestone table
| Milestone | Counted from event | Owner | Depends on | Status |
|---|---|---|---|---|
| Scope and brief approved | 26 weeks before | Council | Brief draft reviewed | Open |
| Venue requirements issued | 24 weeks before | Secretary with project lead | Scope approved | Not started |
| Venue shortlist decision | 20 weeks before | Treasurer and council | Written proposals received | Not started |
| Speaker invitations out | 18 weeks before | Education sub-committee chair | Programme shape approved | Not started |
| Registration opens | 12 weeks before | Secretary | Pricing approved, system supplier appointed | Not started |
| Speaker briefings issued | 6 weeks before | Project lead | Speakers confirmed | Not started |
| Final numbers to venue and caterer | 2 weeks before | Secretary | Registration closing date | Not started |
| Handover documents issued | 2 weeks after | Project lead | Event closed, accounts reconciled | Not started |
Excerpt 3: responsibility matrix rows
| Task | Council | Secretary | Project lead | Supplier |
|---|---|---|---|---|
| Approve the programme | A | C | I | - |
| Write the venue requirements | C | A | R | - |
| Compare venue proposals | I | C | A and R | Venues supply proposals |
| Operate the registration system | I | A | C | R |
| Brief speakers | C | I | R | - |
| Ask the adviser about accessibility questions | A | R | C | Adviser answers |
Excerpt 4: decision log rows
| No. | Decision | Made by | Date | Affects |
|---|---|---|---|---|
| D1 | Day 2 will run two tracks, not three | Education sub-committee chair | Week 24 | Room requirements, speaker count |
| D2 | Networking lunch is for registered delegates only | Council | Week 23 | Catering numbers, registration categories |
| D3 | Venue shortlist limited to three | Secretary | Week 22 | Site visit schedule |
| D4 | Question for adviser: access arrangements for delegates with mobility needs | Raised by project lead | Week 21 | Venue shortlist, owner: council |
Excerpt 5: open questions
- Which venue room layouts can the shortlisted venues confirm in writing for the main plenary? Owner: project lead. Needed by: venue decision.
- Does the partner body's panel seat have a speaker named? Owner: education sub-committee chair. Needed by: speaker invitations.
- What does the adviser say about recording the plenary? Owner: council. Needed by: registration opening.
Using the pack
Review the pack at every milestone. Record changes in the decision log, and move open questions to decisions as they are answered.
If you want someone to keep it current and run the coordination, see outsourced conference project management. For the split of roles, see who does what.
Worked example · Fictional example
A note on the fictional association
Fictional organisation and figures, for illustration only.
The association in this sample does not exist. Its brief shows the size of a typical committee decision set, and shows that unknowns such as the delegate count stay visible.
A real pack would be written from your own documents, with your own dates and your own decision owners.
Use this yourself
Planning pack contents checklist
Use this to check that your own pack, from any source, has the parts that matter.
- Brief with purpose, audience, format, date window and out-of-scope list.
- Milestone table counted back from the event date, each with owner and dependency.
- Responsibility matrix with one accountable name per row.
- Decision log with date, owner and what each decision affects.
- Open questions list with owner and needed-by date.
- Supplier requirements for each supplier type.
- Communications calendar for speakers and delegates.
- Handover section: contacts, files and next steps.
Handle it in-house, or bring in help?
Your team can usually handle this when
- You can build the pack yourselves from these layouts.
- Your event is small and one person holds the plan.
- Approvals are simple and need no formal record.
Outside planning help earns its fee when
- Committees disagree and need a neutral document to approve.
- Finance or procurement requires a defined scope before spending.
- You do not have the time to write and maintain the pack.
Want a pack like this written for your event?
An Event Blueprint writes the brief, milestone table, responsibility matrix, supplier requirements and handover documents from your own facts, with unknowns left visible and each line owned. Send the brief you have, even if parts are undecided.
Questions organisers ask
Is this a real client's pack?
No. Every name, figure and date here is fictional. No client work is shown on this site.
Can I copy these tables?
Yes. Adapt the layouts for your own event and replace every entry with your own facts.
How long is a full pack?
That depends on the scope. See fees, scope and quotations for what shapes the work.
Does a pack include a budget?
A pack structures the budget assumptions for approval by your finance owner. The figures come from you and your suppliers' quotations.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.