How to Write a Contract for a UK-Based Client

The Fortress Framework: How to Bulletproof Your Engagement from Day One#

Use this as your pre-signature risk screen. Lock down scope, exit, liability, and confidentiality before you sign. If any of those are vague, they can become dispute points later.

Before you start: Review the full contract pack as one set: the main agreement, SOW or proposal, pricing, redlines, and the emails or call notes where commitments were made. HMRC guidance recognises that terms can be written, oral, implied, or mixed. The signed draft should reflect the real deal, not just one part of it.

Step 1: Lock down the SOW#

Your SOW should be clear enough that a third party can see exactly what you will deliver, how acceptance works, and what sits outside scope. UK freelance guidance says scope and pay terms should be explicit, so spell them out. Before you sign, confirm the SOW includes:

• objectives tied to the client outcome
• deliverables with clear form, format, and quantity
• acceptance criteria, including approver and timing
• exclusions, especially common client assumptions
• revision limits and a written Change Request path
• dependency assumptions, such as client access, feedback, assets, and sign-off timing

Do not implement changed work on verbal agreement alone. Use signed written authorisation for contract changes. Attach the SOW as a schedule, add a version and date, and make sure every priced item appears there. Avoid vague phrases like "ongoing support" or "reasonable revisions" unless you also set clear limits.

Step 2: Set the exit path#

Most freelance contracts should set out both a no-fault exit and a breach exit. There is no single UK default notice period, so do not treat numbers from templates, such as 30 or 90 days, as automatic defaults. Define the unwind clearly, including:

A simple test helps here. If termination happened tomorrow, both sides should be able to say what is delivered, what is paid, and who handles handover.

Step 3: Cap liability realistically#

Set a liability cap you can defend for the deal size and risk profile. Do not accept unlimited liability by default. Under UCTA 1977, liability for death or personal injury caused by negligence cannot be excluded. Other negligence limits must satisfy reasonableness based on what the parties knew, or should have known, when contracting.

Template figures, such as 125% of charges, are examples, not legal defaults. Set your cap by reference to contract value, insurance, and risks you control. If governing law is England and Wales, draft to that framework. If Scotland applies, verify the wording for that jurisdiction.

Step 4: Define confidentiality and data return#

Confidentiality terms need to cover the whole life of the engagement, not just the active project. Define confidential information, exceptions, access limits, and end-of-contract handling. Where personal data is in scope, state whether data must be deleted or returned at the client's choice at contract end.

Use confidentiality survival wording deliberately. A fixed period may work, but survival can also run until the information stops being confidential. Before signing, confirm where data is stored, who can access it, and whether subcontractors are bound by the same duty of confidence.

The Cash Flow Command: Structuring Clauses That Guarantee Payment#

Once scope and exit are clear, turn them into invoice events you can actually administer. Your payment structure should match project uncertainty, approval complexity, and how much credit risk you can carry.

Before you start: Cross-check the payment chain across the main agreement, SOW, pricing, and approval path. If those documents define different trigger points, you create avoidable payment delays. If you operate as a sole trader, treat payment risk conservatively. You are personally responsible for all business debts.

Step 1: Choose the billing model that fits the job#

Pick the billing model based on how the work will actually run, not what sounds easiest when you sign. No model is automatically safer; outcomes depend on how clearly triggers and acceptance are defined.

Use observable triggers only, such as kickoff, delivery of a named item, or approval by a named approver. Avoid vague triggers like "substantial completion."

Step 2: Write payment terms so they are enforceable in practice#

Write the clause like operating instructions: when you invoice, when payment is due, what counts as acceptance, and whether work pauses if invoices are overdue. Specific UK late-payment interest rates or compensation fee bands are not verified in this grounding pack, so do not hard-code template figures without current verification.

Align payment timing with SOW acceptance timing. If acceptance allows a review window, your milestone language should not accidentally push payment further out than you intended.

Step 3: Define termination compensation you can calculate immediately#

If the client can terminate for convenience, make the exit maths explicit before work starts. Cover at least these points:

• Trigger events: convenience termination, an agreed pause threshold, or client non-response that blocks delivery.
• Calculation basis: fees for work completed, approved non-cancellable costs, and any kill-fee method only if it is explicitly defined in the contract.
• Work product at termination: what you deliver, in what format, and what is withheld until payment, for example drafts or source files if your terms say so.
• Invoice timing: issue on the termination date, within a stated number of days, or at the next scheduled billing point.

If you cannot calculate the final invoice from the contract text alone, tighten this section.

Step 4: Match contract cash flow to HMRC deadlines#

Payment terms should also protect your tax cash flow. If you need to complete a Self Assessment return and are newly filing or reactivating, HMRC says you must notify by 5 October, and late notification can lead to a penalty. You can file on or after 6 April, you need your UTR to use online filing, and payment is due by 31 January.

Maintain those records continuously, including bank statements and receipts, plus the invoice and contract or SOW documents tied to each invoice event. HMRC also states that you can set up monthly or weekly payments to budget for your tax bill, which helps when client payments slip.

Before you finalize payment clauses, make sure your invoice and milestone terms map cleanly to real work.

The Asset Lockbox: Protecting Your Most Valuable Creation - Your IP#

Your starting point is straightforward: if you are self-employed, you usually own IP in commissioned work unless your contract gives rights to the client. Start from that position, then state exactly whether the deal uses an assignment, meaning ownership transfer, or a licence, meaning permission to use.

Before you start: Keep the IP clause aligned with the payment clause. If your contract changes rights after final payment, say exactly what changes before and after cleared payment. Define exceptions up front so you do not promise rights you do not control:

• employment-style wording, where work created in the course of employment is treated differently
• your pre-existing materials
• third-party assets
• subcontractor contributions

Also deal with joint creation risk. If contributions are collaborative and not distinct, the work may be treated as joint authorship. Define what counts as client input, what counts as your authorship, and who owns the combined output.

Step 1: Define background IP and third-party inputs#

Start by naming what you are not selling. Your templates, methods, libraries, prompt sets, design systems, and other pre-existing assets should sit inside a clear background IP carve-out.

Apply the same discipline to third-party materials. If a stock asset, font, plugin, or dataset is licensed for limited use, extra uses will need another licence. Before you sign, include a schedule listing pre-existing materials, third-party items, and any contributor other than you.

Step 2: Build a transfer clause that is enforceable#

If the client wants ownership, use written, signed assignment language. If the work will be created later, future copyright can also be assigned in signed drafting. Make sure the clause covers:

If the client needs to edit or adapt the work, include that right expressly in the assignment or licence terms.

Step 3: Pick the ownership model that fits the deal#

Choose the model based on what the client actually needs, not on habit.

A quick decision question often helps: does the client need ownership, or reliable permission to use and modify?

Step 4: Do not miss implementation details#

The common failure mode here is not the headline ownership clause, but the details around it.

• Moral rights: separate from economic rights; not assignable; any waiver must be written and signed.
• Background IP carve-out: reserve your pre-existing tools, methods, and reusable components.
• Portfolio use: get express permission if you want to show the work later.

Keep a clean evidence file: signed contract, IP schedule, third-party licences, subcontractor IP paperwork, and proof of final payment if transfer depends on payment clearance.

The Cross-Border Contract: Special Considerations for the Global Professional#

For cross-border work, treat the contract as an operations checklist. Confirm who is contracting, then separate UK filing checkpoints from contract and tax items that need jurisdiction-specific verification.

Step 1: Confirm the contracting entity and UK filing basics first#

Get the contracting party right before anything else. State the exact legal entity providing the service before you sign. If you trade as a sole trader, you run the business directly. If you contract through a limited company, that company is legally separate, which changes tax handling and legal responsibility.

If you file in the UK, keep Self Assessment basics in scope: first-time filers must register before using the online service, and you need your UTR. If you need to complete a return for the previous year, HMRC says you must notify by 5 October, and late registration can lead to penalties. Keep records, for example bank statements or receipts, and if you have an existing account, reactivate it before filing to avoid delays. You'll also need to pay your tax bill by 31 January.

Step 2: Build the dispute clause from components, not copy-paste#

Do not assume one default forum fits every deal. Build this part explicitly, but treat final wording as legal-review work for the jurisdictions involved:

• legal system governing the agreement
• forum for disputes
• dispute route before formal proceedings, if any
• enforceability caveat to verify from the contract, counsel note, or governing records before use

Before signing, make sure these terms are reviewed for the actual contracting entity and where enforcement may be needed.

Step 3: Treat tax wording as verified, scenario-specific drafting#

Tax wording is not a template exercise. Do not assume one cross-border tax clause applies in every case; confirm the exact treatment for the service and parties in scope before finalizing contract or invoice wording.

If the engagement includes mixed service types, digital access, reimbursed costs, or platform billing, get local tax advice before issuing invoices. Also, if your UK filing position depends on residence status, confirm it under the UK's Statutory Residence Test before you assume HMRC's online filing service will fit your case. If you lived abroad as a non-resident, HMRC's online filing service may not be available, and you may need commercial software or other forms.

Step 4: Fix payment mechanics in writing#

Pre-sign cross-border checks:

• compliance requirements: Add verified process wording for the jurisdictions in scope.
• contracting party identity: confirm the exact legal name of the entity signing
• evidence trail: keep acceptance and delivery records so you can prove performance and payment status

Conclusion: From Anxious Freelancer to Empowered CEO#

Use this as an operating checklist, not just paperwork. For UK freelancers, the practical baseline is getting Self Assessment and recordkeeping right, then treating contract and IR35 details as items to verify separately.

1. Confirm your business structure early (sole trader or limited company), since it affects tax treatment and legal responsibilities.
2. If you operate as a sole trader and expect to earn more than £1,000 in a tax year, register for Self Assessment early (you need a National Insurance number to register).
3. If you need to complete a return for the previous tax year, tell HMRC by 5 October.
4. Keep records such as bank statements and receipts so your return can be completed correctly.
5. Before filing online, make sure any existing Self Assessment account is reactivated and your UTR is ready.
6. Plan around filing and payment timing: submit on or after 6 April following the tax year end, and pay your tax bill by 31 January. If the online service is not available for your case (for example, some non-resident situations), use the alternative routes HMRC provides.

For IR35 status tests and specific contract clause wording, check current HMRC guidance or specialist advice before relying on them. That is the shift: fewer assumptions, more written decisions you can actually operate.