Post event summary

HackerSquad automatically generates a post-event summary for completed events. This gives you a single page that captures what happened at the event and makes it easier to share outcomes with builders, partners, and your broader community. The post-event summary is built from the activity that happens throughout the event. As builders submit projects and live content is added to the event, HackerSquad turns that information into a structured event recap.

​

See an example

Here is an example of a post-event summary in action.

​

What the post-event summary includes

The post-event summary is auto-generated from:

• Submitted projects
• Live presentations
• Live speakers
• Live demos
• Event gallery photos

As those pieces are added during the event, they feed into the final event page automatically.

​

Why the post-event summary matters

The summary gives your event a lasting artifact after the hackathon ends. Instead of losing the momentum of the event once everyone leaves, you keep a public record of what builders created and who contributed to the experience. This is especially useful when you want to:

• Show what builders shipped
• Highlight speakers and live demos
• Share event photos after the hackathon
• Share outcomes with sponsors and partners
• Give attendees a place to revisit projects after the event

​

Projects and live content power the summary

Submitted projects become the core of the post-event recap. Those project entries can surface key details such as project descriptions and links to source code or demos, depending on what builders submit. Live demos are also included in the completed event experience, alongside speakers and sponsor sections, which helps the summary reflect both what was built and what happened during the event. The post-event summary can also include a photo gallery. Event hosts need to upload their own photos to the event gallery through the event management dashboard if they want those images to appear in the final recap.

​

Prizes and winners

If you configure your prizes correctly during the event, those prizes can also be assigned to the individuals who win them. That means the post-event summary does not only show what was built. It can also reflect who won the featured prizes, which helps connect projects, builders, and outcomes in one place.

​

Keep your event data up to date

Because the post-event summary is generated from event activity, it is important to keep your event records current during the hackathon. Make sure builders submit their projects, live demos are captured, speakers are added, event photos are uploaded to the gallery, and prizes are configured correctly. The more complete your event data is, the stronger your final summary will be.

​

Next steps