Event planning timeline: twelve weeks to event day

An event planning timeline for a small event runs twelve weeks and has six stops. At twelve weeks, fix the date, book the venue and find out every permit’s lead time. At eight weeks, send invitations or open registration with a reply deadline. At four weeks, close replies, send final numbers and lodge the short lead time permits. In the last week, write the run sheet and send final details. On the day, run the plan. The day after, ask for feedback while people still remember.

Twelve weeks is a working number, not a universal one. Eventbrite’s event planning checklist says to start its first planning tasks four to six months out at the very minimum, and that range is right for a conference or a public ticketed event. A wedding, a workshop day, a product launch party or a club dinner in a venue that already hosts functions can be done well in twelve weeks, provided the slow tasks are at the front.

The example used below is Nina and Tomas’s wedding RSVP form: Saturday 12 September 2026, from four in the afternoon at a fictional Old Boathouse, with replies requested by 15 August. Count back from the date and the whole timeline falls out of it.

Twelve weeks out: date, venue and the slow approvals

Write a one page brief first. It holds the goal of the event, the date, a headcount range, the budget and who makes the final call. Every later decision is checked against it.

Then book the venue, and read the hire terms before paying anything. The venue hire agreement example is worth reading at this stage because it names the two things hire disputes are almost always about: time and noise. It prices bump in, the event and bump out as three separate periods and ties the music curfew to the planning permit. If your venue’s terms do not say when access starts, when music stops and what happens to the bond, ask before you sign. How a deposit and its refund are usually worded is explained on the deposit clause page.

Now list the approvals, because some of them take longer than twelve weeks. The City of Sydney publishes its lead times for events in public spaces: an event application up to 6 weeks before a minor event and up to 26 weeks before a major one, planning consent at least 14 weeks before, a road closure at least 12 weeks before, and a temporary liquor licence at least 4 weeks before. Other councils publish different numbers. If any item on your list is longer than the time you have, the date moves or the item goes.

Eight weeks out: invitations and the reply form

Book the suppliers with long lead times around week ten, then send invitations at eight weeks with a firm reply date. The Nina and Tomas form asks for replies by 15 August, four weeks before the wedding, which gives two weeks to chase and two weeks to finalise.

The reply form is where most day of problems are prevented. The RSVP asks eight questions, one per screen, and only two are required: who is replying and whether they can come. The decline answer, “Sadly I cannot make it”, is worded so nobody feels they owe an explanation, and the party question tells people to skip it if they are not coming. A form that only handles yes gets silence instead of a no, and silence is what wrecks a catering count.

Ask for the day of needs now, on the form, not in a follow up email nobody answers:

• meal choice as a tap between options, plus “I will have whatever is going”
• allergies and dietary needs as an open box, so the kitchen gets the guest’s own words
• a mobile number, labelled as only for last minute details on the day
• access needs, which W3C’s guidance on accessible events suggests asking on registration forms so arrangements are made before anyone arrives

For a larger event with tickets, sessions and several sections, a classic registration form suits better than a one question per screen reply. The conference registration form example splits eleven fields into three sections: who is coming, the ticket, and access and catering. Which fields belong on a registration form for each type of event is covered in event registration form fields.

Four weeks out: close replies and lock the numbers

Close replies on the date you printed. Export the responses, count the yes answers and the meals, and send the caterer a final number in writing. Chase the people who have not replied once, by the channel they use, and then count them as not coming.

This is also the week for the permits with short lead times. On the City of Sydney’s list, a temporary liquor licence, an event management plan for a minor event and a temporary food vending permit all need at least four weeks. The council’s separate page on events with food and drink says the temporary food stall register must be completed at least 28 days before the event.

Send suppliers the confirmed numbers, the access time and the bump out time from the venue agreement. Ask each one to confirm in writing.

One week out: the run sheet

Write the run sheet: every task in time order with a name and a phone number against it. Start with the bump in, supplier arrivals and doors open. Include speeches, food service, the last song and the time the venue must be empty.

Eventbrite’s checklist suggests different versions of the schedule for different people, so security sees when guests arrive and crew sees set up and clean up times. For a small event, that can be a single page with the columns highlighted per person.

Send guests the final details: time, address, parking, public transport and anything they need to bring. Keep it short enough to read on a phone.

Event day

Brief the team before doors open. Keep one person free of any fixed task so they can solve problems as they happen, and give them the supplier phone numbers. Check people in against the reply list. Write down anything that goes wrong in a problems log; it is the most useful document you will have when planning the next one.

After the event

Send a feedback survey the next morning. The event feedback form example puts the reason plainly: feedback collected a week later is memory, and feedback collected the next morning is evidence. It is eight screens, starting with an overall rating and a rating of the sessions attended, then the best part, what to change, venue and food, whether they would come next year, and an optional name for a reply.

Within a week, pay suppliers, recover the bond and compare the budget against what was actually spent. Write down three things to change.

The table at the end of this article sets out all fifteen tasks by week with the artifact each one leaves behind. Print it, cross out the rows your event does not need, and put a name next to the rest.

Common mistakes

Booking the venue before checking the permits. A road closure or a planning consent can take longer than the whole plan.

No reply deadline. Without a date, replies drift until the week of the event and the catering count is a guess.

Required questions nobody can answer. Making the meal choice required for guests who are not coming produces fake answers. Keep the required questions to identity and attendance.

Asking about allergies by tick box. The kitchen needs the actual allergy, in the guest’s words.

One run sheet for everyone. Staff skim for their own tasks, so make those easy to find.

Feedback a week later. The details that make the next event better are gone by then.

Build it

The AI form builder page shows how an RSVP or registration form is written from a description: give the event, the date, the reply deadline and the questions, and say which are required. A conversational form, like the RSVP, shows one question per screen with a welcome screen that can state the estimated time, and a thank-you screen for what happens next. A classic form suits a longer registration, and a classic form can be split into steps, which the multi step form builder page covers.

Responses export as a CSV with one column per question and the submission time first, and a single choice answer arrives as its label, so counting yes replies and meals is a spreadsheet filter. The email alerts add-on sends each reply to one address as it arrives, which suits whoever is keeping the caterer updated. The steps inside the builder are in the guide to creating a form with AI. Put the reply date in the welcome screen description, as the Nina and Tomas form does, so nobody opens the link without seeing it. What separates a registration form from an RSVP or a booking form is set out on the registration form question page.