Module 4a · Illustrated Walkthrough
Pursuit & Contracting — Writing What You’ll Own
The illustrated walkthrough — how to write scope you’re willing to own, using the SAFER discipline, so the margin you priced survives contact with the work.
Module 4a throughline — You protect margin before the work begins by writing scope you’re willing to own: specific, finite, and honest about what’s in and what’s out.In Modules 2 and 3 you learned where the margin lives — the fee, the multiplier, the money you have to protect. So here is the question this module turns on: what single document decides whether that margin survives contact with the work?
The problem
Most margin dies in polite scope
Margin rarely dies in execution. It dies earlier — in scope that was written to sound accommodating. “We will assist… we will coordinate… as needed.” At the time it feels like good client service. Six months later it is unplanned meetings, extra review cycles, and a PM explaining why the hours don’t match the fee.
Picture an Oakhaven proposal line: “We will assist the client as needed with permitting and coordinate with stakeholders to support successful completion.” It reads beautifully. Then the client asks for five extra coordination meetings, permit revisions blow past the two cycles the fee assumed, and the team logs roughly 140 unplanned hours. At Grace’s blended rate that’s about $21,000 of labor nobody priced — margin sliding from 12% to 7%. No one intended it. The language allowed it.
Scope isn’t a description of effort. It’s the boundary of responsibility you commit to deliver — so the real question is whether you’re willing to write that boundary down.
?“We will assist the client as needed.” It sounds collaborative. Is it?
Your window
You can only write scope if you’re in early
Scope is written upstream, where your leverage is highest. Recall the leverage curve: the earlier you engage, the more of the project you can still shape. Get in early and you shape the boundary; arrive late and you’re left defending a boundary you never set. Scope writing is collaborative — you build it with Business Development and the pursuit team — but someone has to own the words. That someone is you.
?You’re pulled into a pursuit two weeks before the proposal is due. Is it worth your time?
The standard
Scope is a promise, not a description
A scope of services is a promise: what we will do, where and how we will do it, and what we will ultimately hand over. Written well, it protects three things at once.
Client value
Expectations are explicit, so success is defined the same way on both sides of the table.
Team value
Direction is defined, so the team builds to a commitment instead of guessing at intent.
Firm value
Margin is defendable, because every hour ties back to something we actually agreed to deliver.
Scope is clear when someone new to the project could read it and know exactly what leaves our hands — and, just as important, what does not.
The discipline
SAFER — five tests every line must survive
SAFER isn’t a template you fill in — it’s a filter you run each meaningful scope element through. Weak scope describes activity; strong scope defines a deliverable, a limit, and an owner.
Clear, objective, factual
Define the deliverable, not the activity. Weak: “assist with permitting.” Strong: “prepare and submit permit documents to the identified AHJ and respond to one consolidated review cycle.”
The key provisions scope is built on
Write the conditions that must hold true. “Client will provide consolidated review comments within five business days of submission.” Unstated assumptions are future write-offs.
All items clear and quantified
If it’s unlimited, it’s uncontrolled. “We will conduct up to two coordination meetings during schematic design.” A third is then a decision, not an assumption.
What we expressly exclude
If you won’t say what’s out, someone else will decide it’s in. “Construction administration services are not included.” Exclusions prevent disappointment; they don’t create it.
Who owns what
Make ownership visible before execution. “Client will coordinate stakeholder access and provide required background documentation.” This is how you avoid “we thought you had that.”
?“We will prepare and submit permit documents.” It’s Specific. Is it SAFER?
The craft
Three red flags, and how a strong sentence is built
Three words cause more scope creep than any technical error: as needed, assist, and support. They’re elastic by design. When you see one, stop and ask, “what does this mean in practice?” If you can’t say plainly, rewrite it. Keep sentences short, one commitment each, and never let a compound sentence smuggle in a second, unpriced promise.
Each SAFER element has a reliable sentence skeleton. Fill the brackets and the ambiguity has nowhere to hide:
“We will [produce] and [submit] [named deliverable] to [identified party].”
“[Client] will provide [input] within [N] business days of [event].”
“We will conduct up to [N] [meetings / cycles] during [phase].”
“[Service] is not included; [work] beyond this is an additional service.”
“[Party] will [coordinate / provide] [item].”
Your turn
Rewrite one line, the SAFER way
Here is a real-sounding Oakhaven line. Read it, decide which SAFER tests it fails, then draft your own rewrite before you reveal ours.
“We will support the design team and coordinate with stakeholders as needed to keep the project moving.”
“We will lead up to three stakeholder coordination meetings during schematic design and issue summaries within two business days. Stakeholder scheduling and access are the Client’s responsibility. Coordination beyond three meetings will be treated as an additional service.”
?Before you look: which SAFER tests does the weak line fail?
Before any line leaves your hands: Is it specific enough that a newcomer knows what we deliver? Are the assumptions written? Is the commitment finite? Have you stated the exclusions? Is responsibility unmistakable? Any “no” is a rewrite.
The payoff
Your words become the contract
The scope you write doesn’t stay in a proposal. Grace’s Contract Team turns it into an executed agreement, and your language sets what the firm is legally on the hook to deliver. That’s why scope discipline and the contracting process are one skill, not two.
Write the floor clearly, and everything downstream gets easier — planning ties to real commitments, change becomes structural instead of emotional, and monitoring stays calm.
The step-by-step contracting workflow — intake, tracks, the six priority provisions, signers — lives in the Contract Process Field Guide.
Module 4a · Pursuit & Contracting
You can write a boundary you’re willing to own — specific, finite, and honest about what’s in and what’s out.
You wrote the floor. Next, you step into a project and find the finish line beyond it.