iGEM High School: research, responsibility and documentation

Editorial overview

iGEM High School is not a science-fair experiment with a larger stage. Teams develop a synthetic biology project over a long season and must document the work through a public wiki, safety submissions, attribution, a presentation and judging materials. The official judging questions examine engineering practice, evidence, likely impact, responsible Human Practices and how clearly the project is documented.

The institutional requirement is equally important. A student cannot register a team independently. A Primary Principal Investigator is responsible for registration, safety oversight, payments and compliance, and a secondary-school team needs an eligible school-based adult in that role. Teams also need appropriate working space, training and access to resources. The first feasibility question is therefore not “What should we engineer?” but “Can our institution support a safe, student-led season?”

CompeteMap sees iGEM as a demanding choice for mature students who want research, engineering and public communication to form one project. It can accommodate laboratory, modelling, software and Human Practices contributions, but it is poorly suited to a loosely assembled group without stable supervision. The strongest teams do not hide unsuccessful experiments. They document how evidence changed the design and distinguish demonstrated results from future claims.

Quick Facts

For current dates, eligibility and registration details, see the iGEM High School Competition page.

Test institutional readiness first

Confirm the Primary PI, laboratory or approved workspace, safety oversight, budget and adult availability before recruiting a large team. If experimental work is not feasible, investigate what modelling or software contribution is permitted, but do not assume a purely conceptual project will meet the team's goals.

Create a responsibility map covering experiments, modelling, Human Practices, safety, documentation, finance and project management. Student leadership matters, but oversight cannot be improvised.

Build the public record while doing the work

Do not postpone the wiki and attribution until the end. Record protocols, data, negative results, external contributions and design decisions as they occur. The official deliverables are how judges understand the project and later teams learn from it.

Human Practices should influence the technical work. Speak to affected communities and specialists early enough for their input to change priorities, risks or implementation plans.

Key Takeaways

• Treat iGEM as an institutionally supported research programme, not a single experiment.
• Secure an eligible PI, safe workspace and realistic resources before choosing the project.
• Build documentation, attribution and Human Practices into the weekly workflow.
• Check current fees, deadlines and deliverables on the CompeteMap and official iGEM pages.

Sources checked

• https://competition.igem.org/registration/
• https://competition.igem.org/about/starting-a-team
• https://competition.igem.org/deliverables/
• https://competition.igem.org/judging/project-prizes