On the day & after · Fixing mistakes

Fix the source, then check the public view

When something's wrong, slow down. Confirm the competition, category, and round first, make one clean fix at the source, then verify it shows correctly everywhere. This page covers the common corrections and how to make them safely.

Wrong score

Wrong scores happen when a judge enters the wrong number or the system misses a zone. Never ask a judge to guess a correction on the floor. Always fix the score from the chief or admin view.

Important

Always confirm you're on the right athlete, category, and round before changing a score — a fix applied to the wrong record creates two problems.

1Open the chief view for your discipline.
2Find the athlete's record and locate the attempts table.
3Edit the attempt value directly. GripRank recalculates totals automatically.
4Save the change and watch the leaderboard update live.

Each discipline handles the chief view slightly differently:

Boulder chief view Speed chief view Lead chief view

For speed finals, match outcomes can be corrected via the API endpoint /api/speed/override (POST). Use this only for deliberate head-to-head match overrides, not for re-climbs.

Wrong athlete

Always confirm the name, bib, and category before saving. A single keystroke error affects the entire leaderboard.

Judge overlap

If a judge is still scoring, coordinate a quick hold before editing. Their next save could overwrite your correction.

Display patching

Never edit only a scorecard. Fix the underlying data so exports and public pages stay consistent.

After saving, refresh the chief page to confirm the change is live. Then refresh the public hub to verify the correction propagated. If the hub is frozen, unfreeze it, apply the fix, verify, and re-freeze before continuing.

Wrong athlete data (name, bib, category)

Names, bib numbers, and categories must match the official competition documents. If you spot a mismatch, fix it at the source — the import page or the startlist — rather than patching the display. Editing only the scoreboard or a scorecard creates a ripple effect. The underlying data stays wrong, so exports, public pages, and downstream records will all carry the error forward.

1Navigate to the import or startlist page for your discipline.
2Locate the athlete record and correct the name, bib, or category.
3Save the change and wait for the system to sync.
4Verify the correction appears on the chief view and the public hub.

Boulder import Boulder startlist Speed startlist Speed import Lead import Lead startlist

Wrong round or route setup

A mis-set route or incorrect round count breaks the entire flow. Catch this early and fix it before the next athlete starts. If routes are missing or the count is wrong, judges will submit attempts that don't match the course. The system will reject them or score them incorrectly, causing confusion on the floor and in the chief view.

1Pause scoring for the affected category if athletes are still climbing.
2Open the setup page for your discipline.
3Correct the route count, zone positions, or round parameters.
4Save the setup and confirm the course matches the printed route sheet.
5Resume scoring and brief the judges on the correction.

Boulder setup Speed admin Lead setup

After any correction

Every correction requires a verification loop. Never assume the fix propagated automatically.

1Refresh the staff page (chief or admin) and confirm the change is live.
2Refresh the public hub and verify the correction appears correctly.
3If the hub is frozen, unfreeze it, apply the fix, verify, and re-freeze.
4Brief the announcers and volunteers on what changed so they stop reading old information.

Tip

Keep a quick log of every correction you make. Note the athlete, the original value, the corrected value, and the time. This saves time during audits and helps you spot recurring system quirks.

Publishing & freezing