Prepare and verify questions

Choose an existing version or create a draft

1. 1

   Look in Problems → Catalogue

   If the intended problem already exists, check its version and package before attaching it to a contest.

2. 2

   Use Problemsetting → New problem for a new draft

   Start with the name and statement, then work through the authoring steps. A draft is separate from a published problem.

3. 3

   Set realistic limits

   In Overview, review Memory (MB), CPU (ms) and Wall (ms). These are problem configuration fields, not published platform maximums. Test your chosen values with representative solutions before the round.

Make the statement and reference solution agree

• In Statement, describe inputs, outputs, constraints and examples precisely.
• In Solution, provide the intended reference solution for the authoring workflow.
• Check that the examples and expected outputs follow the same rules as the statement.
• Confirm the permitted languages and exact runtime needs for the contest with the team. Do not publish an unverified compiler-version promise.

Add tests that distinguish correct and incorrect work

1. 1

   Open Tests → Add case

   Give each case a useful label, input and expected output. Include ordinary cases, boundaries and cases where a plausible incorrect solution fails.

2. 2

   Check expected output deliberately

   The authoring form allows blank expected output for running a case without judging it. Do not leave it blank when the case is intended to check correctness.

3. 3

   Review optional checks only if used

   Configure additional validation or checking only when it is part of your intended evaluation. An optional check that is not configured is not a passing test.

Verify the current draft, then publish

1. 1

   Open Verify and publish → Run the checks

   Wait for the report. Inspect compiler diagnostics, individual case results and the overall state.

2. 2

   Resolve Failing or Error results

   Correct the statement, solution, inputs, expected outputs or limits as appropriate, then run the checks again. SKIPPED means not configured, not passed.

3. 3

   Publish a verified draft

   Use Publish after the draft reaches its verified state. Confirm Published before returning to the contest.

4. 4

   Attach and rehearse

   In Contests → your contest → Problems → Add problem, select the intended version, label and score. Rehearse the candidate workflow with authorized test data before a real assessment.