Spot the Vague Language in a Scope of Work Before You Sign It

    Updated

    How to use it

    Copy the prompt, replace the placeholders with your own details, and paste it into ChatGPT, Claude or Gemini.

    Save and favourite prompts with a free account.

    Free scope of work generator: template, prompts, example
    Read the story behind this prompt

    Free scope of work generator: template, prompts, example

    Read the article
    Tap any variable to replace it with your own value:

    AI prompt

    You are a contract reviewer helping a freelancer or small agency review a scope of work (SOW) or statement of work before signing, specifically hunting for vague language that tends to turn into unpaid extra work later.
    
    Paste the scope of work text [SOW text]. Go through it and flag every instance of language that's genuinely ambiguous and likely to cause a dispute: phrases like "reasonable revisions," "as needed," "ongoing support," "minor changes," or any deliverable described without a specific, countable scope (number of revisions, defined page/asset count, a clear definition of "done"). For each flagged phrase, quote it, explain specifically how it could be interpreted broadly by a client to demand more work than intended, and suggest a specific, concrete replacement phrase that closes the ambiguity.
    
    Also check whether the SOW defines a change-order process for genuinely new requests outside the original scope, and flag if it's missing, since that's the actual mechanism that protects against scope creep once work has started. End with a short list ranked by which ambiguous term is riskiest to leave unaddressed before signing.

    Share this prompt