Review results and session activity

Open the contest’s Submissions tab

1. 1

   Check the contest and candidate

   Go to Contests, open the intended round and choose Submissions. Match the candidate and problem before interpreting a row.

2. 2

   Read the evaluation state

   Queued and running are not final results. For completed attempts, inspect the verdict, passed tests, execution time and memory where present.

3. 3

   Allow for pending or delayed results

   The list refreshes automatically. If results remain pending or a connection problem makes the display uncertain, ask the organizer to confirm judging status before making a decision.

Web workspace · Example data View larger

Results & submission review

Zoom in

Zoom in to read the interface details.

Submission results and export controls. Synthetic example data. Example data.

Use participant history for context

Open Participants and the relevant participant profile to inspect the available Contests and Submissions history. Confirm you are comparing the same person, problem and round.

Review the available attempt outcomes rather than treating one successful sample run or a saved draft as the final result. If you need source-level review or evidence that is not available in your workspace, agree how it will be provided before the round.

Separate the question’s score and verdict from participation incidents. Apply the same agreed evaluation criteria to each candidate.

Read Invigilation alongside results

1. 1

   Check Help requests

   Read the candidate’s reported issue, category, timestamp and resolution state. A sent report does not prove that the underlying issue was resolved.

2. 2

   Check Live sessions

   Use session state, Last contact and Flags to identify cases needing follow-up. A long gap in contact may be a device or connection interruption; a reopened session needs its recovery context.

3. 3

   Check Entry-gate reports

   These describe what a device reported before entry. Missing reports, passing checks, failures and authorized exceptions are different states; none by itself proves identity or misconduct.

Export the result you actually need

1. 1

   Choose the appropriate export

   From Submissions, use Standings CSV for standings or Submissions CSV for attempt records. Export roster, in Participants, serves a different purpose.

2. 2

   Check the file before relying on it

   Confirm the contest, candidates and fields match your review task. If judging is still in progress or an authorized rejudge occurs, regenerate exports after results are confirmed.

3. 3

   Keep access controlled

   Store and share exports only through your organization’s approved workflow. A downloaded file is a separate copy; app access controls do not manage where it is forwarded.

Close the review with a clear explanation

Resolve outstanding incidents or result questions with the organizer before treating the review as complete.

Record the decision and its basis through your organization’s agreed process. Tell candidates when and how results will be shared and where to raise a question.

Do not include another candidate’s work, results, credentials or personal information when explaining an individual outcome.