Start free
Browse helpHelp centre

Timing report

The FIS Timing and Data Technical Report (TDTR) for a race, in four steps, filled from the Timing Desk and saved as XML.

TimerTechnical DelegateUpdated 27 October 2026Open in the app ↗
On this page
  1. What it's for
  2. Before you start
  3. Steps
  4. What success looks like
  5. If something goes wrong
  6. Related

What it's for

Every FIS race needs a timing report. The ICR says a technical timing report form as prescribed by the FIS must accompany the race results, reviewed and sent by the chief of timing and confirmed by the TD as approval of the race (FIS ICR Book IV, Alpine, art. 611.3.3, May 2025). Race Bureau builds it in the FIS TR XML v1.17 format, per race, in four steps:

  1. Event data — season, location, event name, date, codex, category, discipline, gender and the Technical Delegate, all prefilled from the event.
  2. Timekeeper & Devices — the timekeeper's details and every device: System A and B timers, start device, finish cells, photofinish, transponders, video, and the result software and connections. Saved as your preset.
  3. Sync & Timing Part 1 — the synchronisation times and, per run, the first, last and best start and finish times of day for System A, System B and hand timing, extracted from the Timing Desk.
  4. Timing Part 2 & Save — any result not timed on System A (bib, run, reason, time taken from), comments per run, the certification, and the save and send buttons.

Before you start

  • The race picked under ACTIVE RACE and timed on the Timing Desk.
  • The serial numbers and homologation of the timing devices.

Steps

  1. Open Results & publish › Timing report. The race under RACE is the active race.
    Event data, prefilled from the event
    Timing report, step 1
  2. On 1 Event data, check every field and the TECHNICAL DELEGATE block.
  3. Press 2 Timekeeper & Devices. Fill in TIMEKEEPER, tick used on each device you ran and enter BRAND / COMPANY, MODEL, SERIAL NUMBER and HOMOLOGATION. Set CONNECTION SYSTEM A, CONNECTION SYSTEM B and VOICE COMMUNICATION. Press 💾 Save as my preset so the next race starts from this.
    Screenshotresults/timing-report-02.png
    Timekeeper and devices
  4. Press 3 Sync & Timing Part 1. Press ⤒ Extract Times from Event — it fills System A's times from Race Bureau's own timing, System B from the window declared System B, and the Hand column from the Handtime calculator. Enter the SYNCHRONIZATION times and confirmations; ⧉ Copy these sync times to the event's other races carries the six sync times only.
    Screenshotresults/timing-report-03.png
    Synchronisation and the per-run times
  5. Under 🖐 HAND-TIMING TAPES — CROSS-CHECK, press ⤓ Upload tape photo for each strip, or post it in the Timing group on the phone.
  6. Press 4 Timing Part 2 & Save. Under TIMING PART 2, press ＋ Add for every result not timed on System A and give its BIB, RUN, REASON and TIME TAKEN FROM; leave it empty when every result came from System A. Fill in COMMENTS RUN 1 / RUN 2 and answer the certification with Yes.
  7. Press 💾 Save report. Then 💾 Save DRAFT XML to check the file, or 💾 Save FINAL XML for the file you send.
  8. Press 📨 Send to FIS (results + timing report) to email both files in one go, or send from Submit to FIS.

What success looks like

The final XML saves without a warning, the report reopens on this race exactly as you left it, and the TD can read it under their documents.

If something goes wrong

  • System A + B is marked not used with no reason: FIS asks for one — go back to 2 Timekeeper & Devices and fill in the reason.
  • The times on step 3 are empty: the race is not timed on this device, or the run was imported without times. Press ⤒ Extract Times from Event again after the import.
  • TBC: the send line on step 4 names a FIS address with a hyphen; the address the files actually go to is the one saved on Submit to FIS › FIS email.
Was this helpful?
Timing report · Race Bureau Help