When Planning Calls: A Board Protocol for Enforcement Correspondence

The envelope usually arrives without ceremony. It is addressed to 'The Occupier', or to a company name that was last correct three tenants ago. Inside, a planning enforcement officer for the local authority explains that a structure, use or advertisement on the site may be unauthorised, and invites a response. For an owner-managed business, the instinct is either to ignore it in the hope it goes away or to reply immediately with an explanation that later proves inaccurate. Neither is a governance position.

Why enforcement letters reach SMEs at all

Local planning authorities act on complaints, aerial imagery, site inspections and cross-checks against business rates records. A mezzanine inserted to gain office space, a yard put to a use the permission does not cover, a sign erected without consent, or a change of use that seemed trivial at the time may sit unremarked for years before someone notices — sometimes a neighbour, sometimes an officer reviewing the register. The passage of time is not in itself a defence; the statutory time limits for enforcement (broadly four years for building works and certain changes of use, ten years for others) are a matter of fact and legal advice, not of assumption.

The response is a board matter

Planning enforcement is a corporate risk, not a property query. It carries the potential for an enforcement notice, a requirement to remove works at the company's cost, a stop notice in urgent cases and, in the more serious scenarios, prosecution. It also carries disclosure consequences on a sale, refinancing or lease assignment. The board should therefore own the decision on how to respond, even where a single director or the operations lead handles the correspondence day to day. Decide at the outset who is the authorised point of contact for the authority and ensure the officer knows it.

The first 72 hours: preserve, do not explain

The most common self-inflicted wound is an informal, well-meant email from a director answering questions that were never asked and characterising the use in terms that are not accurate. Before anything is sent:

• Establish what the letter actually is. An informal enforcement enquiry is not the same as a planning contravention notice under section 171C of the Town and Country Planning Act 1990, which carries a legal duty to respond and criminal liability for false or misleading information. A breach of condition notice and an enforcement notice each have their own regimes and appeal routes.
• Date-stamp receipt. Deadlines matter, and the date on the letter is not always the date it arrived.
• Preserve the site as it stands. Do not remove or alter the works, signage or use while the position is being assessed — removal can look like an admission and can complicate any later application for a certificate of lawful development.
• Instruct a planning consultant or solicitor early if the letter mentions an enforcement notice, a listed building, a conservation area or a contravention notice. The cost of early advice is trivial against a removal bill.

Build the evidence file before you build the argument

The strongest response is documentary. Pull together the original planning permission and any subsequent approvals, including conditions and their discharge; leases and licences showing occupation dates; historic photographs, insurance schedules, service charge records and utility bills evidencing when a use began; earlier correspondence with the council about applications; and any lawful development certificate already held. If the works predate the relevant time limit, evidence of that date is the case. If they do not, the evidence shapes the negotiation.

Briefing the board in one page

A short paper beats a long one. Cover what the authority has alleged; what the file shows; the realistic options (regularise by application, negotiate a reduced requirement, appeal, or remove); the cost and timing of each; the risk if nothing is done; and a recommendation. Record the decision and the reasoning in the minutes. Where the company rents, notify the landlord in writing — the lease will almost certainly require it, and the landlord may be a co-appellant or a source of indemnity.

Negotiate, regularise or appeal?

Three routes, rarely exclusive.

Regularisation — a retrospective application for the works or use, or an application for a certificate of lawful use — is often the cheapest option where the development is acceptable in planning terms. It takes time and involves fees.

Negotiation with the enforcement officer can produce a longer compliance period, an agreed scope of works, or acceptance that only part of the allegation is pursued. It is not a substitute for a formal route, but it frequently shapes one.

Appeal against an enforcement notice lies to the Planning Inspectorate, generally within 28 days of the notice taking effect, on specified grounds. Appeals are slow and public. They should be a board decision taken on advice, with the grounds identified at the outset.

Recording the outcome so it stands up later

Whichever route is taken, the file should close with a short note: what was alleged, what was decided, what was done, when, at what cost, and by whom. Retain it with the property compliance register for at least as long as enforcement action remains possible, and longer if the premises are held for sale. In a later due diligence exercise, a documented and closed enforcement matter is a minor issue; an undocumented one is a discount.

A fourteen-day working checklist

Days 1–2: log receipt, identify the notice type, confirm the authority contact, notify the board chair. Days 3–5: instruct an adviser if the matter is serious and assemble the evidence file. Days 5–8: draft the one-page board paper and agree the point of contact. Days 8–12: respond factually to any statutory request and open negotiation where appropriate. Days 12–14: minute the decision, diarise every deadline, and notify the landlord and insurer as required.

The letter is not the crisis. The crisis is a response written in haste, by the wrong person, without the file. Treat it as a governance event and it becomes manageable.