Before the Promise Lands: A Five-Minute Review for Fixed Dates

In most UK offices, deadlines are promised in ordinary moments. A client asks for confirmation on a call. A line manager checks whether a piece of work can be ready before a board meeting. A project group needs a date for the next stage. The person closest to the work gives an answer, often in good faith, and the date leaves the room.

Only later do the assumptions surface. A approval was expected sooner. A colleague is on leave. A bank holiday has quietly removed a working day. The date itself has not changed, but the confidence behind it has. By then, correcting the promise feels more awkward than testing it would have been.

The safeguard is not a committee. It is a short review with one other person before the date is confirmed. Some teams call this a deadline witness; others call it a pre-commitment check. The label matters less than the habit. Five minutes of calm scrutiny can prevent weeks of quiet drift.

Why a second reader changes the date

A second reader does not need to know every detail of the work. They need to test whether the date rests on a shared understanding or on private optimism. When a deadline is held together by one person's mental model, small gaps are easy to miss. The owner knows what they meant by 'ready', which approvals they assumed would be quick, and which colleague they believed would be available.

A reviewer asks the obvious questions that familiarity hides. They are not there to challenge competence. They are there to test the date. That distinction keeps the conversation practical. The aim is not to make commitment harder, but to make the promise more likely to hold.

What the reviewer should check

The review should be brief, but it should not be vague. Five checks are usually enough for a fixed date that carries real consequences.

• Assumptions. What must be true for the date to hold? The reviewer should ask about resource, sign-off, data, availability and any external response the plan depends on. If an assumption is fragile, it belongs in the open before the promise is made.
• Dependencies. Who else must deliver something, and by when? A date that depends on another team, a supplier or a client response is not a single-team deadline. The reviewer should confirm that the dependency has a named contact and an agreed date, not merely a hopeful expectation.
• Working-day count. Count the real working days, not the calendar days. Weekends, public holidays and known leave all reduce capacity. In the final weeks of 2026, the Christmas and New Year bank holidays can make a short calendar gap look more generous than it is. A simple count often exposes a date that was never realistically resourced.
• Named owner. One person should be accountable for delivery. A team name is not an owner. The reviewer should ask who will notice first if the work slips, and who has authority to adjust the plan before the date becomes a shortfall.
• Evidence of progress. What already exists? A draft, a decision, a signed-off scope or a data extract is evidence. A feeling of momentum is not. The reviewer does not need a detailed status report, but they should see that the date is connected to something tangible.

How to run the five-minute review

Keep the routine lighter than the decision. Before confirming a fixed date, ask a colleague whether they can test it with you for five minutes. Give them the date, the deliverable and the main dependencies. If a short written note helps, use one, but avoid turning the conversation into a formal submission.

The reviewer should ask questions rather than offer a verdict. 'What has to happen first?' is more useful than 'Is this realistic?' The first question reveals the plan; the second invites a general opinion. If the review changes the date, record the reason briefly. If it does not, note that the date has been tested. That record is useful later, when memories differ.

For material commitments, the reviewer should be someone with adjacent knowledge rather than direct involvement. A colleague from another team can often see the gaps more clearly. For routine dates, a peer in the same team is enough. The important point is that the reviewer is not the person making the promise.

Keeping the habit light

A deadline witness should not become a sign-off gate. The purpose is to catch quiet drift, not to add a layer of approval to every task. Most reviews will confirm that the date is sound. That is a useful outcome, not a wasted five minutes. The occasional correction is the return on the habit.

It also helps to make the review reciprocal. If you ask a colleague to test your dates, offer to test theirs. Over time, the practice becomes ordinary, like checking a calculation before sending a quote. It is not an escalation, and it is not a judgement on the owner. It is a small, shared discipline that protects the team from deadlines that only one person believes are realistic.

As 2026 moves into its final weeks, fixed dates tend to arrive with more pressure behind them. Year-end requests, handovers and client commitments can crowd the diary. A five-minute review will not remove that pressure, but it can stop a poorly tested date from becoming the next problem. Plan calmly, test the promise, and let the date leave the room only after someone else has looked at it.