BriefLoft field guide
How to write a clear project scope
Define deliverables, boundaries, responsibilities, dependencies, and acceptance so the work is easier to price and approve.
Draft a scoped proposalScope describes observable work
A clear scope tells the client what will be delivered, what decisions and inputs are required, and where the engagement stops. It should be specific enough to estimate and verify without dictating every implementation detail before discovery begins.
Begin with the outcome the work supports, then translate it into concrete deliverables and boundaries.
Cover six scope questions
Use quantities, formats, phases, platforms, or service capacity where they improve clarity. State assumptions explicitly instead of relying on both parties to interpret shorthand the same way.
- What deliverables or services are included?
- What is excluded or handled by someone else?
- Who supplies content, access, approvals, and feedback?
- How many review rounds or service hours are included?
- What dependencies can change timing or price?
- How will completion or acceptance be recognized?
Add a change path
New information does not have to create conflict. Explain how added requests will be estimated, approved, scheduled, and documented. Update the current proposal or statement of work so the client is never choosing between conflicting versions.
Common questions
How detailed should project scope be?
Detailed enough to price, schedule, assign, and recognize completion. Discovery work may define outputs and decision gates instead of unknown implementation details.
Is scope the same as a contract?
No. Scope explains the specific work; a contract addresses the binding legal relationship and should be suitable for your circumstances.