Route and lane judge training hub
Public, no-auth, mobile-first training for judges who use GripRank during a round: select the correct athlete and route, enter observed results, save/sync cleanly, and call the Chief Judge when a ruling is needed.
1. Observe
What the route or lane judge watches before touching the GripRank screen.
Attempt starts
An attempt starts when every part of the athlete's body has left the ground. Watch the start before tapping any outcome.
Zone control
Award Zone on the attempt where the climber controls the marked Zone hold. If the climber Tops, Zone should also be marked in the app.
Top control
Award Top only when both hands control the finish hold and the judge calls OK. If control is disputed, pause before confirming the app entry.
Skipped problem vs round DNS
If the athlete climbs other boulders but not this problem, leave this problem with no Zone/Top result. Use DNS only when the athlete did not start the round.
Safety and queue pressure
Hold the next start when adjacent problems, landing zones, or crowding make the attempt unsafe. Escalate fairness-impacting delays.
2. Proper start
Boulder judges must know when an attempt has started, because even a false start/no-result can need an app entry.
Know when the attempt starts
For Boulder, the attempt has started once every part of the athlete's body has left the ground/start position. From that moment, GripRank needs an attempt entry even if the climber gets no Zone or Top.
False start still gets recorded
If the athlete false-starts, slips, or comes off before Zone, do not leave it blank. Save a no-result attempt so the app has the real attempt count.
No result is not no attempt
No Zone/Top means no scoring result, but it can still be a started attempt. Record the attempt first; GripRank will handle the scoring impact.
Unsure start call
If you are unsure whether the athlete actually started, pause the entry and call Chief Judge instead of guessing or silently skipping it.
3. Enter in GripRank
What to tap, type, save, and sync in the judge app.
Open the correct row
Select the active round, athlete, and boulder/problem before the athlete starts. Say the athlete/problem out loud if another judge is cross-checking.
Record each attempt as it happens
Use the app attempt controls in order. For a false start or failed attempt, record a no-result attempt without inventing a Zone/Top. For a Zone or Top, mark the result on the attempt where it happened.
Mark Zone / Top / no result
Mark Zone when controlled, Top when completed, and leave no-result attempts as attempts only. When Top is awarded, ensure the Zone indicator is also set if the screen does not do it automatically.
Save and check sync
Tap save/submit before moving to the next athlete. Confirm the row no longer looks pending/offline and that any sync indicator is clear before leaving the problem.
Fix a mistake safely
If you tapped the wrong athlete, problem, attempt, Zone, or Top, stop new entries, reopen/edit the entry if permitted, add a note if available, and call the Chief Judge if the result is disputed.
App screen callouts
Real judge app screenshots should be inserted here when approved assets are available. Until then, these panels identify the exact screen areas judges should look for without fabricating UI.
Boulder entry screen
Insert a real screenshot of the athlete/problem row with attempt controls, Zone, Top, save, and sync indicator when the production judge screen asset is available.
Result correction flow
Insert a real screenshot of edit/reopen/notes controls if the organiser enables judge corrections on comp day.
4. Common route-judge mistakes
The avoidable app-operation errors that create comp-day disputes.
Thinking judges calculate points
Do not calculate boulder points or attempt penalties. Your job is to enter observed attempts/results; GripRank calculates standings.
Skipping false starts
The most common Boulder judging error is not recording a false start because nothing was scored. If the athlete started, record the attempt as no result.
Counting after the fact
Do not wait until the end and reconstruct attempts from memory. Tap or tally the app entry as attempts happen.
Forgetting Top includes Zone
A completed boulder should not be left as Top-only when the app expects Zone to be recorded too.
Calling a skipped boulder DNS
Skipped problem and round DNS are different app states. Escalate if you are unsure which status applies.
Correction examples
Wrong athlete selected
Wrong
Save the result and fix it later from memory.
Correct
Stop, correct the row immediately if edit is available, and notify the Chief Judge/table if the wrong entry may have synced.
Identity errors spread quickly once saved.
False start before Zone
Wrong
Leave it blank because there was no Zone or Top.
Correct
Save a no-result attempt so GripRank has the correct started-attempt count.
A failed start can still be an attempt entry. Blank means the app never saw the attempt.
Top without separate Zone pause
Wrong
Leave Zone blank because the climber did not pause there.
Correct
Record Top and ensure Zone is awarded for the completed boulder.
The route judge records the app fields expected for completion, not a manual points calculation.
Unclear finish control
Wrong
Tap Top to keep the queue moving.
Correct
Hold the entry, preserve what you saw, and escalate before saving a disputed Top.
A disputed judgment boundary should not be hidden inside a saved entry.
5. Escalate
Situations that leave the route/lane judge scope and need Chief Judge direction.
Technical incident
Loose or spinning hold, timer/signal failure, or external interference: stop entry if needed, preserve facts, and call Chief Judge/Chief Route Judge.
Appeal before next detail
If an athlete challenges a Top/Zone call or may need another attempt, stop arguing on the mat and get Chief Judge involvement immediately before the next detail starts.
Coaching or prompting
Escalate suspected coaching/prompting. Do not personally apply disqualification or sanctions from the scoring screen.
Route struck-off or safety stop
If a boulder may need to be cancelled, re-opened, or a start was held for safety, Chief Judge decides how results proceed.
6. Confirmed vs needs-confirmation
Keep product behavior separate from local policy so route judges know when to pause and ask.
App-first training rule
Route judges enter observed attempts and results. GripRank performs result processing and standings calculations after entries are saved.
Needs event confirmation
Needs confirmationExact edit permissions, offline-sync behaviour, finalist quota, and any local departure from standard app workflow must be confirmed by the organiser.
Source notes
- GRI-76 app-first route judge workflow
- GRI-55 Boulder edge-case background
- GRI-34 judge module background