You sign a statement of work once. After week two it sits closed, on both sides. The engagement keeps moving anyway, one helpful sentence at a time, and the document stays where it was. Keeping the two in step is a mailbox job. Every change to an engagement arrives in your mail.
- A scope change arrives looking like the work. It’s one line halfway down a message about something else, usually a question, usually from somebody who has never read the document.
- Each one is small enough to say yes to. The cost is the sum. The sum shows up in the last two weeks, and by then raising it sounds like a complaint.
- The client remembers the last conversation rather than the document. That’s why an argument from a dated email lands and an argument from the contract stings.
- The move that protects the relationship is a price. Say what the change costs, the same day, and hand the decision back to them.
A scope change never arrives labeled
Almost everything else in an engagement tells you what it is on arrival. An invoice query looks like an invoice query. A meeting request looks like a meeting request. Somebody chasing a document is plainly doing that. You can sort a morning on those signals at a glance.
A change to the agreed work is the exception. It looks exactly like the work.
It comes as one sentence inside a message you have to answer anyway. The rest of that message is a real delivery question, and you already know the answer. So you reply to the part you can see, quickly and helpfully. The sentence that mattered goes by unremarked. The thread is closed in your head now, and closed in theirs too, with an unanswered expectation sitting inside it.
From where the client sits, this is a clarification, so it arrives phrased as one. They think they’re being helpful, or mentioning something obvious. In their reading, the agreed work already covers it. So the ask sits there unnamed, and declining an ask that neither of you has named is a strange move to make.
And it usually comes from somebody who has only ever seen the work itself. Your day to day contact, a workstream lead, an analyst who joined in week three. The commercial conversation happened above them. They’ve never seen a deliverables list, and for several of them the fee is news. That one fact changes the reply more than anything else in this guide. You’re telling somebody something they didn’t have. That’s a far easier message to write, and a far easier one to receive.
There’s a timing pattern too. The first two weeks run quiet. The document is fresh and everybody is still behaving like the document. The changes start once you’ve been useful. Scope pressure on an engagement runs roughly in proportion to how well it’s going. Being asked for more is a compliment with a price attached. Say the price, and the compliment is all it is.
One boundary is worth the ink, because these two cases look alike in an inbox and need opposite handling. A sentence describing a whole separate piece of work is not a scope change. It’s new business arriving in a delivery thread, and this collection has a piece on proposal requests that takes it apart properly. This guide is about the narrower and far more common thing. It’s the sentence that expands the job you’re already doing, inside the fee you’ve already quoted.
The document nobody opens after week one
You keep two records of what you agreed to do, and they behave very differently.
One is the statement of work. It’s a single file, dated, complete, signed and closed. It has sat exactly as it is since the day of signature. After about week two, everybody on both sides stops reading it.
The other is the working record: four hundred messages, a dozen calls, three shared documents, and whatever anybody remembers. It’s live, it’s scattered, and it runs the engagement. When somebody asks eleven months from now what you undertook to do, you’ll build the honest answer out of the second record. That works if you kept it in a form you can produce. The general case, that an independent’s engagement file is the mailbox, is made in this collection’s opening piece.
The trouble sits between those two records, and it has a specific shape. The client’s understanding of the scope is the most recent thing anybody said. So when you reach for the contract in month four, you’re setting a piece of paper they last read in March against what they remember. In a working relationship that costs more than the money you were arguing about. Catching up on a long email chain is a real skill in this trade for exactly that reason. The chain is where the agreement lives.
The other direction deserves the same honesty, because most writing on this subject casts the client as the aggressor and the truth is usually milder. A fair share of scope drift is volunteered. On a call in week three you say you’ll also take a look at the second site. You’re being generous, you can see it matters, and saying yes is pleasant. You added it yourself. Two months later it’s part of what everybody expects, and the whole record of it is a sentence you said out loud on a call.
Which is the argument for treating the record as something you write rather than something you have. What the document agreed is fixed at signature. What’s agreed now is whatever the last dated email says. Write those, and you’re the one who gets to be right later.
The clauses that do the work in a mailbox
What a statement of work should contain is a drafting question. Where liability or real money is involved, it belongs with your own adviser rather than a guide about email. What follows is the smaller question of which parts you’ll actually reach for during an engagement. After nine months of delivery there are four, and the rest of the document stays shut.
The deliverables, named as objects with a form. One written report of up to twenty five pages. One working session with the steering group. One model handed over with a note on how it’s maintained. That’s the level to write at, rather than a review of the operating model. The form is the thing that gets changed quietly. A deck becoming a board paper is the same content and two extra days, and it’s a short conversation when the document said deck.
The exclusions. This paragraph does more work than the rest of the file put together, and it’s the one most often missing. The reason is mechanical. When a thing is simply absent from your list of deliverables, saying so is an argument from silence, and the other person is entitled to say they assumed it was covered. When there’s a line saying data migration is not included, you’re reading rather than arguing. Two or three sentences is enough. Write them by looking back at the last three engagements and listing what surprised you, because it’ll surprise you again.
The assumptions, which are really the client’s obligations with dates on them. Most consulting overruns come from the client being late: the workshop moved twice, the data arrived in a form nobody could use, the person you needed for two hours was unavailable for six weeks. That’s a different thing from a scope change, and it costs the same as one. Write it down in advance as named conditions, with dates, and you have something you can point at in a friendly sentence. Leave it unwritten and you have a grievance, and grievances get argued rather than paid.
The change mechanism, written so a human being will actually use it. Almost every statement of work says changes must be agreed in writing by both parties, which is fine and useless. Give a half day the same ceremony as a new phase, and the half day goes unrecorded. Say what a small change needs, which is a confirming email. Say what a large one needs, which is a short amendment. Then use the one you wrote.
Underneath all four is how you’re paid, because that decides what a change even is. On a day rate, an addition extends the bill and the client watches it happen. On a fixed fee it comes entirely out of you, and stays invisible to them. So a fixed fee needs the exclusions working much harder and the change notes going out for smaller amounts. Those notes are the one moment the cost of anything becomes visible.
The sentences worth stopping on
In practice you’re scanning for a handful of phrasings, and they’re all mild. A scope change sounds exactly like a pleasant working message.
The ordinary ones are requests wearing an apology. While you are in there, could you also. It would be good to see the same thing for the other region. The board have asked whether we can add. Just a quick look at. One more thing, and then. Each of these is a person being reasonable. Each one is the beginning of a decision somebody has to make.
The expensive one arrives as a statement: we assumed that included the second site. Read at speed it sounds like background, and it slides past. It’s a report on an understanding the two of you turn out to hold differently. Answer it the day it appears, because an assumption left standing becomes the agreement. Today is as easy as correcting it ever gets.
Then there are the ones that arrive silently, which are harder and cost more.
A new name appears on the thread, and a senior one. A new stakeholder means new questions, a session to bring them up to speed, and often a round of revisions to something already finished.
The deliverable changes form. Could it come as a paper rather than a presentation. Could we have the model as well as the findings.
An activity multiplies. The workshop was one site in the document and is now three. Same word, three times the work.
The end date moves out while the fee stays. A three month engagement delivered across five is a different engagement from the one you priced. Every deliverable can stay exactly as written and you still carried two extra months of calls, context switching and staying available.
And the one that resets everything: your sponsor leaves. The statement of work survives a reorganization, and the agreement behind it starts again from zero. The new person signed nothing, inherited a cost line somebody else chose, and will reopen whichever parts of it suit them. Get twenty minutes with them inside the first two weeks. Say the scope back in plain words. Send a short note afterwards recording what you both now think the job is. Their reply is your new baseline, and it’s worth more than the document they never read.
Catching these is a habit rather than a rule, and the habit is one question asked of the week. When you sit down to write the client update, look back at what you actually did. Ask whether any of it sits outside the document. It’s a different question from the one you ask in the moment, and it’s the one that catches a change which arrived as three small sentences in three separate threads. Every conversation already carries a plain account of itself in one line, so you can put that question to a whole week’s mail and leave the threads closed. The client update itself is a craft of its own, and it has a guide elsewhere in this collection.
Price it rather than refuse it
Scope goes unmanaged because most people can see two moves, and both are bad.
You can say yes, absorb it, and pay for it out of your own margin and your own evenings. Or you can say no, which in practice means invoking the contract. The moment you do that, you stop being the adviser they hired and become a supplier managing a variation. Faced with those two, almost everybody picks the first, every time, until the engagement is unrecognizable.
There’s a third move, and it’s the whole of this subject. Price it and hand the decision back.
It works because it reads as advice. Somebody asked what it would take to add something, and you’re telling them, which is precisely the service they engaged you for on every other question. You’ve given a client a costed option and asked them to choose. Clients do that all week.
The note itself has four parts, and it’s shorter than people expect.
Name what they asked for, in their words, and treat it as reasonable, because it usually is. Say what it would take, in the unit that matters. That’s days, and often elapsed time too, because a client will frequently care more about the end date than the fee. Offer shapes rather than a single price: this instead of something already in the plan, this in addition to it, or this after the current piece finishes. Then ask for a yes in writing, and say plainly that the existing plan continues until you have one.
The option consultants forget is the first one. Instead of. A client’s budget is usually fixed and their priorities usually move, so show them the trade rather than the bill. A surprising number will drop something they’d stopped caring about in order to get the thing they now want. Offering the swap is what opens that conversation.
Four things are worth leaving out. The phrase scope creep, which describes your problem rather than their question. Any version of as per the statement of work. Anything implying they did something wrong. And the document itself as an attachment, which changes the temperature of a whole engagement for the sake of a paragraph nobody will read.
Timing matters more than wording. Send it before you do the work. Once the thing is delivered, the conversation turns into a query about an invoice, and you’ll lose that one, reasonably enough. Same day where you can, while the request is still live in the client’s head and still feels like a question.
Behind all of this sits a rule you set in advance: what you absorb quietly. Under half a day I simply do it, over half a day it gets a note, or whatever threshold fits your rate. Three things make it worth having, and every one of them is about something other than money. It makes you consistent, and consistency is what a client reads as fairness. It settles the question before the call, so you decide the threshold once rather than in a generous moment when you’ve yet to learn what the thing costs. And it keeps the small favors genuinely free, which is what buys the goodwill that gets the priced ones agreed. Charge for everything and you’re tedious to work with. Charge for nothing and the engagement eats you. Setting the threshold is also far easier in a busy month than a quiet one.
One refinement is worth the trouble: when you absorb something, say so. A free half day the client never hears about buys you nothing. I’ve picked this up, it’s about half a day, and I’m not charging for it, in exactly that flat a tone, reads as straightforward rather than petty. It’s the only way generosity gets recorded, and it sets the frame you’ll need three weeks later when something bigger has to be priced.
What happens when the note goes out and the thread stays quiet is a subject of its own, and this collection takes chasing an approval separately.
Writing it down so it holds a year later
Your engagement is the statement of work plus every dated confirmation you sent afterwards. Disputes, when they come, are settled almost entirely out of the second half. Knowing that early turns the confirmations into something you write deliberately.
Four things make them hold.
Confirm inside the thread the change arrived in, rather than opening a fresh message with a tidy subject line. A year and a half later the question is what happened with the second site, and the answer is easiest to find sitting next to the conversation that caused it. Changes agreed on a call are the exception and need writing into a thread of their own, and the general craft of turning what was said in a meeting into something written is a separate guide in this collection.
Use the words somebody will search for. The deliverable’s name, the date, the number of days, the person who agreed it. Those beat as discussed, the above, and the additional piece we spoke about. A confirming email becomes a record on the day somebody can find it.
Make each note cumulative, which is the single most useful habit here. Say what this change costs, and then say where it leaves the engagement. This is the third addition, and with the two from April we are now six days beyond the twenty in the original document. That sentence does more for a relationship than anything else in this guide. It turns a nasty surprise at the end into a series of small facts the client watched accumulate. Clients very rarely fall out with a consultant over the size of an overrun. They fall out over discovering it.
Keep the document and its amendments together as one findable set. Three amendments living in three separate threads leave everybody guessing which one is current on the day it matters. One place, one naming convention, and a version number once there’s more than one.
Keep the ones you absorbed as well. At renewal the only honest basis for a price is what the engagement actually cost you to run, and your invoices hold a different number. The wider argument for keeping rather than clearing belongs to this collection’s opening piece, and what to do about the hours you gave away is picked up in its guide on billable time.
The changes that make the job smaller
Scope moves in both directions, and consultants document one of them.
A workstream gets dropped. Phase two slides into next year. The second site comes off because somebody else is doing it now. This goes unwritten, because there’s no fee conversation attached and everything feels safe.
Two things are at risk. On a fixed fee, a deliverable coming out of the plan leaves the price where it is, and saying so on the day is what keeps it there. Leave it, and the conversation happens at the invoice, when your position is weakest and the client has had two months to assume the saving. A short note is enough: this is coming out, here is what it does or does not do to the fee, here is what happens to the end date.
The other risk is your calendar. On a day rate, a cut is billable time disappearing. Learned in week two it’s a scheduling problem, and this collection has a piece on what to do with the gap between engagements. Noticed in week six it’s an empty month, because the pipeline work that would have filled it was needed back in week two.
There’s a third thing to read in it. Work that shrinks is quite often the first visible sign of something else: budget pressure, a sponsor whose attention has moved, or a reorganization still working its way toward you. A cut that arrives with a thin explanation is worth a phone call rather than a note. That call is usually about renewal, whether or not either of you says so.
When it is no longer the same engagement
Sometimes the job has become a different job. Amending a document that stopped describing it is a way of putting off a conversation you’d be better off having.
The tells are readable. The deliverable named in the original document answers a question everybody has moved on from. More than half of what remains to be done was invented after signature. You’re on your fourth amendment, and stating the current scope takes you a paragraph. The people in the working sessions arrived after the work was scoped. Or the simplest one: you’re doing a kind of work you’d have priced differently had anybody asked for it at the start.
A fresh statement of work beats a fifth amendment for a plain reason. An amendment chain past about three is unreadable, and on the day somebody checks, unreadable and absent amount to the same thing. A re-scope is a legitimate commercial moment. It resets the fee, and more usefully it resets the end date, which by that stage is often the thing hurting you most.
Raise it as an observation, because that’s what it is and the drift was usually mutual. The work we’re doing now isn’t the work described in the March document, which is fine and as much my doing as yours, but I’d rather put a fresh one in front of you so we’re both looking at the same thing. Then the substance: what is finished, what is left, what it costs, what date it lands. Most clients take this well. Most of them know the engagement has moved and have been wondering how to say so.
And occasionally the honest conclusion is that the engagement should finish. Work that has drifted into a job you’d have turned down is a job to complete cleanly, invoice properly, and leave at that. Knowing that in month four rather than month nine is most of the benefit of ever having looked.
The part a tool can hold
All the judgment in this guide stays with you. Deciding whether something is in scope, what it’s worth, and whether this is the week to charge for it, is the actual work. What software can take is the noticing and the keeping, and that’s where this particular subject is usually lost.
Start with the noticing. The thing that slips is a single sentence three paragraphs down a message about something else, read at speed on a Tuesday when a workshop is that afternoon. Point weighs your mail before you get to it, on two questions kept apart: how much a thing matters, and how fast it needs you. So a delivery thread carrying a client’s assumption is ranked on its own merits, rather than by whichever message shouted loudest this morning. How that weighing works is a subject in itself, and why the two measurements stay separate is worth reading if you’ve only ever had one. Each conversation also arrives with a summary in a line, and that’s what makes the weekly question of this guide cheap enough to actually ask.
Be clear about the limit. Your statement of work lives outside Point, in a file Point has never opened, and your fee lives outside Point too. Calling a sentence a scope change takes both of those, so that call stays yours. What Point does is make sure the message carrying that sentence is one you read properly.
Then the keeping. An ask buried in a client’s paragraph becomes a dated item of its own with the conversation still attached, made for you out of the message itself. The change note you’re waiting on is held as a debt owed to you, and it comes back on the date you chose rather than whichever morning it occurs to you. That matters, because a question nobody has answered starts reading as settled after about four days. You can also leave a standing instruction in ordinary words, so the confirmation you need from one particular person reaches you once, on the morning it lands. Setting a watch is what that looks like in a normal week.
Drafting changes behavior most. Change notes go unsent for one reason, and it’s rarely disagreement about whether to send one. Composing a graceful message about money on a busy afternoon is unappealing, so it waits, and by the time it’s written the work is done and the moment has gone. A reply that arrives already written in your own way of putting things turns that into an edit. An edit gets sent today.
For the archive, search works off a description, which is the form the question always takes. You remember that somebody said something about the second site being separate, and that memory is enough to find it. Attachments come out of the threads they were buried in and collect in a single list, each one still tied back to the message it rode in on. That’s the one arrangement where a statement of work and its amendments stay together. Put a question to one of those files and the answer comes back with the part of the document it was taken from. That’s a reasonable way to check whether an exclusion is genuinely in there before you write a sentence to a client claiming it is.
How far Point finishes a thing without you is a separate setting for each type of action. All of them ship in the position where a piece of work gets readied and then stops, waiting on you. The dial is the proper account of it. Acknowledging a client’s message is a fair candidate for raising once you’ve watched it enough times. A note telling a client that what they asked for costs four days is a different matter, and that one stays at review. Everything done for you lands in a log, in order, each entry stamped with the time. Most of it can be taken back from there. The exception is a sent message. Once it has reached the far end it has arrived, and that’s as true in Point as in any mail software.
All of this happens where your mail already is. Point runs over the mailbox you already have, whether that’s Google or Microsoft 365, and the address at the bottom of your statement of work stays exactly as it is.
Point is a mail tool rather than a contract system. Your scope, your rates, your budget and your burn against a plan all live elsewhere, and so does the judgment about whether a half day gets absorbed or invoiced. Ask how many days you’ve spent against how many you sold, and that’s a time and billing question for a time and billing tool. Ask whether anything said to you this week quietly changed the job, and that’s the other half, and it lives in the mail. Whether an AI tool belongs anywhere near a mailbox holding other companies’ plans and material covered by agreements you’ve signed is a prior question, and it’s answered at length rather than assumed. The benefits page lists what Point does, Point for consultants walks the same ground through a working practice, and the product entire sits on one page.
Common questions
Is an email enough for a scope change, or does it need a formal change order?
Your own statement of work names the mechanism, and that’s the clause that governs it. Where real money or liability is involved, the question belongs with your adviser rather than a guide about mailboxes. What’s generally true is that ceremony out of proportion to the change is why changes go unrecorded. A signed variation for a half day feels absurd, so the half day gets recorded nowhere at all, which is the worst of the options available. A dated email naming the change, saying what it costs, and getting a plain yes back is far stronger than a recollection. For small changes it’s usually what the document itself asks for. Keep the heavier mechanism for the ones that move the fee or the end date.
The client says the work was always included. What do I do?
Answer it within a day, before the belief hardens, and answer it as though they’re acting in good faith, because they almost always are. Two people can read the same deliverables list and honestly reach different conclusions, especially when one of them read it once in March. Go to the document first, on your own, and stay genuinely open to finding that they’re right, since about a third of the time they will be. Where the document is on your side, the reply that works quotes rather than argues: here’s the line, here’s what it covers, here’s what we’re talking about now, and here’s what that would take. If the wording is ambiguous, the fair reading is usually the client’s, and the cheaper move is to do it once and write the exclusion into your next engagement.
Should I charge for small extras or absorb them?
Both, on a rule set in advance rather than a decision made while a client is on the phone. Pick a threshold that fits your rate, something like half a day. Absorb everything under it quietly, and price everything over it the same day it’s asked for. Consistency is what a client experiences as fairness. A rule also spares you the worst version of this, which is the consultant who absorbs eight things in silence and raises the ninth with an edge in their voice. Say so when you absorb something, in a flat sentence that keeps the favor out of it, because generosity counts at renewal only once it’s on the record.
The person asking did not sign the statement of work. Does that matter?
Send the note either way. What it changes is who the note reaches. Answer the person who asked, in the thread they asked in, because they were being helpful and deserve a straight answer about what it would take. If the change costs anything worth counting, make sure the note also reaches whoever holds the budget. Copy them into the reply rather than writing separately, which turns a routine costing into an escalation. If your sponsor has changed since signature, the work worth doing is twenty minutes with the new person, restating the scope in plain words, and an email afterwards recording what you both now think the engagement is.
How do I raise scope without damaging the relationship?
By raising it early, in small amounts, and as a costed option. Almost all the damage in this subject comes from the timing rather than the fact. A client told on the day what something costs is being advised. A client told in month five about six accumulated additions is being handed a bill they had no chance to decline. Carry a running total in every note, so the drift stays visible while it’s still small. Use plain commercial words, offer the option of dropping something else instead, and let them choose. If you find yourself needing courage to send the message, that’s usually a sign it should have gone out three weeks ago.
The short version
A scope change looks exactly like the work. It’s a mild sentence inside a message about something else, from somebody who has never read the document, and every single instance is small enough to absorb. The document stops being read after week two, so the engagement runs on the last thing anybody said. That makes the record you can produce later the one you wrote in the moment. Get the exclusions and the assumptions right at the start, because those are the clauses you’ll quote from. Then handle each change the same way. Name it. Say what it would take. Offer it instead of something as well as in addition to it. Ask for a yes in writing before you do the work. Set your free allowance in advance so you’re consistent, and say out loud when you absorb something. Carry a running total in every note, because clients forgive overruns and remember the discovery. Document the cuts as carefully as the additions. And once saying the scope takes you more than a sentence, stop amending and write a new document, because by then the job has changed and the conversation costs less than pretending. Every stage either side of this one, from the first inquiry through to renewal, has its own guide here, and the piece this collection opens with makes the argument across a whole practice rather than one engagement.