Permission Without Purpose: Retiring the Inherited Sign-Off
Photo: UK business managers reviewing approval paperwork and workflow documents in a modern office, via www.curlycraze.com
In many UK service operations, routine decisions still travel through a signature chain. A credit note, a roster change, a small purchase order, a customer exception or a process amendment may require two, three or even four approvals. Each step was probably added for a reason. The difficulty is that the reason may have retired, the system may now enforce the control automatically, or the risk may have moved elsewhere. The visible cost is delay. The less visible cost is management attention, workarounds and decisions that are quietly avoided altogether.
An audit of inherited sign-offs is not an exercise in removing governance. It is an exercise in making governance proportionate. The aim is fewer inherited controls, clearer decision rights and faster routine work, while keeping the controls that genuinely protect the organisation.
Begin with the decision, not the form
Most approval audits start with the policy or the workflow diagram. That is usually the wrong starting point. Policy describes what should happen; it rarely describes what does happen. Begin instead with a set of routine decisions that matter because they are frequent, time-sensitive and low to moderate risk.
Select a sample of recent decisions: perhaps customer credits, temporary staff requests, small value purchases, schedule changes or standard exceptions. For each one, record who initiated it, which approvals were required, what evidence was supplied and how long each stage took. Compare the formal route with the actual route. In many organisations the two diverge, and the divergence is the most useful evidence available.
Trace each step to a live risk
For every approval in the chain, ask a simple question: what specific risk does this step mitigate? The answer should be concrete. 'Financial loss above a defined threshold', 'regulatory breach', 'health and safety exposure' or 'customer detriment' are specific. 'Visibility', 'oversight' or 'because finance likes to see it' are not.
Classify each sign-off into one of four groups: statutory or regulatory, financial, operational or reputational. Then test whether the risk is still live and whether another control already addresses it. A system-enforced limit may have replaced a manual check. A supplier framework may have removed the need for a second quote. A central team may no longer exist, yet its approval step remains in the workflow.
If no live risk can be identified, mark the step as a candidate for removal. If a risk does exist, test whether the current approver is the right person to own it. Seniority is not the same as relevance. An approval that sits with a director because it always has done may be better placed with the manager who understands the operational consequence.
Quantify delay and workaround cost
Inherited approvals are often defended because they appear to cost nothing. They cost time, and time has a price. Measure elapsed time and queue time separately. Elapsed time tells you how long the decision took from start to finish. Queue time tells you how much of that was spent waiting.
Include the practical frictions: waiting for a weekly meeting, an approver on leave, a batch sign-off at month end or a document that must be printed and signed. Estimate management time absorbed by the step, even roughly. If three managers spend fifteen minutes each on a low-value approval every week, the annual cost is not trivial.
Look closely for workarounds. Pre-approval calls, shadow spreadsheets, informal emails before the formal request, batching decisions to avoid thresholds and 'urgent' routes that bypass the queue are all signals that the control is misaligned with the work. A workaround is not necessarily evidence of poor discipline. It is often evidence that the formal process cannot keep pace with operational reality.
Separate accountability from ceremony
Good approval design places accountability with the person who owns the consequence. Many inherited steps are ceremonial rather than accountable. They exist to inform, to copy, to reassure or to spread ownership so widely that no one is truly responsible.
Distinguish between three roles: approve, consult and inform. An approver says yes or no and owns the outcome. A consultee provides input but does not hold the decision. An informed party receives notification after the fact. Many steps currently labelled 'approval' are really consultation or notification. Converting them is often the simplest improvement available.
A short decision rights matrix can help. For each routine decision, define the owner, the threshold, the evidence required, the escalation route and the review date. Keep it visible and keep it short. The purpose is clarity, not bureaucracy.
Test removal in a controlled way
Do not remove a whole chain at once. Choose a controlled pilot covering a defined decision type for thirty to sixty days. Agree in advance what would count as failure: an increase in errors, complaints, audit findings or financial loss. Monitor those indicators and compare them with the baseline.
If performance holds, make the change permanent. If it does not, redesign the step rather than simply restoring the old chain. The lesson may be that a control is needed but that the current form is wrong: too late, too senior, too manual or too broad.
Keep the remaining controls honest
Retiring unnecessary approvals is not deregulation. It is reallocation of control towards the risks that remain. Keep statutory, financial and safety-critical controls intact. Give each remaining approval a named owner, a stated risk and a review date. Add new approvals only with the same discipline: documented risk, defined owner and an expiry point.
Over time, this creates a healthier pattern. Controls are added when a real risk emerges and removed when the risk recedes or is better managed elsewhere. Routine decisions move at the speed the operation requires, and management time is spent on judgement rather than ceremony.
The test is not whether every inherited step can be defended in theory. It is whether it earns its place in practice.