A new website is one of the most visible investments a council or public sector organisation makes. Residents use it to pay, report, apply and find help – often at stressful moments – so getting the partner right matters far more than getting the prettiest homepage.

We have built websites and digital resources for councils, NHS-commissioned services and public sector partners across Merseyside. These are the questions we think every commissioning team should ask before signing a contract – including when they are asking us.

1. How will you meet the accessibility regulations?

Public sector bodies must meet the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018, which point to the Web Content Accessibility Guidelines (WCAG) at level AA. Ask the agency how they test – automated tools alone catch only a fraction of issues – and whether they test with keyboard-only navigation and screen readers. A good answer includes manual testing, an accessible content management workflow and help writing your accessibility statement.

2. Who will we actually be working with?

Large agencies often sell with a senior team and deliver with a junior one. Ask who will design, build and support your site, and whether you will have a single point of contact throughout.

3. How will you involve residents and service users?

The best public sector websites are shaped by the people who use them. Ask how the agency plans to run discovery, user research or consultation. On projects like the Wirral Council and Teenwirral websites, involving staff, young people and members of the public directly influenced the final design.

4. Do you follow GOV.UK and content design principles?

Plain English, task-focused pages and a clear structure make a bigger difference to residents than any visual flourish. Ask whether the agency is familiar with the GOV.UK Service Manual and content design principles, and whether they will help your teams write content that works.

5. Where will our data be hosted, and who processes it?

Ask where the website and its databases are hosted, whether data stays in the UK, which sub-processors are involved and whether the agency will sign a data processing agreement. Forms that collect personal data need particular care, so ask how submissions are stored, secured and deleted.

6. How does this fit our procurement route?

Whether you are using a framework, a quotation process or a competitive tender under the Procurement Act 2023, ask the agency to price clearly against your specification and to separate one-off build costs from ongoing hosting, licences and support. Hidden annual fees are a common cause of budget surprises.

7. Who owns the website when it is finished?

Make sure you own the domain, the design, the content and the code, and that you can move to another supplier if you need to. Be cautious of proprietary platforms that lock you in.

8. How easy will it be for our staff to update?

Your web editors will live with the content management system every day. Ask for a demonstration, training for your team and guidance notes, and check that the editor makes it hard to accidentally publish inaccessible content.

9. What happens after launch?

Ask what support, security updates, backups and uptime monitoring are included, how quickly issues are fixed and how much ongoing changes cost. A website is never really finished – it should improve as you learn how residents use it.

10. Can we see similar work and speak to a client?

Ask for examples of public sector or regulated-sector work, and for a reference you can actually call. An agency confident in its delivery will be happy to put you in touch.

Thinking about a new public sector website?

We help councils, NHS-commissioned services and public sector partners plan and build accessible, easy-to-manage websites. Find out more about our public sector website design or get in touch for an informal chat about your project.

Found this helpful? Let others know!