After the event: measuring whether your build day worked
· buildtolaunch
This guide is for student organizers who just ran a build day, hackathon or co-working session and want to know whether it worked, beyond "lots of people came". You get four numbers to track, simple formulas, a three-question survey and a way to decide what to change next time. It is part of the guide to build days and builder communities.
Short answer
Track four things: how many attendees came back for a second session (return rate), how many left with a live link (projects shipped), how many posted again in the next four weeks (launches after the event), and how many helped someone else. Turnout on the day is a vanity number. Count each measure the same way every time, and compare event to event.
Why turnout is not enough
A full room feels like success. But 80 people who never return are worse for a community than 12 who come every week and build. Turnout tells you whether your promotion worked. It does not tell you whether the event did.
Pick measures that match the point of a build day: people make something, and they keep making things. That gives you four measures.
The four measures
| Measure | Formula | What it tells you |
|---|---|---|
| Return rate | People who came to a second session, divided by people who attended the first | Whether the event was worth coming back to |
| Ship rate | Live links, divided by attendees (or teams) | Whether people made something real |
| Launches after the event | Projects posted publicly in the 4 weeks after | Whether people kept going |
| Helpers | People who answered, mentored or reviewed someone else's work | Whether the group can run without you |
Return rate
The most useful number for a community. To count it, you need a sign-in list with names or emails at each session. Compare the first session with the next one. If you only run one event, measure it by who joins your next event or your group chat within a month.
Ship rate
Define "shipped" before the event. At buildtolaunch's Vibe-a-thon Saigon, the idea was a link that someone else can open, not a slide or a screenshot. Count only links you or a volunteer opened on a phone. Divide by the number of attendees who started building, not by sign-ups, so no-shows do not distort the result.
Launches after the event
Ask teams to post their project in the days after the event. If you use the weekly Launch League board, remember it resets every Monday, so save a screenshot or note the count each week. Otherwise a shared sheet works.
Helpers
Count how many people did something for others: answered a question in the group chat, mentored a beginner, ran a session. This shows whether your community depends on you alone.
A worked example (made-up numbers)
These numbers are invented to show the arithmetic. They are not from a real event.
- 40 people registered. 30 showed up and 24 started building.
- 15 live links were opened and confirmed.
- 12 people came to the next session a month later.
- 6 teams posted again in the following four weeks.
Then:
- Show-up rate: 30 divided by 40 is 75%.
- Return rate: 12 divided by 30 is 40%.
- Ship rate: 15 divided by 24 is about 63%.
- Launches after: 6 teams.
Reading the numbers: show-up is fine, shipping is decent, return rate is the weak spot. The fix is probably a better follow-up, not a better event. That is what you learn from measuring.
Collect the data on the day
You cannot recreate numbers afterwards. Set up four small things before the event:
- A sign-in sheet with name and contact. A shared form on a phone works.
- A ship check. A sheet with one row per team and a column for the live link. A volunteer opens each link.
- A one-minute feedback form at the end.
- A photo of the room, with permission, for the recap.
The three-question survey
Keep it short so people actually answer. Three questions are enough:
- How likely are you to come to the next session? (1 to 5)
- What was the most useful part? (one line)
- What would you change? (one line)
Send it within a day while memories are fresh. Treat answers as opinions from the people who replied, not as proof about everyone.
When to follow up
Follow-up timing matters as much as the numbers. A follow-up window is a standard idea in investor demo days too: Converve's demo day playbook describes a 48-hour window for introductions and a review at day 90. For a student build day, a simple version is:
| When | What |
|---|---|
| Within 2 days | Send the recap with every project link, thank partners and announce the next date |
| After 1 week | Ask who has posted an update. Remind people of the weekly board |
| After 4 weeks | Count your four measures and compare to the last event |
| After 3 months | Review: what would you repeat, change or stop? |
A template for the recap is in event recap template, and community metrics that matter goes deeper on long-term tracking.
What to change when a number is low
| If this is low | Try this |
|---|---|
| Show-up rate | Send a reminder the day before and a second one that morning. Ask people to cancel if they cannot come. |
| Ship rate | Make the goal smaller (one screen, one task), use a single tool and add floor mentors. |
| Return rate | Announce the next date before people leave. Make the next session small and easy to join. |
| Launches after | Give a weekly deadline. Ask each team to post one update, even a small one. |
| Helpers | Hand out roles: host, mentor, timekeeper. Ask individuals directly, not the whole room. |
Change one thing per event. If you change five things you will not know which one helped.
Share what you learned
Put the real numbers in the recap, including the weak ones. Sponsors trust a report with honest figures more than a perfect-looking one, and it helps when you ask them again; see how student organizers get sponsors and tool credits. If your event had a closing session, how to run a demo day shows how to run it so teams leave with a public link.
How buildtolaunch fits in
buildtolaunch is a free community for university students, open to any major, with no coding needed to start. It can help with the "after" part: teams keep building in project Spaces with an AI teammate, and the Launch League board gives them a weekly deadline and a public place to post. Hosts can list sessions on the events page, and students can browse opportunities for what to do next.
FAQ
What should I measure after a build day?
Four things: return rate (who came back), ship rate (how many live links), launches after the event (who kept posting) and helpers (who supported others). These show whether people made something and kept going. Attendance on the day only shows that your promotion worked.
What is a good return rate?
There is no standard number that applies to every community, so compare your own events with each other. Track the share of first-time attendees who come to a second session, and look for a rise over time. If it is low, improve the follow-up and the next-session invite before changing the format.
How do I count shipped projects?
Decide before the event what "shipped" means. A good definition for a build day is a live link that someone else can open and use. Have a volunteer open each link on a phone, and count only those that work.
How soon should I send the recap?
Within two days. The recap should have every project link, thanks to partners and the date of the next session. The longer you wait, the less likely people are to return.
How many survey questions should I ask?
Three is enough: how likely they are to return, what was most useful and what to change. Short surveys get more answers, and you can read all of them. Send it the day after the event.
Do I need special tools to track this?
No. A shared spreadsheet, a sign-in form and a screenshot of the weekly board are enough for a student event. Add tools later if you run many events.