Web Project Scoping: How We Keep Timelines Sane
A practical framework for scoping web projects — timeline, budget, and deliverables that hold up once the work starts.
Reviewed and updated: 20 October 2026
Define the job of the website
Start with the audience and the action they should be able to take. A project is easier to plan when “a better website” becomes a set of specific journeys: understand an offer, compare services or send a useful enquiry.
Make a page and content inventory
List the pages, languages and content types. Identify what already exists, what needs editing and what must be created. Assign an owner for text, photography, brand files and approvals. Missing content is a project dependency, not a detail to discover at launch.
Describe the interactions
Write down how menus, forms, filters or other controls should behave. Identify any external services and what happens when a dependency is unavailable. Separate a visual demonstration from an integration that must work with live business data.
Agree the review points
Review the structure first, then the visual direction and then working pages. Give consolidated feedback through an agreed contact. Changes become easier to assess when they are tied to a specific stage and a shared brief.
Plan the launch and the work after it
Agree the domain, hosting, access, migration and handover responsibilities. Check important journeys on a phone as well as a desktop. Define who will maintain content and software after launch, and how future changes will be requested.
Keep new requirements visible
A useful scope can evolve. When a new requirement appears, record it and discuss how it affects cost, timing and priorities before implementation. That protects the project from different assumptions on either side.