Questions, answered

Click Get started, then use Proto to configure Running Club Management for your business. Begin with a club organization, eligible venue and familiar event. Include approval, reservation, admission and an evidence-based closing rehearsal in the pilot.

The event records support races, club runs and training events with venue, planned timing, capacity and ownership. Agree the operating handoff and capacity unit for the selected event during setup.

A reservation records a place against eligible Open scope. Actual attendance requires the separate admit action and recorded admission time. A reservation line can be admitted at most once.

The reservation action applies a remaining-capacity guard after checking the request, event and lifecycle. Rehearse the capacity and quantity convention with the gate volunteers before the first operating cycle.

Approval and opening are separate handoffs. Admissions Steward starts reservation work when the event is Open and the request can pass the capacity check.

Race Entrant supplies actual timing evidence with the finish duration and timing receipt for the authorized entry. A registration time alone does not establish a finisher.

Independent Reviewer decides the submitted timing scope. Results Publisher then performs a separate authorized execution step with its own authority reference and operation receipt.

The authorized cancellation path revokes unused reserved scope while preserving admitted history. Retained reservation records need the current event and operation context before they are treated as usable places.

A refund needs provider-backed evidence. Cancellation changes event scope; unresolved refund questions remain Needs review until the provider evidence supports the financial outcome.

Configure those connections during setup with agreed identifiers, time zones and evidence rules. Rehearse duplicate messages and uncertain responses before using imported evidence for result execution or event closure.