Free Event Plan Template
An event plan from venue to wrap-up — milestones, vendors, run-of-show and budget.
Part of our free project plan templates.
Your download has started.
Didn’t start? Retry the Word file or get the PDF.
1.Project Overview
| Project name | {{Project name}} |
|---|---|
| Sponsor | {{Sponsor / decision-maker}} |
| Project manager | {{Project manager}} |
| Start date | {{Start date}} |
| Target end date | {{Target end date}} |
| Status | {{Not started / On track / At risk}} |
Keep this block on page one so anyone can see the project, its owner, and where it stands at a glance. Name one accountable project manager and one sponsor who can unblock decisions.
2.Objectives & Success Criteria
- Deliver {{the event}} for {{N}} attendees on {{date}} within the {{$budget}}
- Hit the event goal: {{e.g. registrations, leads, attendee satisfaction}}
- Run a smooth day with no major logistics or AV failures
Write objectives you can measure — “launch the new checkout by Q3 with under 1% error rate”, not “improve checkout”. If you cannot tell whether it is done, rewrite it.
3.Scope
In scope
- Venue, catering, and AV
- Agenda, speakers, and the run-of-show
- Registration, communications, and promotion
- On-site logistics and post-event wrap-up
Out of scope
- {{Sponsorship sales, if handled separately}}
- {{Post-event content production / on-demand videos}}
- {{Travel booking for attendees}}
Naming what is out of scope is what actually prevents scope creep. Be explicit about the work people will assume is included but is not.
4.Milestones & Timeline
| Milestone | Owner | Target date | Status |
|---|---|---|---|
| Venue & date confirmed | {{Event lead}} | {{Date}} | {{Status}} |
| Speakers / agenda confirmed | {{Program owner}} | {{Date}} | {{Status}} |
| Registration open | {{Marketing}} | {{Date}} | {{Status}} |
| Promotion campaign live | {{Marketing}} | {{Date}} | {{Status}} |
| Final headcount & run-of-show locked | {{Event lead}} | {{Date}} | {{Status}} |
| Event day | {{Event lead}} | {{Date}} | {{Status}} |
| Wrap-up & debrief | {{Event lead}} | {{Date}} | {{Status}} |
Milestones are checkpoints, not tasks — a handful of dates that prove the project is moving. Each should be a clear “done / not done”, with one owner.
5.Tasks & Work Breakdown
| Task | Owner | Start | Due | Status |
|---|---|---|---|---|
| {{Shortlist and book the venue}} | {{Owner}} | {{Start}} | {{Due}} | {{Status}} |
| {{Line up catering, AV, and vendors}} | {{Owner}} | {{Start}} | {{Due}} | {{Status}} |
| {{Confirm speakers and build the agenda}} | {{Owner}} | {{Start}} | {{Due}} | {{Status}} |
| {{Open registration and promote the event}} | {{Owner}} | {{Start}} | {{Due}} | {{Status}} |
| {{Build the run-of-show and brief the team}} | {{Owner}} | {{Start}} | {{Due}} | {{Status}} |
Break the work into tasks small enough to track in a week or less. Give each an owner and a due date; a task with no owner will not happen.
6.Roles & Responsibilities
| Role | Name | Responsibility |
|---|---|---|
| Event lead | {{Name}} | Owns the plan, budget, vendors, and the day-of |
| Program owner | {{Name}} | Owns the agenda, speakers, and content |
| Marketing | {{Name}} | Owns registration, comms, and promotion |
| Logistics | {{Name}} | Owns venue, AV, catering, and on-site setup |
Assign responsibilities to roles so the plan survives a team change. Be clear who decides, who does the work, and who needs to be kept informed.
7.Risks & Mitigation
| Risk | Impact | Likelihood | Mitigation | Owner |
|---|---|---|---|---|
| {{Low registration / attendance}} | {{High}} | {{Med}} | {{Start promo early; set a fallback date/format}} | {{Owner}} |
| {{Key speaker or vendor cancels}} | {{High}} | {{Med}} | {{Backups lined up; confirmation deadlines}} | {{Owner}} |
| {{Budget overrun}} | {{Med}} | {{Med}} | {{Track spend vs budget; hold a contingency}} | {{Owner}} |
| {{AV / tech failure on the day}} | {{High}} | {{Low}} | {{Tech check + backup equipment day-before}} | {{Owner}} |
List the few risks that would actually derail the project, rate impact and likelihood (High/Med/Low), and name the action and the owner. Review this table at every status check.
8.Budget
| Item | Estimate | Actual |
|---|---|---|
| {{Cost item — labor, tools, materials}} | {{Estimate}} | {{Actual}} |
| Contingency | {{Estimate}} | {{Actual}} |
Estimate the main cost lines and add a contingency for the unknowns. If your project has no budget, keep the section and write “N/A” — reviewers expect to see it.
9.Approval
Both sign-offs confirm the plan, scope, and budget are agreed before work starts.
A worked example for a company’s one-day annual user conference for ~300 attendees.
1.Project Overview
| Project name | Northwind Connect 2026 (user conference) |
|---|---|
| Sponsor | VP Marketing |
| Project manager | Elena Ruiz (Event Lead) |
| Start date | June 1, 2026 |
| Target end date | October 9, 2026 |
| Status | On track |
2.Objectives & Success Criteria
- Host 300 customers for a one-day conference on October 8 within the $120K budget
- Generate 40 expansion conversations and a 4.5/5 attendee satisfaction score
- Run a smooth single-track day with keynote, breakouts, and an evening reception
3.Scope
In scope
- Downtown conference venue, catering, and AV
- Keynote, six breakout sessions, and the evening reception
- Registration, email campaign, and on-site check-in
- Run-of-show, staffing, and the post-event survey and debrief
Out of scope
- Sponsor sales (handled by the partnerships team)
- Recording and post-event on-demand videos (phase 2)
- Attendee flights and hotels (attendees book their own)
4.Milestones & Timeline
| Milestone | Owner | Target date | Status |
|---|---|---|---|
| Venue & date confirmed | Elena Ruiz | Jun 20 | Done |
| Speakers & agenda confirmed | Program (Dev) | Aug 1 | In progress |
| Registration open | Marketing (Tara) | Aug 8 | Not started |
| Promotion campaign live | Marketing (Tara) | Aug 15 | Not started |
| Final headcount & run-of-show locked | Elena Ruiz | Oct 1 | Not started |
| Event day | Elena Ruiz | Oct 8 | Not started |
| Wrap-up & debrief | Elena Ruiz | Oct 9 | Not started |
5.Tasks & Work Breakdown
| Task | Owner | Start | Due | Status |
|---|---|---|---|---|
| Book the venue, catering, and AV vendor | Elena Ruiz | Jun 1 | Jun 20 | Done |
| Confirm keynote and six breakout speakers; build the agenda | Dev Shah | Jun 23 | Aug 1 | In progress |
| Build the registration page and open sign-ups | Tara Lin | Jul 28 | Aug 8 | Not started |
| Run the email + social promo campaign to the customer base | Tara Lin | Aug 11 | Oct 1 | Not started |
| Build the run-of-show, staff assignments, and day-of brief | Elena Ruiz | Sep 14 | Oct 1 | Not started |
6.Roles & Responsibilities
| Role | Name | Responsibility |
|---|---|---|
| Event lead | Elena Ruiz | Owns the plan, budget, vendors, and the day-of |
| Program owner | Dev Shah | Owns speakers, the agenda, and content |
| Marketing | Tara Lin | Owns registration, comms, and promotion |
| Logistics | Marco Vega | Owns venue, AV, catering, and on-site setup |
7.Risks & Mitigation
| Risk | Impact | Likelihood | Mitigation | Owner |
|---|---|---|---|---|
| Registration tracks below 300 | High | Med | Launch promo early, add a customer-advocate referral push, hold a waitlist | Tara Lin |
| Keynote speaker cancels | High | Low | Confirm by Aug 1 with a backup keynote identified | Dev Shah |
| Budget overrun on catering/AV | Med | Med | Lock vendor quotes; track spend weekly; hold a 10% contingency | Elena Ruiz |
| AV failure during the keynote | High | Low | Full tech rehearsal Oct 7 with backup mics, projector, and laptop | Marco Vega |
8.Budget
| Item | Estimate | Actual |
|---|---|---|
| Venue & catering | $62,000 | — |
| AV & production | $28,000 | — |
| Marketing & registration platform | $14,000 | — |
| Contingency (≈10%) | $12,000 | — |
9.Approval
How it works
- Preview the event plan — objectives, scope, milestones, tasks, roles, risks and budget.
- Download Word/PDF, or copy the text to paste into Google Docs or a sheet.
- Fill in your venue, vendors, agenda and promotion milestones with owners, then track to the day.
Frequently asked questions
What should an event plan include?
An event plan should set the goal and attendee target within a budget, the scope (venue, catering, AV, agenda, registration, promotion), milestones from venue-confirmed through event day and wrap-up, a task breakdown with owners and dates, the roles, the risks, and the budget. This template lays out those sections with a worked user-conference example.
How do you plan an event step by step?
Set the goal, date, and budget; confirm the venue and key vendors; build the agenda and confirm speakers; open registration and run a promotion campaign; lock the final headcount and a detailed run-of-show; deliver the event day with a clear staff plan; then debrief and follow up. The template’s milestones and tasks follow that order.
What is a run-of-show?
A run-of-show is the minute-by-minute schedule for the event day — what happens when, who is responsible, and the AV or logistics cue for each segment. It keeps the day on track and gives every team member and vendor a single source of truth. Build it from the agenda as you approach the event.
How far ahead should you start planning an event?
It depends on size: a small internal event may need a few weeks, while a conference for hundreds often needs three to six months to secure a venue, speakers, and registrations. Work backwards from the date, set milestones for venue, speakers, registration, and promotion, and start promotion early — low registration is the most common risk.