How to Show Your Individual Contributions to a Top VEX Robotics Team on the Common App

When your VEX Robotics team wins a state championship, qualifies for the World Championship, or earns an Excellence Award, every student on the roster can claim that result. Admissions officers know this. The team's record tells them how strong the team was. Your activity entry has to tell them what you did on it.

This takes more care on a top team, because strong teams divide the work sharply. The same team number sits on every trophy, whether a student wrote the autonomous code, rebuilt the drivetrain the night before a regional, or joined in March. You separate yourself by writing about the work you personally owned, in terms a reader can picture and measure.

This guide covers how the Common App activity entry is built, the principles that apply to every role, and what members in each role on a VEX team can claim.

How the Common App Activity Entry Is Built

For the 2026-27 cycle, the Common App renamed its activity section "Activities and Experiences." You still get up to 10 entries, and the character limits are unchanged. Each entry has a position or leadership line of 50 characters, an organization name of 100 characters, and a description of 150 characters, plus fields for grade levels, hours per week, and weeks per year.

Those three text fields do different jobs, and giving each one its own job is the simplest way to separate your work from the team's. The position line names your role. The organization line names the team and carries its record. The description holds what you did.

A strong organization line gives the team number, the school or club, and the team's highest result, such as "VEX V5 Robotics Team 1234A, Example High School; 2026 World Championship qualifier," which uses 82 of the 100 characters. With the team's record placed there, all 150 characters of your description are free for your own work. The position line is optional this year, but on a robotics team it is where your role belongs, so fill it.

Name the competition precisely. In May 2026, VEX Robotics and the Robotics Education & Competition Foundation (RECF), which had run VEX competitions for nearly two decades, ended their partnership. For the 2026-27 season, official VEX events are administered by VEX Robotics with the Global Robotics and Science Foundation and lead to the VEX Robotics World Championship. RECF now runs its own RECF Robotics competitions, which still allow VEX parts and lead to the 2027 RECF STEM World Championship in St. Louis. If your team has results in both circuits, label each result with the circuit it came from.

For hours per week and weeks per year, report the time you personally worked, including time at home writing code or notebook entries. The VEX season runs close to year-round. Each new game is revealed at the World Championship in April, and tournaments run from summer through the following spring, so 40 or more weeks a year is common for a committed member.

Principles That Apply to Every Role

The VEX rulebook lists the roles on a team. Every team must have Drive Team Members, Coders, Designers, and Builders, and many also have Strategists and Notebookers. One student can hold several of these roles at once. Using these titles in your position line gives a reader who knows VEX an exact picture, and your description gives everyone else one.

Name the part you owned. The robot belongs to the team. A lift, an intake, a 15-second autonomous routine, a scouting database, or 140 pages of the engineering notebook can belong to you. Name the subsystem, program, or document, and the reader can see where your work sits.

Measure it with numbers that trace back to you. Team rankings measure the team. Look for numbers that moved because of your work, such as a skills score, the seconds it takes the robot to score one object, a success rate across matches, or the number of teammates you trained. Before and after numbers are the strongest, because they show the change you caused.

Lead with a verb that fits only your work. Designed, wrote, machined, wired, drove, scouted, and trained each tell the reader what your hands were doing. Put the verb first, then the object, then the result.

Count the people you taught. VEX requires a team's work to reflect the skills of the students currently on it, so when a coder leaves, the remaining members must be able to maintain the code. Many teams meet this rule by having experienced members train their replacements. Training a successor is individual work that keeps paying off after you graduate, and it belongs in your description.

Pull your specifics from the team's records. Judges at VEX events ask questions such as "Who was the primary programmer?" and "Which team members built the robot?" The engineering notebook rubric judges use asks for every entry to carry a date and the names of the students who contributed. If your team keeps its notebook that way, it already holds the dates, test results, and design iterations you need for a precise entry.

Drivers

In this season's V5 game, Override, each match opens with a 15-second autonomous period, when robots run on code alone, followed by 1 minute 45 seconds of driver control. Drivers are the students holding the controllers during that second stretch.

Your most individual number is your Driving Skills score. Driving Skills is a one-minute solo run, with one robot on the field and no opponents, and scores are ranked at each event and worldwide. If you were your team's only driver, that score measures your driving on your team's robot, so report it with the best rank it earned, such as your state or world standing.

Beyond that score, count the matches you drove, describe the practice routines you designed, and give the before and after numbers they produced. If you worked with the coders on the controller layout, such as which button runs which mechanism and how sharply the robot turns, say so. Some teams split control between two drivers on two controllers, and if yours did, name the mechanisms you ran.

A driver's description might read "Drove all 64 matches at 9 events; designed timed practice drills that cut scoring cycles from 11 to 7 seconds; Driving Skills 4th in state," which uses 138 of the 150 characters.

Coders

Coders write the autonomous routines and the driver control code behind every button. Your clearest individual number is the Autonomous Coding Skills score, a one-minute solo run in which the robot scores on code alone. Report it with its best rank, the same way a driver reports Driving Skills.

Match results give you a second set of numbers. Each match's 15-second autonomous period decides an Autonomous Bonus for the alliance ahead when it ends, and an Autonomous Win Point, a ranking bonus for an alliance whose robots complete a set list of tasks in that window. If your routines earned these in most of your qualification matches, give the count.

Name your techniques, and keep the names concrete. Odometry, which tracks the robot's position on the field from wheel and sensor readings, and PID control, which slows the robot smoothly as it nears its target, are both recognizable to engineering readers. This season's game also rewards vision and color sensors that let a robot find objects on its own, so if you wrote that code, name the sensor and what it let the robot do.

VEX rules bar teams from using AI language models to write or improve competition code, and they require students to understand any outside library they use well enough to recreate it. The code you wrote is yours to claim in full. If you built on a public library, describe what you added to it. If you contributed to an open source library that other teams use, such as LemLib or EZ-Template, or published tutorials other coders learn from, that work reaches past your own team, and the number of teams using it belongs in your description.

A coder's description might read "Wrote odometry and PID motion control in C++; built 6 autonomous routines; raised Autonomous Coding Skills score from 18 to 52; trained 2 new coders," which uses 148 characters.

Builders

Builders assemble, maintain, and repair the robot. Judges give the Build Award to a robot that is durable, reliable on the field, and built with attention to safety and detail, and those same qualities are what your description should measure.

Name the subsystems you built and how many versions of each you produced. Reliability is your strongest number, so count the consecutive matches your mechanisms ran without a failure, or the failures you eliminated after a fix. Repair speed matters at tournaments, where the gap between matches can be a few minutes, so if you rebuilt a broken mechanism in that window, say how fast. Weight you removed, friction you reduced, and wiring you reorganized so the robot stopped losing power mid-match all count.

V5 rules allow a limited amount of custom plastic that students cut and shape themselves. If you designed and fabricated custom parts, name them and the problem each one solved.

A builder's description might read "Built and maintained drivetrain and lift; redesigned intake mounts after 4 match failures, then ran 40 straight matches with no mechanical fault," which uses 144 characters.

Designers

Designers decide what the robot's mechanisms will be before anyone builds them, usually in CAD (computer-aided design) software such as Onshape or Fusion 360, which lets you model every part in 3D and check that it fits before a single piece of metal is cut.

Name the mechanisms you designed, the number of iterations each went through, and what changed between them. The reasoning behind a design is your work too. If you analyzed the game, compared alternatives in testing, and chose the design the team built, describe that sequence with its numbers, such as how much faster or lighter the final version was.

Two judged awards map closely onto design work. For the Innovate Award, a team submits one novel design element and documents its development from first idea to the version used at the event. The Create Award recognizes a creative engineering solution to a challenge in the game. If the element your team submitted, or the solution judges recognized, was your mechanism, you can claim that connection directly.

VEX rules let teams draw inspiration from other teams' designs as long as they credit the source and make meaningful changes. If your mechanism started from another team's idea, describe what you changed and why, since that shows engineering judgment.

A designer's description might read "Designed lift and intake in Onshape over 5 iterations; my lift was the team's Innovate Award submission at 3 events and won it at 2," which uses 131 characters.

Notebookers

The engineering notebook is the team's record of its design process, covering the problem at each stage, the solutions considered, the tests run, and the decisions made. Judges score it against a rubric. It is central to the Design Award, which recognizes how well a team documents and explains its engineering process through the notebook and an interview with judges. The Excellence Award, the top award at a VEX event, requires everything the Design Award requires plus strong rankings on the field.

Your individual numbers are your share of the notebook and the systems you built for it. Count the pages or entries you wrote, and since the rubric asks for contributors' names on each entry, that count should be easy to find. Name the templates, testing formats, or organization schemes you created that the whole team used. VEX rules bar anyone outside the team from editing the notebook and prohibit using AI language models to write it, so the writing you did is yours to claim.

Many notebook leads also prepare the team for judge interviews, where the rubric rewards teams in which most members can explain their own contributions. If you ran those preparations or led the interviews, say how many events you did it for and which judged awards followed.

A notebooker's description might read "Wrote 140 of 210 notebook pages; built testing templates used in every design cycle; led judge interviews at 8 events (3 Design Awards)," which uses 135 characters.

Strategists and Scouts

Strategists decide how the team plays the game, starting with the analysis of each season's rules that shapes what the robot is built to do. Scouts gather data on other teams at tournaments. The two roles meet at alliance selection. After the qualification matches, the top-ranked teams invite partners to form two-team alliances for the elimination rounds, and each team sends a student representative to make or accept those invitations.

If you wrote the game analysis, name the design decisions it drove, such as the scoring method the robot was built around. If you built a scouting system, whether a spreadsheet, a database, or an app, give the number of teams it tracked and what it measured. If you made your team's alliance picks, count the events and say how far those alliances went.

Teams that are invited rather than doing the inviting still use scouting data to plan each match with their partners. If your data set those plans, describe the decisions it informed.

A strategist's description might read "Built scouting database tracking 120 teams; made alliance picks at 4 events, 3 reaching finals; wrote season game analysis that set robot design," which uses 144 characters.

Drive Team Coaches

A team may send up to three Drive Team Members to the field for each match, and adults may not stand with them. Besides the drivers, that group usually includes a student coach who watches the whole field and calls strategy. In Override, drive team members also feed extra game pieces into loaders at the edge of the field during the match, a job that often falls to the coach.

The coach's work happens in conversation, so describe the decisions you made. Count the matches you coached and the level of the biggest ones. If you met each alliance partner before matches to divide up the field, say so, since that planning is yours. If you ran the team's match loading, give the speed or consistency you reached. Drive team members are also the ones who may raise a ruling with the head referee, and handling those conversations calmly at a high-stakes event is worth a phrase if space allows.

A coach's description might read "Called strategy in 70 matches, including Worlds eliminations; planned roles with every alliance partner before each match; ran our match loading," which uses 144 characters.

Captains and Team Leaders

Captain sits outside the VEX rulebook's list of roles, so each team defines it differently. A reader learns what your captaincy involved only from your description, which makes the description carry more weight here than in any technical role.

Judges evaluate how a team manages its time, people, and resources, and that is the core of a captain's work. Describe the schedule you set and the deadlines it met, how you assigned tasks, and the meetings you ran, such as weekly design reviews. Recruiting and training new members, settling disagreements over design direction, and raising money for parts, registration, and travel are all leadership with concrete results. If your school or club fields several VEX teams under one number with different letters, such as 1234A and 1234B, and you led the whole club, give the number of teams and students.

Many captains also hold a technical role. Put both in the position line, such as "Captain and Lead Coder," and give each a clause in the description.

A captain's description might read "Set build schedule for 6 members; ran weekly design reviews; raised $8,400 from 5 sponsors to fund parts and Worlds travel," which uses 122 characters and leaves room for a technical clause.

Outreach, Mentoring, and Program Building

Some of the most individual work on a top team happens away from the robot. Founding or mentoring teams in the VEX IQ Robotics Competition, VEX's program for elementary and middle school students, running a summer camp, teaching workshops at a library, organizing a tournament at your school, and volunteering as a referee at other events all belong to the students who lead them.

Decide whether this work earns its own entry. If it has its own participants, schedule, and results, such as a middle school program you founded that now runs without you in the room, give it a separate activity entry with the program's name on the organization line. If it was a smaller part of your team role, fold it into your main robotics entry as one clause.

A separate outreach entry might read "Founded VEX IQ program at 2 middle schools; trained 5 teammates as mentors; 34 students on 8 teams, 3 qualified for state," which uses 121 characters.

Multiple Roles and Progression Across Years

On a small team, one student often designs, builds, and codes, and the VEX rulebook explicitly allows a single student to hold several roles. Put the two roles that took most of your hours in the position line, such as "Lead Coder and Primary Driver," and give the others a clause each in the description.

If your role grew over four years, the position line can show the path. "Builder (9), Lead Designer (10), Captain (11-12)" fits in 48 of the 50 characters, and the grade levels field confirms the span. Your description can then focus on your most recent role and add one earlier milestone, such as the first mechanism you designed.

If your school or club runs several teams and you moved from one to another, put the team you finished on in the organization line. When the move reflected a step up, such as joining the club's top team after a strong first season, a short clause in the description makes that clear.

The Honors Section and Additional Information

The Common App's Honors section holds up to five honors, each with a 100-character title, a grade level, and a level of recognition (school, state or regional, national, or international). Your team's biggest results belong here, such as a Tournament Champion title, an Excellence Award, or a Robot Skills Champion award, which goes to the team with the highest combined driving and coding skills scores at an event.

When an award maps onto your role, the title can say so. "Think Award, VEX V5 State Championship (lead coder on Team 1234A)" uses 65 characters and ties the team's programming award to the student who wrote the code. The same works for a notebook lead and a Design Award, or a designer and an Innovate Award. List each award once, in Honors, and let your activity description hold the work behind it.

The Additional Information section now allows 300 words, down from 650. If your team's division of labor takes more than 150 characters to explain, a few sentences there can say which subsystems, programs, or notebook sections were yours, and can link to a code repository or a portfolio of your CAD work.

Beyond the Activity List

Your activity entry states what you did. An essay can show how you think while doing it. Build any robotics essay around a problem you personally worked through, such as an autonomous routine that failed at a regional and the night you spent finding out why. A championship belongs to the whole team, while the decisions you made on the way there belong to you alone.

If your team's faculty advisor writes a recommendation for you, give them specifics they saw firsthand, such as the sessions where you trained new coders, the design review you ran, or the repair you made between matches. A letter built from what the advisor watched you do will describe you as an individual rather than as a member of a strong team.

Schools with strong engineering programs often accept supplementary portfolios. MIT, which uses its own application, offers an optional Maker Portfolio reviewed by faculty, and it accepts team projects as long as you explain your own part. CAD renders of mechanisms you designed, excerpts of code you wrote, and notebook pages you authored are exactly the material such a portfolio is built from.

Work With Cosmic College Consulting

Cosmic College Consulting's team of PhD-credentialed admissions consultants specializes in STEM applicants, including students on competitive robotics teams. We help you identify the work that was yours, find the numbers that measure it, and fit it into your activity list, Honors entries, essays, and portfolio. Schedule a consultation to start building yours.