How to set an annual event calendar your team can actually deliver

You've agreed the spring conference, the monthly shows are selling, and someone has found a good venue for a new workshop series. None of the dates clash. Everyone likes the revenue forecast. Then your producer points out that the conference's final preparations, the next show's delivery and the workshop launch all need her in the same week.

This is where an annual event calendar needs to do more than show opening dates. It needs to show when each event needs particular people, when the business must pay for it, and what you've already promised. Your team can deliver the calendar only when those demands fit together across the preparation, selling and closing work as well as the public dates.

Start with the events you're committed to, calculate the time available from each essential role, and add proposed events one at a time. Where work overlaps, change the plan before approving the date. Don't assume the team will absorb the difference because each event looks profitable on its own.

We'll work through a fictional event business called Northbank and build a practical approval process around it. Every hour, price, ticket figure and decision limit in the example is invented to explain the method. Money amounts are in USD. These are planning assumptions, not staffing benchmarks, supplier quotes or Loopyah customer results.

Decide what the calendar is meant to achieve

Before you fill the year, decide what you want the programme to do for the business. Perhaps the established shows need to fund a carefully limited new format. Perhaps you want fewer dates with stronger profit. Those intentions lead to different decisions when the same producer or marketing manager is needed twice.

Write the commercial purpose beside each proposed event. An established date might provide dependable income, while a new workshop tests whether people will pay for a particular subject. That test needs a spending limit and a clear question. Calling an event strategic doesn't tell the team how much time it deserves.

Our guide to strategic event management covers the connection between the business objective and the individual event plan. For the annual calendar, the extra question is whether the collection of events supports the business after shared costs, workload and funding are considered together.

Separate contracted events, dates already on sale, provisional holds and ideas. A blank space beside an idea is useful flexibility. A date with buyers and signed suppliers involves real obligations. Don't present both as equally easy to move when you're trying to resolve an overloaded month.

Also decide who has authority to add a date. Someone may be allowed to explore a venue without being allowed to announce the event or sign its contract. Make that distinction explicit. Otherwise, the annual planning process can be overtaken by commitments made in separate conversations.

Northbank's starting rule is straightforward. Existing paid commitments get assessed first, new dates need a full workload and cash check, and only its owner can approve the resulting commitment. That doesn't make existing events untouchable. It means changing them requires an explicit decision about the people and obligations affected.

Map the work around every event date

Put the full delivery cycle on the calendar. Include offer development, supplier selection, ticket setup, launch, ongoing promotion, final production, the event itself and the work afterwards. Use the actual tasks your team performs. A repeated show and a new conference won't have identical preparation patterns.

For each phase, identify the role needed and when its work has to happen. "Marketing during March" is too vague if the same person must approve two launches on Tuesday. "Producer for the final venue meeting and programme approval during the conference preparation week" exposes a more useful demand.

Start with weeks across the year. Break busy weeks into days and appointments once a conflict appears. Trying to plan every hour of next December now creates detail that will probably change. Leaving next month's simultaneous launches in a single monthly total hides a decision you need to make today.

Work backwards from genuine deadlines. A print supplier's accepted artwork date can fix an earlier approval. An artist announcement may depend on an agreed release time. The event critical path guide explains how to connect tasks within one production plan. Here, check how those linked tasks compete with the other events using the same people.

Include closure. Someone needs to resolve supplier invoices, reconcile ticket records, answer remaining attendee questions and record what happened. If the calendar assumes the entire team is free the morning after an event, ask who is doing those jobs and when. Quietly carrying them into the next launch doesn't remove the work.

Keep effort and elapsed time separate. A contract might take a week to come back while requiring an hour of your attention. A site visit might need half a working day once travel is included. Record the time someone actively needs to spend and any waiting period that controls when the next task can begin.

The Association for Project Management's resource capacity planning guidance recommends assessing requirements across related work, including skills, physical location and competing deadlines. The useful application for your events is to ask who can actually do the work during the week it's needed.

Calculate the hours you can actually assign

The next step is to establish availability by person and role. Start with agreed working time, then account for leave, recurring duties, travel and other commitments. Don't treat every paid hour as time available for event preparation. Customer support and running the business still need someone to do them.

Northbank's producer, Sam, has forty agreed working hours in the example week. Eight are already needed for recurring business administration and existing customer matters. Northbank also keeps four hours unassigned for ordinary variations in that work. That leaves twenty-eight hours for planned work on the three events we're examining.

Those four hours are an explicit planning choice for this example, not a recommended allowance for every business. Northbank must check whether they are sufficient for its real circumstances. Any leave, additional travel or other work would reduce the available event hours further. Overtime isn't included in the calculation.

Don't subtract something twice. If the recurring eight hours include routine ticket enquiries, the event estimates should contain only the additional enquiries expected for those events. If a site visit estimate includes travel, don't add that same journey again under another heading. Agree the boundaries before comparing the totals.

Make availability specific to skills. A spare marketing hour can't automatically replace an hour of production coordination. Someone may have the time but lack the knowledge, authority or relevant experience. Where another person can take the task, include the briefing and review needed to make that transfer work.

The Health and Safety Executive's Management Standards on demands, relevant to Great Britain, call for achievable workloads within agreed hours and a match between people's skills and job demands. Don't turn a capacity discussion into a request for staff to demonstrate enthusiasm by accepting an impossible week.

Ask the people doing the work to check the estimates. An owner may remember the visible delivery day and miss the revisions that preceded it. Staff may have been completing those revisions outside the recorded plan. You need an honest estimate of what the next event requires, including work that was previously hidden.

Add the events by week and find the first shortfall

Northbank has a spring conference in final preparation, a regular evening show and a proposed workshop launch. For the busy week, Sam estimates fourteen hours for the conference, ten for the show and eight for the workshop. The estimates include the event-specific coordination and handoffs required during that week.

Taken individually, every event fits within Sam's twenty-eight planned event hours. Together they require thirty-two. Northbank therefore has four more hours of planned event work than it can assign without using the time it intended to keep unassigned. The annual total of staff hours won't answer that weekly conflict.

Don't solve this by dividing the work evenly across the month. If the conference's final venue decisions are needed this week, unused producer time several weeks later can't meet that deadline. The same is true of unused time belonging to a colleague who can't perform or approve the required work.

Check the surrounding weeks as well. A proposal to move four workshop hours earlier works only if the earlier week has those hours available and the task's inputs are ready. Moving a task that depends on an unconfirmed tutor or unfinished offer can create a plan that looks balanced but cannot start.

Use completed events to challenge the estimates. Ask what was included in the fourteen conference hours, which supplier decisions remain open and whether late changes are plausible. You don't need a precise timesheet for every past email. You do need enough evidence to distinguish a repeatable task from an optimistic guess.

Repeat this exercise for every role that could stop delivery or sales. Marketing might fit while production doesn't. Finance may have room for routine payments but no time for simultaneous settlements. Keep each shortfall visible rather than adding all departmental hours into one total and declaring the business adequately staffed.

A calendar review should end with a named problem. For Northbank, it is "Sam needs four more usable event hours in this particular week." That description is much easier to act on than "spring looks quite busy." It also gives you something concrete to check after changing the plan.

Check launches and decisions as carefully as delivery days

A calendar can have well-spaced public dates and still create a sales problem. Two events may both need their strongest launch during another event's final week. If the marketing lead is answering live attendee questions, the new launch may receive a hurried page, unfinished creative and little follow-up.

For each launch, identify what must be ready before anyone announces it. Include the confirmed offer, ticket terms, accurate page, approved creative, campaign audience and the person available to resolve problems after release. Preparing those things takes time even if the actual announcement can be scheduled in advance.

Check approval capacity too. If every price, sponsor message and programme change waits for the founder, adding coordinators may leave the same decisions waiting. Record the decisions that require that person, the information needed and a realistic review window. Delegate defined decisions where appropriate before treating new hires as additional usable capacity.

You can prepare some launch work ahead of the busy week. With Loopyah's attendee email tools, a teammate can build a campaign, send a test and schedule it for a chosen time and time zone. That lets you prepare an approved launch message before a busy delivery day instead of relying on someone to assemble it between other tasks.

You still need to confirm the offer, check the content and decide whether the planned send remains appropriate. Put those responsibilities into the calendar. If a scheduled email is ready but the event page or artist approval isn't, the launch isn't ready. Scheduling the send doesn't create an approved offer.

Also check whether the events ask the same buyers to spend at the same time. That's a separate question from staff availability. Two launches may be easy for your team to operate and still compete for attention or budget. Investigate the audience effect rather than assuming that spacing the internal work protects sales automatically.

Test the exact days behind a weekly total

Once the weekly hours fit, look at the appointments and locations. A person can have enough hours across the week and still be required at two venues at once. Check access meetings, rehearsals, event supervision, travel and any approvals that require people to meet at the same time.

Sam's ten show hours might include a fixed venue visit and a delivery call. If the conference needs Sam onsite during that same call, four extra hours elsewhere won't solve the conflict. You need a suitable person to cover the required responsibility, a changed appointment or a changed event arrangement.

The HSE's event management guidance, for Great Britain, stresses coordination, competent staff and appropriate management through the different event phases. Apply the relevant requirements where your events operate. An annual staffing calculation doesn't establish that a particular site's supervision or safe working arrangements are adequate.

Include travel realistically. Finishing a meeting at one venue doesn't make someone immediately available at another. Ask how they will get there, what the journey takes under the expected conditions and whether they need preparation time before taking responsibility. A shared online calendar can record a clash without resolving it.

Rest and recovery also affect the sequence. The HSE's guidance on fatigue explains that working hours, shift patterns and insufficient recovery need to be assessed together. Its Great Britain guidance does not support assuming that willingness to work longer makes an arrangement safe. Agree suitable work patterns for the actual people and duties involved.

For your calendar, the practical implication is to inspect the work immediately before and after each demanding delivery period. Don't place a major approval session after an overnight event simply because the appointment slot looks empty. Confirm who will be available and able to do the job properly.

Resolve the conflict with a change you can verify

Northbank has several ways to address its four-hour shortfall. Start with work that can genuinely move. Suppose four workshop preparation hours can happen in the previous week. That week has four spare assignable hours after its other commitments, and the workshop inputs are already confirmed. Moving the task would bring the busy week down to twenty-eight.

That is a complete proposal only when the person doing the earlier work agrees, the dependencies permit it and the output can remain usable until launch. If the preparation will need repeating after a likely change, include the expected repeat work. Bringing a draft forward can help without eliminating the later approval.

A second option is to simplify the workshop. Perhaps the team can offer a useful paid session without the extra demonstration that requires separate coordination. Check what buyers are being promised and whether the simpler version remains worth its price. Reduce the actual work and revise the offer before counting the hours as saved.

A third option is to hire suitable help. Northbank identifies a contractor who can take six conference coordination hours during the busy week. Sam needs two hours to brief the contractor and review the handover. Sam's workload therefore falls by four hours, from thirty-two to twenty-eight. Six purchased hours have produced four hours of usable relief.

For this fictional option, the contractor is qualified for the assigned scope, available at the required times and able to work without Sam attending the same tasks. All extra contractor costs are assumed included in the quote we'll examine next. If those conditions aren't true, the proposed relief needs to be recalculated.

The remaining option is to move or refuse the proposed date. That can be the best answer when suitable help is unavailable or the event's return doesn't justify the extra cost. Before moving it, recheck the venue, tutor, selling period and audience. A staffing solution that makes the event unattractive to buyers isn't a finished plan.

Don't combine the benefits of mutually exclusive solutions. If you assess hiring help, use the workload and costs of that option. If you move the launch instead, build its revised timeline. You can combine changes deliberately, but the final calendar must show the actual combination being approved.

Recalculate the event's contribution after buying capacity

Extra help changes the financial case. Northbank's proposed workshop is forecast to contribute $1,800 after all its existing direct event costs, before the business's continuing overhead. Those existing costs already include venue, tutor, materials, ticket-related charges and the other work needed for the proposed scope. The forecast excludes the new contractor.

Although the contractor works on the conference, adding the workshop is what makes that cover necessary. Northbank therefore includes the extra cover when assessing whether to add the workshop. The contractor's complete additional quote is $600, including relevant taxes and charges. With the contractor, the workshop's contribution falls to $1,200. Northbank's continuing salaries and other overhead are assumed unchanged by this particular decision. The two internal briefing hours use Sam's existing paid time and are counted in the capacity calculation without creating an additional wage payment here.

That $1,200 isn't a guarantee of profit, and it isn't the workshop's final operating result after overhead. It's the amount forecast to help cover continuing business costs and profit once the extra help is paid. Northbank still needs a credible sales forecast and enough contribution across the calendar to sustain the business.

Suppose the workshop keeps $50 per paid ticket after organizer-borne selling charges and indirect taxes, and incurs $10 in attendance-related costs per paid buyer. Each additional retained paid ticket then contributes $40 before the fixed event costs. Recovering the extra $600 would require fifteen additional tickets under those unchanged assumptions.

That calculation doesn't mean the team should simply increase its sales forecast by fifteen. Buyers need a reason to buy, capacity must permit the sales, and extra attendance must not trigger additional fixed costs. You might accept the lower contribution instead. The arithmetic describes the commercial consequence of the staffing decision, not a sales plan.

Test a weaker result. If the workshop sells twenty fewer retained paid tickets than its original forecast, contribution falls by another $800. After the contractor, the forecast contribution would be $400. All other costs and the average retained ticket amount are held unchanged for this illustrative comparison.

Use the event portfolio comparison guide when two proposals compete for the same team and money. For an annual programme, keep applying that comparison as dates are added. An attractive extra event can be a poor addition if the cover required to deliver it removes most of its return.

Check payment timing across the whole business

Now add the payment calendar. Deposits, supplier balances, advertising, payroll and tax obligations can coincide even when the events happen in different months. Use the dates money is expected to reach or leave the business, with the relevant conditions. Ticket revenue recorded today isn't necessarily money available to pay tomorrow's invoice.

The Australian Government's cash flow statement guidance explains how to forecast receipts and payments, label estimates and calculate the closing balance for each period. Apply that timing discipline across the programme. Check the local tax and accounting treatment with the person responsible for your finances.

Here's a separate simplified Northbank funding example. The business begins a period with $15,000 of unrestricted available cash. Before any further receipts arrive, it must pay $7,000 for conference commitments, $4,000 for show commitments and $3,000 for the workshop. Those payments total $14,000 and would leave $1,000. They are the amounts due during this interval, not the full costs of delivering those events.

Paying the additional $600 contractor invoice during the same interval leaves $400. For this illustration, all other obligations during the interval have already been covered separately. No money is restricted for refunds or another purpose, and no extra payroll, tax or supplier bill is omitted from the stated availability. Your actual forecast must include every obligation.

Northbank's owner has chosen to retain at least $2,000 of available cash through this period. That's an internal decision for this example, not a universal reserve recommendation. The revised plan misses it by $1,600. A later receipt doesn't fix an earlier shortfall unless its timing or suitable funding changes before payment is due.

The plan needs a real change. Northbank could negotiate an accepted payment date, obtain confirmed funding on terms it can support, or delay the uncommitted workshop. Record which change has actually been agreed. Don't issue a calendar that depends on a supplier accepting later payment when nobody has asked them.

Our event cash flow forecasting guide covers the detailed weekly calculation. Keep the combined forecast as well as the individual event views. The same cash balance cannot be counted in full as available funding for several overlapping commitments.

Leave room for the work you can't date precisely

Annual planning involves uncertainty. You may know a conference needs supplier revisions without knowing exactly which week they'll arrive. Put that uncertainty into the estimate and review it as decisions become clearer. A single confident number can make an unconfirmed event appear easier to deliver than a well-understood repeat event.

Use a likely workload and a more demanding plausible case for uncertain phases. Explain what would cause the difference. An additional sponsor approval round, a new venue layout or an unfamiliar tutor needs a reasoned allowance. Don't add a generic percentage to every task and assume the uncertainty has been handled.

Keep a separate note of unresolved timing. If a supplier could deliver its information in either of two weeks, show where the work might fall and whether both possibilities fit. You aren't booking the same work twice. You're checking whether the calendar remains usable when the timing becomes definite.

Protected unassigned time needs an owner. If Northbank's four hours are intended for ordinary variations, somebody should decide when using them changes the plan enough to require another review. Otherwise every event owner can quietly assume those same hours will cover their own late changes.

Reserve capacity also needs to exist in the right role. Unassigned marketing time won't cover a missing production lead. Where a qualified backup is part of your plan, confirm availability, scope and how quickly they could take over. An uncontacted name on an old supplier list isn't confirmed cover.

Check shared suppliers and equipment across the series

Your own team may fit while a shared supplier doesn't. Ask whether the same production company, equipment package or venue contact is expected to support overlapping work. A supplier accepting several dates doesn't establish that the same named crew or equipment will be available for all of them.

Confirm what has actually been reserved. A quote might describe a service without naming the delivery team. That can be perfectly workable, but you need to know how substitutions will be handled and what information a replacement receives. Don't build your internal plan around one familiar technician unless that availability is agreed.

Allow for equipment turnaround between events. Transport, inspection, cleaning and any required preparation take time and may need particular people. An item being unused during the next public event doesn't establish that it can reach the next venue and be ready when setup begins. Check the actual sequence with the supplier responsible.

Shared buying can reduce cost, but record the obligations it creates. A series agreement may require a minimum number of dates or early payments. If you later remove one workshop, check the effect on the remaining prices and commitments. Don't retain the original series discount in the forecast after removing the condition that made it available.

Also consider a disruption affecting several events together. If all dates depend on one supplier, their loss could leave several calendars requiring replacement work at once. Identify a credible alternative for the responsibilities that matter most. You may decide that the shared arrangement is worthwhile, but the decision should include how you'd respond if it became unavailable.

Use a short proposal record before adding a date

You don't need a new planning system to start. A shared sheet can hold the annual view while event plans contain the detail. What matters is that every proposal answers the same questions and changes are reflected in the current calendar. The record below is a starting template, not a requirement to collect more paperwork.

• Event and purpose. Name the paid offer, intended audience, proposed date and commercial reason for running it.

• Commitment status. State whether it is an idea, a held date, contracted or already on sale, with any relevant decision deadlines.

• Work by phase. List the preparation, launch, delivery and closing periods, the roles required and estimated hours in each busy week.

• Fixed appointments. Record onsite requirements, travel, approval meetings and responsibilities that can't overlap with another event.

• Financial case. Attach the sales assumptions, direct event costs, contribution before continuing overhead and additional costs caused by the combined calendar.

• Funding. Show dated receipts and payments, the lowest available cash balance and the approved minimum or funding conditions.

• Remaining conditions. Name unconfirmed suppliers, missing approvals or uncertain work, the person resolving each and the decision deadline.

• Approval. Record who can commit the business, what has been approved and which changes require a fresh decision.

Treat the template as a conversation with the people delivering the event. If an owner can't estimate the preparation yet, agree a limited feasibility task and a return date. Don't enter zero hours merely because the work is unknown. That rewards the least developed proposals with the most attractive forecasts.

One person should maintain the combined view. Event owners supply updates, but someone needs to check whether the changes still fit together. Otherwise each event can have an accurate individual plan while the annual calendar continues to promise the same producer to several teams.

Keep links to the underlying evidence. A current contractor quote, venue hold and agreed availability should be easy to inspect. The calendar shouldn't depend on someone remembering that a conversation was more tentative than the green cell suggests. Use plain statuses that say what is confirmed and what still needs action.

Review the near term more closely than the distant year

Set a review rhythm that reflects how quickly your commitments change. For Northbank, an annual planning session establishes the proposed programme, a monthly review checks the next part of the year, and a short weekly check covers the approaching busy period. These are example choices, not a prescribed cadence for every team.

At each review, compare the current plan with what was approved. Ask whether event dates, supplier information, launch work or staff availability have changed. Focus the discussion on conflicts and decisions. Reading every unchanged task aloud can consume the time needed to resolve the one week that no longer fits.

Look far enough ahead to act. If hiring suitable cover takes time, a review after the overloaded week begins is too late. Likewise, if a venue option expires before the monthly meeting, bring the decision forward. The useful review date comes before the last affordable or practical opportunity to change course.

Update remaining work, not just work completed. Spending six hours on a task doesn't establish that an eight-hour estimate has two hours left. Ask what is still needed to finish it. Supplier revisions or an unresolved approval may have increased the remaining demand despite substantial effort already spent.

Make each changed plan specific. "Marketing is behind" should become an identified launch requirement, a current completion forecast and a decision about support or timing. Record the effect on other events before moving their people. Borrowing someone for a day creates a new question about the work they were going to do.

Agree what the team can stop or defer

A full calendar needs a way to remove work as well as add it. Ask event owners which activities could be reduced without breaking the paid promise, contractual commitments or required delivery arrangements. Essential delivery work and existing commitments still need to be met.

Perhaps a proposed workshop can launch with a single clear demonstration instead of several formats. Perhaps a speculative event can wait until the established series has settled. Explain the consequence of each change. "Simpler" needs to mean fewer actual tasks, with a viable offer and revised costs, rather than unchanged work under a smaller budget.

This matters particularly when the founder is the shared resource. Write down which decisions another person may make, what limits apply and when they must escalate. Delegation works when the recipient has the information and authority to act. Forwarding every decision through a new coordinator can increase the founder's workload.

Give staff a clear way to report that the current plan won't fit. A person shouldn't have to prove that an event will fail before asking for a priority decision. If two owners both say their work must come first, the person approving the programme needs to resolve the conflict and accept the consequence.

Also preserve the ability to refuse an uncommitted date. The question is whether adding it makes the whole business better under a plan you can support. An attractive venue opening doesn't oblige you to launch another event. Sometimes the commercially responsible decision is to protect the events buyers have already paid for.

Record the conditions that would make Northbank's workshop possible

Return to the worked example. The contractor option gets Sam's planned event workload down to twenty-eight hours while preserving the separate four unassigned hours. It reduces the workshop's forecast contribution to $1,200. However, the stated payment sequence leaves only $400 available against Northbank's chosen $2,000 minimum.

Northbank should therefore keep the workshop uncommitted under that current plan. The workload problem has a possible solution, but the cash condition is unresolved. The owner can approve further investigation without authorizing a venue contract, public announcement or ticket launch. Say exactly which actions are permitted during that investigation.

For this example, the owner records the following decision. "Retain the workshop as a proposal. Sam will confirm the contractor's scope and required appointments. Finance will resolve the $1,600 gap against our chosen cash minimum using agreed payment timing or confirmed funding. The event owner will verify the sales case supporting the $1,200 contribution. Return for approval before any commitment deadline."

That is conditional work, with named responsibilities. It isn't permission to proceed because someone expects the conditions to be met. If funding carries interest or other costs, include them in the revised financial case. If the contractor needs additional supervision, revise Sam's hours before recommending approval.

There is also a different route to assess. Moving the four preparation hours into the earlier week could remove the need for contractor cover. It would restore the original $1,800 forecast contribution and leave $1,000 after the stated event payments. That still falls $1,000 short of Northbank's chosen cash minimum, so changing the work alone doesn't settle the decision.

Compare the complete alternatives before choosing one. Moving the workshop date may change deposits, preparation and sales. Refusing it preserves capacity and avoids its future commitments but also removes the forecast contribution. Record the selected arrangement and its conditions rather than approving a mixture of the most favourable assumptions from each option.

Use completed events to improve next year's estimates

After delivery, compare actual workload with the estimates used to approve the calendar. Ask where the additional time went, which roles were repeatedly needed and what the team had to defer. Separate genuine changes in scope from work that the original plan simply missed.

Keep enough detail to improve the next comparable event. "Conference took longer" doesn't tell you much. "Final sponsor revisions required a second approval session during show week" gives you a task to allow for or a process to change. Record the circumstances so the estimate doesn't become a rule for every conference regardless of scope.

Review the commercial result too. If the programme needed repeated last-minute contractors, include those costs when deciding whether the same number of dates makes sense again. Don't keep approving new events using a standalone budget that excludes the support your combined calendar routinely requires.

Include closure work in that review. If supplier settlements and attendee queries continued into the next launch, allow for them next time. If a reusable process reduced preparation, update the estimate using what actually happened. Improvements should change the plan through observed results, not an unsupported assumption that next year will be easier.

Before you confirm the next date, open the busiest week it creates and ask the named people to explain how it will work. Check the exact appointments, the money available before the bills fall due and the promises already made to buyers. Approve the date when those answers describe a feasible plan the team has agreed to deliver.