Start with the client’s decision, not a list of tasks.
A client may ask for more traffic when the real need is more enquiries for one profitable service. Before assigning a content allowance or technical checklist, ask which business decision the work needs to support. The answer changes which pages deserve attention first.
Record the target market, priority offer and the action a useful visitor should take. If the client cannot yet identify these, discovery belongs in the first scope. It should not be an invisible extra.
Put the website boundaries in writing.
One website is not a reliable measure of effort. A small service site and a large store can share a domain count while requiring very different work. Agree the indexable page limit, target market, platform and known constraints.
Separate an audit from implementation. A recommendation to change a template is not the same commitment as editing, testing and releasing that template. Identify who owns development before it becomes an urgent dependency.
Allow for the work before the work.
Access requests, baseline reviews and content discovery consume real delivery capacity. If your first monthly package includes those activities, state which production work remains in that month. This is more useful than promising a full audit and a full production month at the same price without a capacity check.
Agree who can approve briefs and changes. A single consolidated response is easier to plan around than several conflicting rounds from different stakeholders.
Make changes to the brief easy to recognise.
List the allowance for existing pages, new content, implementation hours and reporting. Specify what a content piece includes: word limit, source requirements, review process and revision allowance.
Then name the common exceptions. A new market, a migration, a specialist interview or an additional location should trigger a revised scope. It should not become an argument about the meaning of “SEO included.”
End with an acceptance checklist.
For each deliverable, write down what completion looks like. An audit might require affected examples, priorities and recommended actions. A content piece might require an approved brief, editable draft and source notes.
This is how a delivery partnership becomes easier to manage: the agency can see what was bought, the team can see what is expected, and the client gets a clearer explanation of the work.