Module 4a · Quick Reference
The Scoping Playbook
Reference cards for writing scope the team will own: SAFER, red flags, and sentence patterns.
Module 4a throughline: Protect margin before the work begins by writing scope the team is willing to own: specific, finite, and honest about what is in and what is out.The discipline
SAFER: five tests every line must survive
Run every meaningful scope element through five tests. Strong scope names a deliverable, a limit, and an owner.
Clear, objective, factual
Define the deliverable, not the activity. “Prepare and submit permit documents to the AHJ and respond to one consolidated review cycle.”
The provisions scope is built on
Write the conditions that must hold true. “Client will provide consolidated review comments within five business days.”
All items clear and quantified
If it is unlimited, it is uncontrolled. “Up to two coordination meetings during schematic design.”
What we expressly exclude
Say what is out before a client assumes it is in. “Construction administration services are not included.”
Who owns what
Make ownership visible before execution. “Client will coordinate stakeholder access and provide required documentation.”
Hunt these
Three words that leak margin
These three words cause more scope creep than any technical error. See one, stop, and ask: “what does this mean in practice?” If the answer cannot be stated plainly, rewrite the line.
“as needed”
Never defines a limit. Demand sets the limit instead.
“assist”
Never defines intensity. One email or forty hours both qualify.
“support”
Never defines completion. No line marks the point where the work is done.
Fill the brackets
A sentence skeleton for each element
“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].”
See the difference
One line, rewritten SAFER
“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 it goes out
The five-question test
Is it specific enough that a newcomer would know 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 full teaching walkthrough is in the 4a Module Overview. The contracting workflow is in the Contract Process Field Guide.
Module 4a · Pursuit & Contracting
Write a boundary the team is willing to own: specific, finite, and honest about what is in and what is out.