The Promises Ledger: A Firm's Discipline for Commitments Made to Clients

In advisory work, the most dangerous client promise is rarely the one written into an engagement letter. It is the sentence at the end of a call: “Leave that with me.” Goodwill is built in that moment. So is a quiet liability if the item never resurfaces. Formal undertakings usually have a process behind them. Informal commitments often rely on memory, goodwill and the hope that nothing goes wrong.

A promises ledger changes that. It is a simple, controlled record of every client-facing commitment the firm has made, from the formal to the apparently trivial. It is not a task list and it is not a substitute for matter management. It is a risk tool that gives ordinary client service the same visibility as a regulatory deadline.

Why this belongs beside the risk register

A risk register tracks threats. A promises ledger tracks obligations created by the firm’s own words. The two are related. A missed commitment can become a complaint, a negligence claim, a regulatory notification or simply a damaged relationship that costs far more than the original task.

For UK advisory firms, the commercial case is straightforward. Clients remember what was said. They may not remember the exact wording, but they remember the assurance. If the firm cannot show what was promised, to whom, by when and with what outcome, it is relying on individual recollection. That is not a control; it is a hope.

A ledger also helps demonstrate a professional approach to insurers, clients and internal reviewers. It shows that the firm treats client service as a governed activity rather than a series of personal favours.

What counts as a promise

The definition should be broad enough to be useful and narrow enough to remain workable. A client-facing promise is any statement by a firm representative that a client could reasonably rely on. That includes formal undertakings — for example, an assurance that funds will be held, a document will be provided by a set date, or a step will be taken before completion. It also includes the informal commitments that oil everyday advisory work: “I will look into that”, “We will come back to you this week”, “I will ask the team and confirm”.

The test is not whether the promise was intended to be legally binding. The test is whether the client heard a commitment. If the answer is yes, it belongs in the ledger unless the firm has a clear reason to treat it as routine courtesy. Even then, a short entry is cheaper than an argument later.

The register should distinguish between a promise and an internal task. “Chase the client for ID” is an internal action. “We will confirm the position on ID by Friday” is a client promise. The distinction matters because the ledger is about what the client has been told, not what the firm needs to do.

A practical structure

A workable ledger needs only a handful of fields: client and matter, the promise in plain words, who made it, who owns it, the date it was made, the due date, the evidence of completion and the current status. Add a short field for escalation notes and another for closure.

The promise should be recorded in the client’s language, not internal shorthand. “We will send the revised draft by 20 November” is better than “draft follow-up”. The owner should be a named individual who is accountable for delivery, not simply the person who happened to take the call. The due date should be the date the client was given. If no date was given, the firm should set one internally and, where appropriate, confirm it with the client.

Status labels should be few and unambiguous: open, in progress, at risk, closed and cancelled. “At risk” is the most useful. It gives the firm a way to act before a missed deadline becomes a surprise.

Capture without bureaucracy

The failure mode of any register is that it depends on people remembering to update it. The solution is not a longer form. It is a shorter route from conversation to record.

Firms can add a “client promise” prompt to meeting notes and call logs. A fee earner can forward the relevant email to a central inbox, or complete a three-field web form. Operations can log it. For smaller firms, a shared spreadsheet with restricted editing rights may be enough. The important discipline is that capture happens close to the conversation, ideally on the same day.

Leaders should make capture visible and normal. If the only time a promise is discussed is when something has gone wrong, people will hide the difficult ones. If capture is praised as good client service, the register becomes a source of reassurance rather than a threat.

Deadlines, evidence and escalation

A due date is not an internal target. It is a promise date. If the firm cannot meet it, the client should hear that before the date passes, not after. The ledger should therefore support early warning. A simple rule works well: any item approaching its due date without evidence of progress moves to “at risk” and is reviewed by the matter partner or operations lead.

Escalation triggers should be explicit. Examples include a missed due date by two working days, a client chase, the owner’s unavailability, or any promise touching money, a completion date or a regulatory step. Escalation is not blame. It is a controlled response: confirm the facts, agree a new date, tell the client, record the change.

Evidence of completion can be light. A sent email, a file note, a document version or a short confirmation from the client is usually enough. The point is not to build a second file. The point is to answer the question “how do we know this was done?” without relying on memory.

Closing items cleanly

Closure is where many informal registers fail. An item is closed when the promise has been delivered, the client has been told, evidence is recorded and the owner has confirmed closure. If the promise was superseded, the ledger should say so and by whom. If it was withdrawn, the firm should confirm that with the client. Deleting the entry destroys the audit trail and invites confusion.

A one-line closure note is sufficient: “Draft sent 18 November; client confirmed receipt 19 November.” That sentence is often the difference between a defensible position and an uncomfortable conversation.

A six-week start

A firm does not need a new system to begin. Week one: define the scope and fields. Week two: pilot the ledger with one team. Week three: review what was captured and what was missed. Week four: extend to the wider firm. Week five: train owners on escalation and closure. Week six: audit a sample of closed items and adjust.

By the end of 2026, many firms will be planning for a busier 2027. A promises ledger is a modest investment that pays back in fewer surprises, clearer client conversations and a more confident answer when someone asks whether the firm kept its word.

Client trust is built in small assurances. A promises ledger gives those assurances a place to land — and gives the firm a disciplined way to keep them.