Project exclusions that hold when the client asks anyway.

Your project exclusions are the parts of the job the fee doesn't cover, and the ones that earn their place aren't the parts you were never going to do anyway. Nobody argues about the photography you said you weren't shooting or the hosting you said you weren't buying. The argument comes out of a line that was in the fee and had a size on it, because forty specification sheets is an inclusion and the forty-first is an exclusion, and whether that costs anybody anything depends entirely on whether you wrote a number beside the forty.

What are project exclusions?

An exclusion is a line in your scope stating what the fee doesn't buy, written at the same moment as the line stating what it does. They exist because a client reading a list of deliverables fills the gaps with whatever they'd expect a job like this to include, and those expectations were formed by a different agency on a different project. An exclusion is you answering that quietly, in advance, in writing.

The question that produces a decent exclusion list is one about the client rather than about the work, and it's what they would assume is part of this when it isn't. Asking that honestly gets you most of the way there, and it's also where most exclusion sections stop. Naming the thing is the easy half, and what decides whether the exclusion is worth anything is what happens the day somebody asks for it anyway, which you can only answer if you thought about it in week one.

So an exclusion isn't really a refusal on client work. It's closer to a price list you publish before anybody needs it, and a small number of the entries on that list are the reason certain projects come in on budget while similar ones don't.

What are examples of project exclusions?

The ones you meet on real scopes fall into a few recognizable shapes, and they're worth separating because they behave very differently later on. There's work that belongs to somebody else, where the client's photographer supplies the images, the client's own team opens the firewall and the print vendor handles delivery. There's work you'd happily do that nobody has bought yet, such as a second language edition or a set of social cutdowns. There's work you won't quote at all because you can't see it from here, like an integration with a dealer's ordering system nobody has shown you. And there's the quietest shape of all, a cap sitting on a line you did include: forty specification sheets, twenty brand assets, two revision rounds, two hundred and forty product records.

Most exclusion lists you'll come across are built entirely out of those first two shapes, which is why they read as reassuring and change nothing about how the project goes. There's a real choice sitting underneath them, and it's whether you list what the fee provides and treat everything outside that list as excluded, or list what's excluded and treat everything else as provided. Agencies almost always do the first, sensibly, because a deliverables list is what the client thinks they're buying. What it costs you is that everything then rests on how precisely those included lines are written, and the caps sitting inside them are where the money leaks out.

A client never reads a cap as an exclusion. They read it as you being thorough about the shape of the job, not the size of it.

Which project exclusions actually get argued about?

The caps, nearly every time, because a cap is the only kind of exclusion the client doesn't experience as one. Nobody is surprised when the agency that redesigned the catalog says it isn't shooting the photography. They're very surprised in week six when the forty-first specification sheet turns out to have a price on it, because they read that sentence as a description rather than a limit and moved on.

That gap explains most of the trouble. A client scanning a scope treats the deliverables list as the project and a late exclusions block as standard wording, so any exclusion living far away from the thing it limits gets skimmed on the way past. The ones that hold are attached instead: same paragraph as the included line, same sentence where the grammar allows it, carrying the rate that applies once the cap is passed.

There's a second reason attached exclusions hold, and it has nothing to do with the document. A capped line with a rate beside it hands the client a way to ask for more without feeling like they're pushing their luck, since they can do the arithmetic themselves, decide it's worth it, and send a request that already knows what it costs. A good share of the difficulty in handling scope creep is people avoiding a money conversation, and a published rate means nobody has to open one.

How is an exclusion different from an assumption or a constraint?

An exclusion names work you're not doing, an assumption names a condition that keeps the work you priced the size you priced it, and a constraint names a limit that was already true on the day you quoted. Filing all three under one heading is expensive, because they come apart in three different directions and only one of them is a purchase.

A project assumption is tested when something the client promised arrives in a different shape than the one you costed. Nobody has asked for anything new, the work is the same work, and there's simply more of it than the fee covered, which is a much harder conversation to open without a written number. A project constraint is tested when the client moves a limit they set themselves, usually a date, and the cost is the compression rather than the extra thing.

An exclusion is tested in the most ordinary way imaginable, since somebody simply asks for the excluded item. What happens next is decided by whether you attached a number to it or only a boundary, and that single choice is also what settles the line between in scope and out of scope without anybody having to defend it out loud.

What does an exclusions section look like on a real project?

It looks like rates, mostly, which is not how the section is usually taught. Wrenmoor Lighting Co. makes decorative fixtures and sells them through interior designers and specifiers, and the nine-week job below is a product catalog site plus the specification sheets the specifiers actually download.

Clause 4.5 is the one that looks most like a proper exclusion and it's the least likely to ever be used, because an integration nobody has specified is not a thing a client asks for casually. It's there for honesty and it costs nothing to include.

The three clauses doing the actual work are 4.1, 4.2 and 4.3, and all three are attached to lines that are in the fee. Somebody reading section 2 sees 240 records and 40 sheets, then reads the rate that applies beyond each of them in the same breath. Nothing in those clauses says no to anything, which is why they survive contact with an enthusiastic client.

Who pays when the client asks for an excluded item anyway?

Whoever the document says pays, and at Wrenmoor it was the client, without much drama. In week six the product team decided to keep a discontinued range live for the specifiers who still order from it, which added 38 fixtures to a catalog costed for 240 records and 40 sheets.

All three parts of that were arithmetic. The 38 extra records came to $532 at the $14 in clause 4.2, the 38 extra specification sheets came to $3,230 at the $85 in clause 4.3, and 12 of the fixtures had images that only existed as print-resolution files outside the appendix B specification, which clause 4.1 prices at $60 each for another $720. The change went back the same day at $4,482, taking the engagement to $25,232, and it was approved in writing before any of it started.

Now run the same week with the generic exclusion list, the one that says no photography, no hosting, no ad buying, no copywriting. Every item on that list is still true and not one of them covers a single line of the $4,482, so the agency absorbs six days of work and explains the margin in the closing meeting. A meaningful share of what scope creep costs an agency over a year is made of requests like Wrenmoor's, which nobody on either side recognized as requests at the time.

Where do project exclusions belong in a scope of work?

Beside the line they narrow, and then again in a short section of their own for the ones that attach to nothing. Writing them only in a block at the end is what produces the skim, since by the time a reader reaches section 4 they've already decided what the project is and they're reading for reassurance rather than for terms.

That means a certain amount of deliberate repetition, and it's worth it. The deliverables line reads "240 product records structured from Wrenmoor's data template, further records at $14 each" and clause 4.2 says the same thing again in the exclusions section. Anyone learning how to write a scope of work is usually taught to avoid saying things twice, and this is the one place where saying it twice is cheaper than the alternative. A project scope template with the caps inside the deliverables list reads a little longer and gets argued about a lot less.

The last piece is the route out. An exclusion with a rate still needs somewhere for the request to land, so the scope should name how a change gets asked for and approved, and a change request form attached to the project is enough. Without it the client sends the ask by email, somebody says yes in a reply, and three months later the rate everybody agreed on is the only part of the exchange anybody can find.

The exclusions worth writing sit beside the work, not away from it

Fourteen dollars, eighty-five dollars, sixty dollars. Three small rates, written in week one beside three lines that were already in the fee, and between them they moved $4,482 of week-six work from an argument into an invoice. None of them says no to the client and none of them needed negotiating when the moment came, which is the entire return on the twenty minutes it took to write them down.

After the approval, the thing worth keeping is the record of it. Docket puts the request, the $4,482 and the written yes on one entry attached to the project instead of spreading them across a month of email, so the rate and the agreement to it stay together. That matters most on the changes that felt small at the time, and the ones sitting beside your included lines are exactly those.

Frequently asked questions