SVC Hackathon 2026: Rules & Code of Conduct
Core Principles
- Build with integrity – Your submission should reflect your team's original work and understanding, regardless of the tools used.
- Collaborate respectfully – Value every skill: design, research, storytelling, strategy, and code all matters.
- Stay on theme – Solutions must address technology-based environmental problems (tech-enabled ≠ code-only).
What You Can Build (All Paths Welcome)
Your project can take many forms. Examples include:
- Code-Based: Web app, mobile prototype, script, API integration
- Design/UX: Wireframes, user journey maps, Figma prototypes, service blueprints
- Research/Strategy: Problem analysis, impact assessment, policy recommendations, business model canvas
All Projects Are Hybrid
Because every team delivers a presentation, your final submission should integrate both a core solution element (code, design, research, or concept) and supporting communication materials (pitch deck, live demo, storytelling narrative, community engagement plan, etc). For example: a no-code prototype + research brief + slide deck or a script + user flow diagram + live demo.
Rules
Team & Participation
- Teams must have 4–6 members; we encourage mixed-skill teams (e.g. coders + designers + researchers).
- All roles are valid: project manager, UX designer, researcher, presenter, developer, data analyst, etc.
- Team final formation will happen on the day of the event—it's not required to come with a pre-team formed.
- Participants must meet at least one of the following to participate and compete for prizes:
- High school students 16 and over
- Active students currently pursuing a post-secondary degree
- Industry professionals and community members (see prize eligibility below)
- All team members must be present when judging starts for verification of individuals' understanding of their project and their contribution.
Timeline & Workflow
-
Work begins at 9:00 AM PST and ends when submissions close at 4:00 PM PST.
- All project components—whether code, designs, research, pitch decks, or prototypes—must be created during the event window.
- Final submissions must be uploaded before the deadline at 4:00 PM PST—late submissions will not be judged.
- No pre-event development of the core project solution.
Generative AI Usage Guidelines
"A hackathon is a competition of innovation. Outsourcing innovation is against the spirit of the event."
These guidelines apply whether you're writing code, designing slides, researching solutions, or crafting your pitch.
Permitted Uses of Generative AI:
- Debugging, explaining syntax, generating boilerplate you understand.
- Brainstorming layout ideas, generating placeholder copy or images (with attribution).
- Summarizing public sources, refining survey questions, and organizing notes.
- Polishing language, suggesting slide structure, practicing Q&A responses.
- Learning a new tool or concept during the event.
***Use AI as a productive tool rather than a "do everything for you" solution.
Discouraged / High-Risk Uses:
- Generating your core project idea, solution logic, or value proposition.
- Creating presentation content, scripts, or visuals you cannot personally explain or defend.
- Submitting AI-generated work (code, text, images, data) without review, comprehension, and attribution.
- Using AI to replace team collaboration or critical thinking.
Disclosure Expectation:
If your team uses generative AI in any capacity, be prepared to:
- Explain how and why it was used (and by which team member).
- Demonstrate your understanding of the output.
- Attribute AI assistance in your submission documentation (e.g., "Slide 3 copy refined with AI; concept and messaging by team").
Submissions & Presentation Rules
- Submit all required materials via the Devpost:
- Project demo/prototype (code, no-code, or conceptual)
- Presentation materials (slides, script, or visual aid)
- Completed template document
- Presentations: 5–7 minutes + 2–3 minutes for judge Q&A.
- All team members should be prepared to speak to the part of the project they contributed to.
- No pre-recorded demos that obscure real-time functionality (live, interactive, or walk-through demos preferred), however—pre-recorded videos for portfolio under devpost are accepted, just not for presenting.
Code of Conduct
Please report immediately any violations of this code to the SVC Facilitators and the Host so that they can make disciplinary decisions and take action as soon as possible.
- Any participant who threatens the safety of any other person during the hackathon will be removed from the competition.
- There is a very low tolerance for harsh behavior toward any person, especially judges and mentors. Disciplinary action will depend on the severity and be taken at the sole discretion of the hackathon leaders.
Additional Expectations
- Treat all participants, staff, mentors, and judges with respect and professionalism.
- Use inclusive language and be mindful of diverse backgrounds and perspectives.
- Do not engage in harassment, discrimination, intimidation, or disruptive behavior of any kind.
- Respect shared spaces, equipment, and resources.
Enforcement
Prohibited Activities
-
Plagiarism, asset theft, or using unlicensed third-party content (code, images, data, text).
-
Misrepresenting your project's readiness, origin, or functionality.
-
Accessing restricted systems, networks, or data without authorization.
-
Any behavior that violates the Code of Conduct outlined above.
Rule violations may result in warning, point deduction, or immediate disqualification at organizers' discretion.
Remember: This hackathon celebrates diverse talents. Whether you code, design, research, or strategize—you belong here. When in doubt, choose transparency, originality, and teamwork.
By participating in SVC Hackathon 2026, you agree to abide by these rules and the spirit of ethical, inclusive innovation.
