Begin with a public task, not a page count.
A municipal website redesign is a coordinated change to content, navigation, technology and staff responsibilities. A workable sequence is to understand user needs, inventory the current site, define requirements, test a representative slice, prepare migration, verify launch and assign ongoing ownership.
Start by choosing a small set of important tasks: find a meeting agenda, understand a permit requirement, locate office hours or report a nonemergency problem. Ask residents and staff to show how they complete them today. Record the point where they lose confidence, leave the site or need someone to explain the next step.
The U.S. Web Design System principles recommend involving real users and testing assumptions throughout design. The Digital.gov journey mapping guide offers a way to examine the steps across a service.
Useful output: a short task list, the evidence behind it, named reviewers and a description of what a successful visit should look like.
Inventory pages, documents and dependencies.
A crawl is a starting inventory, not a content decision. Ask the responsible departments what must remain public, what is outdated, which documents need review and which outside systems perform the actual transaction. Include important URLs people reach from bookmarks, official correspondence and search.
Give each page or document an owner and a proposed action: keep, rewrite, combine, archive or review for removal. If two pages answer the same question, choose a destination and preserve any useful facts before proposing consolidation. A retention or disclosure decision belongs with the agency, even when a page receives little traffic.
Use the content audit workbook and local migration checker to record ownership and unresolved destinations. The checker evaluates entered rows; it does not crawl a site or implement redirects.
Useful output: an inventory with decisions, unresolved questions, dependencies and an old-to-new URL map.
Define requirements and acceptance together.
Describe what residents and staff must accomplish before choosing a platform. A useful requirement has an observable result: an editor can update office hours without changing a template, or a visitor can reach the correct payment service from a mobile service page.
Separate a plain link from an embedded tool or an API integration. For each integration, identify the owner, available documentation, permissions, data involved and behavior when the service is unavailable. Include training, documents, content entry and launch support in the scope so vendors are pricing comparable work.
Specify who will review accessibility, privacy, security and records requirements. Define the test coverage and correction process with those reviewers. A checklist or automated scan alone does not establish legal compliance.
Useful output: a reviewable brief with acceptance criteria, assumptions, optional work and responsibility for each dependency. The website requirements scope builder can organize this brief. The cost and scope guide explains which decisions affect initial and recurring costs.
Test a representative slice before every page is built.
Choose a few page types that expose the difficult decisions: a service page, a department page, a meeting or document listing and an interactive form if forms are in scope. Include a long title, missing information and a realistic mobile task. A polished homepage cannot establish that these supporting pages work.
Have intended users attempt the tasks without being coached through the navigation. Ask editors to make a routine change and send it for review. Check keyboard access, focus, reading order, form labels and the clarity of confirmation or error messages.
Keep a decision log. When feedback conflicts, connect the decision to the task, the evidence and the person authorized to resolve it. A review milestone should record what was accepted and what still needs work.
Useful output: approved page patterns, tested task paths, an issue list and agreed changes before migration expands.

Move content with a destination and a verification step.
Migrate approved content into the tested patterns. Check actual headings, document labels, dates, contacts and service links after import. Review a sample from each page type and increase coverage where the migration reveals repeated errors.
Map changed URLs to the most relevant replacement. Redirecting every old page to the homepage removes the context a visitor was trying to reach. Google’s site move guidance explains URL mapping, redirects and monitoring during a move.
Agree on a content freeze or a change log for the final migration window. If a department updates the old site after its content has been copied, someone must reconcile that change before release.
Useful output: checked content, reviewed redirects and a record of changes made during the migration window.
Treat launch as a controlled handoff.
Before switching the public site, confirm who can approve release, what remains unresolved, how the previous version can be restored and who will watch for failures. Test important paths on the actual deployment, including external transactions and supported integrations.
- Public tasks: pages and links lead to the intended answer or service.
- Search access: public pages use the intended canonicals and indexing settings; private previews remain protected.
- Migration: changed URLs reach relevant destinations, with deliberate handling of removed content.
- Staff access: editors have the agreed permissions, training and recovery path.
- Operations: domain, hosting, source files, licenses, maintenance and incident responsibility are documented.
Useful output: written release acceptance, a known rollback approach and a named owner for post-launch issues.

Measure task success and keep an owner on the content.
Record a baseline before redesign when data is available. Afterwards, review whether priority information is findable, where people abandon a process, what staff still answer repeatedly and whether broken links or outdated details recur. Search impressions and clicks are useful visibility signals; they do not establish that a resident completed a task.
Assign review dates according to how quickly information changes. A seasonal program may need a different review schedule from a stable department description. Use the content calendar to track planned updates and exact-revision approvals.
If your team needs implementation, explore local government website design. If the site is sound but upkeep is difficult, review ongoing content support. When a task crosses departments, workflow design can address what happens after the form.
Useful output: a practical review schedule, a baseline for comparison and a backlog tied to actual resident and staff needs.
Specify accessibility evidence and editor readiness before launch.
Write acceptance criteria while the scope is being agreed. Name the applicable accessibility standard and version, the included public pages, forms, documents and third-party transitions, the evaluation method and who will review the findings. Have the agency’s authorized accessibility and legal reviewers determine applicable obligations.
The W3C WCAG evaluation methodology (opens in a new tab) provides a structure for defining and reporting evaluation. Use qualified evaluators and an agreed combination of automated checks and human evaluation. A passing scanner, accessible CMS claim or review of one page is not evidence that the delivered site meets every requirement.
Ask for an issue record with the affected version, reproduction steps, criterion where applicable, impact, assigned owner and retest result. Include a representative end-to-end task, documents and error states. Record any unresolved findings and the authorized decision about them without relabeling them as passed.
The scope guide’s acceptance matrix helps make that evidence request concrete. Separately, use editor practice tasks to confirm that the people maintaining the site can publish and correct approved content. Usability research, conformance evaluation and staff readiness each answer a different launch question.

