As of 13 August 2026, AI can write a proposal scope of work.

What to actually do

1. Hand it to a person

   The route this page recommends

   A person who owns the outcome does this end to end, worth it when the failure is dear.

2. Use a tool built for this

   Second choice

3. Do it yourself

   The distant third

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

   How to actually do it

   1. Open the client brief, relevant emails and meeting notes, and copy the requirements, requested outcomes, deliverables, deadlines and named stakeholders into one working document.
   2. Open your current service description, delivery process and price or proposal template, then add your standard exclusions, client responsibilities, dependencies and approval rules.
   3. Remove unconfirmed claims and mark uncertain points as OPEN QUESTIONS, especially results, dates, integrations, data handling, ownership and acceptance requirements.
   4. Paste the gathered material into the prompt and ask the chatbot to produce the scope of work using only the supplied facts.
   5. Compare every deliverable, exclusion, dependency, date and acceptance criterion in the draft with the client brief and your delivery plan, correcting anything that is missing or overstated.
   6. Ask the chatbot to produce a redline-style list of commitments that are vague, difficult to measure or outside the agreed service, then resolve each item with the delivery owner.
   7. Send the checked scope to the appropriate internal approver and, where it creates contractual, data protection or intellectual property obligations, ask a solicitor or other relevant professional to check those points before sending the proposal.

   Prompt

   Write a client-ready scope of work for a UK business proposal using the information below. Use British English and plain, precise wording. Do not invent facts, prices, dates, deliverables, performance claims or legal terms. If information is missing or contradictory, list it under OPEN QUESTIONS instead of guessing.
   
   Structure the document with:
   1. Purpose and desired outcome
   2. In-scope services and deliverables
   3. Out-of-scope items and exclusions
   4. Client responsibilities and dependencies
   5. Our responsibilities
   6. Assumptions
   7. Milestones and indicative timescales, only where supplied
   8. Acceptance criteria and how approval will work
   9. Change control and what happens when requirements change
   10. Risks, constraints and open questions
   
   Separate confirmed commitments from assumptions and proposals. Make each deliverable specific enough to check, and flag any wording that could create an unintended commitment about results, availability, compliance, intellectual property, confidentiality or personal data. Do not draft a contract or give legal advice. End with a short CHECK BEFORE SENDING list covering scope, exclusions, dependencies, dates, ownership, acceptance criteria and any promises that need approval from a solicitor or other relevant professional.
   
   CLIENT BRIEF:
   [Paste the client brief]
   
   MEETING NOTES:
   [Paste relevant notes]
   
   OUR SERVICES AND DELIVERY LIMITS:
   [Paste your service description, capacity and exclusions]
   
   KNOWN COMMERCIAL TERMS:
   [Paste confirmed price, timescale and payment information, or write none]
   
   INTERNAL NOTES:
   [Paste risks, dependencies and approval requirements, or write none]

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