From Fixed Date to Firm Plan: Building a Client Deadline That Holds

Most delivery pressure does not come from the work itself. It comes from discovering, three weeks out, that the work was always going to take five. A client date arrives, everyone agrees it is achievable, and the timetable is then built forwards from the day the instruction landed. That is the wrong direction of travel. A deadline is a specification, and specifications are read backwards.

The discipline described here is unglamorous. It takes perhaps half an hour at the start of an engagement and ten minutes a week thereafter. In exchange, it replaces the late scramble with an early, factual conversation — which is nearly always the cheaper of the two.

Begin with the date the client actually needs

The first question is not when we can deliver. It is why the date is the date. A board meeting, a regulatory filing window, a supplier cut-off, a planned announcement, a seasonal trading period: each of these fixes a date for a reason, and the reason tells us how much movement exists.

Three clarifications are worth obtaining in writing before any plan is drafted:

• The date itself. Confirm the day, not the week. ‘End of March’ has at least five possible meanings.
• The consequence of lateness. If a slip of one week is inconvenient, the plan needs modest protection. If it is material to the client’s own obligations, the plan needs considerably more.
• The true immovable date. Clients often name a comfortable target and hold a harder date privately. Asking directly which date cannot move, and which is a preference, is not impertinence. It is the basis of an honest schedule.

There is a second date to establish early: the client’s internal review. Approvals rarely happen on the day material is sent. If a document goes to a committee, assume a cycle, not a signature.

Four layers, counted backwards

A workable reverse schedule has four layers, and they are laid down in sequence from the deadline rather than from today.

1. Handover and close. What must be true on the final day? Signed-off documents, transferred files, a completed handover note, an invoice that matches the agreed scope. Reserve the last two or three working days for this and do not spend them on production.

2. Client review and approval. Work backwards from handover to the point at which the client must receive the final draft. Build in the review window the client has agreed, not the one everyone hopes for. Where approval sits with several people, establish who signs and by when — a single named decision-maker and a stated date prevent the slow drift that quietly consumes a fortnight.

3. Production and internal quality review. Allow the time the work genuinely takes at the standard required, plus a scheduled review before anything leaves the building. A review that happens because there is spare time is not a review; it is a formality.

4. Inputs and dependencies. Working further back still, list everything that must arrive before production can start: client data, third-party confirmations, legal or compliance input, access to systems, signed authorisations. Each dependency gets a required-by date and a named owner. Most late delivery is a dependency that was never dated.

Laid out this way, the plan usually reveals the truth within minutes: either there is room, or there is not. Both answers are useful. Only one of them is usually discovered in time.

Buffers placed where they will be spent

A single buffer at the end of a plan is a comfort, not a control. By the time it is reached, it is often already gone. Better practice is to distribute protection where real life intervenes.

• Before client review, not after it. Reviews expand to fill the time available.
• Around third-party inputs, which are the least controllable element in most schedules.
• Across leave and known absences. The UK calendar is not a secret: bank holidays, half-term weeks, the August period and the days between Christmas and the new year all reduce effective capacity. A plan that assumes five full working days in a week containing a bank holiday is arithmetic error dressed as optimism.
• At the handover, as a short closing reserve rather than a long final cushion.

Buffers should be visible and labelled. An unlabelled buffer invites the client to treat it as slack for additional requests; a labelled one invites respect.

One page, shared early

The schedule earns its keep only when the client can see it. A single page is enough: milestones with dates, dependencies with owners, decision points with names, and a short note on what happens if a dependency slips.

Share it in the first week, alongside confirmation of scope. Two benefits follow immediately. The client sees the dates on which they are needed, which improves the quality and timeliness of their input. And the plan becomes a shared reference rather than an internal hope — something to point to without accusation when a date is at risk.

A useful addition is a confidence line: a plain statement of how much contingency remains at each milestone. Green, amber, red is sufficient. It converts a vague sense of unease into a fact that can be discussed.

Updating honestly, and early

A reverse schedule is a forecast, not a promise of omniscience. It will need revision. The test of the discipline is whether revisions are shared while they are still useful.

Set a simple rule: when a dependency passes its required-by date, or when remaining contingency falls below an agreed threshold, the client hears about it within one working day. The message should state what has changed, what it means for the date, and what is proposed. Silence in the hope that matters will recover is the most expensive choice available, because it spends the client’s contingency without their knowledge.

When the arithmetic says the date will not hold

Occasionally the count backwards produces an answer nobody wants. Better to have that conversation in week one than week ten. The options are usually three: reduce scope to protect the date, phase the delivery so the client receives what matters first, or move the date with clear reasoning. Presenting the arithmetic — rather than an apology — keeps the discussion commercial and calm.

The habit worth keeping

Twenty minutes with a calendar at the start of an engagement is a modest investment. It replaces the familiar pattern of compressed weeks, rushed reviews and a final fortnight conducted at speed. Deadlines do not become less fixed by being ignored, and they rarely become easier by being met with urgency. They become manageable when someone counts backwards, writes it down, and shares it while there is still time to act.