Meetup OS · D+1 to D+90
After the meetup: the part most organizers skip
The night ends at T+180. The meetup does not. Twenty steps over ninety days, each with a day and an owner, from the door count to the archived channel.
Why the close is a runner, not a to-do list
Most events vanish from memory by Monday. The week after is where a community's content advantage gets real: the photos, the video, the takeaway assets, and the thank-you that arrives while people still remember who they talked to. At ELC the close mirrors the launch step by step. The registration page that opened at D-28 gets its photos at D+2. The speaker thread that started at D-28 gets the speaker pack at D+2 and the video at D+14. The team channel that got its links at D-28 gets archived at D+90.
The runner is run every morning from D+1 until it prints a date in the future. It refuses to do a step before its day, and it refuses to send any email at all: everything is a draft a person sends. Attendee lists live in a gitignored folder; the config keeps counts only.
The close, step by step
| Day | Step | Owner | What happens |
|---|---|---|---|
| D+1 | Attendance | Head of Community | Approved, checked in, no-shows, walk-ins, from the QR scans. Two lists come out of it: who came and who did not. The headcount every later step uses. |
| D+1 | Photo and video request | Head of Community | Photographer selects by the end of the day, including one wide shot with the most people in it. Videographer delivers one edited video per talk and a 60-second clip per speaker by D+12. |
| D+1 | Debrief | Head of Community | Fifteen minutes with the team while it is fresh: what worked, what broke, venue notes, who got their swag. One line each, onto the event card. |
| D+2 | Photos gate | Head of Community | At least 20 photos in the folder or the run stops and pings the photographer. From D+3, continue with what exists: a thank-you at D+4 is worth less than one with fewer photos. |
| D+2 | Web recap | Founder | The event page stops looking like an ad for a finished event: a real photo of the night as hero, alt text, links to the photos and slides, registration closed. |
| D+2 | Attendee thanks | Head of Community drafts, founder sends | One email per attendee, everything in it: thanks and one takeaway line, the photos, the slides, a post kit with one photo and two lines to paste, the next meetup link, a one-click 1 to 10 score. |
| D+2 | No-shows | Head of Community drafts, founder sends | A separate list, so nobody gets both emails. We missed you, here are the photos, the video is on its way, here is the next one. No guilt trip. |
| D+2 | Speaker pack | Founder | Their photos, a speaker badge for their profile, the alumni welcome, a post kit, and one choice: a podcast episode or a co-written blog post. A check that the swag was handed over on the night. |
| D+2 | Venue | Head of Community | Thanks, the ten best photos for their careers page, a post kit for "we hosted", the outcome of the merch prize, anything to fix, and the question: host again in the next 12 months? |
| D+2 | Public recap | Content marketer | A carousel from the company page tagging speakers, venue and partners. The founder's own post. The recap posted inside the LinkedIn event, which notifies everyone who joined it. Photos on the registration page. Recap in the member Slack. |
| D+3 | Partner reports | Founder | A short report per partner from one template: leaders at the door, show rate, how many of their own people came, photos with their logo in frame, the score. Then "how was it for you and your people?" |
| D+3 | Coffee invites | Founder | Attendees from companies you would like to work with get a coffee invite. Capped at five, because the calendar is the limit. Checked against the outreach ledger first: one cold email per person, ever. |
| D+7 | Leaderboard | Head of Community | Points: one per meetup attended, five per talk given. The people at the top are the next speakers, ambassadors and hosts. |
| D+7 | Follow-ups | Head of Community | One nudge, not two. Collect what came back: venue answer, each speaker's podcast or blog pick, partner replies worth keeping, the average attendee score, shared with the speakers. |
| D+7 | Numbers | Executive assistant | This meetup's figures go into the data registry before anyone quotes them. Invoices: venue, photographer, videographer, catering, swag. |
| D+7 | Brand scorecard | Content marketer | Registrations by UTM source and by person. Posts mentioning the community. Company page followers. Posts published against posts asked for. |
| D+14 | Video | Designer | Talk videos on the channel and on the event page. Each speaker gets their video and their clip. Recap and video in the other community Slacks. Attendees see it in the next newsletter, not in a third email. |
| D+14 | Retro | Head of Community | Each lesson written as "launch step 12: change X" or "close step 07: change Y". A lesson not tied to a step is a feeling. |
| D+14 | Close | Head of Community | A recap section on the event page: numbers, score, photos, slides, video, posts, venue answer, coffee invites. Status: completed. |
| D+90 | Archive | Head of Community | A closing message in the team channel pointing at the recap, then archive it. |
Three rules the close never bends
- Attendance is the door scan, not the registration count. Registrations are what the venue cap allowed. Check-ins are who came. The measured numbers on the Meetup OS page exist because this step wrote them down for eleven meetups in a row. Walk-ins are missed by the scan, so the count is a floor. One meetup outdoors scanned 43 against 60 or more counted by hand.
- One email per person, with everything in it. Attendees get one. No-shows get a different one. Speakers get two, at D+2 and D+14, and both ride in the thread that started before the event. Nobody gets three.
- Measured, not assumed. Every link in every kit carries its own tag, so D+7 can say which speaker, partner or channel brought people. When the kits are built and not shared, the scorecard reads "direct" for every registration and teaches nothing.
Get the printable Meetup OS checklist.
The full D-30 to D+90 checklist, close steps included, 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.
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
What should I send attendees after a meetup?
One email, two days after, with everything in it: a thank-you with one takeaway line, the photo folder, the slides if the speakers cleared them, a post kit with one photo and two lines they can paste on LinkedIn, the link to the next meetup, and a one-click score from 1 to 10. Not three emails. People who did not come get a separate, shorter one with the photos and the next date.
How do I get people to come back to my meetup?
Close the loop on the things you promised. The photos arrive, the slides are published on your site within 72 hours instead of "we'll send them", the video lands on the event page two weeks later, and the person who won the topic vote gets a named front-row seat announced in public. First-timers get a personal message from a community host the same night, not a marketing email. At ELC the target is 60% of first-timers back within three meetups.
How do I measure whether a meetup worked?
Three numbers you can read back a year later: checked in against approved, the average attendee score from the thank-you email, and registrations by UTM source. The last one only works if the tagged links were used. At one recent ELC meetup every registration showed as direct traffic, because the kits with the tagged links were built and not shared. The scorecard is worth nothing without that step.
What do I owe the venue after a meetup?
A thank-you within two days, the ten best photos for their careers page and internal channels, a ready post that says they hosted, and any fix you noticed. Then one question: will you host again in the next 12 months? The venue is the cheapest reach you have and your next booking. Ask while the room is still fresh in their head.