· 26 min read
Event planning template: a practical guide for paid events

An event planning template should help you decide what needs doing, when it needs doing, and whether your event can make money. Start with the downloadable checklist below, replace its sample dates, and turn each task into a specific piece of work someone can finish. Then use this guide to connect the checklist to your budget, ticket sales, venue arrangements, and show day.
So you're planning a paid event. The venue wants a deposit, your designer needs the lineup, and someone has just asked when tickets go live. You can answer all three separately. The trouble starts when those answers don't fit together.
This guide walks you through using the template, building a realistic commercial plan, putting the work in order, and running it through the final week. We'll use one fictional paid event throughout, so you can see how the decisions affect each other. The numbers are worked examples, not industry averages or results from a Loopyah customer.
Download the event planning template
The Excel download is a simple checklist. Its sheet is called "To do", with columns for completion, date, and task. It includes example tasks covering goals, budgeting, venue arrangements, ticketing, promotion, staffing, technology, onsite operations, and emergency planning. A completion counter sits near the top.
Download TemplateSave your own copy before editing. The dates and completion marks in the file are examples. Replace the dates with your deadlines and reset the completed tasks before you start. You'll also find a row about sorting items. Treat that as an instruction for using the file, rather than something required to deliver your event.
Keep the file's limits in mind. It doesn't arrive with a detailed event budget, ticket revenue model, supplier payment schedule, or automatic sales forecast. You'll need those figures in your own working budget. It also doesn't have an owner column. Add one to your copy, or put the person's name at the start of the task. A dated task still needs someone responsible for finishing it.
The point is to give you a starting checklist you can adapt. A paid workshop won't need exhibitor move-in instructions. A food festival may need far more detail on vendors and waste collection. Remove irrelevant tasks, split broad tasks into useful actions, and add the work your event actually requires.
Set up the template before you fill it
The first thing you want to do is put the event date somewhere obvious. Include the public opening time, the finish time, and the venue access window for setup and breakdown. These are different times. Your audience may arrive at seven, while your crew needs access from lunchtime.
Name the file so that a supplier invoice, a team conversation, and a ticket report can all refer to the same event. If you run recurring events, include the date. Keep one working copy that the team can find. Sending a new attachment after every meeting creates competing versions of what has been agreed.
Next, make each task specific. "Ticketing setup" is fine as a heading. As a task, it's too broad. Split it into approving ticket quantities and prices, checking the event page, testing the purchase, and confirming the buyer's information. Each action can have its own deadline and owner.
Write the result you need to see before you tick the task. For the venue, that could be a signed agreement with the approved layout and access hours attached. For attendee information, it could be the final email checked on a phone, with the right venue entrance and start time. "Spoke to the venue" doesn't tell the next person whether the arrangement is settled.
You can add status and notes columns to your copy if they help. Use simple descriptions such as "not started", "waiting for quote", "needs approval", and "done". Explain what a blocked task is waiting for. "Venue quote needed before budget approval" gives the team a next action. A red cell with no explanation gives them a mystery.
Avoid turning this into an afternoon of formatting. Start with the decisions that can delay the event or increase its cost. Give those tasks an owner and a date. Refine the remaining tasks later.
Here's what four filled-in tasks could look like for our example. These are suggested additions to your copy, not fields already supplied in the download.
Approve the venue layout. Deadline: before ticket launch. Owner: Sam. Done when the venue confirms the layout and audience capacity in writing.
Test the ticket purchase. Deadline: before announcement. Owner: Jo. Done when a test buyer receives the correct ticket and confirmation on their phone.
Confirm production access. Deadline: two weeks before doors. Owner: Lee. Done when the venue and supplier agree unloading, setup and collection times.
Send arrival information. Deadline: three days before doors. Owner: Jo. Done when the checked message reaches the intended buyers.
Notice how each task ends with something you can check. That makes handovers much easier.
Start with the event you're actually selling
Before you book suppliers, write a short description of what a buyer gets. Who is it for? What happens during the event? Why would that person pay for it? What is included in the ticket, and what costs extra?
"A live music event for everyone" won't help you choose a venue or write an event page. "An evening of three local electronic acts for people who already attend this scene, with a clear running order and a late finish" gives you something to work with. It suggests an audience, a programme, and practical requirements.
Our fictional example is a one-night music event. The approved audience capacity is 400. The operator plans to release 360 paid tickets and keep the remaining 40 audience places for guest allocations and operational flexibility. The venue must still confirm how everyone onsite is counted under its actual occupancy arrangements. An audience allocation is not permission to ignore staff, artists, or other people in the building.
The ticket gives buyers admission to the show. Drinks are sold separately by the venue, and the operator receives no share of bar sales in this example. That detail matters. You can't put imagined bar revenue in your event budget because the room has a bar.
Write down what a good commercial result looks like too. For this example, the operator wants at least $2,000 of event operating profit before business overhead and income tax. They also want accurate cost records and a reliable contact process for the next event. Attendance is part of the result, but a packed room at a loss wouldn't meet the goal.
Add tasks for confirming these assumptions early. If the artist fee, ticket price, or capacity changes, someone needs to revisit the numbers. Otherwise the team can deliver the programme beautifully while working toward a target the revised event can no longer meet.
Build the budget before the commitments
Separate costs you pay to put the event on from costs that rise with attendance. Venue hire, a fixed artist guarantee, and an agreed production package may stay the same across a range of ticket sales. Consumables or an attendee service may increase for each person. Read the supplier agreement before deciding which category a cost belongs in.
The U.S. Small Business Administration explains this approach in its guide to business costs and break-even calculations. Its break-even calculation divides fixed costs by the selling price less the variable cost per unit. For a paid event, that unit can be a ticket, provided you use realistic retained revenue and include the relevant costs.
In our example, fixed costs total $9,000. That's $2,800 for venue hire, $2,500 for artists, $1,500 for production, $1,200 for a fixed staffing package, and $1,000 for marketing. These are invented costs in USD for explaining the calculation. They are not suggested supplier rates. This simplified model leaves out producer pay and a contingency reserve. Add those, and any other costs your event requires, to your real budget before treating a projected profit as money available to you.
The operator expects to retain an average of $35 per paid ticket after the deductions included in their model. Attendee-related variable costs are a further $5 per paid ticket. That leaves $30 per ticket toward fixed costs and profit. If a deduction is already included in retained ticket revenue, don't subtract it again as a separate cost.
At 300 paid tickets, $30 multiplied by 300 covers the $9,000 fixed cost. At 240 tickets, the event loses $1,800. At 360 tickets, it makes $1,800. All these results assume the fixed package stays unchanged, every sold ticket is retained, and there is no extra revenue or cost beyond the example. Refunds, tax treatment, price changes, or supplier changes would alter the result.
Notice the problem? Even selling all 360 paid tickets doesn't produce the operator's $2,000 goal. You would need 367 tickets at the same contribution, rounded up to a whole ticket. That exceeds the paid allocation. Finding this now is useful. Finding it while reconciling invoices after the show is expensive.
| Label | Event result USD |
|---|---|
| 240 tickets | -1800 |
| 300 tickets | 0 |
| 360 tickets | 1800 |
The operator could reduce fixed costs, change the ticket mix, secure additional confirmed revenue, or change the event format. They could also accept a lower return for a stated business reason. What they shouldn't do is leave a target in the plan that the available inventory cannot reach.
Treat contingency as a real budget decision. Identify what might change, estimate the possible cost, and decide how much room you need. A known extra equipment requirement belongs in the base budget. Calling it contingency doesn't make it disappear. For more detail on building the numbers, use our event budget guide.
Check when the money is available
Here's a planning mistake that can catch an otherwise sensible event. You can expect a profit and still run out of cash before doors open. A supplier asks for payment today. Your ticket revenue may become available later, and an expected sponsor payment may still be waiting on a signed agreement.
Add the payment date beside each cost in your working budget. Record the deposit, balance, any refund terms, and whether the amount is confirmed or still estimated. Your checklist should then include the actions needed to approve and make those payments.
For our fictional event, suppose $3,000 is payable eight weeks before the show, another $2,500 four weeks before, and $3,500 in the final week. Together those amounts equal the $9,000 fixed cost. They do not include the $5 per attendee variable cost, which the operator has agreed to settle after the event in this example.
If the operator has $4,000 available at the start and no ticket proceeds available before the final week, they face a $1,500 shortfall at the four-week payment point. That's a timing problem they need to solve before signing the contracts. They might negotiate payment dates, arrange funding, or change the plan. They shouldn't assume gross sales on a dashboard are cash they can use immediately.
Check your actual ticketing payment and payout arrangements. Allow for deductions, refunds, and any money that needs to remain available for buyer obligations. Don't promise suppliers a payment date based on a payout schedule you haven't confirmed.
Put one person in charge of maintaining the payment calendar. When a supplier revises the amount or deadline, update the budget and the task together. A correct total with an outdated due date can still put your event in trouble.
Confirm the venue and layout before launch
The venue affects what you can sell, how you can deliver it, and which costs you must carry. Inspect it for the actual programme you intend to run. A room that works for a seated talk may need a different arrangement for standing music, exhibition booths, or a workshop with equipment.
Confirm the approved audience layout and capacity with the venue. Record the stage footprint, entrances, exits, queues, accessible routes, toilets, and any areas reserved for artists or suppliers. Ask which arrangements must be approved before tickets go on sale. You need a sellable ticket quantity that matches the event you're putting on.
Read the agreement for access hours, noise restrictions, required suppliers, cleaning, security, equipment, staffing, overtime, and cancellation terms. Ask who pays when the event runs late. A low hire quote can become a costly booking when the necessary services sit outside it.
Check the route into the venue as well as the room. Can production unload during the agreed window? Does another event share the loading area? Where can a queue form without obstructing people nearby? Who opens the building, and what happens if that person is late?
Accessibility belongs in this inspection. The U.S. Department of Justice's accessibility guidance for businesses explains the importance of keeping accessible routes clear. Requirements depend on the location and circumstances of your event, so confirm the applicable obligations with the venue and relevant professionals. In practical terms, don't place a merchandise table or cable case in the route a buyer needs to use.
Add separate tasks for agreeing the layout, confirming access arrangements, approving the venue contract, and checking any local permissions. "Venue booked" shouldn't conceal unanswered questions about the event you can run there.
Turn ticketing setup into a buyer test
Once the commercial plan and venue arrangements make sense, approve the ticket offer. Set the quantities for each ticket type, what each includes, the dates it is available, and any restrictions. Keep the total within your approved inventory. Guest tickets and partner allocations belong in the same capacity conversation.
If you use different prices, budget for the mix you expect to sell. A headline price doesn't tell you your average retained revenue. Selling many discounted tickets can fill the venue while reducing the amount left to pay your fixed costs. Recalculate the worked example if you change the offer.
Give buyers the information they need before payment. State the venue, date, doors time, performance time, age conditions, ticket inclusions, access information, and relevant refund or transfer terms. If a detail is still unknown, decide whether it is reasonable to start selling without it. Don't hide a material uncertainty in an unanswered FAQ.
Price presentation needs attention too. In the United States, the Federal Trade Commission's Rule on Unfair or Deceptive Fees guidance explains upfront total-price requirements for live-event tickets, including known mandatory fees. Some charges have specific exclusions and disclosure rules. Check the requirements that apply to your market and offer, then test what the buyer actually sees.
Run a purchase on a phone before launch. Follow the whole experience, from the event link to choosing a ticket, payment, confirmation, and finding the ticket later. Check names, dates, links, and the final amount. Ask someone who didn't build the page to try it. They will notice missing information you've stopped seeing.
When you sell tickets with Loopyah, sales by source help you see which posts and emails sold tickets. Use that reporting when you review promotion. The planning file should hold the decisions and work that follow from the numbers. You don't need to copy individual orders into it.
Give marketing a sales plan
"Post on social media" is a task you can complete without selling a ticket. Your marketing section needs to explain who you want to reach, why they would buy, what message they will see, and when you will check the result.
Start with audiences you have a credible way to reach. For our music event, that might include previous buyers of a similar show, the acts' own audiences, and people following the local scene. Ask each partner what they will actually share and when. A vague promise to support the event is hard to put on a calendar.
Create the materials those people need. That could be an announcement, a short performance clip, the running order, a ticket link, or a clear explanation of what makes this show worth attending. Assign approval deadlines as well as posting dates. A finished graphic waiting for an unapproved lineup can't launch the event.
Set sales checkpoints based on your own plan. In our example, suppose the operator wants 90 paid tickets sold six weeks before the event, 180 four weeks before, 270 two weeks before, and 360 by show day. This is an invented working target, not a claim about how music tickets usually sell. Compare it with past events if you have reliable data.
Now suppose the actual totals at those first three checkpoints are 70, 135, and 210. Sales are behind the plan each time, and the gap is growing. That doesn't automatically tell you the cause. It tells you when to investigate instead of waiting for the final weekend.
| Label | Target paid tickets | Actual paid tickets |
|---|---|---|
| 6 weeks before | 90 | 70 |
| 4 weeks before | 180 | 135 |
| 2 weeks before | 270 | 210 |
Check whether the right audience is seeing the event, whether the offer is convincing, and whether the purchase works. Review sales by channel alongside spend. Ask the acts and partners what has gone live. Look for repeated buyer questions. A missing start time can be a sales problem, even if your advertising is reaching people.
Then choose an action you can afford and measure. Improve the event page, change weak creative, ask a relevant partner for a specific post, or send a useful message to an eligible audience. Set a date to review what changed. Increasing spend without checking the offer and purchase can make a weak plan more expensive.
If you use Loopyah's attendee email tools, you can send event updates and campaigns and see ticket sales in the reporting. Keep the approval, message purpose, audience choice, and timing in your plan. The tool handles sending; you still decide what buyers need to hear.
Plan buyer communication as part of delivery
The ticket purchase is the start of an experience you now have to deliver. Write down which messages a buyer needs before the event. A small show may need a clear confirmation and one useful arrival email. A multi-day event with different ticket rights may need more detail and more careful audience selection.
Include the correct entrance, doors time, transport information, what to bring, and who to contact with a problem. Explain differences between ticket types where they affect arrival or access. If you change a material detail, create a task to notify the affected buyers rather than quietly editing the page.
Keep operational messages and marketing permissions clear. The UK's Information Commissioner's Office explains the rules for direct marketing by electronic mail, including consent and the conditions for relevant exceptions. Buying a ticket isn't a universal permission to send any promotional message. Check the rules applying to your audience and use their preferences.
Don't ask for personal information without knowing why you need it. A ticket purchase form can become difficult when you add questions simply because other events ask them. If you need accessibility or dietary information, decide who will review it, how the team will act on it, and how it will be handled appropriately.
Give support questions an owner and a response process. "Contact us" needs to lead somewhere monitored. Before the final week, review common questions and update the information everyone uses. That saves staff from giving different answers to the same buyer.
Make supplier and partner promises deliverable
For each supplier, record the agreed service, arrival time, onsite contact, payment terms, and anything your team must provide. Attach the current quote or agreement to your own working records. If the production supplier needs a stage plan before confirming equipment, make that dependency visible in the checklist.
Ask suppliers to explain exclusions while you can still change the plan. Does the package include setup labour? Who provides power? How long can equipment stay onsite? What happens if the programme overruns? These answers affect your budget and running order.
You also need a route for approving changes. A crew member should know whether they can request another microphone or an extra hour of labour, and who approves the cost. Ask suppliers to confirm agreed additions in writing. Small requests can become a large invoice when nobody has kept track.
If sponsorship is part of your event, separate the sales opportunity from the money you can rely on. Record the agreement, payment date, and exact deliverables. A promising conversation doesn't pay the venue deposit. Base a cautious budget on the revenue that is actually secured, and show unconfirmed sponsorship separately.
Then assign the work needed to deliver the package. A logo on a screen needs the correct asset and a production deadline. A physical activation needs a location, access time, and agreed responsibilities. Guest allocations need to be included in capacity. Our event sponsorship proposal guide helps you define the offer before those promises become onsite work.
Put safety and contingency tasks in early
You need competent people to assess the risks of your actual event. A general template cannot establish a safe capacity, choose appropriate security staffing, approve a structure, or replace a venue's emergency procedures. Use the checklist to make sure the right assessment, agreement, and briefing happen.
The UK's Health and Safety Executive says emergency plans should reflect the event's risks. Its guidance covers responsibilities, public communication, evacuation, show-stop procedures, and testing. That is a useful planning reference, while your local obligations and event arrangements still need confirmation.
Start by asking what could prevent you from delivering the event safely or as sold. Consider severe weather where relevant, an unavailable act, an equipment failure, a blocked entrance, or a missing key team member. Agree the response with the people responsible. Don't invent a weather threshold from a blog article or ask an unqualified team member to make a technical safety decision.
Put the decision-maker and communication steps in writing. Who can pause admission? Who can stop the performance? Who talks to the venue, artist, and audience? What information do staff need immediately? A backup plan becomes usable when the people involved understand what they are expected to do.
Include the build and breakdown periods. The event team can spend so much attention on audience hours that setup work receives little oversight. HSE's event management guidance specifically addresses coordination and safety throughout those phases. Keep supplier access and work sequencing in the plan.
Finally, test the communication arrangements and walk through plausible scenarios with the relevant team. Record anything that needs fixing and give it a deadline. A rehearsal that reveals a problem has done its job. A rehearsal nobody follows up hasn't.
Work backwards from the doors opening
There isn't one correct planning window for every event size. A repeat workshop in a familiar venue may be quick to prepare. A similar attendance count with temporary structures, several permissions, and complex production may need far longer. Start with the hardest booking, approval, or supplier lead time, then work backwards.
For our fictional show, an eight-week working schedule might be appropriate if the venue and artists are available and the required arrangements can be completed in time. That's an assumption for the example. If an approval takes longer, the schedule must change before the date is promised to buyers.
Before announcing the event
Confirm the event offer, audience, budget, approved capacity, venue arrangements, and key programme commitments. Decide who can approve costs and changes. Make sure you can explain what is confirmed and what is still uncertain. Prepare the ticket page only once the essential information fits together.
Test the purchase, check the event details, and agree the launch materials with the people promoting it. Confirm how buyers will receive updates. The launch date belongs after this work, rather than acting as a reason to skip it.
While tickets are selling
Review paid sales against your working targets and retained revenue assumptions. Check upcoming payments and outstanding supplier decisions. Deliver the planned marketing and partner actions, then use the results to choose the next ones.
Keep operational planning moving too. Confirm staffing, supplier needs, access arrangements, and buyer information. Don't let a good launch become a reason to delay all the work that happens after the ticket is sold.
Two weeks before the event
Bring the current layout, programme, supplier arrangements, staffing, and audience communication together. Resolve questions while you still have options. Check the latest budget and identify which costs could still change.
Agree the final running order and the information each team needs. If a supplier's arrival conflicts with another supplier's setup, fix the sequence. If a new sponsor request changes the layout, get the relevant approval before adding it to the plan.
In the final week
Reconfirm the important details directly with the responsible people. Check names, phone numbers, access times, equipment, approved layout, and any outstanding payments. Send the buyer information at a useful time and make sure someone will answer replies.
Rehearse check-in and the procedures for common ticket problems. Confirm the contingency arrangements with the venue and relevant team. Avoid making a late change simply because you have a new idea. Ask what it adds, what it costs, and which existing arrangements it affects.
Make the final briefing useful to the team
Your team doesn't need to read the entire planning file while a queue forms outside. Give each person the information they need for their role, including who makes decisions and where to get help. Keep the current running order and contacts easy to find.
For front-of-house staff, cover arrival, ticket checks, accessible routes, guest allocations, support questions, and escalation. Agree how to handle a ticket that can't be found, someone at the wrong entrance, or a buyer who needs assistance. Don't leave junior staff guessing at refund promises or exceptions they have no authority to approve.
For the production team, confirm the programme, cues, artist contacts, access arrangements, and who can approve changes. Check that everyone has the same revision. A running order sent to the artist last week may differ from the one the venue prints today.
For managers, cover the current sales and capacity position, known issues, supplier commitments, emergency arrangements, and the process for approving extra spend. Make the briefing short enough to use, but specific enough that people don't need to reconstruct the plan.
Give staff time to ask questions. "Does everyone understand?" tends to produce nods. Ask someone to explain what they would do if a buyer's ticket fails to scan or an act is delayed. You will learn much more about whether the instructions work.
Use the checklist on show day
Assign someone to verify readiness before doors open. They should check the actual venue against the agreed arrangements, not just tick the tasks marked complete yesterday. A clear route can become blocked during setup. A working device can lose power. Check the conditions you're about to admit people into.
Keep the problem-solving process simple. Staff raise an issue to the agreed lead, the lead decides or escalates it, and the relevant team hears the decision. Record material changes, extra costs, and incidents in the appropriate records. You will need that information after the event.
Protect the programme while responding to problems. A delayed performer may require a revised running order and audience message. An equipment fault may need an approved technical response. The planning file helps you find the agreed people and arrangements; it doesn't give everyone permission to improvise beyond their role.
Use ticket and admission information to manage the event, while respecting the approved capacity and venue procedures. A target to sell more tickets never overrides safe operation. If door sales are permitted in your plan, confirm the available inventory and the person responsible for approving those sales.
Keep breakdown in view. Staff and suppliers need agreed exit times, collection instructions, and responsibility for clearing areas. The event hasn't finished financially or operationally when the final act leaves the stage.
Close the event before you reuse the plan
After the show, reconcile the event's money. Compare ticket sales, deductions, refunds, sponsor receipts, supplier invoices, and additional spending with the budget. Record which costs belong to this event and which are business overhead. A gross ticket revenue total isn't an event profit figure.
For our example, a final result of 330 retained paid tickets would produce $900 of event operating profit under the stated assumptions. That's 330 multiplied by $30, less $9,000. If the actual average retained revenue or final costs differ, calculate the result using those figures. Don't keep the original forecast because it looks cleaner.
Review what caused the differences. Did the paid ticket mix change? Did a supplier charge overtime? Did a partner deliver fewer sales than expected? Were guest allocations used as planned? These answers tell you what to change for the next event.
Debrief the team while they remember the details. Ask what delayed work, what buyers struggled with, and which decisions arrived too late. Keep useful changes specific. "Send the approved entrance map with the arrival email" is easier to apply than "improve communication".
Make a clean copy for the next event, reset completion marks, and replace the dates. Keep the previous event's final records separately. Reusing a template should save thinking you've already done while preserving the need to check new contracts, people, prices, and venue conditions.
Common questions about the template
Can I use this for a small paid event?
Yes. Remove work that doesn't apply, keep the financial decisions visible, and retain the safety and delivery arrangements your event requires. Small doesn't mean casual. A limited-capacity workshop can still lose money if the venue cost and ticket price don't fit together.
Is it an Excel budget template?
No. The download is a task checklist with sample dates and a completion column. Use a separate working budget for costs, retained ticket revenue, cash availability, and scenarios. The budget tells you what is affordable; the checklist makes sure someone completes the work those decisions require.
Should every task have the event date as its deadline?
No. Give the task a deadline that allows the next step to happen. A venue layout needed before ticketing launch must be approved before launch. A buyer email needs time for checking and corrections. Work backwards through those dependencies instead of filling every date cell with show day.
How often should I review the plan?
Review it when decisions or circumstances change, and set a regular team review that suits the event. While tickets are selling, check commercial results and approaching commitments together. In the final week, the review needs to be frequent enough to catch changes before they affect suppliers or buyers. A fixed meeting rhythm is useful only if the information stays current between meetings.
What should I do first after downloading?
Reset the example completion marks, replace the dates, and write the event you intend to sell. Then check whether its budget and paid ticket capacity can deliver the result you want. If those numbers don't work, change the plan before you spend more money completing it.
Author: By the Loopyah Content Team
The Loopyah Content Team shares expert insights, practical guides, and industry updates to help event organizers create unforgettable experiences and stay ahead in the event planning world.









