The Disclosure Line: What Your Consultant Earns the Right to Know

Transparency is a virtue in advisers and, in clients, occasionally a hazard. The instinct to hand over everything — the board pack, the full customer list, the salary bands, the half-formed worry about the finance director — feels like good faith. It usually is. It is also, quietly, a transfer of leverage, and the transfer is rarely reversed when the engagement ends.

None of this argues for secrecy. An adviser given a sanitised version of the problem will give you a sanitised answer to a problem you do not have. The task is to find the line: the point beyond which further disclosure stops improving the advice and starts creating dependency, conflict or exposure.

What genuinely improves the advice

A consultant's output is only as good as the model of your world they can hold in their head. Five categories of information do most of that work, and it pays to be generous with all of them.

The decision and its owner. Not the stated project, the real one. Who signs, who can veto, and what happens if nothing is decided. Ambiguity here accounts for more wasted consultancy than any other single factor.

The constraints that cannot move. A covenant test, a family shareholder who will not sell, a union recognition agreement, a regulator's live interest. Advisers who do not know the immovable objects spend their first month proposing to move them.

The financial reality. Not simply the management accounts, but the cash position, the headroom, and the matters that keep the finance director awake.

The history. What has already been tried, by whom, and why it failed. Organisations are extremely reluctant to volunteer this, and it is the single most valuable briefing an adviser can receive.

The bad news. A key customer signalling a move, a director about to resign, a product with a year left in it. Delivered early and undramatically, it improves the advice immediately.

What does not

Beyond that, disclosure begins to do other work. Several categories reward caution.

Individual performance or grievance matters, shared outside a properly constituted process, create risk for both parties and carry marginal analytical value: what an adviser needs is the shape of the capability gap, not the name in the file.

Information belonging to third parties — customer lists, contact data, supplier pricing — raises obligations under UK GDPR and, often, contractual ones the client has since forgotten. Data minimisation is not administrative pedantry; it is part of why your commercial agreements with those third parties still stand.

Litigation and regulatory matters deserve specific care. Once a third party is briefed on a dispute, the boundaries of legal professional privilege become considerably harder to draw. Keep counsel and consultant in distinct lanes.

And unpublished intentions — an acquisition, a market exit, a restructuring — should be shared on a need-to-know basis, with an explicit written instruction that they sit inside the engagement and outside the consultant's general knowledge.

The dependency test

The subtler risk is not confidentiality but competence transfer. An adviser who holds the only accurate model of your operation, the only consolidated view of a process, the only memory of why the last attempt failed, has become infrastructure. That is comfortable for them and corrosive for you.

A single question is enough to test it: if this adviser disappeared tomorrow, could a competent replacement, given the file, take up the work within a fortnight? If the honest answer is no, the problem is not the contract. It is that knowledge has not been written down.

The remedy is unglamorous. Insist on working papers rather than presentations. Have your own staff in the room, taking notes rather than merely receiving them. Require that models live in your systems, in your formats, with your assumptions labelled. Ask for a two-page method note at the end of every phase — what was done, in what order, with what result. The habit costs an hour a week and removes most of the moat.

Structuring the terms

A handful of clauses do most of the work, and none should be contentious: mutual confidentiality with defined categories, a stated retention period and a destruction obligation that can be evidenced; a need-to-know schedule annexed to the engagement letter, listing the categories of information to be shared, why each is needed, who will hold it and for how long. That schedule reads as bureaucracy and functions as a decision aid, because every addition must be justified in a sentence.

Where personal data is processed, the data protection terms should be consistent with Article 28 of UK GDPR, including sub-processor disclosure and transfer safeguards. Ownership of output should be explicit: methods, models, working papers and any benchmarking derived from your engagement vest in the client, while benchmarks the adviser already holds remain theirs.

Add conflict checks against a named list, refreshed at each phase, with a positive obligation to disclose new engagements rather than a passive hope. Then the handover clause: ten working days, a closing readout, the file in usable form, and final payment conditional on delivery. This is the clause most often omitted and most often regretted.

Keeping the upper hand

The client's advantage rarely comes from withholding information. It comes from holding the record: knowing what was shared, why, on what terms, and being able to pick it all up and hand it to someone else without losing a quarter.

That is a matter of discipline rather than distrust, and it tends to improve the advice as well as protect the client — because an adviser who knows the file will outlast them works rather harder to be useful while they are there.