The Week-Fit Review: Checking Whether Consultancy Advice Survives Ordinary Working Life

A consultancy recommendation can be coherent, well researched and properly costed, yet still fail on an ordinary Tuesday morning. The plan may be sound in principle, but the people who must act on it are already committed elsewhere. For UK clients signing off a final report, the working calendar is not an administrative detail. It is evidence about whether the advice can be delivered.

The calendar as a form of evidence

Most proposals are tested against strategy, budget and risk. Fewer are tested against time. That gap matters because time is the constraint that exposes weak assumptions most quickly. A recommendation may require a finance director to attend three workshops in a month when the same finance director is closing the year-end accounts. It may depend on operational managers making rapid decisions during a period when they are covering frontline absence. It may assume that a steering group can meet fortnightly when the governance calendar has already been fixed for the next two quarters.

None of these problems will necessarily appear in the slide deck. They appear in diaries. A week-fit review asks a simple question: if this advice were accepted today, where would the required work actually sit in the working week?

Three calendars worth checking

A useful review looks at three calendars rather than one.

The first is the decision calendar. When will the client side actually be able to consider, challenge and approve the recommendation? Board dates, committee cycles, monthly management meetings and sign-off thresholds all shape the answer. Advice that requires a decision before the next scheduled meeting may be advice that requires an unscheduled meeting nobody has costed.

The second is the delivery calendar. Which named individuals must do the work, and what else are they already committed to in the same period? A recommendation that depends on a small team during a peak trading week is not necessarily wrong, but it needs to be recognised as a risk rather than treated as a free resource.

The third is the interruption calendar. This includes the recurring pressures that rarely feature in project plans: month-end reporting, payroll cycles, VAT returns, stock counts, seasonal peaks, school holidays and the quieter weeks around Christmas. These are not distractions from the plan. They are part of the environment in which the plan must operate.

A practical week-fit checklist

Before signing off a final report, apply a short set of diary-based checks. The aim is not to undermine the recommendation but to confirm that it has a realistic route into the working week.

• Identify every named person the recommendation depends on. If the report refers only to the finance team or the operations group, ask for names and roles.
• Estimate the time commitment for the first thirty days. Include preparation, meetings, review and follow-up, not only the visible workshop hours.
• Compare that estimate with the actual calendars of those named people. Look for weeks where the commitment is impossible rather than merely inconvenient.
• Trace the decision route. Note the dates by which a decision would need to be taken to keep the plan on track, and check whether those dates align with existing governance.
• Ask what will be displaced. If the same people are already delivering other priorities, the recommendation must say what should stop, slip or be delegated.
• Test the first ninety days against known seasonal pinch points. A plan that assumes calm in a period that is never calm is not yet ready.
• Check the handover points. If the adviser will leave before certain actions are complete, confirm who owns the next step and when it will be reviewed.

These questions are not designed to produce a perfect plan. They are designed to reveal whether the plan has been tested against the client's actual capacity.

Warning signs that advice may be too elegant

Some recommendations read beautifully because they simplify the organisation into a diagram. The warning signs appear when the simplification meets the diary.

One sign is phantom capacity: the assumption that a senior person will somehow find the time because the recommendation is important. Importance does not create hours. Another is decision latency: the plan assumes a decision can be made quickly when the governance route is slow by design. A third is the single point of failure: one individual appears repeatedly in the delivery plan without any acknowledgement of what happens if they are unavailable.

A fourth sign is the seasonal collision. UK businesses often have periods when the same small group of people are carrying reporting, compliance and operational pressure at once. Advice that ignores these periods may still be correct, but it needs sequencing. A fifth sign is the missing stopping rule. If the recommendation cannot say what will be paused to make room for the new work, it is not yet a working plan.

What to ask for before sign-off

A final report does not need to contain a detailed project schedule, but it should contain enough time logic to be credible. Ask the adviser to set out the first thirty, sixty and ninety days in terms of named people, decision points and expected time commitments. Ask where the plan depends on external parties and what happens if their response is slower than assumed. Ask which parts of the recommendation are essential in the first quarter and which can wait.

This is not a request for more paperwork. It is a request for a clearer connection between advice and delivery. A recommendation that cannot survive a diary review is not necessarily a bad recommendation, but it is an unfinished one.

At Harman Dean, the standard we apply is simple: advice should be judged not only by whether it is right in theory, but by whether it can be carried out in the week the client actually has. The week-fit review is a modest discipline, but it prevents a familiar problem: a report that looks elegant on paper and collapses in practice.