In Q1 2026, when we audited the operator hours logged across 18 clients at FORKOFF, the number that surfaced was uncomfortable: 22 percent of total operator hours had gone to work that was never part of the signed engagement. Not rounding errors, not five-minute favors. Full deliverables, Slack threads that turned into strategy sessions, Linear tickets opened at a client's request for things nobody had agreed to build.
The billing was not the problem. The problem was that nobody in the room, on either side, had enough social capital to say "that is not in scope" in real time.
We did not understand that this was a communication-design problem. We had been treating it as a contract problem.
What we thought we had solved
Every engagement at FORKOFF starts with a master services agreement. Ours is specific. It names deliverables, cadences, and what out-of-scope escalation looks like. We had iterated on the language for over a year. By early 2026, we genuinely believed the MSA was doing the alignment work.
In retrospect, the MSA was doing the legal work. Those are not the same thing. A signed PDF is not the same as a shared mental model of where the engagement ends.
What was actually happening was predictable once we named it. Clients would arrive on a Monday kickoff call with full context about their problems, and by the end of week one, the relationship was warm enough that they would start asking. Not bad-faith requests. Genuine needs. "Can you look at why our HubSpot sequence is misfiring?" or "We need someone to review this Linear milestone before the board deck." Reasonable questions in isolation. Collectively, 22 percent of all operator time across 18 retainers over a quarter.
The operators doing the work were not ignoring scope. They were making the more natural choice in the moment: answer the person in front of you. Saying "that is out of scope" requires both parties to have a live, specific shared artifact to point at. Without that artifact, the pushback reads as friction rather than professional clarity.
The memo
We built something deliberately low-tech. A one-page Notion document, delivered to every client on day 7 of the engagement. Not day 1. Day 7.
The memo had two sections and nothing else. The first section listed exactly five things that were explicitly in scope for this engagement: named deliverables, named cadences, named owners on the FORKOFF side. The second section listed exactly five things that were explicitly not in scope, again named, again with a named owner in case they needed to be escalated or added to a future engagement tier.
That was the whole document. No legal language. No hedge clauses. The Notion page took under two hours to draft per client, including the internal review.
Day 7 was intentional. We had tried a version of this as a day-1 document during an earlier internal pilot with three clients and it did not land. On day 1 the relationship has not formed yet. The client reads a "not in scope" list before they trust you and it sounds like you are preemptively protecting yourself. On day 7, after the kickoff has gone well and the first real work has been delivered, the same list reads as "here is what we are going to go deep on together." The posture is completely different. We did not get this right the first time. We got it right by watching what happened in the room when we delivered the document early versus late.
What changed operationally
We tracked the effect across the same 18 clients over 6 weeks after the memos went live. A few things shifted that we had not fully anticipated.
The most immediate change was in Slack. Before the memo, out-of-scope requests typically arrived as direct messages to the operator on the account. After the memo, the same requests arrived with a flag attached: "I know this might be outside what we agreed, but..." That flag matters. It means the client has internalized the frame. The conversation is no longer about whether the work will happen; it is about where it belongs in the engagement structure. Operators stopped having to make a real-time judgment call about how to respond to an unqualified request.
The second change was in Linear. Out-of-scope tickets had historically been opened by clients with no label, no tier designation, and no owner. They sat in the backlog until an operator cleared them or they aged out. After the memo, the rate of unlabeled out-of-scope tickets fell noticeably within the first three weeks. Not because we changed the Linear workflow. Because the clients knew what the labels meant.
By the end of the six-week window, out-of-scope hours had dropped from 22 percent to 4 percent across the same retainer base. We had not changed the MSA. We had not changed pricing. We had not had a single difficult conversation about billing. The scope reduction came entirely from delivering a one-page Notion document at the right moment in the engagement arc.
The three upgrades
Three clients from that cohort upgraded to a larger engagement tier during the six-week window. Each of them had items on their "not in scope" list that they wanted addressed. The memo had named those items specifically, which meant when they were ready to expand, the conversation had a very short path: "We want to add the HubSpot sequence work. Is that the next tier?" Yes. Done.
We tracked this through HubSpot. The upgrade conversion time for those three clients, from the moment they asked about the not-in-scope item to the moment the expanded scope was signed, was under five days on average. We had no equivalent data from before the memos because the process had not existed, but the informality of the prior process would not have supported a five-day close. The memo created a clear surface to transact against.
What this generalizes to
The scope memo is not a consulting template. It is a communication-design intervention for any service relationship where the work is ongoing, the client is smart, and the relationship is warm enough that ambiguity feels safer than clarity.
The five-in, five-out format matters. Not three, not ten. Five forces prioritization on the in-scope list and prevents the not-in-scope list from reading as a wall. The named owner on each item matters. The Notion delivery channel matters more than it looks like it should, because both parties can comment on it, which means the shared artifact can evolve and the evolution is visible to everyone without a meeting.
The day-7 timing is a constraint worth keeping. We tested other windows. Day 7 is the right answer for our engagements. Other teams may find day 5 or day 10 maps better to their onboarding arc. The underlying principle is the same: deliver the document after trust exists, before the first out-of-scope request arrives.
What we got wrong initially was treating this as an internal operations problem. The scope drift was not an ops problem. It was a shared-model problem that only a shared artifact could solve. Once we understood that, building the artifact was straightforward. Deploying it at the right moment in the relationship was the harder skill, and it took a few iterations to get right.
We are still in the same 18 retainers. The memo goes out on day 7 of every new engagement now. The operators who run those accounts spend their time on the work that was agreed on, the clients know what they can push on and what requires a different conversation, and three of them paid more because the frame was clear enough to expand into.
