School Management · 2026 · Preparation Handbook
Before You Build, Know the Rules.
Understand the hackathon, prepare your team, learn the basics, and come ready to build. Everything you need to know before you enter the hackathon.
Know This First
The 8 things every participant should know before anything else.
3 Members
Every team must have exactly 3 members.
1 Team Leader
Each team has one Team Leader — the laptop owner.
1 Laptop
Only the Team Leader may bring/use a laptop for the project.
Build From Scratch
Your project must be created during the hackathon.
Be Original
Do not copy another team's idea, code, or design.
AI Is Allowed
ChatGPT, Gemini, Claude, Copilot and similar tools are allowed.
Understand Your Work
You must be able to explain everything you submit.
School Management
Your project must relate to the school-management theme.
Hackathon Rules
Official rules — read carefully. Everything below is enforced on event day.
Team Rules
- Exactly 3 members per team
- One Team Leader per team
- Each student may participate in only one team
- Students from any class may participate
- Team members should collaborate throughout the event
Laptop Rule — One laptop, three contributors
Only the Team Leader may bring/use a laptop for the project.
Other members contribute through:
- Research & planning
- UI/UX & design
- Testing & feedback
- Documentation & presentation
- Idea development
Project Rules
- Project must be created from scratch during the hackathon
- Do not bring a pre-built project
- Do not copy another team's project, code, or design
- Solve a meaningful school-management problem
- Every member should be able to explain the solution
AI Rules
Allowed: ChatGPT, Gemini, Claude, GitHub Copilot, and similar tools.
- You must understand generated code
- You must be able to explain your implementation
- AI must not be used to copy another team's project
- Teams remain responsible for their final project
Prohibited & Disqualification
Plagiarism or copying, pre-built projects, unauthorized devices, outside developers, hacking school systems or infrastructure, interfering with another team, false information, or serious misconduct may result in disqualification. Organizers and judges have final authority.
How the Hackathon Works
Seven steps from team to presentation.
- 01
Form Your Team
Create a team of exactly 3 students. Choose one Team Leader who will own the laptop and repository.
- 02
Choose a Problem
Think about a real problem in school management — something students, teachers or parents actually face.
- 03
Plan Your Solution
Define problem, target users, solution, main features, and technology stack before coding.
- 04
Build
Create the project from scratch during the hackathon. Focus on a working MVP first.
- 05
Test
Test continuously and fix important problems. Make sure the core flow actually works.
- 06
Document
Prepare the required documentation — team, problem, solution, features, stack, screenshots and more.
- 07
Present
Demonstrate your project and explain your decisions. Every member should be ready to answer questions.
What Can We Build?
Project idea areas within School Management. You are not limited to these — solve any meaningful school-management problem.
💡 You are not limited to these ideas. Any project that solves a real school-management problem is welcome.
Categories come from event settings · 7 configured
Prepare Before You Arrive
Do not build the final project beforehand. Prepare by learning.
Learn Basic Programming
Pick what matches your role — you don't need everything.
- HTML, CSS, JavaScript
- Python
- React / Next.js
- APIs & Databases
- Git / GitHub
Learn UI/UX
- Layout & navigation
- Forms, buttons, cards
- Responsive design
- Basic usability
Learn Git / GitHub
- Repository, commit, push, pull
- Branch & README
- Collaboration basics
Learn Databases
- Tables, rows, columns
- Relationships & CRUD
- SQL basics
Recommended YouTube Preparation
You don't need to watch everything. Pick the topics that match your role and skill level. Titles only — no links.
Beginner
Programming Basics
- HTML & CSS Full Course for Beginners
- JavaScript Full Course for Beginners
- Programming Fundamentals for Beginners
Git / GitHub
- Git and GitHub for Beginners
- GitHub Crash Course
- Git Commands You Should Know
Web Development
- How Websites Work — Frontend, Backend & Database
- Frontend vs Backend Explained
- How APIs Work for Beginners
Intermediate
React
- React JS Full Course
- React Hooks Explained
- Build a React Project from Scratch
Next.js
- Next.js App Router Tutorial
- Next.js Full Course
- Build a Full Stack App with Next.js
PostgreSQL / APIs
- PostgreSQL for Beginners
- SQL Basics for Beginners
- PostgreSQL CRUD Tutorial
- REST API Explained
- How to Build and Consume APIs
- HTTP Methods Explained
Learn to Use AI — Don't Let AI Use You
AI is allowed, but you must understand the code you submit.
- How to prompt coding AI effectively
- How to debug AI-generated code
- How to ask AI for explanations
- How to review generated code
- How to test AI-generated code
- How to avoid blindly copying code
- How to use AI for brainstorming and documentation
Prepare With Your Team
Before the event, teams may discuss and practice together.
- Team roles & communication
- Problem-solving & feature planning
- UI planning & presentation skills
- Research methods
- Git/GitHub basics & development fundamentals
- AI tool usage
Suggested Team Roles
Even with one laptop, all three members have meaningful responsibilities. These are suggestions — teams may organize differently.
Team Leader / Developer
- Laptop owner
- Main implementation
- Git & repository management
- Integration
Research & Product
- Problem research
- User needs
- Feature planning
- Testing & feedback
Design & Documentation
- UI/UX planning
- Documentation
- Screenshots & demo
- Presentation preparation
- Testing
What Should You Bring?
- ✓Student ID / required identification
- ✓Notebook & pen
- ✓Water bottle
- ✓Charger / power bank if appropriate
- ✓Team information
- ✓Ideas / problem research
- ✓Your learning & practice
- ✓Positive attitude
Only the Team Leader may bring/use the project laptop.
What NOT to Bring / Do
- Pre-built project
- Another team's code or copied project
- Outside developer
- Unauthorized device for project development
- Anything intended to interfere with another team
- Anything intended to hack school systems
Documentation Preparation
What you will eventually need to prepare. This matches the final submission requirements — no second format.
Team Name
Your registered team name.
Project Name
Clear, memorable title.
Members
All 3 members with roles.
Problem Statement
What school problem are you solving and for whom?
Target Users
Students, teachers, parents, admin — who benefits?
Proposed Solution
How your project solves the problem.
Main Features
Key features that deliver the solution.
Technology Stack
Languages, frameworks, database, tools used.
How It Works
User flow and system overview.
Screenshots / Demo
Visual proof — screenshots or demo link.
Challenges
What was hard and how you solved it.
Future Improvements
What you would build next.
Must cover: Team, Project, Members, Problem, Target Users, Solution, Features, Tech Stack, How It Works, Screenshots/Demo, Challenges, Future Improvements.
Judging Criteria
A technically impressive project is not enough. Understand the problem, build something useful, make it original, and present it clearly.
On Hackathon Day
- Read the problem carefully.
- Do not rush into coding.
- Define the MVP first.
- Divide responsibilities.
- Keep communication clear.
- Build the most important feature first.
- Test continuously.
- Keep backups.
- Document while building.
- Prepare your presentation before the final minutes.
- Make sure every member understands the project.
- Focus on a working solution rather than unnecessary features.
FAQ
Quick answers to common questions.
Yes. AI tools like ChatGPT, Gemini, Claude and Copilot are allowed, but you must understand your work and be able to explain it to judges.
Before You Come — Checklist
0/13 · 0%Saved on this device only — frontend-only, no account needed.