Hackathon Planning Guide
What is a Hackathon?
A hackathon is an event where people get together and utilize their skills in coding to build something that can solve a problem with a set deadline. These deadlines can last anywhere from 1 day to a week.
Upon first arriving at a hackathon several project ideas are pitched to students. Everyone eventually divides into groups to work on the pitched projects that interest them and then begin furiously coding to build a working prototype for their project. These working prototypes can be apps, websites, or even a hardware hack.
Hackathons can provide a fun way for students to collaborate on a project. Here we've provided guidelines for you to be able to host your own hackathon. Our current guidelines are designed for a day long hackathon that we imagine occuring on a weekend.
Here we've detailed all the necessary steps you will need to take in order to plan for your hackathon.
Planning Your Hackathon
3 Months Before Hackathon:
Locate a venue, finalize a date and time
Find a location for your event, and book a date and time. Try contacting your school, your local library, your neighborhood community center.
Make sure to ask about the maximum number of attendees you can have. This will inform your registration limit for your hackathon.
Be on the lookout for venues with:
- Technical equipment
- Is there wifi? Is it free? Is it fast enough to accommodate all your attendees?
- Are there enough power outlets for everyone attending? Do you need to bring additional power strips and extension cords?
- Is there AV (audio visual) equipment? Is there a microphone or PA system you can use to talk to the entire group at once? Is there a projector you and teams can use to present?
- A variety of workspaces (a large room where you can present to all attendees at once, smaller breakout spaces where individual teams can work on their projects)
Plan event details
See if you can answer the following questions.
- Number of People: How many people will attend? (This will largely be decided by your venue)
- Theme of Hackathon: What will you choose the theme to be?
- Requirements of the Hackathon project
- What hardware will you be providing?
- Will there be judging?
- Will you provide snacks?
- What is your hackathon Code of Conduct
Decide on individual roles
Decide on the roles each individual in the club will take, especially day of hackathon roles. A couple suggestions for possible teams are below. Make sure you decide a point person for each team.
- Budget Team
- Logistics Team
- Marketing Team
Build a web presence
Build a webpage with the following information easily accessible
- Location with date and time included
- Hackathon Theme and Project Requirements
- Hackathon Code of Conduct
- Hardware provided
- Food provided (optional)
- Prizes (optional)
Contact sponsors or potential donors (optional)
You may have sponsors interested in your event. Create a list of companies in your local area that you could potentially reach out to for donations for prizes or food for the event.
2 Months Before Hackathon:
Market your hackathon
You can do some of the following to market your hackathon
- Facebook Event Page
- Flyers
- School Newspaper
Send invitations
There are several ways in which to send invites to attendees of the Hackathon. Make sure the invite links to a form that will be used to determine student interests in projects they want to look into.
- Facebook Event
- Evite.com
- Google form
Create detailed event schedule
Create an expected event agenda that you will send out in the week or month before your hackathon. We've provided you with a sample to see what it could potentially look like.
1 Month Before Hackathon:
Finalize guest registration list
Get a final headcount of guests so that you can determine food costs, number of power strips necessary, number of tables to set up, and any other details.
- Determine food costs
- Determine number of power strips needed
- Determine number of tables needed to set up
- Determine whether accessibility requirements are met
1 Week Before Hackathon:
Send reminder email to attendees
Send a logistical email containing all the information below
- Location with date and time included
- Directions on how to get to the Hackathon and include instructions for parking or entering the building
- Hackathon Theme and Project Requirements
- Hackathon Code of Conduct
- Hardware provided
- Food provided (optional)
- Prizes (optional)
- Point of contact for any questions about the event participants might have
- The link to the website of the hackathon
Review individual roles and responsibilities for the day of the event
Make sure teams are properly prepped for day of responsibilities and everyone is participating in the days events in some way. Here is a sample list of possible teams to set up to handle day of hackathon issues.
- Set-up Team
- Clean-up Team
- Emcee
- Registration Team
- Food provided (optional)
- Prizes (optional)
Day Of Hackathon
Intro paragraph about the day of your hackathon. Below is a sample timeline that you may find helpful when you're planning out the schedule for your own hackathon.
Sample Agenda
Time |
Event |
Things to Consider |
7:00 - 8:00 am |
Set up venue |
- AV equipment setup
- Name tags for participants
- Tables, chairs, and workspaces
- Power strips, extension cords
|
8:00 - 8:45 am |
Registration begins |
|
8:45 - 9:15 am |
Opening Remarks |
- Talk about why event is taking place
- Highlight the mission of Girls Who Code
- Highlight the theme of the day
- Thank all the sponsors and vendors for their support
- Thank all the teachers and students for their involvement
- Explain logistics
- Talk about Code of Conduct
|
9:15 - 10:00 am |
Project Pitches |
- Students get 2-3 minutes to pitch their projects
- Student give their name and their school/GWC affiliation
- Projects should be stated ahead of time and a place on the form should be open for registering teams to do so
|
10:00 - 10:30 am |
Group Selections |
- Based on projects people start to choose which projects they want to work on
- 2 people per group minimum
|
10:30 am - 1:30 pm |
Hacking |
- Students spend their time hacking
|
1:30 - 2:00 pm |
Coding Freeze |
- Students take time to figure out how to present their project
|
2:00 - 2:45 pm |
Poster/Demo Development |
- Students build the demo or poster that they will present their working prototype
|
2:45 - 4:00 pm |
Poster/Demo Presentation |
- You can choose to either have Demo presentations or Poster presentations
- You can have judging during this time too. Judges should take some time to deliberate and discuss the merits of each presentation
|
4:00 - 5:00 pm |
Closing Remarks |
- Closing Remarks
- Thank yous for staff, students, sponsors, vendors, and everyone who participated in the Hackathon
- Prizes Awarded (Optional)
|
5:00 - 6:00 pm |
Clean Up |
- Clean Up
- Remove signs
- Check for lost items
|