Until now, the phone followed the plan and wrote it week by week, but everything that prepares a race — its preparation races, its file, the race itself when it isn't in the catalogue — needed a computer. Not any more. It all happens in the Plan tab, when you think of it.
What changes
Milestones are written on their frieze. Under the milestone frieze, “Add a milestone” opens a sheet: the date (between the season start and the day before the objective), race or raid, the distance, a label, the stages of a multi-day raid (days, km per day, required rest) and the snow. A tap on a milestone reopens it, to edit or delete it. The refusals are the website's, word for word: a three-day raid with no km per day, a milestone on the objective's day or stages that overlap it are said before anything is sent. Then the plan updates — and if it was edited by hand, it asks you first.
The race file, under the race sheet. The bib, the meeting point, registration opening and closing, the briefing and the start time are entered and corrected in “Race file”. What you write there joins the race sheet, the one you can read offline at the start line. The same screen designates the musher and the planned rig (among the team's rig templates), declares secondary participants — a dog entered on another objective of the season, which counts in the race-day roster —, and keeps the logistics links and notes.
A private race, from the race choice. In an objective's form, under “Reference race”, “Create a private race” opens the website's sheet: name, discipline, country and region, rules, distance, duration, loop or point-to-point course, team sizes. Once saved, it becomes the objective's reference race straight away.
Previous plan versions. Under “Plan details”, “Previous plan versions” lists the last three versions set aside (at each editing session and each regeneration), with their time. “Put back in service” restores one and sets the current one aside in turn: nothing is deleted. The sentence that said “this version can only be recovered from the web” is gone.
An empty season can be deleted. A season without an objective shows “Delete season”.
“Load above plan”, “Team below plan”. The website's banner comes to the phone: over the last seven days, the load actually taken on against the plan's, the dog going over if there is one, and “Regenerate the plan from actual load”. After a regeneration, the button withdraws until your next outing, and the sentence says why.
Back on dryland shows. Under “Plan details”, “Dryland and snow” draws dryland, snow and — if the season has an end of snow — back on dryland, and spells it out: “Back on dryland from 20 March 2027 (end of snow)” (an example).
What others see
- The race file stays in your kennel. The bib, deadlines, links and notes don't leave the kennel: no public page, no sharing. Members read it; the owner writes the entry, the musher and the planned rig; the handler can also add links, notes and participants.
- A private race is private. Only your kennel sees it. An administrator may one day promote it to the public catalogue; it then changes owner, and the sheet tells you so before you save it.
- The gap against actual load stays in the kennel. It names one of your dogs, for the kennel's members only; no ranking, no comparison with other kennels.
What the phone doesn't do
These are choices, not oversights.
- It writes nothing offline. Milestones, the race file, a private race, versions, deleting a season: all need the network, and the screen says so straight away instead of pretending. The race sheet itself can always be read offline.
- It doesn't attach a document to a note. The phone counts the documents a note carries; it doesn't open them or add any.
- It doesn't set a milestone's reference race, team sizes or course. It doesn't erase them either: editing a milestone on the phone leaves what you entered elsewhere intact.
- It doesn't compare two versions week by week. It lists them and puts one back in service.
- It draws neither the foot restart nor detraining on “Dryland and snow”: only what is harnessed, from dryland to back on dryland.
Choices made against the obvious
Deleting an empty season, but checking it still is. The obvious: the button only shows on a season without an objective, so just delete. But a season takes everything it contains with it, and an objective added from another device may not have reached the phone yet. Before deleting, the phone counts the season's objectives on the server; if it finds one, it deletes nothing, and says so.
The gap stays silent offline. The obvious: compute with what the phone already has. But it only keeps two weeks of loads, and knowing whether a dog is resting or simply unknown takes a year of history. A verdict built on a truncated read would invent a “below plan” that never happened. Offline, the banner says nothing; online, it reads what the website reads and decides by the same rules, checked against the same table of cases on both sides.
A milestone edited on the phone only sends what the phone shows. The obvious: send the whole milestone back. But the phone doesn't know the reference race or course of a milestone entered on the website; sending them back empty would erase them. So it sends the date, kind, distance, label, stages and snow, and nothing else.
“Delete” under the row, not at its end. The obvious: a “Delete” at the end of each link, note and participant, like a desktop list. But with large text on a small screen, the end of the row squeezed the text into a one-word column. The gesture moves under the row it concerns, in the ink of deletions.