Start free
Browse helpHelp centre

The Technical Delegate's profile

How a TD is invited, what their door opens, what they can read and write, the checklist, the documents and the meeting, the jury forms, the FIS cross-check, the phone — and what the organiser sees of them.

Technical DelegateOrganiserTimerUpdated 27 October 2026
On this page
  1. What it's for
  2. The chain
  3. What the organiser sees of the TD
  4. What success looks like
  5. If something goes wrong
  6. Related

What it's for

The Technical Delegate works through the FIS Technical Delegate door of their own account, one event at a time. On the live event they were invited to they read and write the race screens; on the archived events of the clubs that invited them they read; a live event they were not invited to is not listed at all. Everything the TD files lands with the event for the organiser and for the next TD. This page is the TD's season on Race Bureau, in order, with the organiser's side beside each step.

The chain

  1. Invited — on a FIS race FIS assigns the TD off the calendar and Race Bureau matches the TD number; otherwise the organiser presses Invite on the Technical Delegate card under Set up › OFFICIALS. The link is single-use and lasts 7 days. → Invite TD · Invite and the TD door
  2. The door — signing in asks Where are you working today? when the account holds more than one door; FIS Technical Delegate lands on Events, with My assigned events and the clubs' archived events read-only. → Events · Technical Delegate
  3. What the TD may touch — the lens chip on each screen reads ✎ You can edit on a current invited event and 🔒 Read-only on an archived one; the organiser can untick a race under Event access & chat to hide it, and grants or withdraws Edit on the competitor list under Crew › Profile access. → Event access & chat · Profile access
  4. The race, shared with the organiser — Race Information is the same Header Info the organiser fills (jury, track, weather, setters, forerunners); Competitor Management is the same list, read-only unless granted; the Run Sheet is the same planning sheet. → Race Information · Competitor Management · Run Sheet
  5. Before the race — the twenty-item checklist from ICR 601.4.9.1, per race day, every tick stamped with the TD's name and time; the document pool the organiser shares into and the TD files back, with the seven required-document slots; the team captains' meeting with its attendance roster and FIS checklist. → Pre-race Checklist · Documents · Team-Captains' Meeting
  6. The jury's paper — the current FIS forms opened live: Protest, Minutes with and without protests, Report by the Referee; the filed PDF stays with the event. → Jury & Minutes
  7. The official record of each race — one card per race: both start lists, results, penalty, hand-time calculation, FIS results file and timing report, each row saying Official, Not released yet, Waiting for FIS or Accepted by FIS. Nothing is invented; a gap shows as a gap. → Official documents
  8. The FIS cross-check — the TD sends nothing; the organiser submits. Once FIS confirms, the card reads Timing report valid and Accepted by FIS, and Race Bureau's penalty is checked against the one FIS accepted (Penalty valid, or FIS's value beside ours). → Timing report and penalty check · Submit to FIS
  9. After the race — the TD Report, the Additional Report, the accident and injury reports; and TD Notes, kept TD-to-TD and never shown to the organiser. → Reports & Records · TD Notes
  10. Reference and the phone — ICR Search for the common calls; Comms puts the phone in the event's ROC / Jury group as the TD, and 📋 Header details on the phone's Program tab writes the same Header Info the documents print from. → ICR Search · Comms · Header details on the phone · Race Relay for the TD

What the organiser sees of the TD

  • The Technical Delegate card on Set up reads Invite pending, then ✓ with the TD's first name; the TECHNICAL DELEGATE row of Header info fills in.
  • Event access & chat lists the TD with a tick per race; Team & access › Invited to events lists them as Invited or Active; Profile access shows their scope and whether they hold Edit.
  • What the TD files (TD report, minutes, forms) shows under Bibs & start lists › TD documents & meeting minutes and stays with the event for next season's TD.
  • A TD request or flag can email the club when TD attention item is ticked under Settings › Notifications.
  • The TD's invitation ends when the event is archived; they can still open the archived dossier.

What success looks like

The event is under My assigned events with ROC invite or FIS feed, the race screens read ✎ You can edit, every required-document slot is green before the first start, and after the race the card reads Penalty valid, Accepted by FIS and Timing report valid.

If something goes wrong

  • No current assignments: FIS has not assigned the TD, or the invitation has not been accepted.
  • A field will not save: the race belongs to an archived event, or the organiser unticked this race for the TD.
  • The TD cannot see a shared file: the invitation is still pending.
  • No access. on the phone's Header details: the phone is not connected as the event's TD; use Comms to connect it.
Was this helpful?
The Technical Delegate's profile · Race Bureau Help