A task list becomes useful when every task has one owner, a deadline and a clear way to tell whether it is finished. Use this event planning checklist for a small community gathering, then adapt the venue and program details. The table is ready to copy into your own document or spreadsheet; there is no separate download to unlock.
Put the Public Event Links in One Place
VISU Link can bring together a public event information page, directions and an external response form you already use.
Define the Event Before Assigning Tasks
Write one sentence describing the purpose and who the event is for. Add a working size limit, the person who can approve spending and the person who can decide to change the plan. A small group can combine roles, but each task still needs a named owner.
The worked planning frame below is an original example: a 30-person indoor community talk with a 90-minute program. D means the event day. D−7 means seven calendar days before it. These are suggested working dates for this example, not a venue’s booking rules or a guarantee that four weeks is enough.
The University of Northern Iowa’s entertainment checklist separates practical questions such as the event date, facilities, equipment and staffing. That is a useful model for making responsibilities visible. Its campus procedures remain specific to that university.
If you have not chosen the format yet, start with the distinction between types of corporate events.
Copy the 12-Task Planning Board
Replace each role in the owner column with one person’s name in your private working copy. An organization or committee name alone does not tell you who should answer the next question.
Dependencies show which tasks must be resolved first. Keep the task IDs when copying the table. All rows begin at To do; they are not evidence that an event has already been organized. The last column tells you what to check before changing a row to Done.
| Task | Owner to assign | Depends on | Example deadline | Status | Done when |
|---|---|---|---|---|---|
| T01: Write the purpose, audience and size limit | Coordinator: ______ | None | D−28 | To do | One agreed paragraph defining the gathering |
| T02: Check room availability, access route and usable hours | Venue contact: ______ | T01 | D−24 | To do | Written availability, booking terms and access notes; no spending commitment yet |
| T03: Agree the spending limit and who approves costs | Budget owner: ______ | T01, T02 | D−21 | To do | Cost list with an approved limit and approver; any room booking confirmed within that approval |
| T04: Set a private contact route for access requests | Participant contact: ______ | T02 | D−20 | To do | Named contact and a process for following up |
| T05: Send the invitation with confirmed practical details | Communications owner: ______ | T02, T03, T04 | D−18 | To do | Checked invitation and a working response route |
| T06: Review responses and follow up on unresolved requests | Participant contact: ______ | T05 | D−7 | To do | Current headcount and private follow-up notes |
| T07: Assign named helpers and a substitute for each key role | Coordinator: ______ | T03, T06 | D−7 | To do | Role sheet accepted by the people listed |
| T08: Check the room layout, equipment and setup access | Setup lead: ______ | T02, T07 | D−3 | To do | Completed check and a workable fallback |
| T09: Write the running order and name the timekeeper | Program lead: ______ | T06, T07 | D−3 | To do | One agreed schedule with handoff cues |
| T10: Resolve critical blockers and send final instructions | Coordinator: ______ | T08, T09 | D−1 | To do | Explicit go, adapt or postpone decision |
| T11: Brief helpers, open the event and complete the handoff | On-site lead: ______ | T10 | D | To do | Briefing delivered and room returned as agreed |
| T12: Close costs, thank helpers and record follow-up actions | Coordinator, with budget-owner support: ______ | T11 | D+3 | To do | Actual costs reconciled and next actions assigned |
Review dates against the venue, suppliers and your own capacity. If a deadline has already passed, confirm whether the prerequisite can still be completed before committing to its dependent task. Do not mark a blocked row Done just to make the plan look on time.
Use Four Statuses and Record the Next Action
- To do
- Work has not started. The owner and due date are still assigned.
- In progress
- The owner is working on it and can name the next step.
- Blocked
- A decision, response or prerequisite is missing. Record who can unblock it and when you will check again.
- Done
- The completion evidence exists and has been checked. Sending a request is not the same as receiving confirmation.
Fictional example: T08 is Blocked because the venue has not confirmed a microphone. T08 has missed its D−3 deadline and stays Blocked. The setup lead records D−2 as the next follow-up with the venue contact, not as a replacement for the missed deadline. If the microphone is unavailable, the program lead must agree a workable format with the venue before T10 can close. The deadline has not created an automatic approval.
Share Confirmed Information
Add links after the practical details are confirmed. The task board, approvals and private participant requests stay in your own working tools.
Check Access and Keep the Invitation Accurate
Cornell’s accessible-meeting checklist asks planners to check the venue in advance, provide a contact route for accommodation requests and follow up on those requests. For your event, identify the person who will coordinate practical arrangements and confirm what the venue can provide.
The invitation should state the confirmed place, arrival instructions, start and finish, response method and contact for access questions. Give people a private way to discuss what they need. Keep individual requests in the working notes, not on a public attendance list.
Separate setup and clear-up access from program time. A 90-minute talk does not mean a 90-minute room booking. Confirm when helpers can enter, when participants leave and when the room must be handed back.
A 90-Minute Program Example
This original example is a running order, not a claim about the ideal length of every event. Adjust it with the speaker and venue. Setup and clear-up happen in separately agreed access periods.
| Minutes from the start | Activity | Person leading |
|---|---|---|
| 0–10 | Arrival and seating | Welcome lead |
| 10–15 | Welcome and practical information | Host |
| 15–65 | Main talk or demonstration | Speaker |
| 65–80 | Questions and discussion | Facilitator |
| 80–90 | Closing and next steps | Host |
The five blocks total 90 minutes: 10 + 5 + 50 + 15 + 10. Give the timekeeper a cue for each change. If the opening runs late, the host decides which later block can change; helpers should not each improvise a different finish time.
Make a One-Page Day-of Handoff
Give the on-site lead the latest task board and running order. Add the venue contact, the agreed access hours, the helpers’ roles and the one person who can authorize changes. Keep private contact details in the team copy.
Before opening, resolve critical blockers in T10. A missing optional decoration and an unavailable confirmed room are different problems. State the decision clearly: proceed, use the agreed adaptation or postpone. Tell participants if their practical instructions change.
After the event, compare actual spending with the approved limit, thank helpers and record a small number of assigned follow-up actions. A row is not closed merely because the event date has passed.
For guidance on presenting practical information through a code, see our QR guide for event organizers. Use a public information destination; keep private team notes separate.
Keep the Follow-Up Easy to Find
After the gathering, add public resources and the next event link to VISU Link. It does not replace your budget sheet, task status or participant management.
Frequently Asked Questions
What should an event planning checklist contain?
At minimum, a task, a named owner, a deadline, dependencies and a status. A completion check makes it clear what Done means for that task.
Are D−28 and the other dates mandatory?
No. They are relative working dates in an original small-event example. Confirm real venue, supplier and organizational deadlines before using them.
Can one person own several tasks?
Yes. A small team can combine roles. Each task still needs a specific person who can report progress and make the next action clear.
Is the table already completed for a real event?
No. All rows start at To do. The blocked-microphone scenario and the 90-minute program are fictional planning examples.
Does a 90-minute program require only 90 minutes of venue access?
No. Setup, arrival and clear-up arrangements must be confirmed separately with the venue. The program example totals 90 minutes only.
Does VISU Link manage this checklist or registrations?
The suggested use is to collect public information links and an external response form you already use. Your task board, approvals or participant records remain in your own tools.