Twelve Months, Counted Backwards

Every first-time organiser starts in the same place: excitement, a rough date and a community that says "yes, we'd come." That enthusiasm is real and it matters, but it is not a plan. A plan is a sequence, and the honest sequence for a festival of a few hundred to a couple of thousand people is about a year long.

That might sound excessive for a weekend. It is not. Venues book a year ahead. Insurance underwriters want details you will not have until month six. Publishers take weeks to answer tournament licence requests. Creators fill their calendars a season in advance. The twelve months are not twelve months of work; they are twelve months of waiting for other people, with work happening in the gaps.

Start with the money, not the poster

Before any date is announced, build a budget with three columns: the event you want, the event you can afford if ticket sales are mediocre, and the event you can run if a sponsor pulls out. Your venue, power, network, security and insurance live in all three columns. Your headline creator, your giant LED wall and your merch run probably only live in the first.

Break-even should come from ticket revenue at roughly sixty percent capacity. Sponsorship is a bonus, not a foundation. Many community events have been sunk by a hardware brand that promised a four-figure package in spring and quietly disappeared in summer.

The month-by-month runway

1. Month 12

   Budget, team and date

   Write the three-column budget. Recruit a core team of four to six people with clear owners for venue, tech, programme, safety and finance. Pick two candidate weekends, checking them against major releases and big events like Gamescom in late August.

2. Month 11

   Venue scouting

   Visit at least three venues. Ask for power schematics, capacity certificates and their internet provider's contract details. Walk the load-in route with a tape measure.

3. Month 10

   Contract and deposit

   Sign with the venue, with a cancellation schedule you can survive. Open a dedicated business bank account. Register your entity if you have not.

4. Month 9

   Insurance and licences

   Get public liability quotes. Send tournament licence requests to publishers. Contact your local authority about any event notification they require.

5. Month 8

   Announce and open early tickets

   Publish the date, venue and code of conduct together. Early tickets test demand cheaply and fund deposits.

6. Month 7

   Suppliers

   Book power distribution, AV, staging, network hardware and security. Get every quote in writing with load-in times attached.

7. Month 6

   Programme shape

   Fix your tournament formats, stage schedule skeleton and creator invitations. Recruit a volunteer lead.

8. Month 5

   Safety plan draft

   Write the event safety plan, crowd management notes and accessibility statement. Share with the venue's safety officer.

9. Month 4

   Volunteer recruitment

   Open applications, define roles, set training dates. Confirm creators and sponsors with signed agreements.

10. Month 3

    Floor plan locked

    Freeze the floor plan, run the network design, publish the schedule. Order badges, wristbands and signage.

11. Month 2

    Rehearse on paper

    Table-top walk-throughs: fire alarm at 15:00 Saturday, a power trip in the BYOC hall, a creator who does not show. Write the answers down.

12. Month 1

    Final checks

    Run-of-show document, radio channels, contact sheets, volunteer briefings, a network soak test at the venue if possible.

13. Show week

    Build, open, run, strike

    Load-in, tech checks, doors, the weekend itself, teardown, and a debrief within seven days while memories are honest.

A delayed decision is still a decision. It just gets made by your venue's booking calendar instead of by you.

The mistakes that sink first events

Announcing before contracting. Posting a date to your Discord before the venue contract is signed invites a painful reschedule. Communities forgive many things; they remember broken dates.

No contingency line. Keep ten to fifteen percent of the budget unallocated. Something always costs more: a second generator, an extra security guard required by the venue, overnight storage.

One person holding every password. Shared vaults for ticketing, social accounts and supplier portals are not bureaucracy, they are survival when your lead organiser gets sick on Friday.

Skipping the debrief. The week after the event is when people want to sleep. Schedule the debrief anyway. Every note you capture now saves a month next year.

Once the runway is in place, the next question is physical: where will all of this happen, and will the building cope? That is chapter two.