The objective form asks for a date, training days, closed days, a starting condition. Until now, nothing told you what the engine would do with them before you pressed “Add” and the plan appeared. You discovered the result afterwards, and a wrong entry showed too late.
What you read now
On the last step of the form, above the button, a box titled “What the engine will build” updates on every change. It says, for example: “A 27-week plan, from the start of the season to the race. 6 weeks have already gone by: 21 remain. 5 runs per week, about 135 over the plan. Progressive build in four phases — base, intensity, peak, then recovery before the race.”
Every number comes from the same arithmetic as the engine, not from an estimate. Weeks are counted from the season start to the race, race week included. Runs per week are what you asked for, capped by the days you leave open. The four phases appear as soon as the plan is four weeks or longer; below that, the box says the progression will be compressed.
If you ask for seven training days but close Monday and Sunday, the box says so at once: “You ask for 7 days but leave only 5 open: the engine will settle on 5.” That is exactly the kind of entry you used to see only afterwards.
What the sentence does not say
It does not say pace. The engine caps the speed of every session by sport, phase, effort mode and your team's known top speed; the raw figure for the sport would be wrong for most kennels, and we prefer saying nothing to saying a wrong number.
It does not say weekly kilometres or per-dog load either: those depend on each dog's form at generation time, and the plan shows them once it is built.
A defect fixed along the way
While wiring this sentence, we found that the summary on the right, “Before saving”, listed all seven weekdays as closed as soon as you opened the step, checked or not. The form reader took every checkbox, not only the ones you had ticked. That is fixed: the summary now names only the days you actually closed.