Dated, Versioned, Answered: A Governance Routine for UK Fee Proposals
Photo: UK professional business meeting reviewing printed fee proposal documents with expiry date and version control, via facts.net
A fee proposal is rarely just a commercial courtesy. In UK professional firms it is often the first detailed statement of scope, assumptions, price and service expectations that a client will see. Yet many proposals are sent without a stated shelf life, then left to sit in inboxes while rates, availability and instructions quietly change. By the time a client responds, the document may no longer describe the service the firm can actually deliver.
The solution is not to chase harder or to pressure clients into faster decisions. It is to give proposals a clear governance routine: a stated expiry date, disciplined version control, a measured follow-up cadence and a defined trigger for re-quoting. This is a regulatory and record-keeping matter as much as a commercial one.
Why an open-ended proposal creates avoidable risk
A proposal without an expiry date can be read as an indefinite offer. If the client returns months later expecting the original fee, the firm faces an awkward choice: absorb changed costs, renegotiate in a way that may feel inconsistent, or proceed on assumptions that no longer hold.
The risk is not limited to price. Scope may have moved, key personnel may be unavailable, subcontractor costs may have changed, or the regulatory context may have shifted. A proposal that appears current when it is not can become a misleading communication. For firms subject to professional body requirements, clear and accurate client communications are part of the expected standard, not an optional extra.
There is also an evidential point. If a dispute arises about what was offered, when it was accepted and on what basis, an undated and unversioned proposal is weak material. A small amount of structure at the point of issue prevents a much larger problem later.
Give every proposal a stated shelf life
A proposal should carry a clear expiry date, expressed as a calendar date rather than a vague statement such as “valid for 30 days”. The date should be visible on the covering communication and in the proposal itself. For straightforward work, a 30-day period is often sufficient. More complex matters, particularly those involving third-party costs or regulatory approvals, may justify 45 or 60 days, but the reason should be understood internally.
The expiry date should also explain what happens next. A simple formulation is that the proposal lapses if not accepted by the stated date, and that any subsequent instruction will be subject to a refreshed proposal. This avoids any suggestion that the firm has silently extended its terms.
Where a client is procuring through a formal tender or framework, the expiry position should be checked against the procurement timetable. The aim is consistency, not unnecessary rigidity. An expiry date that conflicts with the buyer’s stated process creates confusion and may undermine confidence.
Make version control survive the email trail
Many proposal problems begin with multiple versions circulating at once. A junior colleague sends a revised PDF, a partner forwards an earlier draft, and the client relies on the wrong figures. The remedy is a simple version protocol.
Each proposal should carry a unique reference, the client name, the issue date, the expiry date and a version number. The final issued version should be clearly marked as such. Superseded versions should not be reissued without a clear note explaining what has changed. Where a proposal is replaced, the covering email should identify the new version and state that it supersedes earlier documents.
A single internal location should hold the live version. If the firm uses a proposal register, the register should record the reference, owner, issue date, expiry date, status and next action. The register need not be elaborate. A shared spreadsheet can be sufficient if it is reviewed consistently and access is controlled.
Follow up on a planned cadence, not on impulse
Follow-up is often handled inconsistently: some clients receive repeated chasers, others hear nothing until the proposal is forgotten. A planned cadence produces better outcomes and a more professional impression.
A workable routine might include a brief acknowledgement check shortly after issue, a clarification prompt around day seven, a status enquiry around day fourteen and an expiry reminder before the stated date. The final contact should confirm that the proposal will close if no instruction is received. Each contact should be recorded against the proposal.
The language matters. Follow-up should be neutral and useful, not pressing. A short note asking whether the client needs any assumptions explained is more effective than a generic reminder. Where a client has gone quiet, it is reasonable to ask whether priorities have changed and to offer to close the file. That is not pushy; it is clear administration.
Re-quote when circumstances change
Not every expired proposal needs to be resurrected. The firm should decide whether to re-quote, and that decision should be based on identifiable triggers: the expiry date has passed, the scope has changed, rates or third-party costs have moved, a key assumption is no longer valid, or the firm’s availability has changed.
A re-quote should be issued as a new version or a new proposal, not as a silent amendment to an old document. It should explain what has changed and why. If a client asks the firm to honour an expired price, any exception should be approved at the appropriate level and recorded with a new expiry date. Informal concessions are difficult to defend and easy to repeat by accident.
A short standard for 2026
For UK professional firms reviewing their proposal process, the essential controls are straightforward: state an expiry date on every proposal; use a unique reference and version number; keep one live version; record status in a proposal register; follow a measured contact cadence; and re-quote rather than extend when circumstances change. None of these measures requires a large system. They require consistency.
A proposal with a shelf life is not less client-friendly. It is clearer. It tells the client what is being offered, for how long and on what basis, and it gives the firm a defensible record when the answer is yes, no or not yet.
