> For the complete documentation index, see [llms.txt](https://docs.gymart.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gymart.org/scoring/index.md).

# Scoring

> Enter scores on the Judges Companion app and manage them from entry to verification.

Out of the box, scoring is simple. Open the Judges Companion app, pick a gymnast, and enter the score. You do **not** have to set up judge profiles or assign judges to apparatus first. A session is ready to score the moment it has gymnasts, and several judges can share a single tablet, taking turns to enter scores.

By default each judge enters two numbers: the **final score** and the **start value**. That is all most meets ever need. You can change how scores are entered, or switch to a full FIG judging panel, whenever you want, but that is optional.

## The basic flow

1. [**Enter scores (Judges Companion)**](/scoring/enter-scores-judges-companion.md) - Judges enter scores on the mobile app. Several judges can share one tablet.
2. [**Enter scores (admin)**](/scoring/enter-scores-admin.md) - Enter or fix scores from the meet admin on a computer.
3. [**Understand score status**](/scoring/understand-score-status.md) - The score lifecycle: not started, in progress, submitted, and verification.
4. [**Handle vault scoring**](/scoring/handle-vault-scoring.md) - One or two vault attempts.
5. [**Export scores**](/scoring/export-scores.md) - Export results as PDF, Excel, or CSV.
6. [**Publish to MeetScoresOnline**](/scoring/publish-to-meetscoresonline.md) - Push final scores to MSO CompleteMeet.

## Choose how scores are entered

Each judge picks their own entry mode in **Judge Setup** on the app. There are two independent settings (how you enter execution, and how you enter difficulty) that combine into four formats, from "two numbers only" (the default) to full deductions with separate D-score components. See [Score entry modes](/judges-companion/index/score-entry-modes.md) and [worked examples of each format](/judges-companion/index/score-entry-mode-examples.md).

## Advanced: FIG multi-judge panels

For a formal FIG competition you can run a full Difficulty (D) and Execution (E) judging panel, with each judge on their own device entering only their part of the score. The app then combines the panel's inputs (including the FIG execution trim) into one final score. This is optional, and most meets never use it.

* [**Set up judge profiles**](/scoring/set-up-judge-profiles.md) - Create a profile per judge. Only needed for FIG panels or QR sign-in.
* [**Assign judges to apparatus**](/scoring/assign-judges-to-apparatus.md) - Map judges to rotations and apparatus roles.
* [**Enter scores - multiple judges (FIG)**](/judges-companion/index/enter-scores-multi-judge.md) - How a D/E panel enters scores.
* [**How FIG execution is calculated**](/judges-companion/index/score-entry-mode-examples.md) - How the app averages and trims E-panel deductions.

## Score configuration

How scores are calculated and ranked is configured per level before the meet, not per judge:

* [**Configure individual score settings**](/levels/individual-score-settings.md) - Tiebreakers, vault decisions, rank method
* [**Configure team score settings**](/levels/team-score-settings.md) - Team score count, selection method
* [**How do tiebreakers work?**](/tiebreakers/index.md) - All tiebreaker algorithms explained
* [**How vault score decisions work**](/levels/vault-score-decision.md) - One vault, average, or best of two
* [**How bump ranks on tie works**](/levels/bump-ranks.md) - Rank numbering after ties

## Related

* [How do I configure competition levels?](/levels/index.md)
* [How do competitions, age groups, and subdivisions work?](/competitions/index.md)
* [How do I set up scheduling?](/scheduling/index.md)
* [How do I view and publish results?](/results/index.md)
* [Glossary](/getting-started/glossary.md)
* [Score settings reference](/settings-reference/score-settings.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.gymart.org/scoring/index.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.