The training plan

“Add an objective” opens a two-step form; the first step describes the race.

• “My race or goal” step (owner): sport (sled, canicross, bikejoring, scooter, skijoring, kart, quad), nature (race, maintenance, expedition, recreational), target date, distance.
  • The sport has no default: the menu opens on “Choose the sport…” and nothing is saved without it. It is what opens the race-day start on the right activity.
• For a race, the “The race” block (1) attaches an event from the catalogue or creates a private one; the team and dogs entered are picked below it.
• Duration (2): “One day” or “Several days”.
• Programme (3), in “Several days”: one line per stage, with its distance and, from the second on, the rest before it (in hours), “to enter” until you set it, never pre-filled.
  • “Add a stage” copies the last one; a summary gives the longest stage, the shortest, the total and the shortest rest.
  • The objective's distance becomes the sum of the stages (“Computed from the race programme”); a multi-day event from the catalogue lends equal stages, to adjust.
• Format (4), after the duration: Sprint for canicross, bikejoring and scooter, or when no stage exceeds 30 km; Long as soon as a stage reaches 100 km, or from 322 km without stages; Mid-distance in between.
  • It says where it comes from (“Deduced from the programme · longest stage 14 km”, “Deduced from the sport · canicross: sprint by default”); your choice then stays put.
  • When editing, the saved format shows as it is; if the programme says otherwise, a line says so, with a button to choose it.
• Effect on the plan: each stage counts with its own distance in race week. The long run is measured on the total distance (Mid-distance, Long) or the longest stage (Sprint), and never exceeds one and a half times the longest stage, whatever the format (15 stages of 35 km: 52 km at most, not 80); the kilometres it no longer absorbs are not moved to another day of the week:
  • in Sprint, “Race pace” goes up to the whole stage;
  • for a multi-day race, two and four weeks before it, a “Race rehearsal” chains the stages (three at most), one a day, then two rest days.
• Location (optional): search, drag the pin or type coordinates; it is used to suggest the region's offline map.

The second step gives the engine your starting point and your constraints.

• Content: equipment (“Trotteur”, “Quad”, “Kart”), terrain (a saved trail, expected snow quality), starting fitness (1) — Deconditioned, Base, Trained —, training days per week.
• Days off (2): ticked once for the whole season; a race still falls on its date no matter what.
• Maximum distance per outing (3), optional: a limit on dryland, one on snow if the sport goes on snow, and your long-run days.
  • As soon as a long-run day is ticked, its limit is entered separately and the first one becomes the one for “other days”.
  • The plan first puts your long runs on those days, then shortens any training outing to its day's limit.
  • Removed kilometres are not moved; a race or a milestone is never shortened. Kart, quad, canicross, bikejoring, scooter: no snow field.
• “What the engine will build” (4), while you fill it in: plan length, weeks already gone, outings per week and their total.
  • It says whether the build fits its four phases (base, intensity, peak, taper; in Sprint, one taper week then race week) or the season is too short.
  • Absent on an “In my hands” plan.
• Generating: the plan is generated on creation; editing an objective reopens the same form, pre-filled.
• “Save” then regenerates the plan: the objective's and its season's settings (Setup tab), adding, editing or deleting a milestone. “Regenerate” (Setup; owner or vet) recomputes without changing anything.
• “Adjust the season” (Season view, under the frieze; owner): the season's dates only. Weeks already run keep their content and phase, logged outings don't move; while nothing has been run, any objective that loses preparation weeks says so (“… than planned”, the race keeps its date); once weeks have been run, the plan keeps its grid and loses nothing — including the day its weeks start on: moving the start from Wednesday to Monday changes the season's date, not the weekday the weeks begin. To change it afterwards, use “Shift the weeks” (below). A race outside the new season is flagged. “Regenerate the plan” is offered objective by objective. On the phone: “Edit season” in the “⋯”.
• “Shift the weeks” (Season view, next to “Adjust the season”; an objective's Plan tab, above the week; and under “Regenerate the plan” in Configuration — on the phone, “⋯” › “Shift the weeks”; owner and vet/coach): your weeks start on another day, for instance Monday. Pick the day; the box gives the switch date and the transition with no session before it (“run as you like”), then regenerates the season's plans on that day, without going back in their progression. Past weeks stay in “Previous plan versions”, your outings don't move, and the week of the switch becomes week 1. What it doesn't do: no shortened week; a plan “held by hand” isn't shifted; if a milestone or the race falls during the transition, shift after it.
• On a hand-edited plan you are asked first, “Save and regenerate” or “Save without regenerating”, which keeps your edits. On an “In my hands” plan, no more regeneration.

The plan opens on the current week: volume, rest, sessions.

• Bars, below the week: one per week, height following the planned volume; a flag marks the objective and each milestone. A click, or “‹” and “›”, changes week; “Team” / “Per dog” toggles the view.
• Week (1): total volume, rest days, what your maximum distances took off it (“−12 km: 2 outings shortened to your limit”), day-by-day breakdown, sessions.
• Session (2): date, distance, “up to” speed, effort zone.
• “Up to” is a ceiling, not a target (3): ride slower if that's your dogs' comfortable pace.
• Sprint plan: “Restart” reads “Race pace” (the pace the longest stage will ask for, in zone 3); a rehearsal session carries “Race rehearsal · stage 1/3”. The “up to” rises at peak (28 km/h on the sled) without becoming a speed to hold.
• Folded below the sessions: “Volume range”, “Why this volume” and “Alerts & adjustments (N)”.
  • “Left out of this plan” and “Reduced load in this plan” list the dogs pulled from the plan or scaled back, with the cause (injury, medication, body condition…) and “View carnet”.

“Edit” opens direct editing of the week; every change is saved at once.

• Who: the owner, kennel in good standing.
• Closing a day (2) when the kennel is unavailable: in “Edit” mode, click it. Its session is removed at once; reopening it doesn't bring it back, a regeneration is what fills it in.
• Session: the distance (3) changes on its row, without a dialog.
  • “Edit session” sets the day (by name; a closed day is not offered), the effort (kilometres and max pace, or duration: “35 min at most”), the zone, the surface, the method, a free instruction.
  • “+ Session” adds one, by default on the first free day, with the last session's surface and method.
• A touched plan is “edited”: a regeneration then asks for confirmation, and MushMate offers to keep it in your hands.
• Week gestures (4), web and phone:
  • “Copy the previous week” replaces the displayed week's sessions (confirmation if it had any); an event session is not copied, a session whose day is closed is left out, the event week is not replaced;
  • “Add a week” adds an empty one at the end; “Remove this week” only exists on the last one;
  • weeks follow the calendar: none is inserted or removed in the middle (a middle week is emptied), and the event week cannot be removed.

A word of the week and a note per day go alongside the dog's sessions.

• Sports: canicross, skijoring, bikejoring and scooter.
• Content: what you do without the dog (strength work, cycling, club session). Every kennel member reads it.
• The owner writes it, day by day with “Write”, or in one go with “Paste the week's text”:
  • each day named at the start of a line (“Monday: …”, “J3 - …”) becomes that day's note, anything before becomes the word of the week;
  • a preview comes before saving; a note already written is only replaced once you confirm.
• The dog's sessions do not change; these notes survive a regeneration.
• On the day, the home page shows the session with the dog (or “Rest”) and the day's note. Do not write health information there.

Once “In my hands”, MushMate no longer regenerates the plan or proposes changes to it.

• Switch (1), under the objective's title: “Adjusted by MushMate” (the starting setting) or “In my hands”.
  • The owner switches with one click, either way, with no confirmation; other members read the state.
  • A plan is needed: the mode takes one over, it doesn't create one.
• What changes (2):
  • “Save” on an objective, a season or a milestone saves, without rewriting anything;
  • the banners keep their alert (a dog injured since the plan, young-dog cap crossed, actual load above the plan, young-dog regime changed), their button becomes “Edit the plan”, no proposal is made;
  • closing a day removes its session, on the web and on the phone; placing it elsewhere is up to you;
  • an “In my hands” chip recalls it on the objective's card.
• What the mode doesn't do: MushMate rebalances nothing. A distance you change moves no kilometre to another day, the following weeks don't adjust.
• Switching back to “Adjusted by MushMate” changes nothing either: the plan stays as it is until you regenerate it.

Three panels: what the engine read, its settings, the forecast form.

• “Why this plan?” (1) plays back in sentences what the engine read from your input: sport, distance, race date, number of weeks, starting condition, training days and days off, dryland and snow start, the return to dryland when an end of snow is set, snow quality, average temperature, milestones, long-run days and maximum distances if entered, the growth cap used.
  • It also says how many dogs a welfare guard took out of the plan, and which.
• “Freshness projections” (2): for a subscribed (or trial) kennel, the forecast form up to race day, team average and dogs to watch; without a subscription, the panel invites you to subscribe.
• “Under the hood of the plan” (3): read-only, the model's global settings that explain the calculation — validated by the product's vet, not by you.

MushMate compares actual load with the plan's over seven days; it flags and proposes, it never regenerates on its own.

• “N things to check” (1) gathers the banners: one line per point, with its action; the explanation unfolds.
• Notable gap: the banner names the dog or the team, the percentage of the gap, the days you went out and the sessions planned — each dog is compared with ITS prescription, which accounts for its weight (a light dog carries a little more than the 25 kg reference, a heavy one a little less), with “Regenerate the plan from actual load”.
  • After a regeneration, this button steps aside until your next outing: the days being judged are already run, so regenerating again would not change them. The banner says since when the rest of the plan has been reset.
  • A run logged at an impossible speed skews the calculation (“Impossible reading”): fix the data before regenerating.
• “A proposal is waiting for you” replaces that banner after a sustained gap, or if you closed a day: it names the cause, charts planned/realised/proposed and lays out the coming weeks.
  • All are taken by default: “Take the proposal” applies it in one click.
  • Unticking a week keeps it as it is (a warning if a jump then exceeds the growth cap); the button becomes “Take these N weeks”. “Keep mine” turns it down.
• “Young-dog limit crossed”: the plan asks a young dog for more than its age bracket allows.
  • The warning names the dog, quantifies the overrun and waits for “I understand and accept this plan” — or, when possible, a regeneration within the limits (on a hand-edited plan, after the same question).
  • Only the weeks ahead count. Overruns in weeks already run stay under “Already run”, folded, and ask nothing more: no regeneration can change them.
  • Your acceptance holds for the objective, dog by dog: a regeneration asks again only for a new overrun, or one higher than what you had accepted (marked “new”). After “Regenerate within the limits”, “Regenerate the plan from actual load” keeps that choice.
  • Nothing is scaled back on its own.
• “Plan out of date”: a dog on the plan was injured, put on medication or moved into a different age bracket since generation; its button regenerates on the spot. A “Plan needs regenerating” banner flags a changed young-dog regime.
• Race: a banner warns when the remaining team no longer meets the event's minimum headcount.

A milestone is a preparation race or raid; saving or deleting one updates the plan.

• “Add a milestone” (Setup) records a date, a type (“Race” or “Raid”), a distance or a label (1).
• For a raid, “Stages (multi-day raid)” (2) gives its race days, daily distance and mandatory rest. A milestone keeps “N days × distance” for now, without a stage-by-stage programme.
• Each milestone opens into its own sheet, can be edited or deleted.

Every regeneration sets the plan aside; “Export” takes it out as CSV or a calendar.

• Versions (1): the current plan is set aside before each editing session and on every regeneration; edits made less than 30 minutes apart count as one.
  • An objective keeps the last three; the oldest is deleted.
  • The collapsible panel lists them with when each was set aside and “Put back in service” (owner, kennel in good standing).
  • After a regeneration, the panel opens on the comparison between the new plan and the one it replaces, and says what changed (weeks, kilometres, peak). “See what changed”, under “Plan regenerated ✓”, leads there.
  • On the phone, the “Plan regenerated” message says the same: the weeks that move, kilometres added or removed, the peak before and after.
  • “Compare with” sets planned/done/proposed against one of them or a proposal in flight.
• “Export” downloads the plan as CSV (by week, by session, with its parameters or its diagnostics) and opens a printable calendar (“Print calendar”), to save as a PDF from your browser.
• On the phone, Objective › “⋯” › “Export the plan (CSV)” hands the same four files (weeks, sessions, parameters, diagnostic) to the share sheet; the parameters need a connection. “Share the calendar as PDF”, in the same menu, gives the website's printable calendar as a PDF.

A “Race” tab gathers the event's file; a badge says where the validation stands.

• File (Race or Expedition objective): the season's races, the attached race definition (“Change race” if needed), “What the plan keeps”, “My entry”, the designated musher, the planned rig, useful links, and notes with attachments.
• Secondary participants: dogs entered on another objective of the season but present at this race.
• Validation: a badge above the plan shows whether it is validated (“Validated by an expert”), requested, under review, or has changes requested, with the reviewer's note.
• With no review requested yet, the owner finds “Request a validation” below the plan if the kennel has an active validation service, otherwise “Find an expert” on the marketplace.

Set once for the whole kennel: what the model charges to every session.

• Where: “Model parameters”, below the list of seasons.
• Weights (1): the reference musher's and each rig's (bike, sled, quad, kart, scooter, pulka, kicksled). The musher's weight is only a fallback (nobody designated, weight not entered, earlier outings): the load follows the weight of whoever drove (Settings › My weight).
• Overtraining window (2), and young-dog regime (3): Cautious, Standard or Sport, with the editor for its caps by age bracket.
• On the phone: “Model parameters” opens from the Plan tab; the weights, the overtraining window (1 to 90 days) and the young-dog regime can be set there too. Only the owner changes them; the other roles read them. Only the window says why it is greyed out: the greyed weights and the young-dog regime without a button do not. Offline, nothing can be changed.

The phone does almost everything the web does: the owner creates, edits, generates and decides.

• Plan tab: a dark block (“Week N of M”, the objective, the phase ribbon, the readiness ring), then “This week”. The team's pace ceiling is tucked under “Plan details”.
• The “⋯” opens “The plan” sheet (owner): “Adjusted by MushMate” or “In my hands”, “Edit the plan”, “Close a day”, “Generate the plan”, edit or create goal and season, export, “Delete the objective…”.
  • Generating, regenerating, deciding on a proposal or acknowledging a young-dog cap overrun work there too.
• “Edit the plan”: one week at a time, distance on each row, day picked by name, adding or deleting a session — online only. Saving an objective (created or edited, its race or its season) updates its plan when you get back to the screen.
• “Close a day” closes or reopens the date but doesn't clear the session: it asks for the realigned proposal, which you accept on its card.
• Each session shows, once the outing has happened, a numeric gap against its prescription (distance as a percentage, “zone exceeded”), silent when it matched.
• The “Plan out of date” warning (injury, medication) shows too; the “Regenerate the plan” button sits at the top of the screen.
• Maximum distances and long-run days can also be entered on the phone; what a week lost to them is only shown on the web for now.
• The phone's Plan reads week by week: “Previous week”, “Next week” and “Back to this week”, with no network and for every role (nothing is written there). Before the season the Plan opens on the first week, with its dates; after it, on the last.
• What follows the week being read: the sessions, their alert chips, the bitches' heats, the person's week (“For you, week 3”) and the “YOUNG” and “SENIOR” chips in “Plan details”. The dark header, the dog that slows the team and the season path keep saying where the season stands; the done-sessions strip stays that of the current week.
• “Before the start”: during week 1, outings logged in the 7 days before the plan's first day are named under the strip (“Before the start: 1 outing · 8 km (Mon, Sep 7)”); on the website, week 1 carries “+8 km before the start”. They tick no session and count neither in “sessions done” nor in “Done”.
• Preparing the race (owner, online): “Add a milestone” under the milestone frieze, and a tap on a milestone to edit or delete it — the plan updates afterwards; “Race file”, under the race sheet, for the bib, meeting point, deadlines, designated musher, planned rig, secondary participants, links and notes (the handler writes participants, links and notes too); “Create a private race” under “Reference race”, in the objective form. What stays on the website: a milestone's reference race, team sizes and course, and note attachments (the phone counts them, without opening them).
• “Previous plan versions”, under “Plan details”: the last three versions set aside, and “Put back in service” (owner, online). The week-by-week comparison stays on the website.
• A season without an objective can be deleted from its screen (“Delete season”, owner); the phone first checks, on the server, that no objective was added meanwhile.
• “Load above plan” / “Team below plan” shows too, online, with “Regenerate the plan from actual load”; offline, it stays silent.
• “Why this plan?” is not on the phone yet, except its season sentences: “Dryland and snow”, under “Plan details”, draws dryland, snow and back on dryland (end of snow) and spells them out.