Template
Project Scope Confirmation Email Template
Updated 2026-08-24
Use this before kickoff, after the project has been agreed in principle. It summarizes the working baseline so you and the client can correct ambiguity before work begins. It is not the out-of-scope response to use after a client asks for something new.
This operational confirmation is not legal advice, a contract, or a substitute for the agreement you actually signed. CREEPLOCK does not send this message; copy it into your own email or client channel.
Friendly
A clear, collaborative default before most project kickoffs.
Subject
Confirming the scope for {{projectName}}
Message
Hi {{clientName}},
Before I begin {{projectName}}, I want to confirm the working boundaries so we're aligned.
Included work: {{includedWork}}
Revision boundary: {{revisionBoundary}}
Not included: {{exclusions}}
What I need from you: {{clientDependencies}}
Working assumptions: {{assumptions}}
If a later request changes these boundaries, I'll flag it before starting, explain any price or timing impact, and ask you to approve it first.
Please reply to confirm this matches your understanding, or point out anything we should clarify before kickoff.
Thanks!Detailed
When several boundaries need to be unmistakable before work begins.
Subject
{{projectName}} — scope confirmation before kickoff
Message
Hi {{clientName}},
Before work begins on {{projectName}}, please confirm the following working baseline:
Included deliverables: {{includedWork}}
Included revisions: {{revisionBoundary}}
Exclusions: {{exclusions}}
Client inputs/dependencies: {{clientDependencies}}
Assumptions: {{assumptions}}
Requests outside this baseline will be assessed separately. If a request affects price or timing, I will document that impact and wait for approval before beginning the additional work.
Please reply with any corrections or confirm that this reflects our shared understanding.Concise
For a simple project or an established client who prefers short messages.
Subject
Quick scope check: {{projectName}}
Message
Hi {{clientName}} — before I start {{projectName}}, can you confirm this baseline?
Included: {{includedWork}}
Revisions: {{revisionBoundary}}
Excluded: {{exclusions}}
Your inputs: {{clientDependencies}}
Assumptions: {{assumptions}}
I'll flag and get approval for any later request that changes price, timing, or these boundaries. Please reply with any corrections or confirm we're aligned.Confirm the baseline, then keep it available
The message creates a written checkpoint; it does not send itself or create a record in CREEPLOCK. After the client confirms, record the project baseline in CREEPLOCK so later requests can be compared with what was agreed.