Taupo Consulting All articles
Finance & Operations

Signed, But Not Sanctioned: A Thirty-Day Review of Board Approvals

Taupo Consulting
Signed, But Not Sanctioned: A Thirty-Day Review of Board Approvals

Photo: UK boardroom table with approval documents and signature folder business meeting, via s3.amazonaws.com

Delegated authority is one of those board controls that looks robust until someone asks for the evidence. A payment has been made, a contract has been signed, a capital purchase has been approved, and everyone involved believes the decision was properly authorised. The question is whether the paperwork proves it. In UK mid-market firms, the gap between perceived authority and documented authority is often wider than directors expect.

The final weeks of 2026 are a sensible time to test that gap. Year-end routines, audit preparation, banking reviews, and the first draft of the 2027 plan all create natural pressure on approval processes. A thirty-day review of board sign-off is not a legal opinion and should not become a bureaucratic exercise. It is an operating check: do the resolutions, mandates, thresholds, and signatures in daily use match the authority the board believes it has granted?

The problem is usually evidence, not intent

Few directors deliberately exceed their authority. More often, authority drifts. A long-serving finance director signs a contract because they have always signed similar contracts. A newly appointed managing director inherits online banking permissions that were never formally updated. A procurement team treats a framework agreement as routine when the spend crosses a board threshold. An interim executive approves a settlement on the understanding that the board would have agreed it anyway.

Each decision may be commercially sound. The weakness is evidential. When a bank queries a mandate, a customer runs due diligence, or an auditor samples transactions, the organisation needs a clear trail from decision to document to signature. If that trail depends on memory and precedent, the board has an authority control in name only.

Week one: assemble the authority map

The first week should be documentary and largely desk-based. Collect the governing documents: the articles of association, the schedule of matters reserved for the board, any formal delegation matrix, committee terms of reference, and board resolutions from the past twenty-four months. Add the operational documents that translate authority into practice: the bank mandate, online banking user limits, contract signing policy, procurement thresholds, treasury policy, and any capital expenditure approval rules.

From these, build a single authority map in a spreadsheet. For each decision type, record the threshold, the required approver or approvers, the source document, and the date the arrangement was last confirmed. Keep the map deliberately practical. A payment above a defined amount, a new supplier contract, a property commitment, a settlement, a guarantee, and a regulatory filing are all decision types that should appear.

The output of week one is not a policy rewrite. It is a one-page view of who is supposed to approve what, and where that instruction is written down.

Week two: test the map against actual transactions

In the second week, sample real transactions from the past twelve months. Select payments above the main thresholds, new supplier engagements, contract signatures, capital spend, customer contracts with unusual terms, and any settlement or exceptional item. For each, ask three questions: who approved it, what evidence exists, and does that match the authority map?

This is where the useful exceptions emerge. A contract may have been signed by a commercial director under a delegated limit, but the indemnity clause may fall within a matter reserved to the board. A payment may carry two signatures, but the bank mandate may still list a former director. A capital purchase may have been approved by the executive committee, but the board resolution may require board approval above a lower figure.

The review should distinguish between minor administrative gaps and substantive authority failures. A missing date on an approval email is a housekeeping issue. A contract signed by someone outside their delegated limit is a governance issue that the board needs to see.

Week three: reconcile bank mandates and contract signatures

Bank mandates deserve separate attention because they are both operational and highly visible. Check the current signatories, the online banking authorisation limits, the dual authorisation rules, and the process for changing a mandate after a director or senior manager leaves. In many mid-market firms, the mandate is updated after a banking event rather than after an organisational change. That lag creates avoidable risk.

Contract signatures need a similar reconciliation. Review who is authorised to sign on behalf of the company, whether that authority is documented, and whether counterparties have been given the correct names. Check whether standard terms and conditions grant signature authority to roles that have since changed. If the company uses electronic signatures, confirm that the workflow reflects the current delegation matrix rather than a legacy template.

This week is not about renegotiating contracts. It is about ensuring that the person holding the pen, or the digital signature, is the person the board intended to hold it.

Week four: ratify, record, and reset

The final week should convert findings into board decisions. Present the authority map, the exception list, and a small number of recommended actions. The board may need to ratify minor historical deviations, confirm revised thresholds, adopt an updated delegation matrix, and instruct management to update the bank mandate. Where a transaction remains material and unauthorised, take advice before deciding how to regularise it.

A useful outcome is a short set of controls that will not collapse under pressure: a named owner for the delegation matrix, a review at least annually and after any senior appointment, a standard board resolution format, and a simple test that sampled transactions are checked against the matrix before the year-end audit.

What the board should see

Keep the board pack short. A one-page authority map, an exceptions schedule with value and status, a list of decisions required, and a timetable for bank mandate and policy updates are enough. The purpose is not to create a new layer of approval. It is to make existing authority visible, evidenced, and current.

By the end of the thirty days, the board should be able to answer a simple question with confidence: if a bank, auditor, or counterparty asked who approved this decision, could we show them? For many UK mid-market firms, closing that evidence gap before year-end 2026 is a modest exercise with a disproportionately useful result.

All Articles

Related Articles

The Friday Bank Detail Change: A 45-Day Review of Supplier Payment Controls

The Friday Bank Detail Change: A 45-Day Review of Supplier Payment Controls

The Indemnity in the Contract, the Cover in the Schedule: A Thirty-Day Board Reconciliation

The Indemnity in the Contract, the Cover in the Schedule: A Thirty-Day Board Reconciliation

The Default Tariff You Chose by Doing Nothing: A 45-Day Energy Procurement Reset

The Default Tariff You Chose by Doing Nothing: A 45-Day Energy Procurement Reset