Projects will be evaluated based on the following set of criteria. Keep in mind that a project that focuses on only Hack or Policy will result in a poor score.

General (/25)

Originality & Creativity (/5)

→ Did the team do something novel, or take a fresh approach to the problem?

Usefulness (/10)

→ Is the project practical?

→ Does it solve the problem?

Impact / General Outlook (/5)

→ How much value does this project provide?

Presentation (/5)

→ Did the team work well together?

→ Is the project nicely presented?

Hack (/25)

Technical Design & Implementation (/5)

→ Did the team use innovative solutions to build the hack?

Complexity (/10)

→ Was the technological aspect of the project hard to build?

→ Did the team use clever techniques or implement complex components?

UX / UI Design (/5)

→ Is the user interface intuitive and easy to use? → Is it aesthetically pleasing?

Completion & Functionality (/5)

→ Is the hack usable? Does it work?

→ Does the hack achieve what the team wanted?

Policy (/25)

Clarity (/5)

→ Are the ideas well organized?

→ How understandable is it?

Scope & Impact (/5)

→ Does the brief clearly state who is affected by the problem?

→ Ex. Definitive population, geographical region, etc.

→ Who is affected by this problem? Who can benefit from the presented solution?

→ Does the solution positively impact a decently sized population?

Evidence & Analysis (/10)

→ Are the claims backed up by specific evidence, facts and statistics?

→ How reputable are the sources used?

→ Is the presented information relevant to the main problem?

→ How strong is the construction and delivery of the arguments?

Feasibility (/5)

→ How realistic is the paper?

→ Does the brief acknowledge potential limitations and negative consequences?

→ How large are those limitations and consequences?