Submission Guidelines

Please prepare a short presentation answering the points below. We do not need a prototype for this phase—we just want to understand your idea first. A clear presentation helps us evaluate every project fairly.

1. Team Name

   Pick a name that can be used publicly. Keep it respectful and appropriate for a public event.

2. Team Members

   List the names of everyone in your team.

3. Roles

   Briefly describe what each person is contributing to the project. For example: design, research, frontend, backend, writing, video editing, etc.

4. Your Idea

   Please explain your idea using the following structure:

   • Problem Statement: What issue are you trying to solve?
   • Proposed Solution: What are you building and how does it help?
   • Expected Impact and Benefits: Who will benefit and in what way?
   • Resource Requirements: What do you need to make this work? (tools, time, people, etc.)

5. How It Fits the Hackathon Theme

   How does your idea connect to the themes of this hackathon? (e.g. community repair, small shop automation, repair content creation, etc.)

6. Why This Idea Matters

   Why do you think this is worth building? Have you noticed this problem in your own life, online, or in your community?

7. Similar Ideas

   Have you seen any projects or products that are somewhat similar? What makes yours different or more focused on repair or impact?

8. Tech Stack or Tools (if any)

   List any tools, languages, or platforms you plan to use. If you’re not building something technical, you can skip this.

9. How Your Project Works

   Use diagrams or short explanations to show how your project is structured. If applicable, include:

   • What are the main parts of the project?
   • How do these parts connect or work together?
   • What tools or platforms will be used for each part?

10. Anything Else You Want to Share?

    Use this space to mention anything we haven’t asked. For example: what inspired you, early sketches, extra ideas, or what you hope to do next.