The Undated Choice: A Kick-Off Decision Diary for UK Consultancy Engagements

Consultancy projects rarely stall because the adviser has stopped working. They stall because a decision sits in a diary that no one has drawn up. A recommendation is made, a meeting is promised, a paper is awaited, and the project drifts into the next reporting cycle without anyone being able to say precisely which choice went unmade. The remedy is not more project management theatre. It is a simple decision calendar, agreed at kick-off, that gives every material choice an owner, an evidence threshold and a date.

Why delivery is rarely the real delay

Delivery plans tend to be full of activity: interviews, analysis, workshops, drafts, presentations. They are much lighter on decisions. Yet a consultancy engagement is, in practice, a sequence of choices. Some are large, such as whether to proceed with a new operating model. Others are modest but still consequential, such as which data set is authoritative or which department will pilot a change. If those choices are not dated, the work may appear to continue while the project quietly loses its forward motion.

The decision calendar corrects that imbalance. It treats decisions as deliverables in their own right. It is not a substitute for a project plan, nor a device for adding bureaucracy to a small engagement. It is a short, visible instrument that makes clear what must be settled, by whom, and by when.

Start with a decision inventory

At kick-off, ask the consultant to produce a first list of decisions the engagement will require. This should be more than a list of meetings. It should identify the choices that will release the next stage of work. A useful inventory will include decisions about scope, data access, shortlisting, preferred options, budgets, governance, implementation sequencing and final sign-off.

For a UK engagement, the list should also capture decisions that may sit outside the project team: approval of expenditure, agreement to consult staff representatives, acceptance of a revised service level, or permission to proceed before a financial year-end. These are often the decisions that cause delay, precisely because they belong to someone who is not in the room.

Name the owner, not the audience

Every decision needs one named owner. A steering group, a board or a management team may be the forum in which a decision is taken, but a forum is not an owner. The calendar should say who is accountable for bringing the decision to the point of choice. That person may be a sponsor, a finance director, a programme lead or a departmental head. The test is simple: if the decision is not made on time, who will be asked why?

Naming an owner also clarifies the difference between consultation and decision. Advisers may recommend; colleagues may be consulted; affected teams may be informed. None of that removes the need for a single accountable person to carry the choice into the diary.

Define the evidence threshold

Decisions slip when the people expected to make them do not know what they are waiting for. The calendar should therefore state the evidence required for each decision. That might be a costed options appraisal, a risk assessment, a legal view, a data extract, a pilot result or a one-page summary of trade-offs.

There is value in being modest here. The evidence threshold should be sufficient, not exhaustive. A decision calendar that demands a perfect evidence base will become a monument to postponement. The client and adviser should agree, in advance, what will be enough to allow a reasonable decision to be taken.

Put dates on the diary, then add buffers

Each decision should have a target date and, where appropriate, a latest acceptable date. The target date is when the choice should be taken in the normal course of work. The latest acceptable date is when delay begins to affect dependent activity. The gap between the two is the buffer.

That buffer matters in UK business life. A decision that requires board approval may need to fit a papers deadline rather than the meeting itself. A choice that affects staff may need to avoid half-term, August leave or the Christmas period. A decision with financial consequences may need to align with month-end, quarter-end or the organisation’s financial year. The calendar should record these constraints openly so that a date is not mistaken for an invitation to decide at leisure.

Read the surrounding calendar

A decision calendar is most useful when it is read alongside the organisation’s other calendars. Board and committee dates, management reporting cycles, regulatory deadlines, payroll cut-offs, holiday periods and major operational events can all compress or extend the time available. A project can be technically on schedule while its key decision has no realistic route to approval before a two-week closure.

At kick-off, the client should provide the consultant with the relevant dates, not as a courtesy but as planning information. The consultant should then test whether the proposed project rhythm is credible against them. If a critical decision falls in the week before a board meeting whose papers have already closed, the calendar is not realistic. Better to discover that at kick-off than in the final month.

Run the calendar as a live instrument

A decision calendar should not be filed after the first meeting. It should be reviewed in every project meeting, with three questions: which decisions are due, which are at risk, and which have been taken but not recorded? The record matters. A decision that is not minuted, confirmed and circulated can be reopened by accident, usually at the least convenient moment.

It is also sensible to distinguish between decisions that are genuinely outstanding and those that are merely awaiting administrative completion. A calendar that treats every signature as a strategic choice will lose credibility. The purpose is to protect the choices that actually determine the shape and pace of the work.

Escalate the silent decision

When a dated decision passes without being taken, the response should be calm and factual. The owner should be reminded, the consequence should be stated, and a revised date should be agreed. If the decision is not important enough to warrant a revised date, it probably did not belong on the calendar. If it is important, the delay should be visible to the sponsor before it becomes a delivery failure.

This is where the decision calendar earns its place. It separates the project’s progress from the adviser’s effort. It allows a client to see that the consultant has delivered the paper, but the organisation has not yet made the choice. That distinction is fair to both sides and useful to whoever is accountable for the outcome.

A modest discipline with a material effect

The decision calendar need not be elaborate. A single table with columns for the decision, the owner, the evidence required, the target date, the latest acceptable date and the relevant cycle is often enough. For smaller engagements, it may sit alongside the project plan. For larger ones, it may become a standing item in governance.

Its value lies in what it prevents: the undated choice, the unowned recommendation, the paper that waits for a meeting that has already passed. UK clients who want consultancy advice to become action should put the decisions on the diary before the work starts. The adviser can supply the analysis, but only the client can supply the date.