Start free
Browse helpHelp centre

Documents, from the print format to the phone

How a start list or results sheet gets its look, goes out with one press, reaches the phones, the public page and the email list, and ends in the archive.

OrganiserTimerTechnical DelegateCoachUpdated 27 October 2026Open in the app ↗
On this page
  1. What it's for
  2. The chain
  3. What success looks like
  4. If something goes wrong
  5. Related

What it's for

A document in Race Bureau exists once, in the workspace: the Run 1 and Run 2 start lists and the results sheet of each race. Its look is set before it goes out; one press releases it; the phones, the public page, the TD's pool and the email list all receive the same sheet; a re-release replaces it everywhere. This page is that road, in order.

The chain

  1. The words on the page — the titles, the footer and the FIS reference under General parameters; the jury, course and forerunners under Header info. Both are per race. → General parameters · Header info
  2. The look of the page — fonts, margins, row shading and the logos, with the page design redrawing as you change them. → Printing parameters
  3. The columns — every sheet opens the same Columns & Filters panel; the race keeps its own copy of the format once you change it, and your named sections live under List formats & export. → Columns & Filters · List formats & export
  4. Who gets the email — the standing address list under Email documents to…: every released document is emailed to it as it goes out. → Email documents to…
  5. Print and release — on the sheet, 🖨 Print PDF opens the preview; 📣 Release now asks Really? and posts the sheet. The bar then reads ✓ Released with the time, 📣 Release again replaces the sheet everywhere, 🗑 Withdraw takes every copy back. → Start lists · Release results
  6. A protest window, when you want one — the results bar opens no clock. A 15-minute protest window (ICR 643) is set per document, from the phone, when a group admin posts an official document and picks ⏱ 15-min protest window; a lodged protest is resolved by an admin. → Release and protest windows
  7. On the phone — the released sheet lands in the event's Race Relay group as a card and on the Docs tab, grouped under Startlists and Results; a document with a window reads PROVISIONAL with a countdown. → Docs and protests
  8. On the public page — every released official document of the event is on /results/<event>, reached from the club's Results card and from the race archive; the newest release replaces the old one in place. → Results and documents pages
  9. With the TD — every official results sheet the timer releases joins the TD's document pool by itself, and the race card under Official documents lists every released version. → Official documents (TD)
  10. In the archive — archiving seals the event; the released documents stay readable in the dossier and on the public page. → Archive an event

What success looks like

The sheet appears in Race Relay's Docs tab and on the public results page within a minute of 📣 Release now, the email arrives at the addresses under Email documents to…, and the bar reads ✓ Released with the time.

If something goes wrong

  • The sheet went out wrong: fix the race, press 📣 Release again; the new sheet replaces the old one everywhere. Or 🗑 Withdraw first.
  • Nothing was emailed: the list under Email documents to… is empty.
  • The header or logos are wrong on the PDF: they come from Header info and Printing parameters, per race.
  • The phone shows an old sheet: pull to refresh; a re-release replaces the card.
Was this helpful?
Documents, from the print format to the phone · Race Bureau Help