13.10.2025
Website Development & UX/UI

Are you preparing a new website for your town hall and don't know where to start? By defining your needs, you save time, secure your budget and make the work of the team supporting you easier.

The specifications document for a municipal website is the document that sets out the objectives, features, regulatory constraints and delivery conditions of a municipality's future website. It defines the town hall's needs before consulting a provider for a creation or redesign.
A municipal website is not limited to presenting the municipality. It must allow residents to find practical information, read local news, access administrative procedures and follow public life.
To make this project a success, you need to take into account the needs of residents, but also those of the staff responsible for publishing and updating content.
How do you write a specifications document for a town hall website? Which sections should you plan? How do you build in RGAA accessibility, data protection and the obligations for publishing municipal acts?
ID Interactive, a digital agency based in Arradon, near Vannes (Morbihan), since 2006, supports companies and organisations in designing websites suited to their needs.
This guide presents the steps for writing a municipal specifications document, the main features to consider and a ready-to-use template.
The specifications document allows a municipality to set out its expectations before launching a web project.
It serves as a reference document between elected officials, municipal departments and the providers consulted.
In particular, it must answer five questions:
Without prior scoping, a local authority risks comparing proposals that do not cover the same services.
The specifications document also helps identify everyone's responsibilities: writing content, validating information, administering the site, hosting and maintenance.
The aim is not to write a complex technical document, but to describe precisely the service expected by the municipality and its residents.
The first step is to understand the main searches carried out by residents and users.
Needs can vary depending on the size of the municipality, its organisation and the services offered.
Frequently useful information includes:
The municipality can draw on requests received at reception, emails, phone calls and staff feedback to identify priority needs.
A creation or redesign project must meet concrete objectives.
For example:
These objectives will then be used to define functional priorities and acceptance criteria.
In the case of a redesign, you need to draw up an inventory of the current site.
This inventory makes it possible to identify:
The local authority must also decide who will be responsible for validating the new content.
A better-designed site will not remain useful for long if the information is not kept up to date.
An effective specifications document must distinguish between functional expectations, technical constraints, regulatory obligations and contractual conditions.
Present the municipality, the context and the reasons for the project.
In particular, state:
Also specify who will be responsible for validating the design, content and features.
The site tree describes how content will be grouped and accessed.
It must be adapted to the actual organisation of municipal departments and to residents' needs.
Here is an example of a starting structure.
This is an example, not a mandatory plan.
A small municipality may need a simpler structure, while a town or an inter-municipal authority may require more sections.
There is no rule requiring a municipal website to have 45 HTML pages. The number of pages must follow from the information and services actually needed.
The home page must help visitors quickly access priority content.
It can include:
A photograph of the municipality can contribute to the visual identity, but it must not hide practical information.
The aim is to make orientation easier, not to multiply animations.
The town hall may want to publish news, public meetings and local events.
The specifications document must specify the information that can be administered:
Also plan archiving rules so that out-of-date information is not displayed indefinitely as upcoming events.
The site can direct residents to existing procedures, particularly on public platforms.
It can also offer certain forms specific to the local authority when relevant.
You need to distinguish:
Information only: state the documents required and the procedure to follow.
Redirection to an official service: send the user to the relevant online service.
A form built into the site: collect a request to be handled by municipal departments.
In the latter case, you need to define the recipient, data processing, acknowledgements of receipt and the protection of the information submitted.
Do not automatically include a form collecting personal data when the procedure is already covered by an appropriate official online service.
The site may have to host official publications subject to specific rules.
Since 1 July 2022, electronic publication has been the default form of publicity for various categories of acts of local authorities.
However, municipalities with fewer than 3,500 inhabitants have a right of option, under the conditions laid down by the General Code of Local Authorities (CGCT).
In addition, Article L.2121-25 of the CGCT provides that the list of deliberations examined by the municipal council is posted at the town hall and put online on the municipality's website, where one exists, within one week.
The specifications document must therefore provide a suitable organisation for the documents concerned:
You need to distinguish between putting a document online for information and publication that has legal effect.
The local authority must validate the rules applicable to its acts with the relevant departments.
The site can offer directories that make searching easier.
For each entry, the specifications document must indicate the useful fields:
The rules for publishing personal data, in particular individual contact details, must be checked before they are put online.
An interactive map can be useful for locating the town hall, facilities and public places.
Before choosing a solution, you need to examine the real needs and the technical and regulatory consequences.
An external map may in particular involve connections to a third party and, depending on the service, data processing or trackers.
It may be better to use a solution proportionate to needs, accompanied by accessible text information.
The specifications document must identify the requirements applicable to the local authority. These requirements must then be translated into verifiable features, responsibilities and deliverables.
Municipal websites are subject to the digital accessibility obligations applicable to public bodies.
In October 2026, the published version of the French General Accessibility Improvement Framework (RGAA) is RGAA 4.1.2.
The project must build in accessibility from the first mock-ups and throughout development.
In particular, the specifications document can require:
In particular, the local authority must plan for the elements needed to meet its obligations:
The accessibility statement, based on an actual assessment, with a justified compliance status.
An Accessibility page, accessible from the site's pages.
The multi-year accessibility plan and the annual action plan, according to the applicable requirements.
Evidence and fixes, to document the audit results and the handling of non-conformities.
An automated score does not replace a full RGAA audit.
The specifications document must define who carries out the audit, when it takes place, who fixes the anomalies and how the results are validated.
As the next version, RGAA 5, is in preparation, the local authority must also plan regulatory monitoring without suspending work in progress.
Contact forms, registrations and other services may lead the town hall to process personal data.
The specifications document must specify:
The local authority must involve its data protection officer, or DPO, in the project.
Public bodies are required to appoint a DPO; this function can be shared under certain conditions.
The site may include trackers linked to browsing, videos, maps or visitor statistics.
You need to distinguish between strictly necessary trackers and those requiring prior consent.
Some audience measurement solutions can be exempt from consent, but only when the conditions set by the CNIL are met.
A statistics tool is not automatically exempt from consent because it is used by a town hall.
The specifications document must therefore require an inventory of trackers and a set-up consistent with the processing actually carried out.
The local authority must provide the information identifying the site's publisher, the managers concerned and the providers involved in its operation, in accordance with the applicable texts.
Separate pages or sections may be needed for the legal notices, personal data and accessibility.
Content must be adapted to the municipality's situation, rather than copied from a generic template.
The CMS, or content management system, allows authorised staff to publish and edit the site's information.
Several solutions can suit a municipal project: WordPress, Drupal or an architecture using a headless CMS, for example Payload CMS with a Next.js interface.
The choice should not be dictated solely by popularity.
The local authority must assess:
For example, a small, mainly informational site may not need the same architecture as a portal with several services and integrations.
The specifications document must specify hosting needs and the expected protection measures.
In particular, it can require:
Hosting in France can be a contractual requirement chosen by the local authority.
However, this location should not be presented as a universal legal obligation applying to every municipal website. The constraints depend on the data, the processing and the rules actually applicable.
The site must be usable on smartphones, tablets and computers.
The specifications document can provide for checks of loading times, responsiveness and visual stability.
The Core Web Vitals — LCP, INP and CLS — are useful indicators.
Performance objectives must be accompanied by a measurement method and acceptance conditions.
A perfect PageSpeed score is not, on its own, proof of compliance or overall quality.
SEO makes it easier for residents to find the public information published by the municipality.
The project must provide for:
These practices also make it easier for search systems that integrate artificial intelligence to discover content.
However, no SEO or GEO optimisation guarantees that municipal information will automatically be included in AI assistants' answers.
Ease of administration is an essential element in the project's success.
Several departments may contribute content: general secretariat, communication, civil registry, culture, childhood or technical services.
The specifications document must determine the available roles.
You need to be able to assign the necessary rights without giving every staff member full access to the whole site.
Approval processes must remain proportionate to the town hall's organisation.
A small municipality can work with a simple organisation, while a town with several departments may need additional approval steps.
In a redesign, migration must be included in the specifications document.
It includes the inventory of content and documents, the preparation of the new site tree and the handling of old addresses.
In particular, you need to plan for:
Official acts and documents require particular attention in order to preserve their availability and publication conditions.
You should not guarantee that all Google positions will be kept exactly after a redesign, but plan the technical measures that limit the risk of regression.
The cost depends in particular on the volume of content, the features, the design, the migration, compliance needs, hosting and maintenance.
To build a budget that can be compared across several proposals, the local authority can separate the following items:
Stage | Examples of services and content |
|---|---|
Scoping and design | workshops, site tree, mock-ups |
Development | CMS, features, integrations |
Migration | pages, media, documents, URLs |
Accessibility | checks, audit, fixes, deliverables |
GDPR and security | forms, trackers, access, protections |
Training | number of staff, materials, duration |
Hosting | technical conditions, backups |
Maintenance | fixes, updates, support |
Future developments | terms and costs of interventions |
Hosting, maintenance and compliance services must be identified precisely to avoid ambiguity.
It is also useful to set the contract duration and reversibility conditions.
To compare the options for a project, you can request an ID Interactive website creation quote.
The municipal website must be able to be operated and maintained after going live.
The specifications document must set out the respective responsibilities of the municipality and the provider.
The services to be defined may include:
Also specify support hours, reporting channels and the expected contractual deadlines.
Reversibility allows the local authority to recover what it needs if it changes provider.
The contract must specify how the following will be handed back:
The provider must explain any technical dependencies that could complicate a migration.
Here is a framework to adapt to the municipality before consulting providers.
This is a functional and technical template. Where appropriate, it must be supplemented by the contractual and administrative documents suited to the public procurement procedure.
Local authority: [Name of the municipality]
Project manager: [Name, position and department]
Purpose: creation or redesign of the website of the municipality of [Name]
Current site: [URL, if any]
Context: [Description of the current situation]
Objectives: [Information for residents, procedures, accessibility, content administration, other needs]
The site must allow the following audiences to access the local authority's information and services:
The priority journeys must be specified for each audience.
Expected sections: [List of sections]
Pages to create: [List]
Content to migrate: [List and estimated volumes]
Official documents: [Type and publication arrangements]
News and calendar: [Fields, categories and publication arrangements]
Media: [Available images, videos and documents]
The table below summarises the expected features, their priority and the comments to be completed.
Content | Priority | Comments |
|---|---|---|
Administrable news | Essential / desirable / optional | [To be completed] |
Municipal calendar | To be defined | [To be completed] |
Directory of services | To be defined | [To be completed] |
Directory of associations | To be defined | [To be completed] |
Contact form | To be defined | [To be completed] |
Procedure pages | To be defined | [To be completed] |
Publication of acts | According to applicable obligations | [To be completed] |
Internal search | To be defined | [To be completed] |
Management of staff roles | To be defined | [To be completed] |
Alerts or urgent information | To be defined | [To be completed] |
Interactive map | To be defined | [To be completed] |
Multilingual | To be defined | [To be completed] |
Each selected feature must be described precisely enough to allow it to be estimated and accepted.
The site must respect the local authority's visual identity.
Interfaces must be adapted to smartphones, tablets and computers.
The main journeys must allow users to easily find procedures, practical information and the contact details of municipal departments.
Mock-ups and components will be validated before development according to the arrangements defined with the municipality.
The project must take into account the RGAA framework in force and the local authority's obligations.
Audit requested: [To be specified]
Scope of the audit: [Pages and journeys concerned]
Deliverables: [Report, fixes, elements for the accessibility statement, other]
Person responsible for accessible content: [To be specified]
Approval arrangements: [To be specified]
Planned processing: [Forms and services]
DPO contact: [Internal contact details]
Trackers and audience measurement: [Solutions and requirements]
Hosting: [Needs and constraints]
Backups: [Frequency and conditions]
Administrator access: [Rights and authentication]
Incident management: [Expected arrangements]
Content concerned: [List]
Documents to keep: [List]
Old URLs: [Inventory]
Redirects: [Rules and checks]
Migration approval: [Person and procedure]
The provider must hand over the elements set out in the contract, in particular:
The municipality's main contact: [Name]
Participating departments: [List]
Approval stages: [List]
Desired schedule: [To be completed]
Institutional constraints: [Approval periods, events, regulatory deadlines]
The final schedule must be set on the basis of the actual scope.
Provisional budget: [To be completed]
Creation scope: [To be completed]
Recurring services: [To be completed]
Maintenance: [To be completed]
Contract duration: [To be completed]
Intellectual property, licences and reversibility: [To be completed]
The local authority must have the award procedure and the clauses applicable to its purchase checked.
Before the site is accepted, the checks must cover in particular:
Anomalies must be recorded and handled according to the project's conditions.
A specifications document makes it possible to compare offers on a common basis.
You need to examine not only the features promised, but also the support and operating arrangements.
Several points deserve particular attention:
Understanding of municipal needs. The provider must identify residents' priority uses and publishing constraints.
Accessibility. The design, audit and fixing methods must be clearly detailed.
Staff autonomy. The local authority must know which operations it will be able to carry out without technical intervention.
Security and maintenance. Contractual responsibilities must be explicit.
Reversibility. The site, content and data must be recoverable under the conditions defined in the contract.
The quality of the financial proposal. Initial and recurring costs must be distinguished.
For a consultation subject to public procurement rules, the selection criteria and the procedure must comply with the rules applicable to the buyer and to the estimated value of the contract.
ID Interactive designs websites and administration interfaces suited to the needs of each organisation.
For a municipal project, the approach can be organised around several stages:
1. Functional scoping. Identifying priority audiences, content and services.
2. UX/UI design. Organising the site tree and interfaces.
3. Development. Setting up the CMS and the selected features.
4. Migration. Integrating useful content and handling old URLs.
5. Testing. Checking the features and the behaviour of the site.
6. Training. Supporting the people responsible for administration.
7. Operation. Hosting and maintenance according to the contractual services chosen.
The project must be adapted to the size of the municipality and the human resources available.
To find out more about creation and redesign options, see our website creation services.
Before consulting providers, check that the document covers the essential points.
A complete checklist does not mean that every function has to be developed. Above all, it makes it possible to check that no important need has been forgotten during scoping.
A good municipal specifications document describes the services expected by residents, the tools staff need and the requirements to be met to run the site over the long term.
It starts with the objectives and real needs, then specifies the site tree, features, regulatory constraints, technology and deliverables.
The choice of CMS, the number of pages or the look of the home page must follow from this scoping.
RGAA accessibility, data protection, the publication of municipal documents and security must be built in from the start of the project, not added only at the end.
Finally, maintenance, training and reversibility conditions must be planned so that the municipality can keep its site alive over time.
Article originally published on 27 November 2023.
ID Interactive supports town halls and local authorities in Morbihan, including Crac’h, Brec’h and Île-aux-Moines. To discover our approach and our local references, see our guide to web agencies in Vannes.
Un cahier des charges est un document qui définit les besoins, les objectifs, les fonctionnalités et les contraintes d’un site internet municipal : contenus attendus, arborescence, obligations légales, exigences techniques et modalités de suivi. Il sert de base commune entre la collectivité et les prestataires consultés : il cadre le projet, permet de comparer les offres sur des bases équivalentes et d’obtenir des devis précis.
Le cahier des charges permet d’éviter les incompréhensions sur le périmètre, de maîtriser le budget et de s’assurer que le site répond aux attentes des administrés. Pour une collectivité, c’est aussi la base de la consultation : les entreprises répondent sur des bases comparables, ce qui fiabilise l’analyse des offres. Un projet bien cadré est plus rapide et plus efficace à réaliser.
Un cahier des charges de site internet municipal décrit au minimum : la présentation de la collectivité et du projet, les publics concernés, l’arborescence et les contenus, les fonctionnalités attendues, le design et l’ergonomie, l’accessibilité numérique, la protection des données personnelles et la sécurité, la migration de l’ancien site, les livrables, l’organisation du projet, le budget et les conditions contractuelles, puis la recette et la mise en ligne. Les obligations applicables (RGPD, RGAA, publicité des actes) y sont intégrées dès l’écriture.
Cela dépend de la taille de la commune et des services proposés, mais un site municipal comprend généralement plusieurs dizaines de pages, réparties entre pages simples, pages détaillées et contenus dynamiques : actualités, agenda, démarches, annuaires et publications officielles. Le cahier des charges peut fixer une arborescence cible sans figer un nombre définitif de pages.
Des CMS reconnus comme WordPress ou Drupal sont souvent recommandés pour leur flexibilité, leur sécurité et leur facilité de gestion par les équipes municipales. Il existe également des solutions plus modernes dites « headless », comme celles basées sur Next.js et Payload CMS : la solution développée par ID Interactive permet de créer des sites plus performants, évolutifs et faciles à maintenir, tout en offrant une grande liberté de personnalisation.
Oui. Intégrer le référencement dès le cahier des charges garantit la visibilité du site sur les moteurs de recherche et facilite l’accès à l’information pour les administrés : structure des contenus, URLs lisibles, hiérarchie des titres, vitesse de chargement et accessibilité se décident en amont. Ces éléments sont coûteux à corriger après la mise en ligne.
Un site municipal doit respecter plusieurs obligations : la protection des données personnelles (RGPD), l’accessibilité numérique (RGAA), avec la déclaration d’accessibilité obligatoire pour les sites publics, les mentions légales et administratives, et la publicité et la conservation des actes dans les délais prévus. L’hébergement et la sécurité des données doivent également être cadrés dans le projet.
Oui, un cahier des charges peut évoluer en cours de projet, mais chaque évolution peut entraîner des coûts supplémentaires et des délais, et doit rester encadrée, notamment dans le cadre d’un marché public. Il est donc recommandé de définir un maximum d’éléments en amont — périmètre, livrables, procédure de recette — et de prévoir les modalités de traitement des demandes d’évolution.