Finish the core product
A deadline is useful only when it pushes the team toward a working main action instead of rushed extra features.
Competition Resources
Choose for fit. Verify every rule. Submit what works.
Competitions are useful when they help a team finish, explain, and honestly document a project—not simply because the opportunity sounds impressive.
Current-cycle status
No competitions have been verified for the current cycle yet.
Opportunities will appear here only after the official current-cycle site, eligibility, deadline, required materials, and AI-use rules have been checked and recorded.
Why Compete
Use a competition as a readiness test.
A suitable opportunity asks the team to prove the same things a strong project should already demonstrate.
Explain the problem and product
Preparing a submission tests whether the team can connect a real user and problem to what the product actually does.
Document the work honestly
Roles, contributions, research, limitations, outside resources, and AI assistance should all be clear before submission.
Fit First
Check the opportunity before investing the team’s time.
A project should enter only when the fit is real, the product works, the team understands the requirements, and the submission can be completed honestly and on time.
Review the project workflowDoes this opportunity match?
- The students and team size are eligible.
- The project fits an official category.
- The main product works and members can explain it.
- The required format and time commitment are realistic.
- School approval, travel, and costs are understood.
Confirm the current cycle.
- Cycle status and official website
- Eligibility and team-size rules
- Deadline, time zone, and every submission item
- AI-assistance and disclosure policy
- Fees, permissions, travel, and school requirements
Record who verified each item and when. If a rule is unclear, contact the organizer instead of guessing.
Typical Submission Package
Prepare the common pieces. Follow the specific rules.
These items are common, not guaranteed requirements. The official competition checklist always decides what the team must submit.
01Working public URLTested today on another device
02Repository and READMEPurpose, setup, and contributions
03Project descriptionUser, problem, product, and evidence
0460–90 second demoThe core action from start to finish
05Screenshots or pitch deckOnly when the official rules request them
06Team and role recordsWho completed and can explain each part
07AI-use disclosureComplete, accurate, and policy-aligned
08Required permissionsParent, school, or other official approvals
Demo Plan
Show one real action completely.
- 0:00–0:15The problem
Name a specific person and problem.
- 0:15–1:05The demo
Record the core action from start to result without skipping.
- 1:05–1:30Learning and next step
State what the team learned and what comes next.
Record the core demoKeep the live site readyUse realistic sample dataNever ask viewers to imagine a feature
Open the full Demo lesson
Honest Submission
AI assistance is part of the story, not something to hide.
Follow the competition’s official AI policy and answer disclosure questions fully.
Say what AI didDescribe generated code, media, research help, or other assistance accurately.
Say what students didIdentify the decisions, direction, testing, review, design, and documented contributions.
Claim only what worksDo not present incomplete features, invented results, or exaggerated user numbers as real.
Explain the productThe team must understand the main feature, data, tools, limitations, and what could go wrong.
Competition Ready
Ready means verified, working, explainable, and complete.
Do not begin serious submission work while the main action remains incomplete.
- 01Eligibility and every current-cycle rule are verified.Official sources, verifier, and verification date are recorded.
- 02The public product opens and the central action works.The live version has been tested on another device.
- 03The team can explain the problem, product, technology, and limitations.No important answer ends with “AI wrote it.”
- 04The recorded demo shows a complete result.Only finished features appear.
- 05Every required material and permission is complete.Whenever possible, the package is ready one week before the official deadline.
- 06Contributions and AI use are disclosed honestly.The submission matches what the team actually built and understands.
Build before you submit