What you need
- Project requirements or proposal
- Client input or notes
- Reference templates (optional)
- List of deliverables
Every step
- 1
Clarify Client Goals and Priorities
Meet with the client to confirm their top goals. For example, if designing a website, find out if their priority is increased conversions or brand consistency. Note at least two specific goals the client emphasizes.
CHECKPOINT · List of client goals and priorities confirmed. - 2
List All Deliverables
Create a table outlining each item to be delivered. E.g., 'Homepage design, About page, Contact form, User guide.' Include quantity and format, such as ‘1 PDF user guide.’
CHECKPOINT · Each deliverable clearly described in a list or table. - 3
Define Project Boundaries and Exclusions
Specify what’s out of scope. For example: 'Redesign of the e-commerce store is excluded.' List 2-3 specific tasks or features that are not included to avoid assumptions.
CHECKPOINT · A list of excluded items or functions is present. - 4
Establish Timeline and Milestones
Create a simple schedule with key dates. Example: 'Mockups delivered by Week 2, final website launch by Week 8.' Use a table: Milestone — Date. Make sure both parties agree to these checkpoints.
CHECKPOINT · Timeline and key milestones outlined in table. - 5
Confirm Acceptance Criteria with Client
For each deliverable, define how you and your client will verify completion. For example: 'Website loads within 3 seconds; Contact form submits data without errors.' List 1-2 acceptance criteria per deliverable.
CHECKPOINT · Acceptance criteria for deliverables documented.
Common mistakes
- Assumptions about out-of-scope items cause disputes; be specific.
- Avoid ambiguous language—define terms and deliverables precisely.
- Business names, dates, and numbers in examples are illustrative; replace them with verified project information.
Finished when
Scope document is detailed, reviewed, and agreed upon by you and the client.
Questions about this task
What if the client requests additional features after scope is agreed?
Handle changes through a formal change request process: document the request, assess impacts, and update the scope, timeline, and budget only if both parties agree.
How detailed should exclusions be?
List any tasks or features the client might reasonably expect based on the project's nature but won't receive. Clarity here prevents misunderstandings later.
Make these steps fit your situation.
Ask a question about this task or prepare a draft you can review.
Work through it with meHelp me make it