The Working Asset Test: Who Keeps the Models When the Consultant Leaves?

Most consultancy engagements are commissioned against a clear end point: a report, a recommendation or a board paper. Yet the value of the work seldom rests on the final document alone. It rests on the spreadsheet that translates an assumption into a forecast, the dashboard that tracks a service, the data set that supports a business case, or the model that lets a finance team test a different scenario. If those artefacts remain with the consultant, or remain usable only while the consultant is available, the client has bought a conclusion rather than a capability.

The report is not the working asset

A final report records what was thought at a point in time. A working model allows the organisation to think again. That distinction matters in 2026, when many UK businesses are being asked to make repeated decisions under tight budgets: reforecasting demand, reprioritising capital, reviewing service levels, or responding to changes in regulation and supply chains. A recommendation that cannot be updated is quickly overtaken by events. A model that can be updated, understood and challenged remains useful.

The ownership question is therefore broader than copyright. It covers the editable spreadsheet, the calculation logic, the macros and scripts, the data connections, the dashboard configuration, the documentation and the credentials needed to operate them. It also covers the right to use third-party tools or content embedded in those artefacts. A client may own the file and still be unable to use it.

Where ownership quietly leaks

Ownership rarely fails in an obvious way. It leaks through assumptions that no one records at the start.

A consultant may build a model using a proprietary framework, template or add-in that is licensed to the consultancy, not transferred to the client. The client receives a PDF or a locked workbook and assumes the underlying asset has been handed over. A dashboard may be hosted in the consultant's own environment, with access dependent on a continuing subscription or a support arrangement. A data set may include third-party information that cannot lawfully be passed on in full. A spreadsheet may depend on a password-protected macro or an unsupported plug-in. Documentation may be omitted because the people who built the model are expected to remain available.

None of these issues is necessarily improper. Consultancies are entitled to protect their background intellectual property, their methodologies and their commercial position. The problem is ambiguity. When ownership is left to a general clause about deliverables, both sides can be right in their own reading and the client discovers the gap only when access is revoked or a key person leaves.

A contract test before kick-off

The most effective protection is a short, specific schedule agreed before work begins. It should list the artefacts the client expects to receive, not merely the final report. For each artefact, the schedule should state the format, the owner, the licence terms, the dependencies and the acceptance test. It should distinguish client data and client-specific outputs from the consultant's general methods and reusable know-how.

A practical clause does not need to be elaborate. It needs to be testable. The following wording is a starting point for discussion, not a substitute for legal advice:

'On completion of the engagement and on payment of the agreed fees, the supplier shall deliver to the client a complete and usable copy of all models, spreadsheets, dashboards, scripts, data sets and working documentation created specifically for the client, in native editable format, together with all passwords, administrator rights, macros, data connections and licence permissions necessary for the client to operate, maintain and update those artefacts independently. The supplier may retain a copy for record-keeping and for its general know-how, subject to appropriate confidentiality obligations.'

The clause should also address timing. A promise to hand over 'on request' after termination is weaker than a handover that happens before final payment and before system access is withdrawn. Where third-party licences are involved, the contract should identify who holds them, who pays for them and what happens if the client wishes to continue using the tool without the consultant.

What to test, not just what to sign

A signed clause is not the same as a usable asset. Before kick-off, the client team should be able to answer a few plain questions. Can our own staff open the file on a standard machine without consultant support? Can we see and change the assumptions, rather than only the outputs? Do we hold the administrator rights for the dashboard or platform? Are there macros, plug-ins or data feeds that depend on a licence we do not own? Can we export the data in a format our systems can read? Is there written documentation that a new analyst could follow? If any answer is no, the ownership clause may be technically satisfied while the commercial benefit is not.

It is also sensible to agree an acceptance test. The client's finance or operations team should attempt a routine update, such as changing a forecast assumption or refreshing a data set, before the engagement closes. That test exposes practical dependencies while the consultant is still contractually engaged and able to fix them.

A short buyer's checklist

Before commissioning consultancy, confirm that the engagement letter or statement of work covers:

• a named inventory of working artefacts, not only final deliverables;
• native, editable formats and the location of the master copy;
• ownership of client-specific outputs and the consultant's retained background rights;
• passwords, administrator access, macros, scripts and data connections;
• third-party licences, renewal costs and transferability;
• documentation sufficient for a new user to operate the asset;
• an acceptance test before final payment and access withdrawal;
• confidentiality and UK data protection obligations for any retained copies.

The commercial case for clarity

Clear ownership is not an adversarial demand. It is a condition of good value. For the client, it reduces dependency and the risk of paying twice for the same work. It supports board assurance, audit trails and continuity when staff change. For the consultant, it sets boundaries and reduces the friction of an untidy exit. The most durable consultancy work is not the work that keeps the adviser indispensable. It is the work that leaves the client more capable than before.

When the final invoice arrives, the question should not be who owns the report. It should be whether the organisation can pick up the working asset, understand it and use it without asking permission. That is the clause worth settling at the start.