Until now, a dog could only be in one objective per season. Preparing an April race and then a summer maintenance objective with the same team was impossible: "This dog is already engaged in another objective for this season". Not any more.
What changes
- Tick a dog in as many objectives as you like. On its chip, the form reminds you where it already is: "also Sled · 450 km (Apr 2)".
- Each objective keeps its plan. But two plans never prescribe the same dog on the same day: the objective whose date comes first prepares it until that date, race day included. The next one takes it back the day after.
- The objective that waits for its dogs says so. A blue banner: "10 dogs follow “Sled · 450 km” first (Apr 2). This plan prescribes nothing to them until then, and takes them back on Apr 3", with a bar showing both periods. In the plan's week, the days when the whole team is on the other objective are hatched, rather than looking like rest days.
It works the same on the website and on the phone.
What others see
Kennel members see the same plans, the same banner and the same hatched days, according to their role. Nothing leaves the kennel.
What it does not do
- No priority to set. The date always decides. On the same date, one of the two objectives leads, always the same one, and the banner says which.
- The second objective's plan doesn't count the first one's kilometres while the first one leads the dog. It assumes the dog is trained, and the plan proposal, which re-reads your real outings, corrects the gap afterwards.
- No recovery is added after the race: the second plan takes the dog back the next day, at its own volume. If your dog needs rest after the race, close those days in the plan.
- Secondary participants in the Race tab don't change: a dog listed there without a plan stays listed without a plan.
A decision taken against the obvious
A session the whole team can't run disappears from the second plan, instead of staying "for the whole team". Keeping it would have prescribed two sessions to the same dog on the same day, so a doubled load.
Also: the form finally says what blocks
A maintenance or expedition objective could refuse to save without a word: a distance with decimals (42.5 km), or a number of days left hidden after switching from "multi-day race" to "maintenance". Decimals are accepted, the hidden field no longer blocks, and if a field still blocks, the form names it: "Can't save yet: the “Distance (km)” field needs fixing."