Technovation 2027 Senior Prep: Build What People Can Use

Choose what a user needs to do before choosing your technology. Technovation 2027 accepts working digital solutions that use code and/or AI, including mobile apps, interactive web apps and AI agents. A static website is not eligible.

At our November 5, 2026 check, the official registration platform showed registration closed. This is a preparation guide. Recheck the organizer before registering.

Match the team to the division

The worldwide program serves ages 8-18, including U.S. and Canadian students. Teams have 1-5 members; Senior is determined by the oldest member being 16-18 on August 1, 2027. Participation is free; Technovation does not provide technology.

Girls and Mixed tracks are available globally, but local support varies. Toronto's chapter does not run the co‑ed pilot. Check the participation options that fit your team.

Keep two deadlines separate

Registration closes March 11, 2027 at 23:59 UTC. Project submission closes May 5, 2027 at 17:00 PDT. Preserve the distinct timezones when planning from the official timeline.

Prepare the Senior deliverables

Submit one combined pitch/demo video of up to 4 minutes, technical files or access links, English written responses and a Business Canvas. A non‑English video needs English subtitles. For a web app, the technical requirement is a code ZIP plus a live interactive URL; other formats differ.

The submission guidelines and division rubric control the full checklist. Test with real users and show at least two iterations. Keep the feedback and what changed.

Keep the decisions student‑owned

AI assistance is allowed. Disclose the tools, affected parts and how you verified or built on their output. AI cannot replace students' thinking or contributions.

Mentors may guide learning and resources, but cannot create the submission. Whether a mentor is mandatory for 2027 is not confirmed. Profiles include parental consent; students under 16 on August 1, 2027 need approval on file before identifiable information is entered.

HAEA preparation advice: keep a log with the user problem, the test, feedback, the change and tools used. Start with one test you can learn from; this is not an official submission template.