HACK PLATFORM — HACKMASTERS

YOUR LOGO HERE

IN COLLABORATION WITH

AGENDA

BRIEF + RESOURCES

SUBMISSION

JUDGING CRITERIA

FAQs

You’ve been selected to join the [HACKATHON NAME] Hackathon. This is your central hub for everything you need during the event — from team links to submission portals and daily schedules.

Keep this page bookmarked. It will be updated regularly.

Event Snapshot

Hackathon Dates: [DATES]

Daily Schedule: 9:00 AM – 5:00 PM

Venue: [VENUE NAME WITH LINK]

Discord Server: All communications will happen on [Discord link].

hacker checklist

Join the Discord Server (link below)
On Discord: Change your per-server/ nickname name to your real name

On Discord: Meet your team & introduce yourself
Submit final project by [DEADLINE]

hack agenda

  
      Time
      What
      Who
    
      09:00 – 09:15
      Opening introduction
      Host/Organisers
    
      09:15 – 09:30
      Demo of reference build or previous prototype
      Host/Facilitator
    
      09:30 – 12:30
      Start hacking
      All teams
    
      12:30 – 13:15
      Lunch
      —
    
      13:15 – 13:30
      
        Team updates: tear downs & build-ups

        • 5 mins per team (3 min pitch + 2 min Q&A)

        • Max 3 slides
      
      Teams A+B+C
    
      13:30 – 15:30
      Continue hacking (some teams may begin next phase)
      All teams
    
      15:30 – 15:45
      Coffee break
      —
    
      15:45 – 17:30
      Continue hacking
      All teams
    
      17:30 – 18:00
      
        Final presentations

        • 10 mins per team

        • Software teams must include a working demo
      
      Teams A+B+C

Time	What	Who
09:00 – 09:15	Opening introduction	Host/Organisers
09:15 – 09:30	Demo of reference build or previous prototype	Host/Facilitator
09:30 – 12:30	Start hacking	All teams
12:30 – 13:15	Lunch	—
13:15 – 13:30	Team updates: tear downs & build-ups • 5 mins per team (3 min pitch + 2 min Q&A) • Max 3 slides	Teams A+B+C
13:30 – 15:30	Continue hacking (some teams may begin next phase)	All teams
15:30 – 15:45	Coffee break	—
15:45 – 17:30	Continue hacking	All teams
17:30 – 18:00	Final presentations • 10 mins per team • Software teams must include a working demo	Teams A+B+C

brief + resources

CHALLENGE BRIEF(S)

LINKS/ FILE DOWNLOADS TO ANY REQUIRED RESOURCES

FILE SUBMISSION

DEADLINE: [DATE + TIME]

FILE UPLOAD WILL BE MADE AVAILABLE CLOSER TO THE DEADLINE

SUBMIT YOUR FILES

judging criteria

  
      Criteria
      Weight
      Evaluation Prompts
    
      Impact
      20%
      
        • Does the project solve a big or small problem?

        • Will it help or inspire many or few?

        • Does it improve society, the economy, or the environment?

        • Consider contributions to social cohesion, economic impact, and sustainability.
      
      Creativity
      20%
      
        • How novel is the idea?

        • Is it a breakthrough or an incremental improvement?

        • Does it anticipate future user needs or technological advances?

        • Does it meet emerging needs creatively?
      
      Relevance
      20%
      
        • How well does it address the challenge?

        • Is the solution usable and technically feasible?

        • Does the model clearly deliver value (e.g. time saved, cost reduced, wellbeing improved)?

        • Is it integrated naturally into the user’s workflow?
      
      Technical Feasibility
      20%
      
        • Is it technically realistic and implementable?

        • Agentic AI: Can the model Perceive, Reason, Act, and Learn?

        • Is it user-centric? Does it balance autonomy with human oversight?

        • Can it handle high-stakes decisions, enable collaboration, and explain its reasoning?

        • Has the team made strong progress during the hack?
      
      Presentation
      10%
      
        • Was the challenge, solution, and impact clearly communicated?

        • Was the pitch engaging, supported by a live demo or video?

        • Were the visuals polished and the slides concise and effective?

Criteria	Weight	Evaluation Prompts
Impact	20%	• Does the project solve a big or small problem? • Will it help or inspire many or few? • Does it improve society, the economy, or the environment? • Consider contributions to social cohesion, economic impact, and sustainability.
Creativity	20%	• How novel is the idea? • Is it a breakthrough or an incremental improvement? • Does it anticipate future user needs or technological advances? • Does it meet emerging needs creatively?
Relevance	20%	• How well does it address the challenge? • Is the solution usable and technically feasible? • Does the model clearly deliver value (e.g. time saved, cost reduced, wellbeing improved)? • Is it integrated naturally into the user’s workflow?
Technical Feasibility	20%	• Is it technically realistic and implementable? • Agentic AI: Can the model Perceive, Reason, Act, and Learn? • Is it user-centric? Does it balance autonomy with human oversight? • Can it handle high-stakes decisions, enable collaboration, and explain its reasoning? • Has the team made strong progress during the hack?
Presentation	10%	• Was the challenge, solution, and impact clearly communicated? • Was the pitch engaging, supported by a live demo or video? • Were the visuals polished and the slides concise and effective?

faqs

You’ve already signed the Hacker Commitment Form, and you’ve joined the Discord Server, which means you’ve been officially accepted to participate in this hack. These FAQs are here to help you navigate the next steps. Make sure you’ve checked your invite email — it includes your team number and access to Hacker HQ and the Discord server.
All communications will take place on Discord. Once inside, turn on notifications and check the information and team channels regularly.
Your team number was provided in your acceptance email.
- During Discord onboarding, select your team number so you're placed in the correct team channel (named 1, 2, 3, etc.)
- If you think there is an error, please @olivia in the discord to clear up any issues.
You should have signed up with your team. Team assignments are now final unless we’ve contacted you directly to discuss changes.
You’ll submit your final project via a submission form linked on Hacker HQ. One submission per team.
You can use any open-source or licensed tools, as well as tools you build during the hack. Keep documentation ready and up to date — judges may ask about your approach.
Judging will take place on the final day of the hackathon. More details will be shared closer to the time.
You signed the hacker commitment, so we strongly urge you to still attend in order not to let your team down. However, if it is unavoidable, you must notify @olivia on Discord as soon as possible.
Please post your question in the #event-questions discussion forum on Discord. A member of the team will respond as soon as possible.

need help?

Post in #event-questions on Discord or ping @Olivia or @Lily directly. We’re here to help.