TroubleshootingPublic guide6 min readUpdated 8/1/2026
Troubleshoot readiness blockers
Find why a meet cannot move forward and resolve missing lists, unsigned requests, or incomplete assignments.
See it in RipScore
A visual map of this workflow
1 / 2
Meet readiness · desktop
Readiness is assignment-complete, not approximate
One missing diver-event list keeps the meet blocked even when every other athlete is approved.
Quick steps
- 1Open the meet readiness panel.
- 2Look for missing, submitted, invalid, or unapproved list counts.
- 3Expand the blocker to identify the diver and event.
- 4Send a reminder or open the relevant list.
- 5Approve the list only after it is valid and signed.
- 6Refresh readiness after the correction saves.
Most common causes
The most common readiness blockers are assigned divers with no list yet, away-team requests that have not been confirmed, lists that were submitted but not approved, and invalid dive codes.
Do not hide missing rows
Missing rows are important. If a diver is assigned to an event, that expected list must count in readiness even before a database row exists.
Jack summary
Readiness blockers usually mean an expected diver-event list is missing, submitted but unapproved, invalid, unsigned, or tied to an away-team request that still needs action.
Why is my meet not ready?What does this readiness blocker mean?How do I find missing dive lists?