Dates

Saturday, 23rd August 2025 (10 am to 8 pm) 

Eligibility

The prerequisites for participating in GenZ Can Hack are as follows:

1. Residency Requirement:
   - Participants must be residents of Canada.

2. Age Range:
   - Individuals aged between 13 to 18 years are eligible to participate.

3. Independent Learning:
   - Participants should be self-learners, as no coaching will be provided during the competition.

4. Equipment:
   - Each participant should bring their own computer and a code editor.

5. Acceptance of Terms:
   - Agreement to abide by the terms and conditions set forth by our coding club is mandatory.

6. Rule Adherence:
   - Participants should be able to follow the rules and guidelines provided for the hackathon.

7. Creativity and Problem-Solving Skills:
   - A prerequisite is possessing good creative and problem-solving abilities, crucial for navigating the challenges of the Hackathon.

8. Self Learning

Project and Submission Requirements

The criteria that may lead to disqualification include:

1. Plagiarism:
   - Copying others' ideas or replicating projects from Google without due acknowledgment, highlighting the importance of respecting intellectual property.

2. Copyright Compliance:
   - Utilizing images without proper copyrights, emphasizing the need for participants to ensure they have the appropriate permissions.

3. Rule Adherence:
   - Failure to adhere to the rules stipulated by Kids for Kids Toronto Coding Club.

4. Non-Acceptance of Terms:
   - Disagreement with the terms and conditions outlined by the coding club.

5. Late Submission:
   - Projects not submitted on or before the specified deadline date.

Judging Criteria and Winner Selection

Criteria:

  1. Innovation (25 points):

    • Novelty of the solution: Does the project offer a unique approach to "Sea Debris" or efficiency?

    • Creativity in addressing sea debris challenges: How original and inventive is the solution?

  2. Technical Complexity (20 points):

    • Complexity of implementation: Does the project involve advanced technical concepts or integration of multiple technologies?

    • Use of relevant tools and technologies: Is the project built using appropriate coding languages, frameworks, or hardware components?

  3. Impact and Sustainability (20 points):

    • Potential for Sea Debris: How significant is the projected impact of the solution on reducing sea debris or promoting sustainability?

    • Scalability and long-term viability: Can the solution be scaled up to reach a larger audience or sustained over time?

  4. User Experience (15 points):

    • Ease of use: Is the project intuitive and user-friendly, especially for Generation Z users?

    • Accessibility: Does the solution cater to diverse user needs and preferences?

  5. Presentation Quality (10 points):

    • Clarity and organization: Is the presentation clear, well-structured, and effectively communicates the key concepts?

    • Engaging delivery: Does the team effectively engage the audience and convey enthusiasm for their project?

  6. Teamwork and Collaboration (10 points):

    • Collaboration dynamics: How effectively did team members collaborate and leverage each other's strengths?

    • Contributions of team members: Did all team members actively contribute to the project's development?

Scoring:

  • 5 points: The project demonstrates exceptional innovation, technical complexity, and potential impact. The presentation is clear, engaging, and well-organized. Team members exhibit strong collaboration and contribute significantly to the project's success.

  • 4 points: The project shows solid innovation and technical implementation, with a clear potential for impact. The presentation effectively communicates key ideas but may lack some polish or engagement. Team members collaborate well but may have minor areas for improvement.

  • 3 points: The project meets basic requirements and demonstrates some innovation and technical competency. The presentation is adequate but lacks clarity or engagement. Team members work together adequately but may have limited collaboration or contribution from all members.

  • 2 points: The project falls short in innovation, technical complexity, or impact. The presentation is unclear or poorly organized, making it difficult to understand the project's significance. Team members show little collaboration or contribution to the project.

  • 1 point: The project lacks innovation, technical complexity, or impact. The presentation is confusing or unstructured. Team members demonstrate minimal collaboration or contribution to the project.