> 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/understand-score-status.md).

# Understand score status

> Every score carries a status that tells you where it stands, from not yet entered to final. Here's what each one means and what you can do at each stage.

A score doesn't jump straight into the final results. It carries a status that changes as a judge enters it, submits it, and (if needed) revokes it. Knowing these statuses lets you see at a glance what's done, what's in progress, and what still needs attention during the meet.

## Prerequisites

* You are entering scores through the [Judges Companion app](/scoring/enter-scores-judges-companion.md) or the [admin interface](/scoring/enter-scores-admin.md).

## The five statuses

A score is always in one of these states:

| Status          | What it means                                                                                                                        |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| **Not Started** | No one has entered this score yet.                                                                                                   |
| **In Progress** | A judge has started entering the score and saved it, but hasn't submitted. The values are a work in progress.                        |
| **Submitted**   | The judge submitted the score. This is the finished state: the score is official, shows on the leaderboard, and feeds into rankings. |
| **In Review**   | A submitted score was revoked back for editing. The previously entered values are kept so the judge can adjust and resubmit.         |
| **Scratch**     | The gymnast did not compete. They are withdrawn from this event and removed from rankings.                                           |

There is no separate "verified" status. Verification is tracked alongside the score as its own marker (see below).

## How a score moves between statuses

```
Not Started → In Progress → Submitted
                                 │
                          (judge revokes)
                                 │
                 ┌───────────────┴───────────────┐
          Put in review                    Reset completely
                 │                                │
            In Review                        Not Started
        (keeps the values)              (clears the values)
```

A judge revoking a submitted score chooses one of two outcomes:

* **Put in review** keeps everything entered and moves the score to In Review so the judge can fix a value and resubmit.
* **Reset completely** wipes the entered values and sends the score back to Not Started, as if it had never been scored.

See [Revoke a score](/judges-companion/index/revoke-score-inquiry.md) and [Reset a score completely](/judges-companion/index/reset-score.md) for the steps.

## Verification (head judge)

Separate from status, a head judge can mark a submitted score as **verified** to signal it has been checked. In Meets you can filter scores by Verified or Unverified, and verification can be undone. Verifying a score does not lock it or change its status: a verified score is still a Submitted score, and it can still be revoked if a correction is needed.

## What this means if you're a judge

You enter your scores and submit them, which moves the status to **Submitted**. If you spot a mistake afterward, revoke the score: choose **Put in review** to keep your values and edit them, or **Reset completely** to start over. Once you resubmit, the status returns to Submitted.

## What this means if you're an admin

You see every submitted score across all apparatus. The head judge can mark scores as verified once they look correct, and you can filter on verification to see what still needs a check. Submitted scores already feed the results, so verification is a confidence marker, not a gate.

## Timestamps

The system records a timestamp at each transition:

* **Time submitted** - when the judge hit submit
* **Time reviewed** - when the score was put in review
* **Time revoked** - if and when the score was revoked
* **Last updated** - the most recent change of any kind

These create a full audit trail for every score in your meet.

## What's next

* [Export scores](/scoring/export-scores.md)

## Related

* [Enter scores with the Judges Companion app](/scoring/enter-scores-judges-companion.md)
* [Enter scores from the admin interface](/scoring/enter-scores-admin.md)
* [How does scoring work?](/scoring/index.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/understand-score-status.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.