Website governance

This governance framework outlines the objectives of Warwickshire County Council’s websites and online services, explains management roles and processes for colleagues and users, and sets out good practice principles for ongoing improvement.


Our websites, intranet and digital media (or ‘web services’) are intended to provide:

  • accessible and easy-to-use services
  • relevant, accurate and up-to-date information
  • communications channels to inform and engage.

Roles and responsibilities

Management and development of council websites is the responsibility of the E Services Team, as part of Customer Services, with support and advice from Service Development, Marketing and Communications, Information Management and ICT Services.

Ensuring their information is always up to date is the responsibility of each service. Heads of service are accountable for the accuracy of this information and will ensure suitable representatives monitor their information on a regular basis, making updates as required.

New web services

Requests and questions about new online content and websites should be made to the E Services Team, while requests for online forms should be made to the Service Development Team.

We can help services to identify:

  • who the likely users are and what they’re trying to do
  • how they do it currently
  • the problems or frustrations they experience
  • what users need from the service to achieve their goal.

Requests will be assessed and prioritised by the Customer Service Transformation Board.

The E Services Team will also review changes to existing pages for consistency and clarity of presentation, and as part of the publishing workflow process.

Requests for new systems and applications should be submitted to ICT Services to ensure compliance with ICT strategy, architecture and standards. Services should consult with their ICT Business Partner in the first instance.

Usability and accessibility

Services must adhere to accessibility standards – WCAG 2.0 to a AA level.

The E Services Team must be involved at the earliest stage to advise on the usability and functionality of online third party applications. They will work with third party providers to improve usability and functionality based on user needs and compliance with our standards and policies.

We will do usability and accessibility testing before new web services go live. This will either be carried out in-house or by a panel of external users. The project manager is responsible for scheduling in enough time for testing to be carried out in liaison with the E Services Team.

Publishing process

Requests for new digital content should be submitted to the E Services Team. Dependent upon the nature and quality of the content, they will:

  • approve the request for immediate action
  • review the request in more detail, which may require asking for clarification from the requester
  • decline the request, explaining why it is not appropriate – for example, if there is no clear need, if it’s an editorial request or if the need can be met with existing content.

Changes can be made by department editors if one exists, adhering to guidance from the E Services Team.

At each stage, the E Services Team retains the right to change the wording, layout or presentation to better adhere to our standards, meet best practice, and achieve the business objectives of the organisation.

Publishing documents

Information should be published in HTML format unless there is a clear need to do otherwise, in which case other open formats, including PDF and CSV, should be used. We will not publish scanned documents unless the documents are not available in any other format.

Official documents should be made available online as part of the publishing process, adhering to the council’s records management guidelines, including being uploaded to the Electronic Document and Records Management System (EDRMS).

Content standards

All online content should be designed around user needs. We will use evidence to determine user needs and test content against those needs.

Content should be written using plain English, avoiding jargon and legalise and must comply with the corporate style guide.

Content standards and development – more information

Public information

We aim to publish once, but make available across channels. In simplest terms this means linking to existing content. We will use technology to achieve this where possible – for example, through the use of application programming interfaces (APIs).

Information intended for public use should be published on and made available to staff through links on the intranet where necessary. Where information is provided by another organisation (eg details of medical conditions, best held on NHS Choices), our content should link to it to avoid duplication.

How to question a decision

If you are unhappy with a publishing decision, please discuss the issue again with your E Services Team contact, considering alternatives. If the issue still cannot be resolved it can be escalated to the Corporate Webmaster and then, if necessary, to the Head of Customer Services.

Structure and design

The structure of our websites, including changes to information architecture and navigation, is informed by the analysis of usage data and by emerging good practice.

Homepages and navigation are focused first on user needs and top customer tasks, with access to council news and campaigns also provided. Changes must not be influenced by opinion or personal preference.

Visual design (including use of colour, text style and page layout) must focus on the needs of site users and adhere to council branding guidelines, but not be driven by it.

Review and improvement

To maintain high quality web services, we continuously review and improve our sites.

Statistics and other usage data will be routinely published and analysed to highlight performance and opportunities for improvement. E Services officers will meet regularly with service areas to support the needs of the business and requests for changes will be considered against these analytics.

Periodic qualitative evaluation should also be made to gather more specific or topical views from users, through surveys, polls, online forums and face to face conversations.

This framework will be reviewed regularly to take account of changes in technology, accountabilities and emerging good practice.