Planning resource

Website planning checklist

Make the important decisions before design begins. This checklist turns a broad idea into a website that can be scoped, quoted and built clearly.

Illustration of a completed planning checklist

Before design starts

Make the decisions that shape the website.

There is no need to write a technical specification. Accurate business information gives the designer something real to organise, quote and build.

Begin with people

Who needs the website, and what must they be able to do?

Customers, languages and service area

  • Name the main customer groups and the questions each group asks

  • Choose English, Spanish or additional languages from real customer needs

  • List services and genuine service areas

  • Decide whether every service is available in every area

  • Identify seasonal visitors, residents and overseas buyers where relevant

Pages and customer journeys

  • Home, service, about, work or evidence, contact and appropriate legal pages

  • A clear next step on every important page

  • Phone, enquiry form, booking or payment routes

  • Confirmation messages and who receives each enquiry

  • Information customers need before committing

Use real material

Words and photographs

Assign an owner for every page. Gather accurate service details, prices where useful, frequently asked questions, team or business information and proof of work. List the photographs needed and confirm permission to use them. Avoid placeholder content when the real material will change the layout.

Domain, email and ownership

  • Confirm who owns and renews the domain

  • Choose who controls DNS and do not change it without a launch plan

  • List required business email addresses and devices

  • Agree administrator access and handover

  • Record hosting price, backups, maintenance and exit arrangements

Before work begins

Agree the scope and the finish line.

  • Approved page list and functions

  • Named person supplying business facts and approvals

  • Review stages and decision dates

  • What is included, separately quoted or deliberately excluded

  • Redirect plan for an existing site

  • Browser, device and form tests before launch

  • Training, access and support after launch

Start with a conversation

You do not need to prepare a technical brief.

Tell Jon what the business does and what you need the website to achieve.