Part I · Chapter 1 · The Ask · lesson 1
Work backwards from the date they asked for
14 min
Part I · Chapter 1 · The Ask · lesson 1
14 min
The message is four lines long and somebody in procurement sent it. They want your report before the contract renews. The renewal is twelve months from today.
Nobody has mentioned a control. Nobody has mentioned a firewall, a policy or a password. The only object in the email is a date.
So: if you said yes this afternoon, when would the work actually have to have begun? Pick a date before you read on. Out loud, or at least on purpose.
Predict
Four dates, and only one of them is in the email.
The report date is the one you were given. Work backwards from it.
Before the report there is fieldwork — somebody independent looking at what you produced. That stretch belongs to their calendar, not yours.
Before fieldwork the period closes. Before that it opens, and it stays open for however many months of operation are being described.
And before it opens, the work the period will describe has to already be in place. Work done during the period is visible inside the period, which is a different thing from being the ground the period stands on.
The start date is the fourth date. It is the only one that constrains you, and it is the one nobody writes down.
The model below runs that subtraction. Today is an input rather than the system clock, so the answer is the same every time anybody opens it. The buyer's date is twelve months out. Six weeks of fieldwork, which is unremarkable. Eight weeks of work before the period opens, which is optimistic.
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
Hold the dates and both work legs still. Shorten the period until the day work must start is no longer behind you, and stop at the longest period for which that is true.
Calendar months the window must cover before it closes.
| Length of the period, months | Days until the period must open | Days until work must start |
|---|---|---|
| 1 | 292 | 236 |
| 2 | 262 | 206 |
| 3 | 231 | 175 |
| 6 | 142 | 86 |
| 9 | 50 | -6 |
| 12 | -42 | -98 |
Not there yet — keep moving the controls.
A twelve-month period, closing six weeks before the report, means the period closes on the 21st of August 2027 and therefore opened on the 21st of August 2026. That is six weeks in the past.
Take eight weeks off that for the work that has to land first, and the start date is the 26th of June 2026 — ninety-eight days before the email arrived. The buyer's year does not contain a year of room. It contains about eight months of room, and that is the challenge's answer: at eight months the start date moves back into the future, and the target stops being something the calendar rules out on its own.
Notice what the two lines do. They are not slopes anybody can argue with. Every month added to the period pushes both dates back by a month, exactly, and no amount of effort applied in October changes where the 21st of August was.
The first three dates are negotiable in the way dates usually are. A reviewer can sometimes start a week earlier; a report can be chased. The fourth one is a different animal, because it is the only one nobody can buy their way past afterwards.
A period describes a stretch of time that has already happened. If a control was not running in August, there is no version of September in which it was. Money shortens fieldwork and chases a report. Nothing fixes August.
Check
That is the thesis of this whole subject, and it sits in the first lesson because everything after it is a refinement: this is a calendar problem long before it is a security problem. The security work is real, and most of it is work worth doing anyway. The calendar is the part that decides whether any of it can be described by a date somebody has already written into a contract.
Because the email does not look like it contains a calculation.
It names a document and a date, both of which read as procurement. The person who receives it is usually the person who can see the whole company, which means they are also the person with the least time, and the reasonable response to a four-line email is a four-line reply.
There is a quieter reason too. The subtraction produces an answer that is awkward to say out loud, and a date already in the past is not a finding anybody wants to carry into a meeting. So the honest version arrives late, from whoever eventually opens a calendar, and by then the sunk cost is an argument rather than a number.
The way out is unglamorous: run the subtraction in the reply. A date behind you is a negotiation if it is raised in week one and a mess if it surfaces in month eight, and the difference between those two is only who mentioned it first.