The Approved Departure Log: Making Room for Judgement Without Losing the Thread
Photo: David Howard , CC BY-SA 2.0, via Wikimedia Commons
Every advisory firm has a standard way of doing things. It also has a handful of clients for whom the standard way is adjusted: a deadline compressed, a document accepted in a different form, an unusual payment route agreed, a step in the onboarding sequence deferred until Monday. These adjustments are usually sensible. They are also usually invisible. The difficulty is not that exceptions happen. It is that an exception granted in good faith on a busy Thursday can become an expectation by the following quarter, and a precedent by the end of the year.
An approved departure log is a modest response to that problem. It is not a bureaucratic hurdle. It is a short, practical record that answers four questions: what was departed from, why, who approved it, and when the permission ends. Used well, it keeps flexibility as a conscious client-service choice rather than an accidental rewrite of the firm's operating model.
Why memory is the weakest control
Most firms already rely on memory to manage exceptions. A partner recalls that a client was allowed to send documents by a different route. A manager remembers that an engagement was extended without a fresh letter. That works until the partner is on holiday, the manager leaves, or the client asks for the same treatment two years later. At that point, the firm has no way of distinguishing a considered concession from an oversight.
Written records do more than support memory. They create a visible trail that can be reviewed, questioned and, where necessary, closed. The log also protects the individual who granted the exception. A note showing the rationale and the approver is far more useful than a vague recollection when a decision is later examined by a colleague, an auditor or a regulator.
What belongs in the log
The log should be short enough to complete in a few minutes and specific enough to be useful months later. A simple table works well. The following fields are sufficient for most UK advisory firms:
| Field | What to record |
|---|---|
| Date of request | The day the exception was raised |
| Client and matter | A clear identifier, not just the client name |
| Standard position | The step, rule or deadline being departed from |
| Exception granted | Exactly what has been agreed |
| Reason | The client need or operational pressure behind it |
| Risk note | Any regulatory, commercial or reputational consideration |
| Approved by | The named individual with authority |
| Conditions | Any safeguards, limits or monitoring attached |
| Expiry date | The date on which the exception lapses |
| Review date | When the log entry will be reconsidered |
The expiry date is the field most often omitted and the one that matters most. An exception without an end date is not an exception; it is a change to the process that nobody has formally agreed. Even a generous expiry date, such as three months or until the next engagement review, preserves the principle that the departure is temporary.
Who may approve what
A log is only useful if it is matched by clear approval thresholds. Without them, staff either escalate everything or approve too much. A three-tier structure is usually adequate.
Tier one: routine operational flexibility. A manager or senior associate may approve minor departures such as a short extension to an internal deadline, an alternative format for a routine document, or a small change to a meeting schedule. These should still be logged, but the approval burden is light.
Tier two: material client-service exceptions. A partner or head of department should approve departures that affect the engagement terms, the timing of a significant deliverable, or the route by which client money or sensitive information is handled. The risk note becomes more important at this level.
Tier three: departures touching regulatory or contractual requirements. The firm's compliance lead or management board should approve any exception that interacts with anti-money laundering checks, professional conduct rules, contractual warranties or regulatory reporting. Some requirements cannot be waived at all. The log should make that clear rather than implying that every rule is negotiable.
Thresholds should be written down and reviewed annually. They are not a sign of distrust; they are a way of making sure the right people are making the right decisions at the right level.
The monthly half-hour review
The log only earns its keep if someone reads it. A monthly review, chaired by a partner or operations lead and attended by compliance where appropriate, can be completed in thirty minutes. The agenda is simple: review new entries, confirm that expired exceptions have lapsed or been renewed, identify any exception that has been requested more than once, and ask whether the standard process should change.
That last question is where the real value sits. If three clients have asked for the same alternative payment route, the issue may not be client behaviour. It may be that the firm's standard route is slower or less convenient than it needs to be. If a particular deadline is compressed every quarter, the standard timetable may be unrealistic. The log turns individual favours into management information.
Turning exceptions into evidence
The review should produce a short note: exceptions granted, exceptions closed, recurring themes, and any recommended change to the standard process. Over a year, those notes form a useful record. They show that the firm exercises judgement, monitors its own departures and adjusts its procedures when the evidence supports it. That is a stronger position than either rigid adherence to a process that no longer fits or quiet flexibility that nobody can explain.
For UK firms operating in a climate of increasing scrutiny, the log is also a proportionate response to the question every client eventually asks: why was this done differently? A dated entry with a named approver and a stated reason is a better answer than an email search conducted under pressure.
A small discipline with a long reach
The approved departure log is not a grand reform. It is a single page, a simple template and a monthly conversation. But it addresses a familiar weakness: the gap between what a firm intends to do and what it actually does when a valued client asks for something different. Handled well, that gap becomes a source of learning rather than a source of risk.
