What Are the Stages of a Website Design Project?

By Dave TanguayPublished Updated Editorial draft

Quick Answer

A website project usually moves through requirements, content and structure, design, development, testing and launch. The stages can overlap, but each needs a clear output and a decision before dependent work moves forward. Agree who supplies content, who approves changes and what must pass before launch.

Knowing the next deliverable makes a website project easier to manage. A color preference, a missing service description and a broken booking connection are different kinds of work. Each belongs in the project plan with an owner and a way to check the result.

The sequence below is a practical planning model. The exact scope and review points should be agreed for the project rather than treated as a fixed package or timeline.

1. Define requirements and constraints

Start with the business, intended visitors and the tasks the website must support. Record the existing site’s useful content and known problems, required integrations, ownership, budget constraints and timing.

The output should be an agreed brief and scope: which pages and functions are included, what depends on another service, and what still needs investigation. Questions left open should be visible rather than buried in assumptions.

Before moving on, confirm the main visitor tasks and who can approve decisions. The business website planning guide provides a brief you can prepare for that discussion.

2. Plan content and page structure

List the pages and decide how visitors will find them. Identify the purpose, main question and next step for each page. Inventory text, photographs, downloads and existing URLs before choosing what to keep or replace.

The output may include a sitemap, page outlines and a content responsibility list. Agree who writes or supplies each item and when it is needed. Real content can reveal space, navigation and functionality requirements that placeholder text conceals.

For a redesign, decide which established URLs remain and which need a documented change. Google’s site-move guidance explains URL mapping and related checks when addresses change. A visual redesign does not automatically require new URLs.

3. Design and review the important experiences

Use the level of design detail needed to answer the current questions. A wireframe can explore content order and navigation. A more detailed mockup or prototype can explore appearance and interactions. These are different deliverables, so clarify what the review is expected to establish.

The GOV.UK Service Manual’s guidance on prototypes explains their value for exploring and testing approaches before committing to production implementation. The same principle can inform a business website without adopting the government’s entire delivery process.

Review representative mobile layouts, content priorities and important states. Feedback is more actionable when it names the task or problem: a service is hard to find, instructions are unclear or an action is easy to miss. Record the approved direction and remaining questions before dependent development continues.

4. Build the agreed website

Development turns the approved content and design into an editable, functioning website. Work can include templates, responsive styles, forms, platform configuration and connections to other services.

The output should be a working version in an appropriate review environment. Check representative content and real interactions, not only an empty template. Record which functions are connected, which use a test configuration and which still await access or approval.

Design and development may reveal details that need another decision. Use a change record to explain the effect on scope, cost or timing before adding substantial work. A different button label and a new booking integration should not be treated as equivalent requests.

5. Test and decide whether the site is ready

Define acceptance around the requirements. Complete inquiry, booking or purchase tasks, check the resulting information, and review important pages on relevant devices and browsers. Include content accuracy, links, accessibility, performance and measurement.

W3C recommends evaluating accessibility early and throughout development. The final review should confirm the relevant work, while earlier checks help find problems before they are repeated across the site.

The output is a test record with resolved findings and any accepted limitations. The person approving launch should know what passed, what remains open and whether an unresolved issue affects an essential task.

6. Launch, verify and hand over responsibilities

A launch plan should identify the changes, timing, recovery option and responsibilities. Where applicable, include domain and email dependencies, redirects, search settings and connected services.

Verify the actual public site after the change. Repeat the important tasks and check that the intended production configuration is active. A successful save in the review environment does not confirm the public result.

Handoff should cover the agreed account access, editing instructions, license ownership, support route and ongoing work. The website maintenance guide explains how to record recurring responsibilities.

Keep decisions and dependencies visible

For each stage, keep the deliverable, owner, review date, decision and next dependency together. A short decision record can prevent the same issue from being reopened without context.

When timing changes, identify the cause: missing content, access, an unresolved requirement or additional work. Update the plan around those facts. The designer-versus-developer guide helps clarify responsibilities, and the website cost guide explains why different scopes produce different estimates.

Key Takeaways

  • Give each stage a concrete deliverable and an approval decision.
  • Plan real content and established URLs before dependent design work.
  • Use prototypes to answer design questions before production implementation.
  • Test the requirements throughout the project and verify the public result after launch.
  • Hand over account access and ongoing responsibilities explicitly.

Frequently Asked Questions

Do the stages always happen in a strict order?

No. Content, design and technical work can inform each other. Keep dependent decisions visible so parallel work does not rely on an assumption that has not been approved.

How long should a website project take?

Timing depends on scope, content readiness, integrations, access, review and testing. Ask for a schedule tied to specific deliverables and dependencies rather than a duration without assumptions.

What should I approve at the design stage?

Agree what the deliverable demonstrates. A static mockup can establish visual direction but may not demonstrate form behavior or an integration. Record what is approved and what still needs implementation or testing.

What happens if requirements change after approval?

Describe the change and its reason, assess the effect on completed and future work, and agree any adjustment in scope or timing. Keep the decision with the project record.

For a new site or redesign, review WordPress website design and web development services, then share your requirements so the deliverables and review process can be scoped.

Archives