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
- Verified result publication
Verified result publication
Execute an approved race result through its own authority and retain the publication operation outcome.
OverviewCompleted Race Results×
Running Club Management · Verified result publication
New
Completed Race Results
Race entries
| Parent | Event | Registered at | Finish seconds | Timing receipt | Decision at | |
|---|---|---|---|---|---|---|
| EVN-61012 | EVN-686 | 10 Oct | 830 | TR-133 | 19 Oct | |
| EVN-91163 | EVN-714 | 09 Oct | 80 | TR-730 | 13 Oct | |
| EVN-37576 | EVN-212 | 22 Oct | 150 | TR-903 | 28 Oct | |
| EVN-74902 | EVN-385 | 25 Oct | 640 | TR-522 | 29 Oct | |
| EVN-61052 | EVN-992 | 16 Oct | 380 | TR-606 | 20 Oct |
6 of 6 records
EVN-686Race entries · RE-20668
CompletedParentEVN-61012
Registered at10 Oct
Finish seconds830
Timing receiptTR-133
Decision at19 Oct
What you can do
Give result execution its own recorded handoff
An approved race entry is ready for the next authorized step, but review approval does not itself execute publication. Results Publisher performs the separate result action using the approved evidence scope. The action has its own authority reference and operation receipt so the club can distinguish the review decision from the execution outcome.
Event Coordinator and Auditor can then follow the result from submission through independent review to completed execution. This helps the team explain an exception without assuming that a status in the review queue proves every later step succeeded. Keep the timing receipt and the reviewed revision available throughout that discussion.
How the work is organized
- Approved scope. Results Publisher identifies the approved entry and timing evidence before requesting execution. The publication handoff must refer to the result actually reviewed, rather than a later change in the finish duration.
- Separate authority. The execute step carries its own authority reference. The reviewer decides whether the result is acceptable; the publisher uses the authorized execution path for that accepted scope.
- Outcome evidence. The operation receipt records the execution outcome. A completed entry and its supporting receipt let the club inspect what was executed, while an unresolved operation remains visible for investigation.
What to agree during setup
Assign the publisher responsibility and agree how the person receives the approved result scope. Establish where the reviewer decision and execution authority can be inspected during a handoff. If the club uses an external results destination, define that connection and the evidence of delivery before relying on it for public distribution.
Decide how the team responds when an execution request has an uncertain outcome. Inspect the operation receipt before attempting the action again. Also agree how a corrected timing result returns through the required review and execution path so that the prior approval is not reused for changed evidence.
Check the handoff on an actual case
Use an approved rehearsal result whose timing receipt and finish duration have been independently checked. Results Publisher identifies the authorized revision and performs the separate execution step. Inspect its authority reference and operation receipt with Auditor, then confirm the entry’s completed outcome.
Next, try a result that is still Submitted and has no independent approval. Confirm that it cannot use the eligible approved-result path. In another rehearsal, change the timing evidence after review and check that the publisher cannot treat the earlier approval as authority for the changed result. Finally, introduce an uncertain execution response and have the team investigate the existing operation outcome before deciding whether any further action is needed.
What your team sees
- Completed Race Results — Completed entry scope with finish seconds, timing receipt and decision context.
- Exception Receipts — Unresolved publication or other event operation outcomes requiring investigation.
Follow the work through
Follow verify and publish race results, then include the outcome in close or cancel and reconcile. Agree external distribution in integrations.
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.
- Operation receipts
- Durable receipts for every guarded operation attempt.
Who uses it
Permissions- Results Publisher
- , Independent Reviewer, Event Coordinator, Auditor.
- The publisher executes approved scope, the reviewer retains the independent decision responsibility and auditors inspect the recorded handoff.
Set up Running Club Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.