Free website scope checklist: 12 decisions before you quote

Turn a page count into a brief you can estimate. Copy this checklist into your own project notes; no email address required.

Use it in a 15-minute discovery call

Write an answer or “not decided” beside each item. An unanswered question is a prompt for discovery, not an assumption you should quietly price as included. This is a scoping worksheet, not a legal agreement.

Outcome: What should the website help visitors do? Name one primary action.
Pages: List each page, its purpose and whether it needs a unique layout. Five URLs may use only two layouts, or need five different ones.
Features: Define the form fields, bookings, search, payments or integrations. Record what each must do and what is excluded.
Content: Who supplies final copy, images and required legal text? In what format, and by which date?
Migration: Is old content being moved? Count pages, files and redirects. Agree who checks the migrated result.
Access: Who owns the domain, hosting and service accounts? Use invitations; do not put passwords in these notes.
Design direction: What existing brand material is available? Which version must be approved before build?
Feedback: Name the person who consolidates feedback, the included rounds and the response deadline.
Checks: Agree the relevant devices, browsers, forms and acceptance checks. Specialist audits need their own defined scope.
Timing: Record input dates, review dates and the process for revising the schedule when dependencies slip.
Costs: Separate your fee from paid fonts, plugins, hosting and renewals. Name who buys and renews each item.
Handover: Define training, account transfer, correction/support period and responsibility for future edits.

Copyable brief

Project / scope version:
Primary visitor action:
Pages and unique layouts:
Features and acceptance checks:
Content owner / ready date:
Migration count / exclusions:
Account owners / access route:
Design approval stage:
Feedback owner / rounds / deadline:
Target dates / dependencies:
Third-party costs / renewals:
Handover / support boundaries:
Unanswered questions:
Next decision / owner / date:

Download the free text worksheet

A fictional example of a useful boundary

“Services page: approved existing layout, final copy supplied by the client, up to six service summaries, one enquiry form using the agreed fields, mobile checks and one consolidated feedback round. A booking integration is excluded.”

The boundary is useful because you can identify when a later request changes it. It does not determine whether any particular contract term is enforceable.

Choose the next step

If major features are still undecided, agree a discovery stage. When the scope is clear enough, estimate discovery, design, build, content entry, communication, revisions, testing and handover using the free quote calculator. Save written client approval separately.

View the £19 project kit See the worked example