A contest scoreboard covers one contest. For a standing that spans several (a season table, a multi-day olympiad, a league) you create a scoreboard: it adds several contests together into one standing, keyed by space member, so the same person appearing in five contests is one row rather than five.
Scoreboards are listed on the Scoreboards tab of the Contests section. Creating, editing, rebuilding and deleting them needs permission to write contests.
Add scoreboard asks for:
Name, shown as the title of the scoreboard.
Slug: lowercase letters, digits, hyphens and underscores, starting with a letter, unique within the space. It identifies the scoreboard in its public address and in the API, and is accepted anywhere the scoreboard's id is.
Best of: count only this many best contests per member towards the total; zero counts all of them. A contest left out by the rule still shows its score on the row, in muted type, and does not add to the total.
Visibility: Public scoreboards can be read by anyone, including people who are not signed in; Private ones only by members of the space.
All four can be changed later on the scoreboard's Overview tab.
The Contests card lists the contests the scoreboard counts, each with its label, status and problem count. Add contest picks a contest and an optional Label, the column header shown for it, such as "Day 1" or "Practice"; left empty, the contest's name is used. Drag contests to change their order, which is the order of their columns.
All contests on a scoreboard share one format. The first contest added sets it, and a contest in another format is refused.
Adding a contest brings its participants onto the scoreboard as members, so the work is proportional to the size of the contest. Remove stops its scores counting, and a member who was on the scoreboard only through that contest leaves with it.
The Attributes card adds member profile fields as extra columns: school, city, grade, country. Each entry is the attribute key, its type, and an optional Label for the column header; left empty, the profile field's own label is used. Drag attributes to reorder their columns. Removing an attribute removes its column and leaves the members' values untouched.
Each attribute also becomes a filter on the standing, typed from the profile field: numeric fields compare with the usual numeric operators, text fields with equality, contains and starts-with.
The Results tab is the standing. Columns run: rank, name, total score, one column per attribute, then for each contest its own total followed by one column per problem in it. Problem headers combine the contest's position with the problem's letter (1A, 1B, 2A) so the same letter in two contests stays distinguishable. Countries and regions are shown with their names and flags.
Problem cells are the same score cells as on a contest scoreboard, first-to-solve outline and stale marker included. Ties share a rank range, and the official rank covers only officially ranked members while a second rank counts everyone.
The mode switch offers Results, contest time only; Frozen, offered while a contest on the scoreboard is frozen, in which that contest contributes its results as of its freezing time and the others their current ones; and Upsolve, offered when a contest on the scoreboard allows upsolving.
A public scoreboard has its own page on your space's site, at /scoreboards/<slug> (the shorter /s/<slug> leads to the same page), with the same modes, the attribute filters and a preview of each contest. Link to it from a page or a post. A private scoreboard's page opens only for members of the space.
Rebuild recomputes every row from the contest scoreboards, after a confirmation. Rows are kept up to date as contests are judged, so this is a repair rather than a refresh. It runs in the background, a member at a time, and the scoreboard stays readable throughout; follow it in Background tasks.