Passing Statuses

In RUFUS Race Manager (RRM), every passing is assigned a status that reflects its condition in the system. Statuses ensure data is validated consistently, laps and checkpoints are preserved, and operators can later review or override results with confidence.

Statuses are evaluated in a strict precedence order. Even blocked or invalid passings always carry the correct lap and checkpoint context.

Passing Status Precedence

Core Statuses

• ORPHAN → Chip or bib not recognized in the event.

• WRONG_RACE → Participant exists but the passing was recorded on a device not in their race plan.

• RACE_CLOSED → Passing occurred after the race was closed.

• DEVICE_CLOSED → Passing occurred on a device marked as inactive.

• CHECKPOINT_CLOSED → Passing occurred at a checkpoint that was closed.

• EOTR (End of the Road) → No further checkpoints left in the race plan; participant has reached the end of scope.

Time Validation

• TIME_INVALID → Passing timestamp is earlier than race start or otherwise invalid.

• TIME_VALID → Passing timestamp is valid (internal status during processing).

Bounce and Duplication Control

• BOUNCED_BY_CHECKPOINT → Ignored because it occurred within the checkpoint bounce window.

• BOUNCED_BY_DEVICE → Ignored because it occurred within the device bounce window.

Note: Manual and floating passings are immune to device bounce but still respect checkpoint bounce.

Validation and Blocking

• BLOCKED_MISSING_START → Passing was blocked because no valid start exists and race policy forbids creating a synthetic start.

• VALID → Passing is correctly assigned and accepted.

• PROMOTED → Passing was moved forward to the next valid checkpoint (e.g., expected checkpoint closed). Internal status, not visible in the UI.

User Actions

• VALIDATED_BY_USER → Passing has been manually confirmed as valid.

• INVALIDATED_BY_USER → Passing has been manually marked as invalid.

Internal / System-Only

• ASSIGNED → Internal status: passing has been matched to a participant before final validation.

• SYNTHETIC_START → System-generated start passing when policies allow automatic creation.

Quick Reference Table

Status	Meaning	Typical Scenario
ORPHAN	Chip/bib not recognized	Unregistered chip crosses a mat
WRONG_RACE	Participant exists but on wrong device scope	Runner registered for 10k crosses the marathon-only mat
RACE_CLOSED	Race not accepting passings	Passing occurs after event is stopped
DEVICE_CLOSED	Device not active	Reader disabled during warm-up period
CHECKPOINT_CLOSED	Checkpoint inactive	Passing at closed split point
TIME_INVALID	Timestamp invalid	Passing before official start time
BOUNCED_BY_CHECKPOINT	Too soon at same checkpoint	Runner re-steps on the mat within bounce window
BOUNCED_BY_DEVICE	Too soon at same device	Chip double-read by overlapping antennas
BLOCKED_MISSING_START	Finish without valid start	Runner crosses finish but no start recorded and no synthetic start allowed
PROMOTED Internal status, not visible in the UI.	Passing moved forward	Start mat closed → passing assigned at Finish
VALID	Correctly assigned and accepted	Normal participant crossing
VALIDATED_BY_USER	Manually confirmed	Judge confirms a disputed crossing
INVALIDATED_BY_USER	Manually invalidated	Operator rejects a false passing
EOTR	End of race scope	Finish recorded, all later passings closed
SYNTHETIC_START	System-created start	First crossing at Finish triggers synthetic start (policy-dependent)