Criteria & How We Judge

The following details the sections of the criteria, and the respective weightings of each section.

The weightings used here, align with a sentiment of:

Projects that execute effectively as a team

Projects that sufficiently integrate with our network

Projects that sufficiently gain market validation

Projects that achieve results that align with network outcomes

Judging Criteria

INNOVATION

10%

FEASIBILITY

10%

EXECUTION

20%

INTEGRATION

15%

SUCCESS

20%

VALIDATION

15%

PITCH

10%

CRITERIA

How We Judge

INNOVATION

10%

FEASIBILITY

10%

EXECUTION

20%

INTEGRATION

15%

SUCCESS

20%

VALIDATION

15%

PITCH

10%

The following details the sections of the criteria, and the respective weightings of each section.

The weightings used here, align with a sentiment of:

Projects that execute effectively as a team

Projects that sufficiently integrate with our network

Projects that sufficiently gain market validation

Projects that achieve results that align with network outcomes

CRITERIA

How We Judge

INNOVATION

10%

FEASIBILITY

10%

EXECUTION

20%

INTEGRATION

15%

SUCCESS

20%

VALIDATION

15%

PITCH

10%

The following details the sections of the criteria, and the respective weightings of each section.

The weightings used here, align with a sentiment of:

Projects that execute effectively as a team

Projects that sufficiently integrate with our network

Projects that sufficiently gain market validation

Projects that achieve results that align with network outcomes

Submission Artefacts

Each team should appoint 1 ‘Team Representative’ to submit your project on the submission portal by

23 MARCH 2026

23 MARCH 2026

11:59 PM ET

11:59
PM ET

Project’s GitHub Repo Link

Project’s GitHub Repo Link

Team leader to create the project's GitHub Repo and share the access with the rest of the team to collaborate on.

The team will save all submission items onto this Github Repo where the judges may access the items during the judging period.

GitHub repo should host the application’s code, a README file, any other deployment files and testing instructions.

Project Details

Project Details

Project Description (max 100 words)

Selected hackathon track

A list of tech stack (solutions, technology infrastructure, technology services, etc.) used by the team to build your project

In the “Details” section of your submission form on Dorahacks, include the link to a publicly-accessible Google Drive folder containing your pitch deck in PDF format.

Project Demo Link

Project Demo Link

This is the URL to the live working environment of the solution the team has developed.

Project Demo Video

Project Demo Video

This is the URL to the project demo video of the solution the team has developed.

Pitch Deck in PDF

Pitch Deck in PDF

Here’s a potential structure you can adapt for your pitch deck:

Upload this PDF file into your publicly-accessible Google Drive folder to be submitted under the "Details” section of your submission form on Dorahacks.

Here’s a potential structure you can adapt for your pitch deck:

Team and Project Introduction

Upload this PDF file into your publicly-accessible Google Drive folder to be submitted under the "Details” section of your submission form on Dorahacks.

Team and Project Introduction

Project Summary

Provide a comprehensive overview of your solution, keeping in mind that the 7 judging criteria will form the basis of judges’ assessment.

Future Road Map

Any key learnings and room from improvements? Outline the next steps for your project if you were to continue developing it.

Demo

Showcase the technical strengths, usability and performance of your solution here! You must pre-record your demo, upload it to Youtube, and insert the link in your deck.

Note: Submissions without a demo video link in the deck will not be scored

Hedera testnet on-chain account

Hedera testnet on-chain account

Provide your Hedera testnet on-chain account as a proof of an on-chain transaction.

Submission Portal

Reminder that all teams should submit before the following date, to qualify for the hackathon prizes.

23 MARCH 2026

23 MARCH 2026

11:59 PM ET

11:59 PM ET

01

Make sure ALL members of your team have registered for the hackathon.

02

Only the Team Representative will need to submit the project on behalf of the team.

All teams are encouraged to submit as soon as possible before 16 March 2026 to avoid last-minute submissions and missing the deadline.

03

Begin your submission via StackUp platform. If all the submission items are not yet completed, you may put placeholders.

04

If you need to make edits or updates to your submission, you may do so before the submission deadline via StackUp.

05

If you face any issues or require help during submission, contact us on the 

#mentor-assistance channel on the Apex, or email us at support@hellofuturehackathon.dev

Calendar