The highest level(s) of influence this method typically matches with on the IAP2 public participation spectrum is…

INFORM
Inform

To provide the public with balanced and objective information.

CONSULT
Consult

To obtain public feedback on analysis, alternatives and/or decisions.

INVOLVE
Involve

To work directly with the public throughout the process.

COLLABORATE
Collaborate

To partner with the public in each aspect of the decision.

EMPOWER
Empower

To place final decision making in the hands of the public.

Purpose
Decision Making, Implementing Decisions, Community Building
Time
Multiple days
Resources
Moderate (3-4) staff members
Budget
Low Cost (under 10k)
Participants
Unlimited

A Hackathon is a short, high-energy event where diverse participants — such as designers, community members, developers, policy thinkers or creatives — come together to rapidly develop solutions to a specific challenge. Traditionally associated with technology or innovation, hackathons are increasingly used in community engagement to prototype new ideas for civic issues, policy design, or social innovation.

Hackathons typically run over 1–3 days and include brainstorming, team collaboration, mentoring, and final presentations. They are particularly useful for engaging younger participants, creatives, or digital-savvy groups in problem-solving. While intense and time-bound, hackathons foster experimentation, skill-sharing, and inclusive innovation. They’re best used when there’s a clear challenge, permission to test ideas, and an interest in co-creation over consultation.

What you'll need

Virtual Delivery

• Collaboration platforms (Slack, Discord, Google Docs)
• Virtual meeting tools (Zoom, Miro, Gather.town)
• Shared file storage (Google Drive, Dropbox)
• Virtual whiteboards and timers
• Tech support and help desk volunteers

In-person Delivery

• Wi-Fi-enabled venue with breakout spaces
• Laptops, chargers, power boards
• Catering, signage, and physical materials
• Team support stations, mentors, facilitator
• Extensive Kit of Facilitation Resources Checklist
• Event signage + visible schedule board

How to guide

A hackathon is an intensive, time-bound event where participants collaborate to develop solutions—often digital, but not exclusively—to a defined challenge.

Steps to Implement:

    1. Define the challenge and objectives

      • Clearly state the problem or opportunity participants will address.

      • Ensure the goal is achievable within the timeframe and aligns with broader organisational or community objectives.

    2. Plan logistics

      • In-person: venue, workstations, internet access, power, catering, and breakout spaces.

      • Virtual: video conferencing platform with breakout rooms, collaboration tools (e.g., Miro, GitHub, Google Docs), and tech support.

      • Decide on the duration (typically 24–48 hours for short hackathons, longer for multi-day events).

    3. Recruit participants

      • Target diverse skills and experience relevant to the challenge.

      • Include mentors, subject matter experts, and facilitators to guide teams.

    4. Prepare resources and tools

      • Provide datasets, software access, and reference materials in advance.

      • Create a clear schedule with check-ins, mentor sessions, and milestone deadlines.

    5. Run the hackathon

      • Kick off with an orientation, explain rules, and clarify deliverables.

      • Facilitate team formation, collaboration, and access to mentors.

      • Encourage regular check-ins to track progress and maintain momentum.

    6. Present and evaluate outputs

      • Teams present their solutions via demos, pitches, or prototypes.

      • Judges (internal or external) evaluate according to predefined criteria.

    7. Follow up

      • Share outcomes with all participants and stakeholders.

      • Consider next steps for implementing winning ideas or continuing development.

Tips

  • Encourage diversity – mix skills, experience, and perspectives to generate creative solutions.

  • Clarify goals and scope – avoid vague challenges that can frustrate participants.

  • Provide support – mentors and facilitators help teams stay on track.

  • Foster collaboration, not competition – even in competitive formats, teamwork is key.

  • Use technology effectively – ensure all participants have access to collaboration tools.

  • Celebrate all contributions – recognise effort, creativity, and learning, not just winning solutions.

  • Plan for follow-through – identify which ideas have potential for implementation and who will take them forward