Example scenario
An application round at a public education institution
Application guidance, timetable changes and result announcements sit in different menus. Applicants sometimes mistake a document from the previous year for the current version.
How would we approach it?
We bring the current cycle’s dates, requirements and documents onto a dedicated application page. Previous cycles are archived by year, and the institution’s editor checks that each new notice links back to the correct application.
Start with what people come to do
Visitors should be able to find the documents they need, the conditions for applying and the right contact without knowing the department name. We use these tasks to organise websites for public agencies, education institutions and local authorities.
We identify the most frequently used services and notices first. Service pages explain who can apply, what to prepare, which dates matter and where the official process starts. Where an existing external system handles the application, the link makes that destination clear.
Plan announcements and documents as an archive
Application guides, decisions, notices and annual reports each call for their own fields. For example, a notice has a closing date and a report has a publication year. Consistent fields help people filter the archive and help editors provide the information each time.
For a redesign, we inventory existing pages and documents. We review what to migrate, archive or redirect with your authorised team, and identify information that should be readable on the page as well as available as a download.
Give the right people permission to publish
The person preparing a service page may be different from the person checking and approving it. Editorial roles, drafts, approvals and urgent notices are designed around that division of responsibilities. The handover explains what editors need to update when a department or contact changes.
We test representative tasks before launch, such as publishing a notice, finding an archived document and opening a service page on a phone. Integrations are scoped with the institution and its existing providers, including data ownership and access.
Include accessibility in acceptance testing
We check keyboard navigation, visible focus, heading order, colour contrast and form instructions on the agreed page types. Where existing documents or media need remediation, the handover identifies the work and who can take it forward.
The handover records editorial permissions, content guidance, hosting and backup responsibilities, and the agreed schedule for maintenance after launch.
Questions before you start
Is this only for municipalities, or can it suit other public institutions?
The structure can suit different public bodies publishing service guides, notices, archives and department contacts. We begin by mapping the organisation, the main tasks people visit the site to complete and any separate publishing needs for headquarters or local branches.
How are old notices, decisions and PDFs transferred?
We inventory records by document type, date, department and existing URL. The institution confirms what will move, stay archived or be withdrawn. We plan redirects for records that remain public and check sample items before launch.
Will we have to replace e-government or an existing application platform?
Where an official transaction channel already exists, the service page can explain requirements and guide users to it. Integrations that exchange data are quoted after the institution's technical team and provider confirm permissions, a test environment and ownership.
How is accessibility handled in the proposal and at handover?
The scope names measurable checks such as keyboard navigation, contrast, form labels, heading order and mobile use. PDFs and archived files are assessed separately. If the institution requires a particular standard or audit, we define that assessment before quoting.
Will staff need the agency every time they publish a notice?
The editor can be configured so authorised staff update notices, documents and service pages. Handover can include publishing a sample notice, replacing a document and testing a role change. The proposal records responsibilities for software maintenance, backups and support.