What the Counterparty Already Signed: A Consent Audit for UK Group Reorganisation

A group reorganisation is usually presented to the board as a structural matter: a new holding company, a share transfer, an entity merger, a simplified chain. The legal file grows, the org chart is redrawn and the completion date is set. What can remain oddly invisible is the permission of the counterparty. Long before the board approves the new structure, customer contracts, supplier terms, leases and financing agreements may already have decided what the group is allowed to do, what it must ask for and what happens if it proceeds without asking.

That is not a reason to treat the reorganisation as unworkable. It is a reason to treat consent risk as an operational dependency rather than a legal appendix. The board should see which relationships can be disrupted, which permissions are conditions precedent and which notices can safely follow completion. Consent is not simply a question of whether a clause exists. It is a question of whether the group can keep trading, billing, servicing and supplying while the clause is satisfied.

Consent risk is an operational dependency

A change-of-control clause is often read as a legal protection for the counterparty. In practice it is a dependency on the group's own continuity. If a key customer can terminate on a change of control, the risk is not confined to the contract schedule; it reaches revenue, service levels, staff retention and the assumptions behind the capital plan. If a landlord's consent is required before assignment of a lease, the risk sits in the premises from which the business operates. If a lender treats a reorganisation as an event of default, the risk touches liquidity. These are board-level exposures, not merely drafting points.

The audit therefore starts with a simple proposition: the group should know, entity by entity, which third-party relationships require consent, notice or both before the structure changes. That map should be built before legal notices are drafted, not after the completion timetable has been fixed around them.

Build the entity map before the contract pile

A common mistake is to begin with the contracts that happen to be easy to find. The better starting point is the entity map. Which companies are changing ownership, changing name, transferring assets or ceasing to contract directly? Which entities remain in the chain but sit beneath a new parent? Which counterparties deal with more than one entity, and which contracts are held by a subsidiary that will no longer sit where it did?

From there, the audit can draw on the contract register, procurement records, finance facilities, property files, IT licences and framework agreements. It should include arrangements that are not always labelled as contracts: statements of work, side letters, variations, guarantees, letters of credit and service schedules. The aim is not to read every page. It is to identify the clauses that travel with the structure.

Read for triggers, not just titles

Change-of-control clauses are not standard. Some define control by reference to voting rights; others by board composition, ultimate beneficial ownership or the identity of the parent. A reorganisation that leaves the same ultimate owner in place may not trigger a clause in one contract but may trigger it in another. Assignment and novation provisions can apply even where control does not change. Notification obligations may sit alongside consent requirements, with different deadlines and different consequences.

The audit should record four things for each relevant clause: the trigger, the required action, the consequence of non-compliance and the counterparty contact. A consent that is 'not to be unreasonably withheld' is a different operational risk from an absolute consent right. A notice period of thirty days is a different timetable risk from a condition precedent to completion. The board does not need the full clause language in its pack, but it does need the consequence translated into commercial terms.

Rank consents by commercial criticality

Not every consent deserves the same attention. A tiering approach helps the board see where management time should go. Tier one should include contracts without which an entity cannot trade, bill or deliver its core service: major customers, essential suppliers, critical premises, core banking facilities and regulatory permissions where consent or notification is required. Tier two should include material but substitutable relationships, where a delay is manageable but a refusal would be costly. Tier three should include administrative notices that can be handled through a standard process.

The ranking should be tested against customer concentration, revenue dependency, operational continuity and the practical availability of alternatives. A consent from a landlord may be routine in one property and existential in another. A supplier notice may be a formality until the supplier is the only provider of a component or service. The board should see a heat map, not a list of equal line items.

The timetable is the governance control

Consent processes take time, and counterparties do not work to the group's completion calendar. Landlords may require surveys or references. Banks may need credit committee approval. Customers may want assurance about service continuity. Regulators may have their own notification windows. The audit should therefore be run backwards from the intended completion date, with realistic assumptions about how long each consent or notice may take.

The board's control is the sequence. Which consents must be obtained before completion? Which can be obtained after completion without breach? Which notices must be sent by a particular date to avoid termination rights arising? Which counterparties need a conversation before a formal letter arrives? The timetable should show dependencies, owners and escalation points, not just a legal checklist.

Rehearse the notice sequence

A consent plan that has never been rehearsed is a plan that assumes counterparties will behave as expected. The board should ask for a dry run of the notice sequence: who signs, who speaks to the counterparty, what the group says if asked why the reorganisation is happening, and what happens if a key consent is refused or delayed. This is not about scripting every conversation. It is about ensuring that the group's most important relationships are handled deliberately rather than discovered by a formal notice.

The rehearsal should include the fallback position. If a consent is not forthcoming, can the structure be varied? Can the contract be novated to a different entity? Is there a commercial solution that avoids the trigger altogether? The board does not need to solve these questions in advance, but it should know that they have been considered and who owns the response.

What the board should ask for

A consent audit is most useful when it gives the board a small number of clear questions. Which consents are conditions precedent to completion? Which contracts can be terminated or suspended if notice is not given? Which relationships are concentrated in a single counterparty or a single entity? Who is accountable for each tier-one consent? What is the escalation route if a key counterparty refuses? And has the board seen the consent position as a single dashboard rather than a legal appendix?

In a UK group reorganisation, the structure may be internal, but the permissions are external. The counterparty has already signed the terms that govern the group's freedom to move. A consent audit brings those terms into the board's view before the structure changes, so that the group can proceed with its eyes open rather than its fingers crossed.