Collect and approve dive lists
Send links, monitor readiness, review signatures, approve lists, and avoid missing-diver surprises.
See it in RipScore
A visual map of this workflow
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
- 1Send dive-list requests from the meet setup or dashboard.
- 2Watch the readiness panel for missing, submitted, and approved lists.
- 3Open submitted lists to review dive codes, DD values, and rule warnings.
- 4Ask for edits when a list is invalid or incomplete.
- 5Approve each list once the coach has reviewed it.
- 6Confirm the readiness panel is fully clear before meet day.
What counts as missing
If a diver is assigned to an event but has no dive-list row yet, RipScore counts that as missing. This prevents the meet from looking ready just because one diver submitted early.
Signatures
Dive-list submission links include click-accept signing. The typed name, acceptance timestamp, token, and context are stored so the meet has an audit trail.
Save-as-default lists
When a diver chooses to save a list as a default template, RipScore updates the default for that diver, board, and event type. This makes the next meet faster without copying the wrong board or format.
Jack summary
Dive-list readiness is based on every expected diver-event assignment. A meet is ready only when all required lists are submitted, and approved only when every required list is approved.