Module 4a · Illustrated Walkthrough
Pursuit & Contracting: Writing Scope the Team Will Own
The illustrated walkthrough: how a project manager writes scope worth owning, using the SAFER discipline, so the margin priced at the outset survives contact with the work.
Module 4a throughline: A project manager protects margin before the work begins by writing scope worth owning: specific, finite, and honest about what is in and what is out.In Modules 2 and 3 you learned where the margin lives: the fee, the multiplier, the money you have to protect. 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, and it dies quietly, a phrase at a time. “We will assist… we will coordinate… as needed.” At the time it feels like good client service, and six months later it is unplanned meetings, extra review cycles, and a project manager explaining why the hours do not match the fee.
Consider an Oakhaven proposal line: “We will assist the client as needed with permitting and coordinate with stakeholders to support successful completion.” The line commits to no limit. 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 is about $21,000 of labor nobody priced, with margin sliding from 12% to 7% while no one involved ever intended it. The language allowed it.
Scope is the boundary of responsibility the firm commits to deliver, not a description of effort, and the only question left is whether a project manager is willing to write that boundary down.
?“We will assist the client as needed.” It sounds collaborative. Is it?
The window
When can a project manager still shape the scope?
Scope is written upstream, where leverage is highest, and the leverage curve explains why: the earlier a project manager engages, the more of the project remains open to shaping. Engage early and the project manager shapes the boundary, whereas arriving late means defending a boundary someone else set. Scope writing is collaborative, built with Business Development and the pursuit team, and someone still has to own the words. That someone is the project manager.
?You are pulled into a pursuit two weeks before the proposal is due. Is it worth your time?
The standard
What does a scope of services actually promise?
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, that promise protects the client, the team, and the firm at the same time, and written loosely it protects none of them.
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
Commitments are written down, so every hour ties back to something we actually agreed to deliver and margin is defendable.
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
What five tests must every scope line survive?
SAFER is not a template to fill in but a filter to run each meaningful scope element through before the language ever reaches a client, and every element earns its place by surviving all five tests. Weak scope describes activity, whereas strong scope names a deliverable, sets a limit, and assigns 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 a commitment is unlimited, it is 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 the scope will not say what is out, someone else will decide it is in. “Construction administration services are not included.” Exclusions prevent disappointment rather than create it.
Who owns what
Make ownership visible before execution. “Client will coordinate stakeholder access and provide required background documentation.” This is how a team avoids “we thought you had that.”
?“We will prepare and submit permit documents.” It is Specific. Is it SAFER?
The craft
Which words leak scope, and how is a strong sentence built?
Three words cause more scope creep than any technical error: as needed, assist, and support. These words are elastic by design, and elasticity is the whole problem, since a commitment that can stretch will stretch. When one appears, a project manager stops and asks, “what does this mean in practice?” When the answer cannot be stated plainly, the line gets rewritten. Sentences stay short, one commitment each, and no compound sentence smuggles in a second, unpriced promise.
Each SAFER element has a reliable sentence skeleton, and filling the brackets turns a general intention into a commitment a reader can hold the firm to:
“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, and [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, so read it once for meaning, read it again for what it fails to bound, decide which SAFER tests it misses, and 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 a project manager’s hands: Is it specific enough that a newcomer knows what we deliver? Are the assumptions written? Is the commitment finite? Does the line state the exclusions? Is responsibility unmistakable? Any “no” is a rewrite.
The payoff
How does written scope become the contract?
The scope a project manager writes does not stay in a proposal, since Grace’s Contract Team turns it into an executed agreement and that language sets what the firm is legally obligated to deliver. Scope discipline and the contracting process are one skill, not two.
Write the floor clearly and everything downstream gets easier, since planning then ties to real commitments, change becomes structural instead of emotional, and monitoring becomes a routine confirmation of what was already agreed.
The step-by-step contracting workflow, covering intake, tracks, the six priority provisions, and signers, lives in the Contract Process Field Guide.
Module 4a · Pursuit & Contracting
A project manager can write a boundary worth owning: specific, finite, and honest about what is in and what is out.
Module 4a wrote the floor. Module 4b steps into a project and finds the finish line beyond it.