Skip to content

1. Purpose, Audience, Scope

1.1 Purpose

This document explains the RaceTribe platform structure for technical and operational stakeholders.

It focuses on:

  • what the platform currently provides;
  • what the platform does not currently provide;
  • how the main modules interact;
  • how data ownership and transfer are handled;
  • what is planned in the near term.

1.2 Audience

  • pilot customers and technical partners;
  • product and engineering teams.
  • timers and operation leads;

1.3 In Scope

  • Public Results Portal and Event Manager high-level capabilities;
  • Event, Registration, and Timing domain boundaries;
  • data flow between modules and domains;
  • current limitations and near-term roadmap.

1.4 Out of Scope

  • low-level API contracts and endpoint-by-endpoint reference;
  • infrastructure deployment runbooks;
  • implementation details for every UI screen;
  • step-by-step user guides and troubleshooting content.

1.5 Terminology

  • Event: the full event context that can contain multiple races;
  • Race: a specific competition unit where standings and results are calculated;
  • Run: a specific run attempt under a race.

In most operational flows, users mainly work with Event and Race. When a race has only one run, run-level configuration is merged into race configuration for simpler UX.