The Diary Is the Brief: Aligning UK Proposals to a Client’s Approval Cycle

Most proposals are not rejected. They are mistimed. A document that would have been persuasive in September can become an administrative inconvenience in March, and the difference is rarely the quality of the argument. It is the client’s approval machinery: the board paper deadline, the budget window, the audit committee cycle, the procurement queue and the fortnight when half the decision-makers are on leave.

For UK advisers, this is a client-relationship issue before it is a project-management one. A proposal is not read in isolation. It arrives inside a governance rhythm that the client already lives by. Reading that rhythm accurately is a form of respect, and it is also a commercial discipline.

The proposal as an item in a queue

It helps to stop thinking of a proposal as a standalone document and start thinking of it as an item entering a queue. Someone has to sponsor it. Someone has to review it. Someone has to compare it with alternatives, confirm the budget and decide whether it goes to a formal meeting. Each of those steps has a date attached, even if the client has never written that date down.

A proposal that arrives three days before a board meeting is not early. It is late. A proposal that arrives during the August lull may be read, but it will not be decided. A proposal sent after the finance team has locked the current-year budget may be technically live but commercially frozen until the next planning round. None of this is a comment on merit. It is a comment on sequencing.

The adviser’s task is to understand the sequence before choosing the moment of submission.

Start with the approval chain, not the calendar

A generic calendar is of limited use. UK clients do not share one rhythm. A listed company, a private family business, a regulator, a local authority and a venture-backed scale-up will each approve spending in different ways. The starting point is therefore the approval chain: who decides, who influences, who can stop the proposal, and what evidence each of those people needs.

Once the chain is clear, the calendar becomes useful. The practical questions are:

• Which formal meeting must approve this decision, and when are its papers due?
• Is there a pre-read or steering group that must see the proposal first?
• Does the budget sit in the current financial year, the next planning cycle or a separate capital process?
• Does the audit and risk committee, or an equivalent assurance forum, need to review the proposal before commitment?
• Are there known blackout periods, such as the Christmas shutdown, the August holiday season or a regulatory close?
• Who is the sponsor, and when is that sponsor available to socialise the proposal before it becomes formal?

These questions produce a timing profile, not a guess. The profile should be short enough to use: one page per significant client or opportunity. It should be updated when a gate moves, because gates do move.

Back-plan from the gate

Once the hard gate is known, the submission date can be set by working backwards. A board paper may need to be circulated several working days before the meeting. The finance team may need a week to confirm the budget line. The sponsor may need two conversations before they are willing to put their name to the proposal. Legal or procurement may need to review the terms before the paper is complete.

This backward plan should distinguish between sharing and submitting. There is a useful middle stage in which the adviser shares a draft or a summary for informal comment. That is not a formal submission. It is a way of testing the shape of the proposal without starting the clock. Used well, it reduces the risk of a formal document being rejected for reasons that could have been resolved earlier.

The back-plan should also include a decision not to submit. If the next gate is too close for the proposal to be properly considered, the better course is often to aim for the following cycle and say so plainly. A client who is told that a proposal will be held until the next paper deadline is being managed, not neglected.

When to chase and when to hold

Follow-up should be tied to the gate, not to the adviser’s anxiety. If the proposal is in a pre-read phase, a short written note asking whether the sponsor needs anything further is appropriate. If it is waiting for a committee date, chasing the committee is pointless. The useful question is whether the paper is complete and whether the sponsor has what they need to present it.

There are moments to hold back. The week before a board meeting is usually not the time to introduce a new commercial argument. The first week of January is usually not the time to ask a finance director to reopen a budget that has just been closed. The Friday before a public holiday is usually not the time to send a document that requires a considered response.

Holding back is not passivity. It is the deliberate choice to avoid wasting the client’s attention. The adviser who understands the difference between a live opportunity and a live decision will be trusted with more of both.

UK rhythms worth mapping

Several UK rhythms recur often enough to be worth checking. The financial year ending 31 March shapes budget behaviour for many organisations, with planning activity concentrated in the final quarter and new spending often constrained until the next year is confirmed. Audit and risk committees tend to have fixed cycles, and papers may need to be prepared well in advance. Board meetings are frequently supported by pre-reads, meaning the real deadline is earlier than the meeting date. The summer holiday period and the Christmas shutdown can add two to three weeks to any decision that requires several people in a room.

These are patterns, not rules. The point is not to assume that every UK client behaves in the same way. The point is to ask early enough that the answer can be used.

A commercial habit, not an administrative one

A timing profile takes an hour to build and a few minutes to maintain. It improves the quality of the proposal because the adviser knows what the reader needs and when the reader will read it. It improves the relationship because the client is not asked to absorb a proposal at the wrong moment. And it improves the commercial outcome because fewer proposals are lost to avoidable delay.

The best proposal is not the one that is sent first. It is the one that arrives when the client can actually decide.