Quality assurance and readiness gates
Event pre-launch quality checklist
Registration is about to open, and the committee wants to know whether anything has been missed.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
A pre-launch checklist asks one question per item: what evidence do we hold? Mark each item yes, no, unknown or not applicable, name an owner, and attach the evidence.
Unknown items are not passes. If a critical item is unknown, the honest status is not ready, and the next step is to find out.
What pre-launch means here
Pre-launch is the point where the event becomes public: invitations, a registration page, a call to speakers or a first announcement. After this, changes cost more because other people have acted on what you said.
The checklist is a release check on your own planning. It is not a safety or compliance approval, and it cannot promise that the event will go well.
Six areas to check
| Area | Evidence to hold | Typical owner |
|---|---|---|
| Scope and authority | Approved brief, named approvers, decision log with no overdue items | Secretariat head |
| Date and venue | Written venue confirmation of date, rooms and conditions | Event owner |
| Suppliers | Written confirmations of scope and dates, see supplier confirmation evidence | Project lead or secretariat |
| Registration and links | Tested form, confirmation message and links, see link and registration testing | Registration owner |
| Programme | Draft running order checked against the timing stress test | Programme owner |
| Fallbacks and sign-offs | Named fallbacks and the final authority sign-off plan | Event owner |
How to treat unknowns
Split items into critical and other. A critical item is one where being wrong would force a public change or a cancelled commitment, for example the date, the venue booking or who approves speakers.
Any unknown critical item blocks launch until it is resolved or the committee accepts the risk in writing, with a named person. Unknown items that are not critical can go into the decision log with a date.
Run the check in one sitting
- Print or share the checklist with the owners of each area.
- Each owner marks items and attaches evidence before the meeting.
- In the meeting, read only the no and unknown items. Do not re-read the yes items.
- Record a decision for each open item: fix, accept the risk, or move the launch date.
- Repeat for items changed since the last pass, not for the whole list.
Worked example · Fictional example
A fintech association checks its forum two weeks before opening registration
Fictional organisation and figures, for illustration only.
A fictional fintech association plans a one-day forum for about 200 members. Of 24 checklist items, 17 are yes with evidence, 3 are no, 3 are unknown and 1 is not applicable.
Two of the unknowns are critical: the venue has not confirmed the second breakout room in writing, and nobody is named to approve the keynote's slides. The secretariat holds the launch for one week, gets the room confirmed, and assigns the approval to the programme chair.
Use this yourself
Pre-launch checklist
Copy each line and mark yes, no, unknown or not applicable. Add owner, evidence and date.
- Purpose, audience and format approved by named approvers:
- Date confirmed in writing by the venue:
- Rooms and layouts confirmed in writing for each session:
- Each supplier confirmed in writing for scope and date:
- Speaker list approved by the person who owns that decision:
- Registration form tested end to end:
- Confirmation message checked against the master programme:
- All public links opened on phone and desktop:
- Names and titles checked against the source list:
- Language versions match the master:
- Running order tested with a late start and an overrun:
- Fallback named for each critical dependency:
- Final sign-off owners named for each area:
- Open items listed with owner and decision date:
Handle it in-house, or bring in help?
Your team can usually handle this when
- One person can collect evidence and the owners reply quickly.
- The format is familiar and suppliers are already confirmed in writing.
- Few critical items are unknown.
Outside planning help earns its fee when
- Many critical items are unknown and nobody owns them.
- Several committees or departments each hold part of the sign-off.
- You need a bounded, prioritised list of unresolved decisions before the committee commits.
Unsure what is still unresolved before launch?
A planning diagnostic is a bounded review of your brief, decision log and supplier confirmations that returns a prioritised list of unresolved decisions by workstream. It does not certify safety or compliance. You keep every decision; the review shows which ones are still open.
Questions organisers ask
Can a completed checklist show that the event is safe?
No. The checklist records what planning evidence you hold. Safety, legal and structural questions belong with the competent parties, and their answers are evidence you attach, not conclusions the checklist draws.
What if every item is yes?
Check that the yes answers each point to evidence you can open. A yes with no evidence should be treated as unknown until someone shows the document.
How often should we repeat it?
Run the full list once before launch. After that, re-check only items that have changed, and again before final sign-off.
Who should own the checklist?
One coordinator, usually the secretariat head or project lead, holds the list. The owners of each area supply the evidence.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.