What to put in the out-of-scope section: exclusion examples by service type

Open a scope of work template and you'll often find a heading like "Exclusions" or "Out of scope", followed by an empty box. The deliverables section has examples. The timeline section has examples. The exclusions section is left for you to fill in, and it's the section that does the most work later, when a client asks for something you didn't plan to do.

This article fills in that box. You'll get worked exclusion lists for four common freelance services, a quick method for finding the exclusions specific to your project, and three before/after rewrites that show how to make exclusions read as a clear description of the project rather than a list of warnings.

Not legal advice. The examples below are for a plain-language scope summary or proposal, which describes the work. A scope summary isn't a contract. Payment terms, ownership, liability and cancellation belong in a contract, ideally one reviewed by a qualified lawyer where you work.

What the out-of-scope section is for

An exclusion is a short line that says "this is not part of this project". It sits next to your deliverables and assumptions, and it describes the edges of the work.

For a freelancer, the section does three practical jobs:

  1. It answers questions the client hasn't asked yet. "Does the website include my email set-up?" is easier to answer in the proposal than in week four.
  2. It gives you something to point to. When a request comes in that's listed as not included, the conversation is "that's on the list, here's a quote", not a debate about what was implied.
  3. It shows the client what they need to arrange elsewhere. If photography isn't included, they know to book a photographer.

What it is not for: protecting yourself legally. "We accept no liability for..." lines don't belong in a scope summary. If you need that kind of wording, it goes in your contract.

How to find the exclusions for your project

Generic lists help, but the exclusions that matter most are the ones next to your actual deliverables. For each deliverable, ask four questions:

Anything that comes up and isn't in your deliverables list is a candidate exclusion. You won't list all of them. Pick the ones a reasonable client in this project might assume are included. If you used the AI hidden-dependency check from the vague-brief article, its findings are a good starting list.

Exclusion examples by service type

These lists are starting points. Delete what doesn't apply, and only keep a line if it's something your client could plausibly expect. Each line starts with "Not included:" and, where it helps, says what you will do or how the client can get it.

Web design

Copywriting

Social media management

Development

A note on the lines about outcomes (search rankings, follower numbers, third-party audits): anything that sounds like a promised result is worth excluding explicitly, because clients sometimes assume it comes with the job.

Making exclusions read as clear, not hostile

Exclusions often go wrong in tone. Lines written in capitals, with "must" and "will not", can make a client feel accused before the project starts. They also tend to be vague, which defeats the point.

To rewrite one, work through three moves:

  1. Lead with the item, not the client. A neutral label like "Not included:" followed by the thing itself. Drop "the client must" and "under no circumstances".
  2. Offer the nearby alternative. If there's something you do provide that's close, name it. The client sees what they get, not just what they don't.
  3. End with the route forward. Tell them how they can get it: a separate quote, a provider who bills them directly, or a later phase.

Here are three before/after rewrites.

1. Social media (replies)

Before: "We do NOT monitor or respond to comments or DMs. The client is solely responsible for all community management."

After: "Not included: replying to comments and messages. I'll flag any that look like they need your reply in the weekly update. Community management can be added as a separate quote."

The after version keeps the boundary and tells the client exactly what they will get.

2. Web design (third-party costs)

Before: "All hosting, domain and plugin costs are the client's responsibility. We are not liable for any third-party plugin failures."

After: "Not included: hosting, domain and paid plugin fees. These are billed to you directly by each provider, and I'll recommend options during setup."

The liability sentence is gone. If you need wording on third-party failures, it belongs in your contract, not here.

3. Copywriting (results)

Before: "Writer makes no guarantees regarding search engine rankings and cannot be held responsible for traffic."

After: "Not included: guaranteed search rankings or traffic. I'll write each post around the keyword you choose and follow the on-page basics listed in the deliverables."

Same boundary, stated as a fact about the project instead of a defence.

Common mistakes

Where exclusions go in the workflow

Write the exclusions after you've asked the client your questions and before you send the quote, so the price matches the boundary. Then put them in the scope summary or proposal the client confirms. When a "just one more thing" request arrives, check it against the list. The out-of-scope request email guide has replies for that moment, and the client onboarding checklist shows where the scope summary fits between the first call and kickoff.

Want the full template?

The Scope Guard & Client Onboarding Kit includes a one- to two-page scope-summary template with a "Not included" section, next to deliverables, client responsibilities, assumptions and revision rounds. It also includes an AI prompt that drafts exclusions from your hidden-dependency audit, with a check step so you review every line before it goes to a client.

It works with any chat AI assistant, plus Google Docs or Word, and Google Sheets or Notion. It isn't a contract and it isn't legal advice.

The kit isn't on sale yet. See what's in the kit

← All posts