A proposal can be persuasive and still cause trouble later if the scope is vague. “Website content support” can mean five pages or fifty; “revisions as needed” can mean one round or ten. The scope section is where those meanings get pinned down — or not.
Three lists, each specific
- Included: countable deliverables. “Up to 8 help articles of 600–900 words, two review rounds each.”
- Not included: the things a reasonable client might expect but you are not doing. “Translation, design, and uploading to the CMS.”
- Assumptions: what must be true for the plan to work. “Subject experts are available for one 45-minute review per article within three working days.”
We will support the team with documentation and make revisions as needed.
Included: one onboarding guide (up to 20 pages) and five task SOPs, each with two review rounds. Not included: video, translation, and legal review. Assumes: your operations lead approves each draft within three working days.
Assumptions protect both sides
Writing down assumptions is not defensive. It tells the client what they need to provide, and gives both sides a fair basis to revisit timeline or fee if an assumption turns out to be wrong.
Make change visible
Add one sentence on how changes are handled: “New items are estimated separately and added only with written approval.” It turns a future argument into a routine step.
Contract terms, liability and other legal wording belong with a legal professional. A clear scope section complements a contract; it does not replace one.
Examples in this guide are fictional and written for teaching — not client material or measured results.
