Public life & community
We scope public-information websites and digital-service journeys for councils, counties, municipal teams and public organisations. The structure starts with resident tasks, accurate information and a publishing process that the responsible team can maintain.
01 / The audience
People visit a public-service website to complete a task, check a notice or contact the right department. They should not need to understand the organisation chart first. We map common tasks and the teams responsible for them before proposing navigation or a digital service.
Group services using language people recognise. Each service page should explain eligibility information supplied by the organisation, the steps to take and whether the next action happens online, by phone or elsewhere.
Assign content owners, review dates and an archive approach for notices and documents. Published contacts, opening hours and application instructions need a maintenance process as well as a page design.
Payments, applications, resident accounts and case tracking require clear system ownership and functional requirements. We distinguish links to existing public systems from new services that need design and development.
02 / A useful page plan
This is a planning starting point. The final page list depends on your services, content and the actions your visitors need to complete.
Task-led navigation to useful instructions and responsible departments.
Dated updates, documents and clear archive behaviour.
Roles, department contacts and the correct official enquiry routes.
Clear hand-offs to applications, bookings or other agreed systems.
03 / Search & discovery
We review titles, crawlable service information, document discoverability and internal links. Public pages should clearly identify the responsible organisation and distinguish current instructions from historical notices. Search visibility should support service access rather than distract from it.
We can review technical accessibility, page structure, content gaps and the path from discovery to enquiry. SEO setup, ongoing search work and a standalone audit have different scopes. Search engines and AI platforms make their own inclusion and ranking decisions.
04 / Behind the website
We begin with discovery around ownership, review, access, integration and publishing requirements. Accessibility evaluation and any required specialist review are part of an agreed project plan, not an automatic claim attached to a basic website package.
We agree which tool owns the information, who receives a request and what the visitor sees next. Provider subscriptions, additional infrastructure and custom development are identified in the proposal.
05 / Review your current site
06 / Working together
We discuss the audience, priority tasks, existing tools and who will approve the content.
We agree the pages, functionality, provider connections, responsibilities and billing before building.
Design and content are reviewed against the agreed visitor journeys on mobile and desktop.
We test the final destinations, agree ownership and plan updates around the way your team operates.
07 / Common questions
Public-service platforms usually need a separate discovery and quotation process. The work depends on publishing responsibilities, integrations and the tasks residents need to complete.
We can begin with a structure and user-journey audit, then agree a focused improvement scope rather than assuming the entire platform must be replaced.
Start a project
Bring your questions, your current website or an idea for what comes next.