Status and race time rules

Audience: Event organisers and operators needing to understand why a competitor has the status or race time that Manager is showing.

Plain-language explanation of the rules Manager uses to decide each competitor's status (OK, MP, DNF, DNS, InForest, etc.) and race time.

Status: Stub — not yet written. The authoritative rules live in web/.ai/STATUS-RULES.md; this page will mirror them in user language with examples.

What this page will cover

• [ ] The full list of status values and what each means to a human
• [ ] How status transitions happen automatically (start punch → InForest, finish punch → OK/MP, timeout → DNF)
• [ ] How race time is computed from start and finish
• [ ] Which source of truth wins when sources disagree (allocated start vs. punched start, radio finish vs. card finish, etc.)
• [ ] Manual operator overrides — when to use them and what they do
• [ ] Worked examples:
  • A competitor who finishes but forgets to punch finish
  • A competitor whose SI card download contradicts the radio punches
  • A competitor with an allocated start in the morning but no punch all day
  • A team relay where one leg is missing a punch

Related

• Start times
• Downloading SI cards
• Resolving issues on the day
• web/.ai/STATUS-RULES.md — developer-facing authoritative rules