Managing Diligence Advisor Change Requests Without Slowing the Deal

It is week three of a financial diligence on a £140M carve-out, and the QoE lead emails: "While we were in the management accounts we noticed the intercompany recharges are a mess. Want us to unwind them properly?" You have about ten minutes before that turns into billable work. Managing diligence advisor change requests is what you do in those ten minutes: decide whether the ask is in scope or out, put a number on it if it is out, and pick a response that is not the default "yes, go ahead." Get that triage right and the deal keeps moving; skip it and the email becomes a line you first read on the final invoice six weeks later.

The hard part is that the ask is almost always reasonable. Unwinding messy intercompany recharges probably is worth doing. So the question is never "is this good diligence?" but "is this priced, and against which budget?" Most deal teams collapse those two questions into one, answer yes to the first, and never ask the second. The drift that follows is rarely one big ask; it is a run of small reasonable ones, each waved through in the moment because stopping to price them felt like the slow option.

What counts as a change request in due diligence?#

A change request is any work an advisor proposes that sits outside the scope and deliverables agreed in the engagement letter. It can be an extra jurisdiction the legal team wants to cover, a deeper working-capital analysis the QoE lead suggests, a data set that turned out messier than scoped, or a new question the deal throws up mid-stream. If it was not in the original scope and it will consume advisor hours, it is a change request, whether or not anyone uses the term.

The reason this matters is that the engagement letter is where the money is defined, and a vaguely drafted one quietly authorises drift. Writing on M&A engagement letters for Thompson Coburn LLP, David J. Kaufman and Matthew E. Misichko note that "a broad definition will likely provide an investment bank with more opportunities to earn a fee", and advise clients to define scope narrowly and to insist on "a cap on third party fees, which cannot be exceeded without client approval". The same logic governs every diligence workstream, not just the lead advisor's. Where scope is loose, "additional work" is the advisor's discretion to expand. Where it is tight, every expansion has to come back to you as a request, which is exactly what you want.

The trap is treating a change request as a yes/no question. It is first a classification question and then a pricing one. The right reflex to "want us to unwind the intercompany recharges?" is not "yes" or "no" but "is that actually outside what we engaged you for, and if so, what does it cost and against which cap?" Building the governance habit that stops these asks accumulating in the first place is the subject of our guide on how to prevent diligence advisor scope creep. This post is the narrower, faster job: the live triage you run on a single ask once it has already landed in your inbox.

How big is a change request, really?#

A single change request looks small and a run of them is not. There is no clean public dataset on diligence change-order size, but the closest analogue, construction change orders, is well measured and the pattern is instructive. A Dodge Data & Analytics study cited by Rhumbix found change orders account for an average of 10% of total contract value, with troubled projects running as high as 25%. Diligence is more exposed than construction, not less, because the entire job is to find things that were not in the original picture.

Put that against a diligence budget and the figures stop being abstract. On a UK core-mid-market deal, financial due diligence alone commonly runs £75,000 to £200,000 depending on complexity and entity count, per FD Capital's vendor due diligence guide, and a full multi-workstream programme that runs several of those strands in parallel comfortably reaches the mid-six figures. A 10% change-order rate on an illustrative £400k programme is £40k of unbudgeted work, roughly the cost of a small standalone workstream, arriving as three or four "while we were in there" emails that each felt trivial in the moment. The unit you should hold in your head is not the deal total; it is the change, and the change is bigger than it looks.

That chart is a construction benchmark, not a diligence one, and the comparison has limits: diligence engagements are smaller, shorter, and more discretionary than a build contract. Use it for the order of magnitude, not the decimal. The honest reading is that change orders are a material, recurring share of cost in any scoped professional engagement, and a diligence with a deliberately porous boundary between "thorough" and "out of scope" is squarely in that population.

Why does waving it through feel faster?#

Saying "yes, go ahead" feels faster because the cost of triaging the change is visible now and the cost of skipping the triage is invisible until the invoice. The ten minutes you spend getting a number and making a call is felt; the £15k it saves you arguing about in eight weeks is not, yet. The asymmetry that this hides is what makes the in-the-moment decision matter: before the advisor starts, the work still has a price, a clean approval, and a live alternative you can reach for, which is to descope something else to fund it. Once the hours are spent, all three are gone, and the only conversation left is whether you will pay for work that genuinely helped the deal. You almost always pay.

That live alternative is the part most teams never use, and it is the single most useful move in change-request triage. "Can we drop the lower-priority working-capital sensitivity to fund unwinding the recharges?" keeps the workstream cap flat, forces a real conversation about what the diligence is actually for, and turns an open-ended "yes" into a trade you chose. It only exists in the ten-minute window. After the fact there is nothing to trade, because both pieces of work are already done.

Managing diligence advisor change requests starts with classification#

The first move in the ten minutes is to classify the ask, because the advisor and the deal team usually disagree about whether it is even a change. Three quick tests sort almost every one. Is the requested output on the deliverables list in the engagement letter, or is it a new deliverable? Does the work assume something the original scope explicitly assumed away, such as a clean ledger or a single jurisdiction? And does it consume material additional hours, or is it five minutes of a partner's judgement they would have spent anyway? An ask that fails the first two tests and passes the third is an in-scope clarification; you proceed and price nothing. An ask that adds a deliverable, breaks a scope assumption, and burns real hours is a change request, and naming it as one in your reply is what unlocks the rest of the triage.

That naming step matters more than it looks, because the advisor often genuinely believes the work is in scope, and a 30-second check against the deliverables list settles it without anyone feeling accused of padding. The unwinding-the-recharges ask is the clean example: the engagement letter scoped a QoE on the assumption the management accounts reconciled, the recharges do not reconcile, so the unwind is new work that the fee estimate never assumed. Calling that a change request out loud is not bureaucracy. It is the difference between a £15k decision you make and a £15k surprise that makes itself.

How do you price and decide it in ten minutes?#

Once the ask is classified as a change, the rest of the triage is two steps you can do before the advisor picks up the work: get a bounded number, then make a deliberate call. The whole thing should take minutes, because anything heavier is the thing people skip when the deal is busy, which is exactly when change requests cluster.

Descope-to-fund only works if you can see the headroom to descope against, and that is the part a spreadsheet hides until month-end. Knowing the new ask is £15k is half the decision; the other half is knowing which £15k of already-agreed work you would trade for it, and whether the workstream cap has room either way. Advilink is built for exactly that moment: it holds each workstream's agreed scope and cap in one live view, so when a change lands you can price it against real remaining headroom instead of guessing. It is one approach among several, but the visibility is the point, and it is why the full diligence cost breakdown by workstream is worth keeping current rather than rebuilding from invoices.

The reason a not-to-exceed number is non-negotiable is that engagement structure decides how a change behaves. A fixed-fee workstream forces the change into the open as a fee renegotiation; a time-and-materials workstream absorbs it silently and you only see it in the hours, which is why the choice between time-and-materials and fixed fee in due diligence is really a choice about how visible your change requests will be. Cap the specific task and you get fixed-fee visibility on a T&M engagement for that one piece of work.

Two steps is the whole job in the moment, and the deal does not slow for it, because bounding a change while it is still a proposal takes less time than reconstructing it from an invoice does. Understanding why due diligence costs overrun in the first place makes the case plainly: almost every overrun mechanism, the extra jurisdiction, the T&M lag, the assumption that turned out false, traces back to a change that was reasonable to approve and unreasonable to leave unpriced. With dealmakers signalling more discipline rather than less in Deloitte's 2026 M&A Trends Survey of 1,500 corporate and PE leaders, where 90% of PE respondents expect to do more deals and value realisation hinges on execution, the team that can bound a change in ten minutes is the one that closes without a budget surprise. The slow team is not the one that prices changes; it is the one that argues about them after the fact.

Frequently Asked Questions#

What is a change request in due diligence?#

A change request is any advisor work that falls outside the scope and deliverables set in the engagement letter, such as an extra jurisdiction, a deeper analysis, or a messier data set than scoped. It will consume advisor hours and fees that the original estimate did not assume, so it needs to be priced and approved before the work starts, not discovered on the invoice.

How do you handle a scope change request without blowing the budget?#

Run a short triage the moment the ask lands: classify it as an in-scope clarification or a genuine change, and if it is a change, get a not-to-exceed number against a specific workstream cap, then make an explicit approve/descope/decline call. The discipline is bounding the work while it is still a proposal, when you still have leverage, rather than after the advisor has already done it.

How do you tell an in-scope clarification from a real change request?#

Use three quick tests. Is the requested output already on the engagement letter's deliverables list, or is it a new deliverable? Does the work assume something the original scope explicitly assumed away, such as a clean ledger or a single jurisdiction? And does it consume material additional hours? An ask that adds a deliverable, breaks a scope assumption, and burns real hours is a change request; one that fails those is an in-scope clarification you simply proceed with.

How much can change requests add to diligence advisor fees?#

There is no public diligence-specific dataset, but the closest analogue is instructive: a Dodge Data & Analytics study found construction change orders average 10% of contract value and run to 25% on troubled projects. On a £400k multi-workstream diligence programme, a 10% rate is around £40k of unbudgeted work, usually arriving as several small "while we were in there" asks rather than one visible decision.

Should you ever say no to an advisor change request?#

Yes, but declining is only one of three valid responses, alongside approving and accepting the variance, or descoping a lower-value piece of agreed work to fund it within the cap. Descope-to-fund is the underused option: it keeps the workstream cap flat and forces a real conversation about what the diligence is for, instead of quietly growing the budget.

Sources#

1. Top ten issues to negotiate in an M&A engagement letter during an economic downturn. David J. Kaufman and Matthew E. Misichko, Thompson Coburn LLP, 2020. Defining scope narrowly and capping third-party fees so they cannot be exceeded without client approval.
2. How Much Are Change Orders Costing Your Construction Business?. Rhumbix, 2023, citing a Dodge Data & Analytics study. Change orders average 10% of total contract value, up to 25% on troubled projects (construction analogue).
3. UK Vendor Due Diligence Guide. FD Capital. UK mid-market financial due diligence £75k to £200k on a core mid-market deal.
4. 2026 M&A Trends Survey: A tale of two markets. Deloitte, 2026. Survey of 1,500 corporate and PE leaders; 90% of PE and 80% of corporate respondents expect more deals in 2026, with value realisation hinging on disciplined execution.