Event recap template: a copy-and-paste recap for build days and student events
· buildtolaunch
This guide is for a student organizer or club lead who has just run a build day, co-working session, hackathon or meetup and needs to write the recap. You get a copy-and-paste recap template, a shorter version for a social post, a sponsor email and a checklist for the first 48 hours. For the wider picture, see the full guide to build days and builder communities.
Short answer
An event recap is a short public post, sent within 48 hours, that says what happened, shows what people made (with links), thanks the people who helped and announces the next date. Keep it to one page. The most useful recap is not a photo album: it lists the projects, the numbers you actually tracked and the next step for readers.
Why a recap matters
Most events lose their energy the next morning. A recap does four jobs:
- It keeps attendees engaged. Seeing their project listed is a reason to come back.
- It proves the event happened. Sponsors, universities and future partners want evidence, not a promise.
- It helps non-attendees decide. A reader who sees real projects and a real date is more likely to join next time.
- It forces you to measure. Writing the numbers down shows what worked.
The 48-hour checklist
| When | Do this |
|---|---|
| During the event | Photograph the room and the screens (ask permission first). Note the names of helpers and partners. Save every project link. |
| That evening | Write down the numbers: registered, attended, projects shipped. Do it while you remember. |
| Next morning | Send a thank-you message to helpers and partners. |
| Within 48 hours | Publish the recap. Share it where the event was announced. |
| Within a week | Send the sponsor email (below) with the recap and your numbers. |
Major League Hackathon's organizer guide advises sending sponsors a thank-you email with an event recap right after the event, then reconnecting when you plan the next one. The same habit works for any partner.
The recap template
Copy this block and fill in the brackets. Delete any section you cannot fill honestly.
TITLE: [Event name]: what [number] people built in [duration]
ONE-LINE SUMMARY
On [date], [number] people met at [venue or online] to [goal of the event].
[One sentence on what happened, for example: "[Number] shipped a project
someone else can open."]
WHAT WE DID
- Format: [co-working / build day / hackathon / demo day]
- Length: [start time to end time]
- Tool or theme: [one line]
- How we decided what counted as "shipped": [for example, a live link]
WHAT PEOPLE MADE
1. [Project name], by [name, only if they agreed]: [one sentence]. [Link]
2. [Project name], by [name, only if they agreed]: [one sentence]. [Link]
3. ...
HOW WE CHOSE FAVOURITES (if you did)
[Voting on a board / judges with a rubric / no ranking]
THE NUMBERS
- Registered: [number]
- Attended: [number]
- Projects shipped (live links): [number]
- First-time builders: [number, only if you asked]
WHAT WORKED
- [One thing]
- [One thing]
WHAT WE WILL CHANGE
- [One thing]
- [One thing]
THANK YOU
[Venue], [partners], [helpers], [mentors], [everyone who came]
NEXT
- Next session: [date and time], register at [link]
- Keep building: [where members can post this week's work]
- Want to host or help? [how to contact you]
Tips for filling it in
- Ask before naming people. Put a name or a photo only if the person agreed. A project link without a name is fine.
- Use only numbers you tracked. If you did not count attendees at the door, say "about" and give your best estimate, or leave it out. Never round up to look bigger.
- Link to every project. A list of live links is the most useful part of the page.
- Keep "what we will change" honest. One real lesson earns more trust than five compliments.
The short version for social posts
[Event name] is done. [Number] people, [number] projects shipped in [duration].
Highlights:
- [Project] by [name]: [one line]
- [Project] by [name]: [one line]
Thank you [venue], [partner] and everyone who came.
Full recap with all the links: [link]
Next session: [date], sign up: [link]
Post it in the same places where you announced the event, and tag partners who agreed to be tagged.
The sponsor and partner email
Subject: [Event name] recap and thank you
Hi [name],
Thank you for supporting [event name] on [date]. Here is what happened:
- [Number] people attended, and [number] shipped a project.
- [One sentence on how your support was used, for example: "Your credits
let everyone build with the same tool."]
- Full recap with project links: [link]
What we learned: [one sentence].
What we plan next: [one sentence, with a date if you have one].
If you would like to take part again, I would love to hear what would make it
more useful for you. [Your name and contact]
Send it the same week. If a sponsor asked you for specific information beforehand, such as the number of first-time builders, include it.
What not to put in a recap
- Invented numbers. If you did not track it, do not claim it.
- Photos of people who did not agree. Ask at the door and respect a no.
- A list of every thank-you in the world. Name the people who made it possible, not everyone you have ever met.
- A vague next step. "See you soon" is not a date.
Make the recap work for the next event
Keep every recap in the same format and store them in one place. After three events you can compare return attendance and projects shipped, which tells you more than any single headline number. For which measures to track, see community metrics that matter and after the event: measuring whether your build day worked. If you are planning the event itself, how to host a student hackathon or build day has a timeline from six weeks out to the day after, and how to run a demo day covers the showcase part.
Where buildtolaunch can help
buildtolaunch is free and open to students of any major. After an event, participants can keep working in project Spaces with an AI teammate and post what they made to the Launch League, a public board that resets every Monday, which gives your recap a link to point to and a weekly reason to return. For a real recap to read, see the Vibe-a-thon Saigon recap. Upcoming events are on the Events page, and students can sign up here.
Read the full guide: build days and builder communities.
FAQ
What should an event recap include?
A good recap includes the date and place, what the event was, what people made with links, the numbers you tracked, a thank-you to helpers and partners, and the date of the next event. Keep it to one page and publish it within 48 hours.
How soon should I publish an event recap?
Within 48 hours. After that, most of the attention has moved on, and you also start forgetting details. Write the numbers down on the evening of the event, even if you publish the full recap the next day.
Where should I publish the recap?
Publish it where people found the event: your Luma or Facebook event page, the community group chat and your club's page. Add a short social post that links to the full recap. Keep one permanent link so sponsors and future partners can find it.
How do I write a recap if few people came?
Write it the same way and be honest about the numbers. A small event with five live projects and a clear lesson is a fine recap. Focus on what people made, what you learned and the next date.
Should I name the participants?
Only if they agreed. Ask at registration or on the day, and let people choose between a name, a first name or just a project link. This also applies to photos.
Do I need a recap for a small weekly co-working session?
A one-paragraph version is enough: who built what, with links, and the next date. Consistency matters more than length, because weekly recaps become the record you use to show a community is growing.