TSA Competitions: choosing an event is part of the challenge

Editorial overview

TSA Competitions are best understood as a school-based programme rather than one uniform contest. TSA describes its competitions as part of an intracurricular programme connecting STEM skills with leadership and career development. That history still shows in the event catalogue: technical knowledge matters, but so do planning, documentation, communication and the ability to work within a chapter.

TSA offers separate middle-school and high-school competitive-event programmes spanning individual and team formats. TSA events deliberately mix technical work with documentation, interviews, presentations and teamwork rather than using one common contest format. This breadth is the programme's strongest feature and its main complication. A student can find a credible match for interests ranging from coding and structural design to video production and leadership, but a chapter that chooses events casually can spend months preparing work that does not suit its members.

At the National TSA Conference, the ten finalists in each event are named and the top three receive trophies. That event-by-event structure is more revealing than a single overall ranking: TSA rewards specialised preparation inside a broad community. CompeteMap's view is that the programme is most worthwhile when a teacher and students treat event selection as an early design decision. The burden can be heavy—membership, chapter coordination, state rules, long projects and travel all matter—but the combination of making, explaining and defending technical work is unusually substantial.

Quick Facts

For current dates, eligibility and registration details, see the TSA Competitions competition page.

Checked on 2026-09-03.

Review Evaluation

Rated Advanced. Preparation varies by event and can combine technical design, construction, testing, documentation, presentation and teamwork over several months.

Start with the event, not the trophy

Choose an event by reading its current guide from beginning to end. A title such as Coding, Structural Design and Engineering, or Promotional Design gives only a rough idea of the work. The actual rules may combine a pre-conference file, an onsite test, a physical object, an interview or a presentation. Make a one-page requirements map before committing: deliverables, team size, checkpoints, materials, judging stages and conference obligations.

Students enter through an affiliated school TSA chapter and its advisor. That means fit depends partly on local capacity. Before choosing an ambitious build event, confirm that the chapter has the workspace, supervision, budget and calendar to finish it safely. If those resources are limited, a well-matched communication, research or software event can be a better choice than a project selected only because it looks impressive.

Prepare the explanation alongside the object

In TSA, a technically competent product can still be weakened by poor documentation or an uncertain interview. Keep a decision log from the start: what problem was identified, what alternatives were considered, what changed after testing and why the finished design is defensible. This makes the portfolio more accurate and the presentation less rehearsed in the wrong way.

Teams should also practise handoffs. One student may be strongest at building, another at analysis and another at presenting, but judges need to see a coherent project rather than three separate performances. Short mock interviews can expose gaps in shared understanding before the conference.

Understand the pathway before committing

State delegations organise qualifying pathways to the National TSA Conference. State event offerings, schedules and adoption of national rules can differ, so the national catalogue is not a substitute for local instructions. Confirm the chapter affiliation timetable, state conference rules and any limits on the number of events a student may enter.

The top three national finalists in each TSA event receive trophies. TSA publishes results for the National TSA Conference by competitive event. Those outcomes are meaningful, but the programme's deeper value is the disciplined cycle of making, testing, explaining and revising. Students who want a quick, direct-entry contest may find the chapter structure frustrating; students who enjoy sustained technical teamwork can find it unusually rich.

Key Takeaways

TSA is a family of competitions, so the first important choice is the event. Read the exact guide, confirm the local pathway and match the project to the chapter's real resources. Prepare documentation and presentation at the same time as the technical work. The programme rewards students who can make a solution understandable, not merely produce an object or score.

Sources checked

• https://tsaweb.org/competitions
• https://tsaweb.org/about
• https://tsaweb.org/membership/membership-faq
• https://tsaweb.org/conferences/recent-national-tsa-conferences