Part IV · Chapter 8 · The Second Year · lesson 5
The period that has to run continuously from now on
14 min
Builds on Work backwards from the date they asked for
Part IV · Chapter 8 · The Second Year · lesson 5
14 min
Builds on Work backwards from the date they asked for
Your first window ran for twelve months and closed on 30 September. The report about it will be issued in the middle of November.
Between now and then, a buyer will ask for the current one. Then another buyer will ask the same thing in March, and a third in July. None of them wants to hear that the period is between runs.
So the second window opened on 1 October, which was yesterday, and nobody held a meeting about it.
Predict
A window has three legs in front of it, and only one of them survives into a second year.
Remediation is work that has to land before the window opens, because a control fixed halfway through a period has half a period of evidence. In year one this is most of the project.
The window is the stretch of time you will later make claims about.
Fieldwork is the gap between the window closing and the report existing.
In a second year the remediation leg is gone. Not reduced — gone. There is nowhere to put it, because the next window opened the day the last one closed, so anything you fix now gets fixed in front of the reviewer rather than before them.
Below, work backwards from a report date to the day the window has to open. The remediation leg is set to zero, because in a continuous cycle there is no gap to put it in, and fieldwork is six weeks.
Window countdown
Hypothetical model, not a forecast
Works backwards from a target report date to the day the observation window must already have opened, and the day work must have started for it to open on time. It answers when you must start, and it will never answer whether you are ready — no arrangement of dates can tell you that.
It assumes
It ignores
Your last window closed on 30 September 2026, so the next one has to open on 1 October 2026 with no gap at all. Fieldwork is six weeks and there is no remediation leg. Move the target report date until the window opens on exactly 1 October 2026.
| Window length, in months | Days from today until the window must open | Length of that window, in days |
|---|---|---|
| 1 | 199 | 30 |
| 2 | 168 | 61 |
| 3 | 140 | 89 |
| 6 | 48 | 181 |
| 9 | -44 | 273 |
| 12 | -136 | 365 |
Not there yet — keep moving the controls.
A report dated 12 November 2027 needs a window from 1 October 2026 to 1 October 2027. Today is the second of October, so that window opened the day before yesterday and the figure the model reports is negative by one day.
Nothing is wrong. That is the normal state of a second year: the period you will be examined on is already running, and the only question is whether the controls inside it are running too.
Watch what the two lines do as the window gets longer. Ask for a one-month window and the opening date is nearly a year away, which feels comfortable and produces a document almost no buyer wants. Ask for the twelve months buyers do want and the opening date is behind you. There is no setting on that chart where a twelve-month window and a comfortable start date coexist, and that is not a planning failure — it is what continuous means.
In year one the sequence is: fix things, then open the window, then collect evidence of the fixed things working.
In year two the window is already open. So a control you redesign in February produces February-to-September evidence inside a window that started in October, and the four months before the redesign are still in the period and still get asked about.
That is not a reason to avoid redesigning controls — a control that needs redesigning is worse than a design change mid-period. It is a reason to say so in writing when you do it, with the date, rather than letting the artefact trail start abruptly in February with no explanation attached. The engine's view of this is the same as a reviewer's: an artefact that does not reach back to the start of your window leaves the earlier part of the window spoken for by nothing.
Here is a composite second-year calendar, built from the ordinary case rather than from a disaster.
Four annual controls and a fieldwork week, in one month, owned by substantially the same three people. This is the collision, and it recurs every October for as long as nothing moves.
The fix is a one-off and it only runs in one direction. You can pull an annual control forward — run the restore test in July instead of October, eleven months after the last one — and the only cost is doing it slightly sooner than you had to. You cannot push one back, because thirteen months between instances means there exists a twelve-month window containing none of them, and that window is the one somebody will ask about.
So staggering is paid for once, in early work, and it buys a flatter year for ever. It is the single highest-value hour of scheduling in a second year and it appears on nobody's plan, because in year one the cluster was the project succeeding.
Check