Start with the problem and a measurable outcome
Describe what is happening today and what should change. For a website project, “more leads” is too broad: specify the audience, the action you want visitors to take and how you currently measure it. Record the baseline if available. If you have no measurement yet, include analytics setup in the scope rather than inventing a target.
Define deliverables and boundaries
List what must be delivered, in which languages and formats, and what is explicitly outside the project. A website brief might include five page templates, migration of twenty existing pages, one language and editor training. Ask separately about copywriting, photography, hosting, maintenance and third-party licences. These are often different services with separate costs.
Make responsibilities visible
Name the decision maker and the people who will supply content, approve designs and provide access. Ask the agency who will perform the work and which tasks are subcontracted. Set a review window and identify dependencies. A launch date is only credible if both parties know when content and approvals will be ready.
Copy this starting template
Business and audience: Problem to solve: Current baseline and desired outcome: Required deliverables and exclusions: Languages and markets: Available content and technical systems: Budget range and what it includes: Target dates and dependencies: Decision maker and review process: Acceptance criteria and handover: Questions the agency should answer:
Compare one sample scope
Suppose one proposal includes design only and another includes development, content migration and three months of support. Their totals are not comparable. Put each deliverable on a separate row, ask each agency to mark included, excluded or optional, and record quantity, revision allowance, delivery date and fee. Keep ongoing costs separate from the project fee. Ask about taxes and currency explicitly.
Agree what completion means
Before starting, decide how deliverables will be checked and who accepts them. For a website this can include agreed device testing, working forms, editor access, a redirect list and handover documentation. Clarify ownership, source files, licences and post-launch support in the written agreement. A small paid discovery phase can help define uncertainty before a larger commitment; it is not a substitute for agreed scope.