The idea
Service scope describes what will be delivered, under what conditions, and how completion will be recognised. Clear scope reduces mismatched expectations and gives the team a basis for planning. A broad promise such as full support can mean very different things to different people. Define outputs and boundaries in the customer’s language, while keeping contractual details consistent with appropriate professional advice and organisational policies.
Apply it
List deliverables, included activities, exclusions, customer inputs, dates, and acceptance conditions. State assumptions that affect effort or timing. Distinguish a promised output from an outcome influenced by factors outside your control. Identify who can approve the scope and accept the work. Check that the delivery team understands and can meet each commitment. Use examples to clarify ambiguous terms rather than relying on longer but equally vague descriptions.
Worked example
A website support service includes a monthly update check, one content change of an agreed size, and a backup verification. It excludes redesigns and third-party software fees. Completion means the agreed checks are recorded and the content change is reviewed against the request. The service does not guarantee that every external plugin will never fail. These boundaries help the customer compare the offer accurately.
Guided practice
Write a scope sheet with three deliverables, two exclusions, customer inputs, and acceptance conditions. Identify one phrase in your current offer that could be interpreted too broadly. Use a real business, a community project, or a clearly labelled fictional case. Work on one offer or customer segment so your notes remain comparable. Write your answer before reading it aloud. Replace vague claims with a name, number, date, or observable action. Keep a short list of assumptions and the evidence you would need to check them. Save this worksheet for the next lesson.
Checkpoint
Could the customer and delivery team agree whether the work is complete? Replace an ambiguous promise with an observable output and a clear boundary. Do not mark the lesson complete until you can explain your choice and identify one practical next action.