Visit eRegister.com →

Service

Government website redesign

Replace your aging agency website with a modern, mobile-first experience that residents can actually use — on a fixed timeline and a fixed budget.

The Challenge

Your residents deserve better than a 2008 website

Most agency sites were built years ago, on platforms that are no longer supported, with content structures that no one on staff fully understands. They’re slow on phones, fail accessibility audits, and bury the answers residents are actually looking for.

A modern redesign isn’t just a new coat of paint. It’s a rethink of the information architecture, the content, the accessibility posture, and the publishing tools your team uses every day.

Common pain points we solve

  • Site fails WCAG 2.2 / Section 508 audits
  • Mobile experience is unusable
  • Editors avoid the CMS because it’s painful
  • Search results return junk — or nothing
  • Page load times exceed five seconds
  • Inconsistent branding across departments

What’s included

A complete redesign engagement

Discovery & content audit

Stakeholder interviews, content inventory, analytics review, and a residents-first information architecture.

Brand-aligned visual design

High-fidelity designs that match agency branding standards and pass an accessibility review before any code is written.

Accessible component library

Reusable, WCAG 2.2 AA components your editors can recombine without breaking the design system.

Mobile-first build

Built for phones first, then tablet and desktop. Works on every device residents actually own.

Content migration

We migrate existing content into the new structure, with redirects so old links keep working.

Editor training & launch

Live training sessions and written runbooks so your team can publish confidently from day one.

Outcomes

What success looks like

Mobile-first

Pages built to load fast on phones

WCAG 2.2 AA

Accessibility target

Self-service

Residents find answers without calling

SLA

Uptime commitment in writing

Who it’s for

Cities, counties, state departments and districts

A redesign fits a single department site or a central site that serves every department. The buyer is usually the IT director, the communications lead or the clerk’s office that owns the website. If your site is hard to update, hard to read on a phone or failing accessibility checks, this is where to start.

What your agency provides

  • A project lead who can gather feedback and make decisions
  • Access to your current site, CMS and analytics
  • Brand standards, logos and any style guide
  • Department reviewers who know their content
  • Time for user acceptance testing and sign-off

The process

How a redesign runs

  1. 1

    Discovery and scoping

    We interview stakeholders, review analytics and inventory every page. You get a written scope with milestones and acceptance criteria.

  2. 2

    Design and architecture

    We draft the new site map and page designs. Your team reviews them, and they pass an accessibility review before code is written.

  3. 3

    Build and iterate

    We build in two-week sprints and demo working pages at the end of each one.

  4. 4

    Test, train and launch

    Your team tests the site. We move the content, set redirects, train your editors and launch with a runbook.

  5. 5

    Hypercare and transition

    We stay close after launch, then hand off to your maintenance contract or in-house team.

Each phase ends with a deliverable your team signs off on. The full plan is on our implementation page.

Related work

How it fits with our other services

Contracting officers can see every service on our capabilities statement. To get a proposal, tell us about your site on our contact page.

FAQ

Questions about a redesign

Can you respond to our RFP or work through a cooperative contract?
Yes. We respond to your solicitation, or help you write one. Our fixed-fee statements of work tie pricing to deliverables, not hours.
How long does a redesign take?
It depends on the size of the site and how much content moves. Your written scope sets a date for each phase before the build starts.
Who owns the code and content when the project ends?
Your agency owns its content. The statement of work sets ownership of the code, designs and documentation before work starts, so handoff holds no surprises.
Will the new site meet accessibility requirements?
We design and build to WCAG 2.2 AA and Section 508. Designs are reviewed for accessibility before code is written, and editor training covers keeping new content accessible.
What support do we get after launch?
A hypercare period follows go-live. After that, you can move to a maintenance contract with us or take it in-house with our runbooks.

Let’s talk about your project

Tell us what you’re trying to accomplish and we’ll respond within one business day with next steps.