A four-partner strategy boutique in Manchester is engaged by a private-equity-backed industrial business to write a three-year growth plan. The engagement letter — two pages, signed in a hurry the week before the kick-off — describes the work as "strategic review and growth roadmap" and references an attached project plan that itself describes interviews, market analysis, and a board paper. Two years on, after the acquired add-on businesses underperform, the PE sponsor's investment committee reviews what went wrong. The committee's letter to the consultancy alleges that the growth plan failed to model integration risk, failed to test market assumptions against an independent data source, and failed to flag a regulatory headwind in one of the target segments. The claim is for £2.3m — the difference between the modelled EBITDA and the realised number, plus the partial write-down on one of the acquisitions.
The defence of that claim will turn on one question more than any other: what exactly was the strategy consultancy retained to do? The two-page engagement letter, signed in a hurry, does not say. The attached project plan describes activities, not outputs, and is silent on the boundary between strategic recommendation and the client's own investment decision. The board paper does not record any explicit limitation on the reliance the sponsor's investment committee could place on the work.
Scope-of-engagement risk is the single largest driver of disputed PI claims against UK strategy consultancies. It is the gap between what the client thinks the consultancy was supposed to do, what the consultancy thinks it was retained to do, and what the contemporaneous documents — engagement letter, SOW, deliverables, steering committee minutes, email trail — can actually prove. Insurers see it every year and the same patterns recur.
This guide is for partners, principal consultants and finance directors at UK strategy and advisory firms who want to understand how scope-of-engagement disputes drive PI claims, what their engagement documentation should look like, and how the PI policy interacts with the contractual position. It is a companion to our main management consultants PI guide, which covers the wider PI landscape for the sector.
Why strategy advice is different
Strategy work sits at the high-trust, low-volume end of consultancy. The fees are usually significant. The deliverables are documents — a board paper, a model, a recommendation. The client's executive team or board acts on those documents, and the commercial outcome that follows may be months or years away. By the time the outcome is known, the consultancy has long since closed the file, billed the engagement, and moved on.
That structure creates three risks PI underwriters know about and price for.
The first is that the value of a strategic recommendation is, by definition, contested at the moment the claim is brought. The client argues the recommendation was wrong; the consultancy argues the recommendation was sound but the execution failed, or the market moved, or the client's own decisions intervened. The chain of causation is long, the counterfactual is speculative, and the defence is documentary. Insurers know that the better the documentary record, the more defensible the position.
The second is that the deliverables themselves are seductive. A polished board paper, a clean recommendation, a confident model — these are the products strategy firms sell, and they read on their face as definitive. The qualifications that any honest strategy partner would attach in conversation — the assumptions, the sensitivities, the things the model deliberately does not capture — often live in appendices, footnotes or speaking notes rather than in the headline recommendation. When a claim arrives years later, the headline recommendation is what is read into the record.
The third is reliance. A strategic deliverable is often shared further than the consultancy expected. The sponsor's investment committee, the financier's credit team, the chair's external advisers, a future acquirer — any of these may end up reading the document and, in litigation, may assert that they relied on it. Whether the consultancy owed a duty of care to those further readers is a question of English law on which the engagement letter, the deliverable's own reliance language, and the surrounding circumstances all matter.
What the engagement letter should actually say
A defensible scope-of-engagement position starts at engagement-letter sign-off, not at claim notification. The engagement letter and any SOW underneath it should answer six questions clearly.
What is the scope of services? Not just the activities — interviews, analysis, workshops — but the outputs. A market-sizing report. A board recommendation on a defined set of options. A diligence opinion limited to commercial matters only. The narrower and more specific the description of the output, the harder it is for a later claimant to argue the consultancy should have done something else.
What is explicitly out of scope? This is the harder side of the same question and the one most engagement letters duck. If the strategy work does not include integration planning, regulatory analysis, environmental risk, IT due diligence, employment-law review, financial modelling beyond a stated horizon, or testing of client-provided data, the letter should say so. Out-of-scope language is not unfriendly drafting — it is the consultancy's contractual answer when the client later argues the work should have flagged something the consultancy was never asked to look at.
Who is the deliverable for, and who may rely on it? A strategy report delivered to "the board of X Limited" reads differently in litigation from a strategy report delivered to "X Limited, its sponsors, financiers and advisers, who may all rely upon it." Reliance language should be drafted deliberately, not by accident. If the only intended user is the executive committee, the letter should say so and the deliverable itself should carry consistent reliance wording.
What are the assumptions and limitations? A strategy recommendation is built on assumptions — about the market, the client's own capability, the data the client has provided, the regulatory environment, exchange rates, capital availability. Those assumptions should be stated in the deliverable and referenced in the engagement letter. The same goes for limitations on the work — the time available, the data made available, the access granted to client personnel.
What is the liability cap and how does it work? Most strategy SOWs cap the consultancy's liability at a multiple of the fees under the SOW, with carve-outs for confidentiality, IP infringement, fraud, death or personal injury. The cap should match what the PI policy can comfortably respond to, and the carve-outs should be checked against the policy wording — a consultancy with a £1m PI limit that has signed an uncapped indemnity for IP infringement is carrying contractual exposure that its policy may not pick up.
What is the post-delivery cover obligation? Increasingly, MSAs and SOWs require the consultancy to maintain PI cover for a defined period after delivery — six years is typical, eight or ten years occasionally. The firm needs to be able to honour that commitment for the life of the obligation, including in run-off if it ceases trading.
A good engagement letter is not a long engagement letter. It is one that answers these six questions in language the consultancy and the client both understand and that, three years later when the dispute arises, can be read into a witness statement without embarrassment.
How scope creep happens — and how it bites
Scope creep is not a procurement story. It is a relationship story. A trusted strategy partner is asked, in passing, to look at something adjacent — a quick view on the labour market, an informal benchmark, a sense-check on a candidate acquisition. The work is done as a favour, billed against the existing engagement code or not billed at all, and produces an email, a slide, or a verbal view that the client then acts on.
The PI claim, when it comes, will name that adjacent work as part of the engagement. The client will argue that the consultancy held itself out as competent to advise on the adjacent question, charged for the engagement that included it, and is therefore on the hook for its consequences. The consultancy will argue that the adjacent work was outside scope and was not advice within the meaning of the engagement letter. The contemporaneous record — the email trail, the timesheets, the slide circulation list — will decide which version sticks.
The practical defence is discipline at the moment the adjacent question is asked. A change order or scope-extension note, even a one-paragraph email confirming what is and is not being undertaken and on what basis, is the difference between a defensible position and a contested one. The cost of writing that note at the moment is twenty minutes; the cost of not writing it, three years later, is the difference between a claim that closes out and a claim that crystallises.
Reliance, third parties and the deliverable's own wording
English law on duty of care to third parties relying on professional advice is well-developed but fact-specific. The starting point is that a duty is owed to the named client. A duty to a third party arises where it is reasonable to foresee that the third party will rely on the advice, the third party does so rely, and the relationship is sufficiently proximate. Strategy consultancies routinely produce deliverables — diligence reports, fairness opinions, growth plans — that are foreseeably going to be shared with financiers, sponsors, advisers and sometimes acquirers.
The deliverable's own reliance wording matters. A report that says on its front page "this report has been prepared solely for the use of X and may not be relied upon by any other party" reads differently in litigation from a report that is silent on the point or, worse, carries language addressed to a broader audience. Consultancies that produce diligence-style reports should have a standard reliance paragraph and should resist client requests to broaden it without thinking through the implications.
Where third-party reliance is intended — a financier needs to be a named beneficiary of a strategy report, or a sponsor's investment committee is being asked to rely formally on a piece of diligence — that intention should be priced into the engagement, documented in a reliance letter, and reflected in the PI policy. Some PI insurers ask to see specific reliance letters above a fee threshold; the broker should be raising that at renewal.
Claim sources specific to strategy work
The following claim patterns recur and are worth recognising at engagement-letter stage rather than at notification.
Growth-plan and market-entry claims. As in the opening scenario — the client acts on a growth plan or market-entry recommendation and the commercial outcome falls short. The dispute turns on what was promised, what was modelled, and how the assumptions were qualified. Defence costs alone reach six figures on a contested matter.
Commercial diligence omissions. A commercial due diligence report missed or understated a material customer-concentration, contractual, regulatory or market issue. The buyer or financier claims the diminution in value. Diligence claims are heavily document-driven and the deliverable's reliance language is central.
Restructuring and turnaround advice. A strategy firm advises on a turnaround that fails to stabilise the business. The administrator or successor management argues that the strategic recommendation was flawed or that warning signs were missed. These claims often pull in directors' duties points and can be politically charged.
Pricing and commercial strategy claims. A pricing recommendation leads to volume or margin loss the client did not anticipate. The dispute turns on the data inputs, the elasticity assumptions, and whether the recommendation properly captured competitive response.
Cost-take-out and operating-model claims. A cost programme designed by the consultancy delivers less benefit than the business case promised, or delivers it later, or with greater service disruption. The claim is for the shortfall in benefits.
Board-paper liability. A board paper written by the consultancy is later said to have misrepresented the position to the board. Even where the consultancy did not sign the paper, its role in drafting can pull it into a directors' duties or shareholder dispute.
What to ask your broker
A renewal conversation with the firm's broker should not stop at "what's our limit and what's our premium." For a strategy consultancy, the questions that matter are these.
How does the PI wording define "professional services," and does it capture the full range of work the firm now does — including strategy, diligence, interim, training and any AI-augmented deliverables? Where the firm has expanded into adjacent work since the last renewal, the wording may need updating to keep pace.
How does the policy respond to contractual liability and indemnity wordings in client MSAs? Most modern PI policies respond to civil liability arising from breach of duty in the performance of professional services, but many exclude or qualify cover for liability assumed under contract beyond what the firm would owe in tort. A client indemnity that goes wider than the consultancy's underlying liability may not be picked up; that gap should be identified before the contract is signed, not after.
How are sub-contractors and associates treated? If the firm runs on an associate model, the definition of "insured" and the conditions imposed on associate work need to support the way the firm operates.
What is the retroactive date, and is it being preserved through any insurer move? Losing the retroactive date in a broker transfer is one of the most common ways a strategy consultancy ends up with a claim that no policy will respond to.
How does the policy interact with the firm's post-delivery cover obligations under client MSAs? If the firm has signed up to maintain cover for six, eight or ten years after delivery, the practical question is how that obligation will be honoured in run-off if the firm ever ceases trading.
Where does cyber sit alongside PI? Where the firm runs cloud-hosted models, holds client data, or uses generative AI in deliverables, a standalone cyber policy alongside PI is increasingly the market position. The two policies should be placed in a way that avoids gaps and avoids duplication.
Frequently asked questions
Does my PI cover strategic advice that turns out to be wrong?
Yes, in principle — that is exactly what consulting PI is for. The policy responds to civil liability arising from a breach of duty in the performance of professional services, and strategic advice is professional service. What the policy will not do is rescue a position that has been undermined by other features of the engagement — a missed notification, an unrecorded scope extension, a contractual indemnity that goes wider than the policy responds to, a sub-contracted associate who was not properly inside the policy's definition of insured. The strength of the underlying engagement documentation is what makes the cover work.
What happens if my SOW is vague about scope?
A vague SOW does not, by itself, exclude cover under your PI policy — but it materially weakens the defence of any claim that depends on what was and was not in scope. Insurers and defence counsel work from the contemporaneous record; if the record does not establish the boundary clearly, the client's version of scope is harder to push back on. The remedy is engagement-letter discipline at sign-off, not at the point of dispute.
Can a third party who reads my report sue me?
Possibly. English law allows third-party claims in negligent misstatement where it is reasonable to foresee that the third party will rely on the advice, the third party does so rely, and the relationship is sufficiently proximate. Whether those conditions are met is fact-specific. Reliance language on the deliverable itself — restricting use to the named client, or extending it deliberately to named third parties on stated terms — is the practical control. A consultancy that wants to limit third-party reliance should say so on the deliverable; a consultancy that intends to allow third-party reliance should price for it and document it.
Does scope creep affect my insurance cover?
It affects the defence of any claim arising from the work, more than it affects cover. Most PI wordings respond to work performed by the firm in the conduct of its professional services, whether or not that work was on a formal SOW. The issue is that scope-crept work is, by definition, unrecorded or under-recorded, and a claim arising from it is harder to defend on the documentary record. A change-order discipline that captures scope extensions in writing protects both the defence position and the policy response.
How do liability caps in MSAs interact with my PI policy?
A liability cap in an MSA limits what your client can recover from you under the contract. It does not, in itself, limit what a third party can claim. PI responds to your civil liability whether or not it is capped contractually, up to the policy limit. A cap is useful — it gives you a contractual ceiling — but it is not a substitute for cover, and the carve-outs in the cap (confidentiality, IP, fraud, personal injury) are often the most exposed parts of the contract. The PI wording's response to those carve-outs is worth checking specifically.
Should I notify a circumstance if I am not sure it will turn into a claim?
Yes, generally. Claims-made policies require notification as soon as practicable after the firm becomes aware of a circumstance that may give rise to a claim. The test is not "will it crystallise" — it is "may it give rise to a claim." A precautionary notification does not commit the firm to anything; it preserves the right of the current policy to respond if the matter does crystallise later. Late notification is the single most common reason a claim fails to be covered.
How does retroactive date work if I move broker or insurer?
The retroactive date on the new policy is the date from which work giving rise to a claim is covered. If the new policy is written with a retroactive date matching the inception of the new policy, all prior work is uncovered. The whole purpose of a properly handled move is to preserve the original retroactive date — usually the date the firm first held continuous PI cover — so the new policy responds to claims arising from any work since that day. Losing the retroactive date in a broker transfer is, with late notification, the most common way a consultancy ends up with an uncovered claim.
Do I need higher limits for diligence work than for advisory work?
Diligence work is more exposed than advisory work because the deliverable is more frequently relied upon by third parties — sponsors, financiers, future acquirers — and the loss alleged is usually the diminution in deal value, which can be a large multiple of the diligence fee. Firms that run a meaningful diligence practice typically carry higher PI limits than firms doing only board-level advisory. The specific number depends on the largest realistic exposure on a single piece of diligence and on what client MSAs and financier reliance letters require.
Related guides
- Management consultants PI insurance UK guide 2026
- Public-sector consultancy PI — contract assignment and right-to-audit
- Management consultants sector page — speak to a broker
About Apex Insurance Brokers — Apex Insurance Brokers Limited is authorised and regulated by the Financial Conduct Authority, FCA firm reference 724952. Registered in England and Wales, Companies House 07014570. Last reviewed: May 2026.
This guide is general information about Professional Indemnity Insurance for UK strategy consultancies and is not advice tailored to any individual firm's circumstances. For advice on your own renewal please speak to a broker — contact@apexinsurancebrokers.co.uk or 0117 325 0027.
FAQPage JSON-LD (hand-rolled — add via Yoast Custom Field or theme injection)
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Does my PI cover strategic advice that turns out to be wrong?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes, in principle — that is exactly what consulting PI is for. The policy responds to civil liability arising from a breach of duty in the performance of professional services, and strategic advice is professional service. What the policy will not do is rescue a position that has been undermined by other features of the engagement — a missed notification, an unrecorded scope extension, a contractual indemnity that goes wider than the policy responds to, or a sub-contracted associate who was not properly inside the policy's definition of insured."
}
},
{
"@type": "Question",
"name": "What happens if my SOW is vague about scope?",
"acceptedAnswer": {
"@type": "Answer",
"text": "A vague SOW does not, by itself, exclude cover under your PI policy, but it materially weakens the defence of any claim that depends on what was and was not in scope. Insurers and defence counsel work from the contemporaneous record; if the record does not establish the boundary clearly, the client's version of scope is harder to push back on. The remedy is engagement-letter discipline at sign-off."
}
},
{
"@type": "Question",
"name": "Can a third party who reads my report sue me?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Possibly. English law allows third-party claims in negligent misstatement where it is reasonable to foresee that the third party will rely on the advice, the third party does so rely, and the relationship is sufficiently proximate. Reliance language on the deliverable itself — restricting use to the named client, or extending it deliberately to named third parties on stated terms — is the practical control."
}
},
{
"@type": "Question",
"name": "Does scope creep affect my insurance cover?",
"acceptedAnswer": {
"@type": "Answer",
"text": "It affects the defence of any claim arising from the work more than it affects cover. Most PI wordings respond to work performed by the firm in the conduct of its professional services, whether or not on a formal SOW. The issue is that scope-crept work is unrecorded or under-recorded, and a claim arising from it is harder to defend on the documentary record. A change-order discipline that captures scope extensions in writing protects both the defence position and the policy response."
}
},
{
"@type": "Question",
"name": "How do liability caps in MSAs interact with my PI policy?",
"acceptedAnswer": {
"@type": "Answer",
"text": "A liability cap in an MSA limits what your client can recover from you under the contract. It does not in itself limit what a third party can claim. PI responds to your civil liability whether or not it is capped contractually, up to the policy limit. A cap is useful but is not a substitute for cover, and the carve-outs in the cap — confidentiality, IP, fraud, personal injury — are often the most exposed parts of the contract."
}
},
{
"@type": "Question",
"name": "Should I notify a circumstance if I am not sure it will turn into a claim?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes, generally. Claims-made policies require notification as soon as practicable after the firm becomes aware of a circumstance that may give rise to a claim. The test is not will it crystallise but may it give rise to a claim. A precautionary notification does not commit the firm to anything; it preserves the right of the current policy to respond if the matter does crystallise later."
}
},
{
"@type": "Question",
"name": "How does retroactive date work if I move broker or insurer?",
"acceptedAnswer": {
"@type": "Answer",
"text": "The retroactive date on the new policy is the date from which work giving rise to a claim is covered. If the new policy is written with a retroactive date matching the inception of the new policy, all prior work is uncovered. The whole purpose of a properly handled move is to preserve the original retroactive date so the new policy responds to claims arising from any work since the firm first held continuous PI cover."
}
},
{
"@type": "Question",
"name": "Do I need higher limits for diligence work than for advisory work?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Diligence work is more exposed than advisory work because the deliverable is more frequently relied upon by third parties — sponsors, financiers, future acquirers — and the loss alleged is usually the diminution in deal value, which can be a large multiple of the diligence fee. Firms that run a meaningful diligence practice typically carry higher PI limits than firms doing only board-level advisory."
}
}
]
}