Building the race is one thing. Taking it live, in local time, with others if need be, and closing it with its report: that is what this page is about.
Save keeps your work. Publish live sends it: this button, and this button alone, is what shows the race to your crew and to the public. Until you publish again, the people following see the previous version.
Before anything goes out, Le Cairn reviews everything in a “Before publishing” window. What blocks: no name, no date, no checkpoint, a finish still at kilometre 0 — and above all no athlete in the race. What only warns: no cut-off time, a distance that does not match the track, a date already gone. You fix it, or you click “Publish anyway”.
The race code suggests itself from the name and the year — CHOUFFE26 for the Trail de la Chouffe 2026. Letters and digits only. It is what you read out to your crew and share to the public; it locks while the race is online.
One live race per account. Publishing another one takes the first offline. Its tracking is kept: check-ins, messages, pebbles and alerts come back if you republish it.
Take offline stops the tracking, and destroys nothing: everything comes back when you republish. To close a finished race, it is Close, at step 6.
Before publishing
1 thing to fix before this race can go live.All in order.
✕ No athlete in the race — add one from your notebook, 🏃 Athletes tab.✓ 3 athletes — Zoé, Karim, Noor.
And this, which does not block:
⚠ No cut-off entered: no alert will warn of a risk of missing one.
ClosePublish anyway
⚡ Published live!
2
⏰ It goes live on its own 24 h before
In Le Cairn · by e-mail
A safety net for rushed days. In the 🧩 Modules tab, the “Automatic go-live” switch is on by default: “If the race is not online 24 h before its start, it goes online on its own — the last saved version — and you get an e-mail.” This applies to any race that has a date, in the local time of the race.
The e-mail says all you need: the race code, which version went out and when it was saved, the other race of the account that went offline if there was one, and 🎒 what is missing from the drawers for this race, athlete by athlete.
A race you took offline after its automatic go-live does not go back on its own: each start is handled once.
No safety net for a race? Turn the switch off: it will only go out if you click “Publish”.
Automatic go-live
If the race is not online 24 h before its start, it goes online on its own — the last saved version — and you get an e-mail.
The day before the start
⏰ “Trail des Miettes” is live — start tomorrow at 8:05
Race code: MIETTES26
It is the last saved version that went online — the one saved on 09/10 at 21:14.
🎒 What is missing from the drawers for this race: Zoé — 2 × Lemon gel
3
🌍 Local time
In Le Cairn · in the apps
Next to the start time, a “Time zone” field: the one of the place of the race. Brussels by default, which is the time of France, Belgium, Switzerland, Spain and Italy. Change it only if the race is not run on Paris time: Réunion Island, Québec, Nepal… 25 zones are offered.
You often have nothing to do: the track suggests it. When the GPX is imported, the first point — the start — sets the menu to its zone, and Le Cairn says so: “🌍 time zone from the track: Réunion Island”. Suggested, never imposed: a zone chosen by hand prevails.
From then on everything reads on the local clock: cut-offs, passages, projections, weather, nutrition reminders, the automatic go-live — for the athlete, the crew and the public, wherever they are. And if your computer is not on that time, Le Cairn translates: “That is Friday 16 October at 03:00 where you are.”
🌍 time zone from the track: Réunion Island
Time zone
Belgium · France · Switzerland · Spain · Italy — GMT+1/+2Réunion Island — GMT+4⌄
⏰ Start at 05:00 — Réunion Island. That is Friday 16 October at 03:00 where you are.
4
👥 Together: co-editing
In Le Cairn
On your race card, the 👥 button invites another person to prepare it with you, by the e-mail of their Cailloux account. They can edit the race and take it live. Deleting and closing stay yours.
On their side, the race shows up under “👥 Shared with me”, with your name. They can step out whenever they want: you keep yours. And if you both save the same race from 2 devices, Le Cairn does not decide for you: it warns that the race was changed on another device, and lets you reload or overwrite.
When the invited person publishes, the race stays with you: it is your other live race that goes offline, not theirs.
The end-of-race report goes to your address, not to the invited person. Closing removes the share.
👥 Trail des Miettes — co-editing
The invited person edits the race and can put it live. Deleting and closing stay with you.
address of the Cailloux accountnoor@example.comInvite
Nobody yet. Enter the address of a Cailloux account.
Noor Haddad— edits and publishes✕
✓ Noor Haddad can now co-edit this race
5
⚠️ The “race without athlete” alert
By e-mail
Le Cairn refuses to publish an empty race. But the automatic go-live publishes it anyway: a race that starts with nobody on the line, nobody can check in or drop a pebble on it — neither the athletes' app nor the crew's. So Cailloux warns, rather than refusing.
Every morning, after 9:00, it looks at the starts of the next 3 days. A race about to go online — or already online — without a single athlete gets an e-mail, once: “has no athletes yet”. And if nothing has moved the day before the start, the go-live e-mail says it first, in its subject: WITHOUT ANY ATHLETE.
The remedy fits in one sentence, and the e-mail gives it: add them in Le Cairn, from your notebook, 🏃 Athletes tab, then publish the race again — that is what brings them into the live tracking.
⚠️ “Trail des Miettes” has no athletes yet — start on Saturday 11 October at 8:05
Your race “Trail des Miettes” starts on Saturday 11 October at 8:05, and it has no athletes yet.
Without athletes, nobody can check in or drop a pebble during the race: neither in the athletes' app nor in the crew's.
Add them in Le Cairn, from your notebook, 🏃 Athletes tab.
⚠️ “Trail des Miettes” is live WITHOUT ANY ATHLETE — start tomorrow at 8:05
6
🏁 Closing: the archive and the report
In Le Cairn · by e-mail · in the app
The race has been run. The 🏁 Close button archives it with its report, stops the live tracking if it is still running, and frees the code for a next edition. Le Cairn tells you so beforehand, and refuses if a Back from the race is still pending in the Cupboard — kit taken out of the drawer and not yet put back.
The report arrives by e-mail, athlete by athlete: “Finished in 5h32” or the drop-out and where, the real start if it differs from the plan, each passage with its time, gap and stop time, the intakes taken and the ones that were not, the drink prepared. With an attached table for a spreadsheet.
The race joins “🏁 Closed races” in Le Cairn: its 📊 Debrief compares planned and actual segment by segment, gives the percentage of planned time and the drift per hour, and accepts the GPX from the watch. You can duplicate it for next year, or delete the archive. On the athlete's side, the checked-in finish opens the 📊 End-of-race debrief: what goes back to the drawer, what went down well — and a finisher card to share.
Race report — Trail des Miettes
Zoé Martin — Finished in 5h32
Actual start 08:12 (planned 08:05) — gaps are counted from the actual start.
09:41 Bonnezue, km 15.5
+6 min
stop 4 min
11:20 Engreux, km 23.3
on time
stop 7 min
13:44 Finish, km 31.4
−4 min
What was taken: 9 of 11 · Not taken: 2
Drink prepared: 6 doses — Lemon maltodextrin
📎 bilan-MIETTES26.csv
⚠️ What you need to know
A few rules the race applies without asking you. Better to know them before race day.
A race stays live 7 days before and 2 days after its date. Outside that window, it goes offline on its own during the night. Nothing is lost: everything comes back if you republish it, and the automatic go-live will bring it back 24 h before the start.
The automatic go-live publishes the last saved version. A device left without network has not sent its changes: open Le Cairn on it, let it save, then publish again. The e-mail tells you when the version that went out was saved.
Offline is not closing. Offline keeps everything and waits; closing archives, sends the report and frees the code. A deleted archive is gone for good.
The night cut and the morning alert run on Brussels time. Only the 24 h go-live follows the race's time zone.
The live tracking only sees what you have published. If you change something on race day, republish: “Save” does not reach it.
The 3 things to do before the start
Check the time zone if the race is not run on Paris time. A race built before 1.1 stayed on Brussels.
Leave the automatic go-live on, or publish yourself the day before. Either way, read the e-mail: it says what is missing from the drawers.
Read out the race code to your crew and share it to the public — the code, never your account.
👥 One live race per account. If you prepare 2 races the same weekend, it is one or the other: publishing the second takes the first offline, tracking kept.
I published 10 days ahead, and it vanished? That is the 7-day window: the following night, it went offline, losing nothing. If the automatic switch is on, it goes back on its own 24 h before the start; otherwise, republish it.
My crew cannot see my changes? You saved, you did not publish. Click “⚡ Publish live”: Le Cairn reminds you of it, showing “🔴 Live” at the top of the editor.
Who gets the report? The e-mail of the account that created the race, as text, with the attached table. People invited to co-edit do not get it.