Hackathon Organizer Guide
  • Introduction
  • overview
    • What is a Hackathon?
    • What is MLH?
    • MLH Hackcon
    • MLH Community Values
    • Event Types
      • Digital Events
        • Digital Mini Events
          • Marble Races
          • Pokemon Showdown
          • Wiki Races
          • Hacker Hangouts
        • Streamyard
  • General Information
    • Hackathon Timeline
    • Finding the Date and Purpose
    • Build Your Leadership Team
    • Locking Down a Venue
    • Hackathon Budgeting
      • Legal Considerations
    • Getting Sponsorship
      • Introduction to Fundraising
      • Understanding Your Sponsors
        • Evaluating In-kind Sponsorships
      • Potential Sponsor Perks
      • Sponsorship Prospectus
      • The 5-Step MLH Sponsorship Process
      • Cheat Sheet: Emailing Your Sponsors
    • Hackathon Website
      • Making an Accessible Design
      • Placeholder Website
      • Main Website
    • Marketing Your Event
      • Promoting Your Event
        • Marketing Email Template
      • Marketing Goals & Timelines
    • Managing Registrations
      • Registrations
      • Free Registration Tool - OrganizerHQ (OHQ)
      • Sending Reminders
        • Email Templates
      • Check-in Process
    • Event Logistics
      • Hackathon Communication Platform
      • Project Challenges
      • Ordering Swag and Prizes
      • Set Up Your Event
      • Working with Food Vendors
      • Hosting Hackers with Dietary Restrictions
      • Distributing Meals
      • Transportation/Travel Plans
      • Hardware
      • Prepare Your Emergency Plan
    • Judging and Submissions
      • Rules for Your Hackathon
      • Judging Plan
      • Cheating Check
      • Judges Communication and Recruiting
      • Hackathon Submission Portal
        • Using Devpost
        • Using Devfolio
        • Using DoraHacks
    • Hackathon Scheduling
      • Detailed Run of Show
      • Run-Through with the Team
      • MLH Tips and Templates
    • Mentorship
    • Day of Logistics and Hacker Experience
      • Help Desk Recommendations
      • Fun Mini Events
      • Workshops
      • Opening Ceremony
      • Closing Ceremony
    • After the Event
  • Organizer Resources
    • Template Links
    • Getting Support from Others
    • Leadership Resources
    • Marketing Resources
    • Registrations Resources
      • GDPR in Europe
    • Host Exciting Mini-Events
      • Cup Stacking
      • MLH Mini Events
        • WereWolf
        • Slideshow Karaoke
        • !Light
        • MS Paint Bob Ross
    • Keeping Records
    • Software for Hackathons
  • Contributors
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. General Information
  2. Day of Logistics and Hacker Experience

Closing Ceremony

PreviousOpening CeremonyNextAfter the Event

Last updated 1 year ago

Was this helpful?

Once you’ve selected your winners for the event, it's time to announce them in a closing ceremony! Having a closing ceremony ensures that hackers get enough recognition of their achievements and your other supporters also get a chance to say a final word to your attendees. It also helps everyone to sum up with the same energy they had during the start of the hackathon and reflect on the great experience they had overall! Typically we have seen the following best practices for hosting a closing ceremony:

  • When the closing ceremony is coming up make an announcement saying that the closing will be starting soon.

  • Talking over slides is the best format for this. In advance, ask your sponsors to give you a list of their prize winners.

  • Make sure to inject a lot of energy and excitement into your announcements!

  • This is a big moment for your event, and ending strong is super important — people tend to remember the beginning and the end of an event afterwards for years to come.

  • Make sure you celebrate all the hackers' achievements, what they were able to build and what that means!

  • Having a playback of their submission video can be a great way to showcase projects as well. Keep in mind that if you have any live demos that setup time and running over take more time than you think. Plan for 10 minutes for each team that live demos(with 3 for actual demo time and 1-2 for the crowd to ask questions, and the rest for setup/swapping to the next group). We recommend instead encouraging hackers to see each others projects while final deliberations for judging is going on instead of live demos at closing ceremony.

Check out an example closing ceremony deck after the opening ceremony slide example

here