0.3 · Install the operating system

BeginnerDuration ~7 min readTools Google Sheets or similar, Luma account, Calendar

The big idea: your event needs one document, one event page, and one recurring hour. From today, everything that matters about the event lives in those three places instead of in your head.

The analogy

Every set has a binder. The 1st AD carries it, and it holds the call sheet, the shooting schedule, the contact list, the location details, and the day’s revisions. Nothing in it is clever. What makes it powerful is that it’s the same binder every day, in the same place, updated before call time, so when a producer asks a question the answer comes from the binder instead of from somebody’s memory of a conversation last Tuesday.

The crew trusts it because it’s always current. That’s the actual mechanism, and it’s worth sitting with. A document nobody updates is worse than no document at all, because people stop checking it and start asking you again.

Your event needs the same binder. Today you build it, empty.

How it works

Right now the August event lives in a lot of places. A venue quote in your email. A sponsor name in a voice note. A budget number you’re carrying around in your head because you’ve run the math enough times to trust it. None of that is wrong, exactly. It just isn’t shareable. The moment somebody offers to help, you find out you have nothing to hand them, because the only complete version of the event is you.

A master timeline, one spreadsheet, fixes that in the least glamorous way possible. Everything about the event that has a date, a cost, a name, or a status goes into it, and nothing important lives anywhere else. That rule is the whole idea. Spreadsheets aren’t exciting, but they’re what this industry actually runs on, from run of show to budget, and the reason is simple. A sheet is the cheapest thing two people can look at and agree about.

Four tabs, and each one gets filled by a specific lesson later, so you’re not writing content today. You’re building the container.

Runway is the event calendar working backwards from the date. You’ll build it in Lesson 1.3, where you’ll also mark the critical path, the chain of tasks where any slip pushes the whole event back. Later, in 2.1, your promotion dates land on this same tab, because a launch post is a milestone like any other.

Budget is income against expenses in three versions, Good, Better and Best, plus the dates where you decide whether to commit. Lesson 1.4 fills it.

Sponsor pipeline is one row per brand, moving through stages: prospect, contacted, call, proposal, closed, fulfilled. You write the prospectus in 1.5 and work the pipeline in 2.4. A sheet is genuinely the right tool here. Dedicated sponsor software starts making sense several sizes up from where you are.

Volunteers is every station, every shift, and the name attached to each one. Lesson 2.7 fills it and turns that count into your recruiting number.

Then the block in your calendar. DevOpsDays, the volunteer-run conference series this course keeps borrowing from, kicks off semi-monthly organizer meetings around seven and a half months out, and the reason they give is visibility. Somebody has to look at how tickets, sponsors and submissions are actually going, on a schedule, rather than whenever panic arrives. Your runway isn’t seven months. It’s closer to ten to sixteen weeks, so the same principle compresses. Weekly.

One hour, same day, same time, repeating. You open the sheet, update every tab, and decide what happens this week. If you have a team, that block is the meeting. If you’re solo right now, it’s still a meeting, just with one attendee, and it protects you from the thing that quietly kills solo-led events. Everything feels fine, and fine, and fine, and then there are two weeks left.

Last piece. Luma is your registration tool of record, and the event shell should exist long before the public ever sees it. Create it under a Filmmakers Connect calendar rather than your personal account, so the page reads “Presented By” the community. Set the title, the date, a placeholder description. Then leave it alone. Nobody sees it until you share the link.

Creating it early sounds pointless and isn’t. The link becomes a real thing you can paste into the sheet, into a sponsor email, into a message to a guest who wants to check the date. Adding your cohosts now means they get access and a calendar invite without a scramble later. And Luma starts tracking the funnel from page views to registrations to who actually showed up, which is exactly the data that makes your no-show math real in 2.2. A page that doesn’t exist collects nothing.

The binder, the four tabs, the hour, the link. That’s the operating system. Level 1 starts filling it.

The pattern

One sheet, one page, one hour. The sheet holds every date, number, name and status. The Luma page holds registration. The weekly hour is when you open both and decide the week. Anything that lives only in your head can’t be delegated, and anything that can’t be delegated stays yours forever.

The receipts (evidence, if you want it)

• DevOpsDays confirms its organizer team at 9 months out specifically to “start distributing the work,” and kicks off semi-monthly meetings at 7.5 months out because “it is good to establish a healthy cadence with check-in points and being able to get visibility on how ticket, sponsorship and submissions are going” (devopsdays.org/organizing).
• The same guide’s “Distributing the work” section assigns named owners for talk proposals, speakers, sponsorships, registration and invoicing, venue and local logistics, merchandise, and evening events. It also warns that you’ll accumulate vendor logins and social accounts that need storing “securely, centrally, and sanely” (devopsdays.org/organizing).
• Spreadsheets remain the industry default for the run of show (Stagetimer, what is a run of show), and DevOpsDays structures its budget the same way: income against expense categories in Good, Better and Best tiers (devopsdays.org/organizing).
• Sponsor pipelines run on spreadsheets at community scale. Dedicated sponsor-management platforms appear at property and agency scale (SponsorCX).
• Critical Path Method: identify the longest chain of dependent tasks, which sets the minimum project duration, and know that slippage on that chain slips the whole project (Asana, critical path method; applied to events at Meegle). You’ll meet it properly in Lesson 1.3.
• Runway compression: large conferences typically need 6 to 12 months, mid-size events 3 to 6 (Lyyti, event planning timeline). The course’s 10 to 16 week figure is the compressed shape of the DevOpsDays skeleton for a 100 to 150 person community event, derived in the industry map and built properly in 1.3.
• Luma hosts and managers: you can add up to 5 hosts per event, rising to 70 once the managing calendar is verified, and each can be set to show on the public page, hold backend access, or both. Team Calendars display “Presented By” above the calendar name (Luma help, adding hosts and managers).
• Luma Insights tracks page views, live traffic, top referrers, top cities, custom utm_source links and guest referrals before the event, then check-in data after it (Luma help, event insights).

Your one move

Open a new spreadsheet and name it after the event. Create four tabs and name them exactly: Runway, Budget, Sponsor Pipeline, Volunteers. Leave every one of them empty. Then open your calendar and drop a repeating one-hour block on the same day and time each week, running until the week after the event, called “Event planning.” Twenty minutes, done when the sheet has four named tabs and the calendar block repeats.

Want to go further?

Create the Luma event shell too. Put it under a Filmmakers Connect calendar, set the title and date, write one placeholder line of description, and add your cohosts as managers. Don’t share the link with anyone yet. Then paste the event URL into the top cell of the Runway tab, so the sheet and the page know about each other from day one.

The needle: an event is won before doors open, and every decision you win has to land somewhere you can find it again. The sheet is where won decisions go to stay won.

Terms introduced

Terms introduced in this lesson

• Master timeline
• Critical path

Each term links to the glossary, where it is defined by the way you just used it.

Check

Check yourself

1. A volunteer messages you: 'I can help chase sponsors this week, what do you need?' You realize the sponsor names are split across a few chat threads, a note on your phone, and your memory. What is actually stopping you from handing the work over?

   Nothing, you just need to type the list out for herSponsorship should only ever be handled by the lead organizerShe needs more experience with sponsors before she can helpThe work isn't in a place anyone but you can pick up, so it can't be distributed yet

2. DevOpsDays organizers start meeting semi-monthly while their event is still more than half a year away. Your event is about three months out and you are the only lead. What does that mean for your planning cadence?

   No cadence needed, a solo lead can decide things as they come upSemi-monthly, because that is the documented practice and you should copy itWeekly, because a shorter runway compresses the interval between check-insDaily, because a solo lead has more to carry

3. The venue isn't signed and the guest list isn't locked, so you're holding off on creating the Luma event until things firm up. What does waiting actually cost you?

   Nothing, an empty event page has no valueThe venue depositThe link, the cohost access, and the insights data all arrive on launch day instead of before it, which turns your launch into a build dayOnly the page views you would have collected in the meantime

Check answers

You can move on when you can… open one document that answers any question about the event, say which lesson fills each of its four tabs, and point at the recurring block in your calendar where the event actually gets decided.

Mark this lesson complete

Go deeper

• Next up: Level 1 begins with 1.1 · Strategy before logistics, where you write the event concept that everything in your new sheet is built to serve.