These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Running Club Management
- Features
- Race result review
Race result review
Submit actual timing evidence for an independent decision before any result publication step.
OverviewPending Review Entries×
Running Club Management · Race result review
New
Pending Review Entries
Approval waits for the independent reviewer
| Parent | Event | Registered at | Finish seconds | Timing receipt | Revision | |
|---|---|---|---|---|---|---|
| EVN-90623 | EVN-359 | 15 Oct | 460 | TR-761 | 950 | |
| EVN-85345 | EVN-194 | 06 Oct | 820 | TR-350 | 90 | |
| EVN-93475 | EVN-267 | 26 Oct | 620 | TR-834 | 670 | |
| EVN-99634 | EVN-921 | 21 Oct | 380 | TR-961 | 450 | |
| EVN-21874 | EVN-523 | 16 Oct | 200 | TR-402 | 670 |
6 of 6 records
EVN-359Race entries · RE-66163
SubmittedParentEVN-90623
Registered at15 Oct
Finish seconds460
Timing receiptTR-761
Revision950
What you can do
Review the evidence that establishes a finish
Race Entrant supplies the timing evidence for the authorized race entry. The entry records its registration time, finish duration in seconds and timing receipt alongside the parent event and revision. Registration establishes entry context; a finish result needs the timing evidence and the independent review that follows it.
Independent Reviewer examines the submitted result scope before deciding it. The review outcome is separate from publication execution. Keeping these steps distinct lets Event Coordinator explain why a registered entry may still be awaiting evidence, why a submitted result needs correction or why an approved result has not yet completed its publication step.
How the work is organized
- Evidence submission. Race Entrant submits the authorized entry with the finish duration and timing receipt. The receipt should identify the actual timing evidence used for the result, so another person can inspect the same basis.
- Independent decision. Independent Reviewer examines the submitted revision independently of the entrant. The reviewer approves or rejects that scope rather than treating the registration record as proof that the entrant finished.
- Publication handoff. Results Publisher receives eligible approved scope for the separate execution action. Approval remains a review conclusion until the authorized publication step records its own outcome.
What to agree during setup
Agree the source and format of the timing receipt and how finish duration is expressed in seconds. Decide who resolves a disagreement between the submitted duration and the timing evidence. Keep the parent event clear when similarly named runs occur on different dates.
Establish how the entrant is authorized to submit a particular entry and how the reviewer remains independent. Rehearse corrections to submitted evidence before using the process during a live event. The reviewer and publisher should be able to identify the exact revision under discussion without reconstructing the handoff from messages.
Check the handoff on an actual case
Prepare an illustrative race entry with a registration time but no submitted finish evidence. Ask the team to explain why it cannot yet be treated as a verified result. Race Entrant then supplies the authorized timing receipt and finish duration, and submits the entry for Independent Reviewer to examine.
Use a separate rehearsal case where the duration conflicts with the referenced timing evidence. Have the reviewer reject that submitted scope through the authorized action and inspect the recorded outcome. Correct the evidence through the agreed path and obtain a decision on the current revision. Finally, leave an approved entry awaiting Results Publisher and confirm that the team still distinguishes approval from completed publication execution.
What your team sees
- Pending Review Entries — Submitted race entries with registration context, finish seconds and the timing receipt for review.
- Completed Race Results — Entries that have completed the authorized execution path, available for comparison with the reviewed evidence.
Follow the work through
Rehearse verify and publish race results. Define timing-provider handoffs in integrations and review the evidence questions under reports.
What it keeps track of
Data model- Race entries
- Race entry records carrying timing evidence and review status.
- Events
- Races, club runs and training events with capacity and lifecycle.
- Organizations
- Running club organizations that own events, venues and members.
- Operation receipts
- Durable receipts for every guarded operation attempt.
Who uses it
Permissions- Race Entrant
- , Independent Reviewer, Results Publisher, Event Coordinator, Auditor.
- Entrants supply evidence, reviewers decide independently and publishers execute eligible approved results through a separate action.
Set up Running Club Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.