Meetup OS · D-30 to D-day
Tech event planning checklist, meetup version
Six phases, every item with an owner, from the day you write the title to the five-minute signal on the night. This is the list the ELC team works from, with the private parts left out.
How the phases work
The build happens in three sittings on three different days. First sitting, everything gets created and nothing gets published. Second sitting, members hear first. Third sitting, at least four days later and on a Tuesday to Thursday, the public hears. A runner enforces the order: it refuses to send a public invite before the four days are up, and it refuses to announce to members before every speaker has approved the text about their own talk.
Two things stay manual whatever the tooling: a human approves the cover design, and a human checks the registration page by hand before any invite goes out. Every email is a draft that a person sends. The full D-30 to D+90 cycle is on the Meetup OS page; this page stops at the five-minute signal.
01 · D-30 to D-28, one sitting of about two hours
Build everything, publish nothing
Owner: Event manager, founder approves the design
- Title and abstract written as a thesis. Under 80 characters, the meetup number in front.
- Cover approved by a human before it goes anywhere. Check how it crops on the registration page and on LinkedIn.
- Internal event page with title, abstract, sections, cover, team contacts. Published to the web for the team.
- Registration page created private: cover, venue with an exact map pin, capacity. Speakers shown as faces with first names and company logos.
- Capacity set to about twice the real venue capacity. Half the approved registrations will not come; the numbers are on the Meetup OS page.
- LinkedIn event created, name under 75 characters. Nobody invited yet.
- Meetup.com event created, not announced.
- Deck copied from the master: cover slide, one card per speaker.
- One calendar invite: team, helpers, venue contact, photographer, videographer, speakers.
- Every link pinned in the team channel.
- One joint email to all speakers: intro call, two or three photos, the deck link.
- Each speaker edits and OKs the description of their own talk on the registration page.
- Venue asked whether their merch can be the prize for the best question of the night.
02 · D-26, right after the build, about 45 minutes
Members first
Owner: Event manager, founder for partners
- Wait until every speaker has OKd their description. The runner refuses to continue before that.
- Members newsletter with the private link: for members before the public announcement, the date it goes public, one ask.
- The same message, shorter, in the member Slack channel with the cover image. This starts the four-day clock.
- Existing partners get their reserved seats, one personal email each.
- Dated promo schedule pinned in the team channel: D-21 announcement, D-14 teaser, D-7 logistics, D-1 reminder, D-0 morning, D+1 recap. Four or five registration-page blasts in total, not more.
- Brand kits drafted for partners, speakers and attendees: one ready post, one Slack blurb, one tagged link each.
03 · D-22, a Tuesday to Thursday, at least four days after members, about 30 minutes
Go public
Owner: Event manager, founder for LinkedIn invites
- Registration page switched to public. One click, and a human checks title, abstract, date, venue pin, cover, capacity and slug first.
- Web event page built, deployed, submitted to search engines.
- Invites from the registration platform to all members, sent between 12:00 and 13:00.
- Meetup.com: announce to the group.
- LinkedIn event invites, filtered by the event city and the IT industry. The cap is 1,000 a week; repeat weekly.
- Announcement in every other community Slack you belong to.
04 · D-7 to D-1
The week before
Owner: Content marketer, Head of Community, founder
- D-7 logistics blast with one line of social proof: the registration count.
- D-7 pre-event poll opens: what is your #1 question on the topic. One question, anonymous.
- D-5 speaker teaser: each speaker says one provocative thing they will cover.
- D-3 People to Meet email: four to six named attendees who agreed, with a one-line why-meet.
- D-3 first-timer email: how the night runs, do not skip the networking, look for the sticker on your name tag.
- D-2 bring-the-question: the three sharpest pre-submitted questions open Q&A on stage with the asker's name.
- D-2 slides locked. Takeaway assets received, QR codes generated.
- D-1 poll closed and compiled into one slide. Final reminder blast. Last-call message to the team.
- D-1 the loadout packed, see below. Never the morning of.
05 · Packed the night before
The loadout
Owner: Event manager
- Tech: laptop and charger, clicker, every HDMI and USB-C adapter you own, microphones, a USB stick with backup slides.
- Sound: an offline music playlist. Venue wifi will fail at least once.
- Ops: name tags and black markers, sign-in sheet, printed QR codes, first-timer stickers. Expect 20% more first-timers than the list says.
- Brand: roll-ups, printed direction signs from the street to the room.
- Emergency: gaffer tape, extension cords, spare batteries, pen and paper.
- Prizes: a bottle of good wine for the sharpest question, three status prizes for the quiz, a guest pass for the first-timer draw.
06 · Event day, T-3h to T-5min
The setup clock
Owner: Event manager, Head of Community, founder
- T-3h event manager on site, catering received.
- T-2h room set: chairs, screen, projector, microphone, registration desk.
- T-90min final tech check on the real screen with the USB backup. Photographer briefed: one wide shot with the most people in it, speakers in action, networking. Videographer briefed: two or three attendee interviews.
- T-90min walk-in test: one team member walks from the street to a seat as a stranger. Fix the signage where they hesitated.
- T-60min doors open, music on, greeter at the door putting stickers on first-timers.
- T-30min first-timer huddle by the bar, 15 minutes, each first-timer walked over to one regular.
- T-5min five-minute signal.
- Three checks that catch most failures: the walk-in test, the audio check from the back row with music playing, and the speaker safe zone with bags, water and slides tested on the real screen.
Get this as a printable checklist.
The full D-30 to D+90 Meetup OS checklist as one printable page, plus the ELC meetup lessons as they land, in the Leaders' Brief. One email a month.
One email a month. Unsubscribe is a reply.
You're on the list.
A welcome email is on its way. The checklist is at engineeringleaders.io/meetup-os/checklist/, open it now.
Or open the Meetup OS checklist now: the first phase is open, the rest unlocks with the same signup.
For companies
Want ELC to run the whole night at your office?
Your venue, your speaker. The ELC team brings the topic, the audience of 3,300+ engineering leaders, the games, the host and the photos. A median of 125 confirmed registrations across the last 13 public meetups.
See what ELC runs for companiesQuestions organizers ask
How far in advance should I plan a tech meetup?
Thirty days. ELC creates everything at D-30 to D-28, tells members at D-26, goes public at D-22 and starts the promo cadence at D-21. Speakers need their intro call at least two weeks before the date, which is the real constraint on the calendar. Less than three weeks and the speaker side gets rushed, which is what the audience notices.
What should be on an event planning checklist for a meetup?
Six blocks: the build with nothing published, the members-first announcement, the public launch on a Tuesday to Thursday, the week-before touchpoints, the loadout packed the night before, and the setup clock on the day. The lists above are the ones ELC runs, with the private parts left out. Print them from the Meetup OS checklist page.
How many registrations should I expect to show up?
About 60% of approved registrations at a free tech meetup with a room of 100 to 130, measured at the door by QR scan across ELC's last public meetups. That is why the registration cap is set to about twice the real capacity. The full numbers are in the measured table on the Meetup OS page.
Why tell members before the public?
Members get first pick of the seats, four days before anyone else, from a private link. It is the one thing a member gets that a stranger does not, and the public launch then starts with registrations already on the page.