Consultancy agreement terms to consider

A consultancy agreement should distinguish the result being purchased from the time or effort being supplied. Define the deliverables, assumptions and client inputs, then connect the fee arrangement to those obligations. Avoid relying on a broad promise to provide support where the parties expect different outcomes.

Review ownership of work, permitted use of existing tools, confidentiality and any subcontracting. Contract wording alone does not settle employment status or tax status; actual working arrangements may require a separate assessment. Keep that issue distinct from the commercial scope review.

Define the output and the limits of the engagement

Describe the report, analysis, implementation or support being purchased. State the assumptions and information the client must provide. A consultancy can be engaged to advise rather than to guarantee a business result, so the scope should distinguish the promised work from outcomes dependent on management decisions or market conditions.

Identify acceptance criteria where a defined deliverable is expected. Explain how comments are provided, how many revision rounds are included and what counts as additional work. An open-ended obligation to revise until satisfied can create uncertainty for both parties. The client needs usable work, while the consultant needs a clear route to completing the agreed assignment.

Connect fees with effort, milestones and changes

For day-rate work, agree how time is recorded, any budget cap and approval for exceeding it. For fixed fees, define the scope on which the price depends. A fixed price should not be mistaken for an obligation to provide unlimited additional analysis. Record changes before the team relies on revised instructions.

Check deposits, expenses, invoice timing and payment disputes. Applicable late-commercial-payment rules may affect qualifying debts. ^[1] The client should understand when payment becomes due and the consultant should know which supporting records are required. Avoid linking payment to an undefined internal approval process that can remain unresolved indefinitely.

Resolve ownership and background material

List newly created deliverables, pre-existing tools and third-party components. Copyright ownership in commissioned work does not automatically pass simply because the client paid for it. ^[2] Decide whether the client needs assignment or a licence broad enough for the intended use, including internal distribution, modification or use by another adviser.

If the consultant retains a model or methodology, define how the client may use the delivered result without acquiring the entire underlying tool. Check whether editable files are included. Legal permission and practical usability are separate: a broad licence is of limited operational value if the client receives only a format it cannot maintain or adapt as agreed.

Address people, status and subcontracting

Identify the named personnel and how replacements are approved. Check whether subcontracting is permitted and which confidentiality, data and IP obligations must flow into the subcontract. A consultant should not promise rights in a subcontractor's work without obtaining the necessary agreement. The client should know who will access sensitive information.

Employment and tax status require a separate assessment of the real working arrangements where relevant. Calling someone an independent consultant does not settle every status issue. Explain actual control, working practices and responsibilities to the appropriate adviser. Keep that assessment distinct from the commercial question of what deliverable the client expects.

Allocate reliance and responsibility sensibly

State who may rely on the advice and for what purpose. A report prepared for one decision may not be suitable for a different transaction or an external investor. If third-party reliance is expected, address it before delivery. Do not circulate the report more widely on the assumption that payment creates unrestricted reliance rights.

Review liability limits against the assignment and information supplied by the client. Clarify how errors are raised and corrected. The consultant may need to identify limitations in source data, while the client needs a clear understanding of what was checked. Avoid presenting a narrowly scoped review as comprehensive verification of the whole business.

Plan completion and handover

Agree final files, working instructions and any ongoing support. Record what remains outside scope and who takes the next implementation decision. If the assignment ends early, assess payment for completed work, use of unfinished material and return of information.

Read Contract variations and written approval for variations. Commercial contract review can help align the consultancy scope, fee, IP and exit terms with the actual assignment, including the expectations of the people commissioning and using the work.

State what the client must decide after delivery

A consultant's report may recommend options without implementing them. Identify who approves the next stage, what further information is needed and whether implementation support is included. This keeps the handover useful and avoids a client assuming that an advisory fee includes unlimited follow-up execution. Record any separate proposal for later work rather than allowing the completed assignment to drift into an undefined continuing engagement.

Illustrative scenario

A consultant produces a strategy report using a pre-existing analytical model. The client expects to own everything, while the consultant intends to reuse the model. The agreement distinguishes newly commissioned material from background tools and records the client's permission to use the delivered report for its intended business purpose.

Preparation checklist

• Define outputs, assumptions and acceptance arrangements.
• Agree day rates, caps and approval for additional work.
• Separate background materials from newly created work.
• Check confidentiality, subcontracting and handover requirements.