Service Scope Document: Define Your AI Offer Boundaries

The job that pays £500 and somehow eats two weeks always starts with a fuzzy scope. This writes a clear scope document: what's included down to formats and revision counts, and an explicit list of the extras clients drift into asking for. Set it at the start and the awkward conversations don't happen. For anyone whose projects keep ballooning.

Help me write a clear service scope document for my productised AI-assisted service to eliminate scope creep and set client expectations. Service: {SERVICE_NAME}. Standard deliverables: {WHAT_IS_INCLUDED}. Here are things clients sometimes ask for that I want to exclude: {COMMON_SCOPE_CREEP_EXAMPLES}. Write the scope document with four sections: (1) What is included: specific deliverables, formats, and number of revisions, (2) What is not included: clear exclusions with no-blame language, (3) Client responsibilities: what the client must provide and when, (4) AI usage disclosure: a transparent one-paragraph statement explaining how AI tools assist delivery and what human oversight is applied. Use professional but plain language suitable for a client contract or proposal appendix.