Robotics competitions score two very different things at once: what the robot actually does on the field, and what the team can explain about how they built it. Get the split wrong and either the fastest robot wins regardless of craftsmanship, or a slick presentation outscores a robot that barely moved. This guide walks through how organisers typically structure robotics competition scoring — field/mission points, judged interview rounds, tie-breaks — and how to run the whole thing without a spreadsheet war room.
Two scoring tracks, not one
Most school and college robotics contests (FLL-style, VEX-style, or a custom in-house format) run two tracks that are scored and ranked separately, then combined for an overall result:
- Field / mission score (objective): points for completing tasks on a physical field within a time limit — moving objects, hitting targets, completing an autonomous run, parking in a zone. A referee or scoring app records the point value per task as it’s achieved; the total is a hard number, no opinion involved.
- Judged categories (subjective): a panel interviews each team away from the field and scores things the field score can’t show — robot design and engineering choices, the build/programming process, teamwork, and how well the team can explain their own code and mechanisms. This runs on a criteria rubric exactly like a judged Arts item, with each judge marking a printed or digital sheet.
Keeping these as two visibly separate numbers — rather than quietly blending them into one mystery score — is what keeps both the fast-but-rough teams and the polished-but-slow teams able to see exactly where they stood.
How the field/mission score usually works
A typical field round has a published points table — for example 15 points for moving an object into a zone, 10 for an autonomous task completed without human control, 20 for a precision placement. Common structural choices organisers have to settle before day one:
- Multiple attempts, best score counts. Most formats give each team 2–3 timed runs and keep only the highest-scoring run, which smooths out one bad start.
- Autonomous vs. driver-controlled split. Many formats award bonus points for anything the robot does without a human at the controls, scored separately from the driven portion of the same run.
- Penalties for field contact or interference. Touching a restricted zone, a human reaching onto the field, or a robot exceeding a size limit typically costs points rather than disqualifying the run outright — published in advance, not improvised mid-event.
- A hard time limit per run, usually 2–3 minutes, enforced by a visible countdown so both the team and the referee are working off the same clock.
Judged-category rubrics
The interview/judged side usually splits into named categories with its own weight — a common pattern is Robot Design (mechanism choices, build quality), Innovation Project or Programming (the logic behind the code, not just that it works), and Core Values/Teamwork (how the team collaborated and communicated). Each category gets its own criteria rubric and its own judge panel or rotation, scored the same way a stage item’s judges mark a printed sheet — numeric scores per criterion, signed, and tabulated centrally rather than averaged by each judge on paper.
Combining the two tracks into a result
Organisers generally pick one of three approaches, and all three are legitimate — the only rule is to publish the choice before the event, not after:
| Approach | How it works | Best for |
| Field score decides the winner; judged awards are separate trophies | Field ranking is the official placing; “Best Design”, “Best Innovation” etc. are standalone recognitions alongside it | Competitions where the physical task is the headline event |
| Weighted combined score | Field score and judged score are each converted to a percentage of their own maximum, then combined at a published weight (e.g. 60% field / 40% judged) | Formats that want to reward both engineering and performance equally |
| Judged categories gate advancement | A minimum judged score is required to advance regardless of field score, keeping a fast-but-unsafe or unexplainable robot out of finals | Multi-round formats with a qualifying round before finals |
Tie-breaks
A sensible published order, decided before the event, typically runs:
- Highest single field run (not the combined total) between the tied teams
- Highest autonomous-only score, if the format has one
- Fewer penalties incurred across all runs
- Earlier run time in the schedule, as a last resort
What to settle before the day
- Robot size/weight limits and what happens if a robot fails inspection
- Whether teams can repair/modify between runs, and how long a repair window is allowed
- Field setup consistency — identical field dimensions and object placement for every run, checked between teams
- Who can be at the controls during the driver-controlled period (one driver only, or a driver + operator)
- Age/grade divisions, since a Junior division robot and a Senior division robot are rarely held to the same field or time limit
Running it on eTalenter
Set a robotics competition up as a Team item (most robots are built and run by a multi-member team, registered as one entry) under Assign Competitions to Groups, with age/grade divisions set up the same way as any other age-group split. Since the field score is a fixed, objective number rather than a judge’s opinion, record it through Assign Results Manually — the same path used for Sports items — one row per run, keeping the best attempt. Run the judged categories (Design, Programming, Teamwork) through the normal judging-and-scoring panel with a criteria rubric per category, exactly as a judged Arts item is scored. Keep the two tracks visible as separate columns in Review & Assign Winners before deciding how they combine into a final placing, then publish results and print certificates per category once tabulation is confirmed.
FAQ
Does a robotics competition need judges at all, or just a scoreboard?
Most formats use both — a referee or app for the objective field score, and a separate judge panel for the design/process categories that a scoreboard can’t capture.
What happens if a robot breaks mid-run?
The run’s field score typically stands as scored up to that point; most formats don’t allow a restart within the same timed attempt, though teams usually get another scheduled run later in the day.
Can one student build and run the robot alone?
Rules vary by organiser — some allow individual entries, but the common pattern (and the one the Team-value judging categories assume) is a small multi-member team sharing build and drive roles.
Is the judged interview scored the same way as a stage item?
Yes — a printed or digital criteria rubric per category, marked by each judge on the panel and tabulated centrally, the same mechanism used for any judged Arts item.
How many attempts does a team usually get?
Two or three timed runs is common, with only the best-scoring run counting toward the final field score.
Related reading: see how multi-judge panels are tabulated in our judge scoring and tabulation guide, how objective results are recorded for other non-judged formats in our coding competition scoring guide, and how ties are resolved generally in how to break a tie in a competition.
Running a school or college robotics competition? See how eTalenter handles mixed objective-and-judged scoring on our competition management platform, or open a live demo and log in as a demo coordinator or judge — no sign-up required. Questions? Message us on WhatsApp at +91 96056 56508 or email support@etalenter.com.
Was this guide useful?
