Name the deliverable and its boundary
“A new website” leaves several interpretations open. A baseline becomes more useful when it names the pages or templates, the expected functionality and the handoff. Refer to the signed scope where it exists; the workspace record should reflect it.
- List the deliverables and quantities.
- Describe the included review process.
- Name the agreed handoff.
Make client responsibilities visible
A delivery date may depend on copy, images, access or consolidated feedback. State who provides each item and how a delay will be discussed. Avoid turning an assumption about client readiness into an unspoken promise from your team.
Write exclusions as useful boundaries
An exclusion should clarify a likely question. For a small website, that might be new pages beyond the listed set, ongoing hosting, copywriting or post-launch support. Use the actual agreement rather than adding a generic block of exclusions the client has never seen.
Keep the baseline stable
When new work arrives, record it as a separate change. Rewriting the original description to include every addition makes it harder to see what happened. Export a brief for the project folder and keep the formal contract in its normal place.
A working checklist
Check items as you work. Your ticks stay on this page and reset when you leave.