Advice That Survives Monday: Turning a Consultancy Report into a Working Decision

Most consultancy projects end in the same way: a polished document is circulated, thanked for, and quietly filed. The work may be sound. The analysis may be thorough. Yet within a fortnight the report has joined the pile of documents that were read once and changed nothing. For UK clients paying for advice, that is an expensive outcome—not because the adviser failed, but because nobody planned for the advice to survive contact with the day job.

Advice has a shelf life. It is freshest in the final meeting, when the findings are still in the room and the sponsor is still attentive. After that, operational pressures return, inboxes fill, and the recommendation competes with everything else. The remedy is not a longer report or another governance layer. It is a modest adoption routine built around three anchors: a named executive sponsor, a one-page decision summary and a 30-day check on whether anything has actually changed.

Commission the use, not just the document

The first opportunity to prevent a report going unread comes before the adviser is appointed. At commissioning, UK clients should state what the advice is for: which decision it should inform, which behaviour it should alter, and who will own the change once the project closes. A brief that asks only for a review, a diagnostic or a strategy invites a document. A brief that asks for a decision and an adoption plan invites something more useful.

This does not mean every project needs a transformation programme. A small business may simply need a clear view on pricing, premises or a supplier contract. A larger organisation may need a board-level recommendation on operating model or risk. In each case, the commissioning conversation should include the question: what will be different on Monday morning if this advice is accepted? The answer belongs in the brief, not in the final presentation.

It is also sensible to agree the shape of the output at the start. A short decision paper, a one-page summary and a supporting appendix will usually serve better than a single monolithic report. The client should reserve the right to ask for the summary first. If the adviser cannot express the recommendation plainly at the outset, that is worth discussing early rather than at handover.

The sponsor is an owner, not a sign-off

Executive sponsorship is often treated as a formality: a senior name on the cover, a brief appearance at the kick-off, a signature at the end. That is not sponsorship. A genuine sponsor owns the conditions in which advice is used. They attend the key reviews, resolve competing priorities, make time for the team to act and can explain the recommendation without reading from the slides.

For UK clients, the practical test is simple. Can the sponsor state the recommendation, the main trade-off and the first action in three sentences? If not, the advice is not yet embedded at the level where decisions are made. The sponsor need not be the chief executive. They do need to be senior enough to unblock the work and close enough to understand the operating reality.

Sponsors should also protect the review meeting from becoming a presentation. The most valuable sessions are decision forums: what are we accepting, what are we rejecting, what remains uncertain and who will act. A sponsor who asks those questions is doing more for adoption than a dozen endorsement emails.

Put the decision on one page

Every consultancy report should carry a one-page 'so what' summary at the front. Not an executive summary that repeats the contents page, but a decision page. It should state the decision requested, the three findings that matter most, the recommendation, the principal risk or cost, and the first three actions with owners and dates.

The one-page test is not about dumbing down. It is about respect for the reader. A busy finance director, operations lead or non-executive should be able to understand the advice in five minutes and know what is being asked of them. If the summary cannot be written clearly, the thinking may still be incomplete.

UK clients should ask for this page before the final report is bound. It is far easier to challenge a muddled recommendation at summary stage than after the appendices have been polished. The page also travels well. It survives forwarding, extracts well into board papers and gives the sponsor a ready-made script for conversations in corridors and on calls.

Review for decision-readiness, not perfection

The review meeting should focus on whether the advice is ready to be used. That means testing the evidence, surfacing dissent and agreeing the conditions under which the recommendation would not hold. A useful question is: what would make us decide not to act on this? If the answer is vague, the analysis may be less robust than it appears.

Minutes should record decisions, not just attendance. Where a recommendation is accepted, note the owner and the date. Where it is deferred, note why and what would trigger a return. This small discipline prevents the familiar drift in which everyone remembers the meeting differently and nobody remembers who was to do what.

It also helps to involve finance, legal, HR or operations before the final report, depending on the subject. Late objections are often not objections to the advice itself but to the absence of the people who must implement it. Early involvement costs time; late exclusion costs adoption.

Book the 30-day adoption check before close-out

The most practical safeguard is a 30-day adoption check, scheduled before the project closes. It need not be elaborate. A short meeting, chaired by the sponsor, with a simple tracker: which actions have started, which have stalled, what has blocked them, and has any decision actually changed?

The check is not an audit of the adviser. It is a check on the client system. If the recommendation has not moved, the useful question is why: competing priorities, unclear ownership, missing resource, or a change in circumstances. The answer may be to embed the advice more firmly, revise it, or stop. All three are legitimate outcomes.

Holding the check at 30 days is deliberate. It is early enough to correct drift and late enough to see whether the first actions were realistic. For larger programmes, a 60- or 90-day review may follow, but the 30-day check should not be skipped. It is the point at which advice either begins to become practice or begins to become archive.

Give the advice an expiry date

Finally, good advice should carry a review date. Recommendations rest on assumptions about markets, costs, regulation and internal capacity. Those assumptions age. A report that was right in the autumn may need revisiting by the following spring. Setting an expiry date is not a criticism of the adviser; it is a mark of mature commissioning.

A short assumptions register, included with the one-page summary, makes this easier. It tells future readers what the advice depended on and what would need to change before it was relied upon again. That is particularly valuable in UK organisations where teams reorganise, priorities shift and the person who commissioned the work moves on.

A modest routine with a clear return

None of this requires a new bureaucracy. It requires a named sponsor, a decision page that can be read in five minutes, and a check on whether the advice took root. Together, those habits give a consultancy report a better chance of surviving Monday morning—and give the client a clearer return on the fee.

The measure of good advice is not how impressive it looks in the final meeting. It is whether it is still shaping decisions a month later, when the adviser has gone and the day job has returned.