FOREWARN//BDBoot sequence

Disaster Hackathon

3.0

Launch in

--:--:--:--

DaysHrsMinSec

D-1515-day run-up to launchD-0

> link: FOREWARN//BD ........ ok

> loading C5 pipeline ....... ok

> syncing risk signals ...... ok

> opening humanitarian space

01
Stage 01 / 05LiveNew in 3.0

COMMIT

Instructions

The ground rules. Partners commit to challenges, the Jury and mentors come on board, and the Handbook is published at the official launch.

WhenNow, until the official launch

[ Flowchart 01 ]

How to take part, start to finish

Follow the arrows. The two diamond steps are Jury decisions.

  1. You01

    Form an interdisciplinary team

    Bring different skills together and pick a priority area.

  2. CREATE02

    Register your team

    Registration opens with the official launch.

  3. CREATE03

    Work through the knowledge modules

    Every registered team gets them.

  4. CREATE04

    Submit a concept note and a video

    Fully remote.

  5. Jury05

    Shortlisted?

    20 to 25 teams go forward.

  6. CHECK06

    Virtual mentoring, module by module

    With FOREWARN Experts, Youth Pool and domain mentors.

  7. CHECK07

    Submit a revised proposal

    Validated with data and tools from partners.

  8. Jury08

    Top five?

    5 teams go to CULTIVATE.

  9. CULTIVATE09

    Residential prototyping

    Hands-on technical mentoring.

  10. CULTIVATE10

    Test with partners and users

    Field validation, then an implementation plan.

  11. Jury11

    Final presentation and awards

    All five teams are ranked and awarded.

  12. CULTURE12

    Pilot, improve, scale

    Partners own and pilot promising tools.

[ Flowchart 02 ]

What COMMIT puts in place

Before any team registers, the foundation has to hold.

  1. Foundation 0101

    Theory of Change and visioning

    Shared vision and ToC

  2. Foundation 0202

    Stakeholder map, partner commitments and roles

    Concept note, ToR and Handbook

  3. Foundation 0303

    Jury and mentors onboarded

    Plan, roles and partner agreements

  4. Foundation 0404

    Handbook, outreach and official launch

    Priority challenge areas

[ Stage by stage ]

What each stage asks of you

StageWhat you doWhat you submitWho decidesOutcome
CREATERegister, complete the knowledge modulesConcept note and videoJury shortlists20–25 teams
CHECKTake module-wise virtual mentoringRevised proposalJury selects5 teams
CULTIVATEPrototype at the residential workshop, test with partners and usersPrototype, implementation plan, presentationJury ranks5 awarded teams
CULTUREDevelop and pilot with a partnerSustainability planPartners own; SBH and FOREWARN follow upPiloted tools

[ Build rules ]

What the Jury rewards

Practical, affordable and easy to use

Shaped with the communities it serves

Works with weak phone coverage and low literacy, not only on smartphones

Connects with Union and Upazila Disaster Management Committees, the National Disaster Management Information System and Start Network's early action plans

Represents communities with dignity

Follows safeguarding, do-no-harm and data protection principles

[ Fair play ]

Who does what, and never

Jury

Assesses CREATE submissions, CHECK proposals and CULTIVATE presentations against published criteria, and shortlists, selects and ranks teams.

Does not mentor teams or run the process.

Mentors

Provide module-wise virtual mentoring in CHECK and hands-on technical mentoring in CULTIVATE.

Do not score or select teams.

Organising Team

Coordinates partners, knowledge modules, logistics, communication and follow-up, and applies the rules consistently.

Does not score, rank or mentor teams.

[ Handbook ]

The full rulebook

The Handbook, concept note and Terms of Reference are published at the official launch.

Hackathon 3.0 HandbookAvailable at launch

[ Questions ]