As of 13 August 2026, AI can draft a UK website development contract.

What to actually do

1. Hand it to a person

   The route this page recommends

   Someone with a licence or accountable authority has to sign this before it counts.

2. Use a tool built for this

   Second choice

3. Do it yourself

   The distant third

   A chat interface, chat-fluent skill, and roughly 1 hour until you can act on the result.

   How to actually do it

   1. Open a document containing the project brief, quotation, statement of work, emails and current payment terms, and remove unnecessary personal data before using them.
   2. Gather the legal names and addresses of both parties, the exact deliverables, exclusions, milestones, acceptance criteria, price, VAT treatment, payment dates, ownership expectations and termination position.
   3. Decide which UK jurisdiction applies and record who provides hosting, maintenance, content, approvals, third-party services and ongoing support.
   4. Paste the gathered facts into the prompt, replacing every bracketed slot and leaving [TO CONFIRM] where the parties have not agreed a term.
   5. Ask the model to produce the agreement, schedules and completion checklist, then copy the draft into a document without treating missing terms as agreed.
   6. Compare every name, date, price, deliverable, milestone, ownership statement and responsibility against the quotation and project records, and ask the other party to confirm disputed commercial points.
   7. Send the completed draft and the model's risk list to a UK solicitor for review, especially the intellectual property, data protection, warranties, liability, indemnities and termination clauses.
   8. Only circulate the solicitor-reviewed version for signature after both parties have approved the commercial terms and the final document identifies the correct legal entities.

   Prompt

   Draft a UK website development agreement between [CLIENT LEGAL NAME AND ADDRESS] and [DEVELOPER LEGAL NAME AND ADDRESS].
   
   Project details:
   - Website or application: [DESCRIPTION]
   - Deliverables: [DETAILED LIST]
   - Exclusions: [WHAT IS NOT INCLUDED]
   - Milestones and acceptance process: [DETAILS]
   - Start date and completion date: [DATES OR CONDITIONS]
   - Price, VAT treatment, payment schedule and late-payment terms: [DETAILS]
   - Change-control process: [DETAILS]
   - Hosting, maintenance, support and third-party services: [DETAILS]
   - Client content and approvals: [DETAILS]
   - Ownership of bespoke code, designs, documentation and pre-existing materials: [DETAILS]
   - Open-source software and licences: [DETAILS]
   - Confidential information: [DETAILS]
   - Personal data, controller and processor roles, security measures and any required data processing terms: [DETAILS]
   - Warranties, remedy for defects and service levels: [DETAILS]
   - Liability cap, exclusions and indemnities: [DETAILS]
   - Termination rights and consequences: [DETAILS]
   - Subcontracting: [DETAILS]
   - Insurance: [DETAILS]
   - Dispute process, governing law and courts: [England and Wales, Scotland, or Northern Ireland]
   
   Use plain UK English and structure the agreement with numbered clauses and schedules. Do not invent facts, prices, dates, legal obligations or agreed terms. Where information is missing, insert [TO CONFIRM] and list the issue in a completion checklist. Distinguish clearly between commercial choices that I must decide and clauses that need a solicitor's review. Include practical definitions, acceptance criteria, payment, intellectual property, confidentiality, data protection, security, warranties, liability, termination, handover and dispute provisions. Do not present this as legal advice. At the end, provide a clause-by-clause risk and missing-information list for a UK business solicitor to check.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.