A website timeline is a chain of decisions and dependencies. Design and code can move quickly while content approval, integration access or unclear ownership holds the whole programme back.
Scope changes the shape of time
A focused marketing site can move through discovery, content, design, build and QA more quickly than a migration, ecommerce store or custom platform. Page count is only one variable.
Content is often the critical path
Real copy, images, product data and legal information should be available early enough to influence design and testing. Placeholder content hides layout and governance problems.
Approvals need an owner
Name one person who can resolve conflicting feedback and approve each stage. Long stakeholder chains create idle time and late reversals.
Integrations create external dependencies
APIs, payment providers, CRM systems, analytics, domains and email services may require accounts, contracts or third-party support. Record those lead times before committing to a launch date.
QA and launch need protected time
Responsive, accessibility, browser, content, redirect, form and deployment checks are part of delivery. Removing that time only moves risk into production.
Plan with ranges and gates
Use an indicative range, stage exit criteria and visible dependencies. A date becomes credible when the work, owners and assumptions behind it are clear.