How to Write Scope Exclusions in a Client Proposal

Put scope exclusions beside the deliverables they qualify. A client deciding between two proposals should be able to see what is included, where the boundary falls, and how to request more work.

Pair each exclusion with a deliverable

• Research: Includes six stakeholder interviews and a findings memo. Excludes customer recruiting, incentives, and survey fieldwork.
• Design: Includes one landing page design and two consolidated review rounds. Excludes development, hosting, and additional page designs.
• Launch: Includes a handoff session and implementation notes. Excludes ongoing reporting and campaign management.

These fictional examples define the boundary with a count, an output, or an owner. A phrase like “anything outside scope” leaves the reader to guess.

Copyable scope block

Included: [output, quantity, and review rounds]. Client provides: [inputs and due date]. Excluded: [adjacent work and outside costs]. If [dependency slips], we’ll confirm the effect on timing before proceeding. Requests beyond the included work receive a written estimate of scope, fee, and schedule for approval.

Handle a request that crosses the boundary

Quote the relevant line, ask what outcome the client needs, and describe the smallest viable addition. Send the revised deliverables, fee, and timeline together. Record which version both sides approved before assigning the extra work.