Answers

What a scope of work should actually contain

A scope of work should spell out exactly what is being delivered, by whom, on what schedule, and how everyone agrees it is finished. At minimum that means the named deliverables, the milestones and timeline, who owns each task, what you are expected to supply, how revisions and changes get handled, and a clear line around what the engagement does not cover.

That last part matters more than most buyers expect. A scope of work is the document that turns a confident sales promise into something you can actually hold an agency to. The test is simple: if a line cannot be checked off as done or not done, it is marketing language, not scope. When clients ask what should be in a scope of work, the honest answer is anything specific enough to be verified, and nothing that is only there to sound impressive.

Name the deliverables, not the activity

Vague scopes describe effort. Strong scopes describe output. Ongoing SEO is effort. Four optimized service pages published and indexed, with titles, meta descriptions, internal links, and schema markup, is output. You want that kind of line throughout, because effort is impossible to dispute while a concrete deliverable is impossible to fake. If an agency resists naming concrete deliverables, that reluctance is itself information.

• The exact assets being produced, counted where it makes sense: pages, articles, ad sets, creatives, reports.
• The platforms and properties involved, so there is no confusion about whether work touches your site, your ad account, or both.
• The standard each deliverable is held to, such as whether a page counts as done at draft, at publish, or only once it is live and crawlable.

Pin the timeline, the milestones, and the owners

A deliverable with no date is a wish. The scope should map each major item to a milestone and a realistic schedule, even when some of the work is continuous rather than one time. Just as important, it should say who is responsible for each part, including the things that depend on you. Most engagements stall not because the agency went quiet but because an approval, a login, or a piece of content was sitting on the client side for weeks. Writing the owner next to each task settles that argument before it starts.

• A milestone or cadence for each deliverable, written as a realistic window rather than a single immovable date.
• The named owner of every task, split clearly between the agency side and yours.
• The dependencies that block progress if they slip, so both sides can see the critical path.

Spell out your inputs and what sits out of scope

Every engagement needs things only you can provide: brand assets, access to accounts, decisions, sign offs, sometimes photography or product information. A good scope lists these as explicit client responsibilities so the timeline is honest about what it assumes. Then it draws the boundary. The out of scope section is not there to limit you. It is there so that when a new request comes up mid project, both sides already know whether it is included or a separate conversation.

Boundaries protect the buyer as much as the agency. Without them, creep runs in both directions: the agency quietly narrows what it delivers, or the client quietly expands what they expect, and the relationship sours over work nobody agreed to. A written boundary keeps the goodwill intact because nobody is left guessing.

Say how changes and reporting work

Projects change. The scope should say what happens when they do, rather than leaving it to a tense email later. That means a defined revision process, a path to request work beyond the original scope, and a stated cadence for reporting so you are not chasing an update. You do not need heavy process. You need enough that a change of direction is a known procedure instead of a fight.

• How many rounds of revision a deliverable includes before it is considered accepted.
• The path for requesting new work, and how that affects the timeline and the agreement.
• The reporting rhythm and what each report will actually contain, so you can judge progress against the deliverables.

What a scope of work is not

A scope of work defines what the agency will do and what you receive. It should promise the pages, campaigns, reports and standard of work in specific terms. A separate conditional search offer can also set agreed searches, a measurement city, a start date and a fee remedy if the threshold is missed. No agency controls Google's results, an ad auction or your revenue, so read the measurement and remedy clauses closely. A bare promise of a fixed position or lead count is a warning sign.

At Ninetyfifth Marketing, the scope of work is tied directly to the site we build, because we perform SEO and AI search optimization only on sites we build. That removes a common source of scope disputes, where one firm writes the plan and another owns the website that has to change for the plan to happen. How the engagement and its initial term are structured is covered on the /services/seo/ page, and the commercial side lives on /pricing/. The scope builds on that, translating the engagement into the specific list of things that will actually get done.