revize.com No paid content found

Government and municipal website design differs from typical business site design because the primary goal is public service, not sales. A city or county site must help residents find services, access public records, and complete tasks like paying a permit fee or reading meeting minutes — often under accessibility and transparency requirements that don't apply to a private business. If you're planning or redesigning a government site, the sections below cover what to plan for, how to choose a CMS, and the pitfalls that most often derail these projects.

The Core Differences From a Business Site

The practical consequence: a government site is judged on whether a resident can complete a task — renew a license, find a meeting agenda, report a pothole — not on how it looks in a hero banner.

Content and Features You Need to Plan For

Before design starts, inventory the content that residents actually come for. Typical required elements include:

• Public notices and legal notices — often with posting deadlines.
• Meeting agendas and minutes — for council, boards, and commissions.
• Permits, licenses, and applications — with downloadable forms and, where possible, online submission.
• Department directories — staff names, roles, phone numbers, and hours.
• Payments and fees — utilities, taxes, fines, registrations.
• Emergency and alert information — a place for time-sensitive notices.
• Public records / FOIA request instructions.
• Job postings, bids, and RFPs.

A useful planning exercise: list the top 20 tasks residents perform, then map each to a page. If a task takes more than two clicks from the homepage, the navigation needs rework.

Accessibility and Compliance Expectations

Government sites are generally held to accessibility standards such as WCAG and, in the U.S., Section 508. You don't need to memorize the spec, but you do need to plan for it:

• Text alternatives for images and icons.
• Keyboard navigation for every interactive element.
• Sufficient color contrast — check your brand palette before locking the design.
• Accessible PDFs — scanned documents are a common failure point; plan a remediation process.
• Plain-language writing — short sentences, defined acronyms, no jargon.

Accessibility is easier to build in from the start than to retrofit. Treat it as a design constraint, not a final QA step.

Choosing a CMS for Non-Technical Staff

Most municipal content is updated by staff who are not web developers. The CMS should support:

• Publishing by non-technical users with a simple editor.
• Role-based permissions and approval workflows, so a department can draft while a communications lead approves.
• Scheduled publishing for notices with deadlines.
• Version history and audit trails.
• Long-term maintainability — an active vendor, documented updates, and a clear migration path.

Revize, the source for this topic, positions itself as a municipal website design company and CMS provider serving government clients. When evaluating any vendor in this space, ask the same questions: Who updates the site day to day? What happens when a staff member leaves? How are security patches handled?

Common Pitfalls to Avoid

• Outdated PDFs as the primary content format — they're hard to search, hard to read on mobile, and often inaccessible.
• Buried contact information — residents should not have to hunt for a phone number.
• Mobile-unfriendly service pages — most residents arrive on a phone.
• Department silos — inconsistent navigation and duplicate content across sections.
• No content ownership — pages that go stale because no one is responsible.
• Launch-and-abandon — a redesign without a plan for ongoing updates and training.

A Practical Starting Checklist

1. Inventory the top resident tasks and map them to pages.
2. Audit existing content for accuracy, duplication, and accessibility.
3. Define accessibility and plain-language standards before design.
4. Select a CMS with role-based publishing and approval workflows.
5. Assign a content owner for each department section.
6. Plan a post-launch training and review cycle.

If you handle these six items before design begins, the visual and technical work becomes far more straightforward — and the site is more likely to actually serve the people who use it.

A government or municipal website is a public-service platform, not a marketing site. Before you build or redesign one, plan for four things that rarely appear on a business site: accessibility compliance, public-records and transparency obligations, a document-heavy content model (agendas, minutes, permits, ordinances), and procurement rules that shape who can bid and how the project is managed. If your project is a small town site with a handful of pages, the same four apply — just at a smaller scale. The sections below cover what each one changes in practice, plus how to choose a CMS and run the redesign.

How a municipal site differs from a business site

The practical consequence: decisions that are cosmetic on a business site — URL structure, document naming, who can publish — become governance questions on a municipal site.

Core features a city or local government site needs

• Meeting agendas and minutes, posted on a predictable schedule and archived by date, with the meeting body (council, planning commission, board) clearly labeled.
• Public documents: ordinances, resolutions, budgets, bids/RFPs, and forms — ideally in a searchable document library rather than scattered PDFs.
• Permits and licenses: what's required, how to apply, fees, and status where the process allows it.
• Staff and department directories: who to contact, for what, and how — with roles that survive staff turnover.
• News, alerts, and notices: emergency notices, road closures, public hearings.
• Payments and service requests where the jurisdiction supports them (utility bills, taxes, reporting a problem).
• Calendar consolidating public meetings and community events.
• Search that works on documents, not just pages — residents usually arrive looking for a specific form or record.

Choosing a CMS: municipal-specific vs general-purpose

There is no single correct answer; it depends on your publishing volume, IT capacity, and procurement constraints.

A CMS built for municipalities tends to fit when:

• You need agenda/minutes workflows and document archiving out of the box.
• Many non-technical staff across departments will publish.
• You want accessibility features and compliance tooling built into the authoring experience rather than bolted on.
• You prefer a vendor who already understands government procurement and records practices.

A general-purpose CMS can work when:

• You have in-house developers or a strong IT department to configure and maintain it.
• Your content model is simple and your publishing team is small.
• You need tight integration with systems you already run and are prepared to build the government-specific pieces yourself.

Evaluate both against the same criteria: accessibility conformance, document management, multi-department permissions, search quality, hosting and security, migration support, and total cost over the contract term. Ask each vendor to demonstrate a real agenda-to-archive workflow, not a slide.

Accessibility and compliance considerations

Accessibility is the requirement most likely to change your design and content decisions, so treat it as a constraint from day one rather than a cleanup task.

• Target a recognized standard (commonly WCAG 2.x at the level your jurisdiction or funder requires) and state it in the RFP so vendors respond to the same bar.
• Plan for accessible documents, not just accessible pages. A scanned, untagged PDF of a meeting packet is a common failure point; build a process for producing tagged, readable documents.
• Budget for ongoing testing and remediation — every new page and uploaded file can introduce a new issue.
• Consider captioning and transcripts for public meeting video, and plain-language alternatives for complex notices.
• Keep an accessible way to contact the government for anyone who cannot use the site.

Accessibility also interacts with procurement: if conformance is a contract requirement with defined acceptance testing, you have recourse when deliverables fall short.

Typical steps and stakeholders in a municipal redesign

1. Define the project and the decision-makers. Identify an executive sponsor (often the city manager or an equivalent), a project lead, and a working group with representatives from IT, communications, the clerk's office, and major departments.
2. Inventory content and documents. You will find duplicates, outdated PDFs, and orphaned pages. Decide what is migrated, rewritten, or retired — this is usually the largest hidden cost.
3. Write requirements, including accessibility and records. Specify the CMS capabilities, document workflows, integrations, hosting, security, training, and support you need.
4. Run procurement. Follow your jurisdiction's rules for RFPs, evaluation criteria, and vendor selection; publish the timeline.
5. Design with residents, not just staff. Test navigation and search with realistic tasks ("find the permit for a fence," "read last month's council minutes").
6. Migrate and redirect. Preserve URLs where possible and set up redirects so public links and citations don't break.
7. Train publishers across departments and document who owns which section.
8. Launch, then maintain. Schedule content reviews, accessibility audits, and a plan for the next refresh.

Common pitfalls to plan around

• Underestimating document migration. Meeting archives and permit forms are often the bulk of the work.
• Treating accessibility as a final QA step instead of a design and authoring requirement.
• No content ownership after launch, so pages go stale and residents lose trust in the site.
• Broken public links from a redesign that changes URL structure without redirects.
• Assuming a new CMS fixes content problems — it doesn't; the content model and governance do.

If you are early in the process, the highest-value first step is a content and document inventory plus a written accessibility target. Those two artifacts shape your requirements, your budget, and your vendor questions more than any feature list.

e-Gov (electronic government) is the delivery of government information and services through digital channels, most visibly through public-facing municipal and agency websites. It affects design because an e-Gov site is not just a marketing presence — it is a service delivery tool. That means accessibility, transparency, and public trust requirements drive decisions that a typical business site never has to make. If your municipality mainly publishes meeting minutes and office hours, a standard informational site may be enough. If residents are expected to apply for permits, pay fees, or find records online, you need an e-Gov approach.

What separates an e-Gov site from a business site

The core difference is the audience and the obligation. A business site optimizes for conversion; an e-Gov site optimizes for equitable access to services that residents are entitled to use.

Why accessibility, transparency, and trust shape the design

Accessibility

Because government services must be usable by everyone, accessibility is a design constraint from the start — not a retrofit. In practice this means semantic HTML, keyboard navigation, sufficient color contrast, readable font sizing, and text alternatives for images. If a resident cannot complete a form with a screen reader, the service is effectively unavailable to them.

Transparency

e-Gov sites carry public records: agendas, budgets, ordinances, bids, and notices. Design has to make these findable and durable. That usually means a clear information architecture, stable URLs for documents, and an archive structure that does not bury older material.

Public trust

Residents judge a government site differently than a storefront. Consistent navigation, plain language, visible contact information, and a clear sense of who published what all reduce the friction that erodes trust. A confusing municipal site reads as an inaccessible government, not just a bad website.

Common features of e-Gov sites

• Service portals — permit applications, license renewals, utility payments, and report-a-problem forms
• Document access — meeting minutes, agendas, budgets, and public records, often with search
• Multilingual support — translated content or language toggles for diverse populations
• Notices and alerts — emergency information, public hearings, and service disruptions
• Department directories — staff contacts and responsibilities organized by function
• Accessibility statements and compliance pages — required disclosures about how the site meets standards

Compliance and procurement differences

Two things reliably distinguish an e-Gov project from a private-sector build:

1. Compliance obligations. Government sites are typically held to accessibility standards and public-records rules that private sites are not. These are design inputs, not afterthoughts.
2. Procurement process. Municipalities often must follow public bidding, request-for-proposal, or contract approval processes. That changes the timeline and the vendor relationship compared with a business buying a website directly.

A content management system matters more here than on a business site, because non-technical staff across departments need to publish and update content without breaking accessibility or structure.

When you need a dedicated e-Gov approach

Use a dedicated e-Gov approach when residents are expected to transact with government online — applying, paying, submitting, or retrieving records — or when the site must meet formal accessibility and transparency obligations.

A standard informational site is usually sufficient when the site's job is limited to publishing static information: office hours, contact details, and basic announcements, with no online services and no formal compliance mandate.

The deciding question is not how large the municipality is, but what residents are expected to do on the site.

Getting a business website designed involves more than picking colours and fonts. A typical project runs through five phases: planning and content gathering, structure and wireframing, visual design, build and technical setup (domain, hosting, email), and launch with ongoing maintenance. The design work itself is only one part of the process — and the decisions you make early on, especially about structure and platform, directly determine how straightforward your domain, hosting, and connectivity setup will be later.

This guide walks through the whole sequence so you can plan realistically before you contact a designer or developer.

Phase 1: Planning and Content Gathering

Most delays in website projects come from content, not code. Before any design starts, you need to answer some basic questions and assemble raw material.

Questions to settle first

• What is the site for? A brochure site that generates enquiries, an online shop, a booking system, or a portfolio all lead to very different builds.
• Who is it for? The audience shapes tone, structure, and how much explanation each page needs.
• What does success look like? Enquiry form submissions, phone calls, online sales, or simply credibility when someone searches your business name.
• Who maintains it afterwards? If you want to edit text and images yourself, that pushes the project toward a content management system (CMS) rather than hand-coded pages.

Content to prepare before design begins

A designer can work with placeholder text, but the site will be better and faster to finish if you supply:

• Your logo in a vector format (SVG, AI, or EPS) if you have one
• Company description in short, medium, and long versions
• Service or product list with a sentence or two on each
• Contact details, opening hours, and location information
• Photographs — ideally original, high-resolution images of your team, premises, or products
• Any legal text you are required to display, such as a privacy policy

If you do not have photography, say so early. It affects both the design approach and the timeline.

Phase 2: Structure and Wireframing

Before visual design, the pages and their relationships need to be mapped out. This is usually called the sitemap and wireframe stage.

• Sitemap: a list of every page and how they nest. A typical small business site might have Home, About, Services (with sub-pages), Case Studies, and Contact.
• Wireframes: simple, unstyled layouts showing where headings, text, images, and buttons sit on each page type. No colours or fonts yet.

This stage is where you catch problems cheaply. If a page has no clear purpose, or if the navigation is confusing on paper, it will be worse once designed. Approving wireframes before visual design saves significant rework.

A note on mobile

Design should be planned mobile-first or at least mobile-aware from this stage. Most small business traffic now arrives on phones, and a layout that only works on a wide desktop screen will need to be redesigned, not just resized.

Phase 3: Visual Design

With structure agreed, the designer applies branding: typography, colour, imagery style, and spacing. You will typically see one or two key page designs first — usually the homepage and an inner page — before the rest are produced.

Things worth deciding at this point:

• Brand consistency: does the site match your existing signage, stationery, and social profiles?
• Accessibility: sufficient colour contrast and readable text sizes are not optional extras; they affect how many people can actually use the site.
• Calls to action: every page should make the next step obvious, whether that is calling, enquiring, or buying.

Expect at least one round of revisions. Two rounds is common; unlimited revisions usually signal a project that will drift.

Phase 4: Build and Technical Setup

This is where design meets infrastructure, and where choices start to have long-term consequences.

Domain names

Your domain is your address on the web. Points to settle:

• Do you already own it? If so, confirm you have login access to the registrar — not just the designer.
• Who should own it? The business should. A domain registered in a developer's name is a common and avoidable problem.
• Which extension? .co.uk and .com are the usual choices for UK businesses. Registering both and redirecting one to the other is a reasonable precaution.

Hosting

Hosting is the server space where the site lives. The right choice depends on the build:

Ask specifically about backups, uptime expectations, SSL certificates (the padlock in the browser), and what happens if you want to move the site later.

Email and connectivity

Your domain usually carries your business email, so email setup should be planned alongside the website, not after it. If staff work from an office, the broadband connection at that location affects how comfortably you can upload content, use cloud tools, and take video calls. Fibre availability varies by premises, so it is worth checking what is actually available at your address rather than assuming.

Build and testing

Before launch, the site should be tested on real devices, checked for broken links, and reviewed for spelling and grammar. Forms need to be submitted and confirmed as arriving in the right inbox. This stage is unglamorous but it is where most launch-day surprises are prevented.

Phase 5: Launch and Aftercare

Launch itself is usually quick: the site is moved to live hosting, the domain is pointed at it, and SSL is confirmed. The work that follows matters more.

• Backups: confirm they run automatically and that you know how to restore one.
• Updates: if the site uses a CMS, software and plugins need updating to stay secure.
• Analytics: some form of traffic measurement helps you judge whether the site is doing its job.
• Content ownership: make sure you have admin access to the CMS, the domain registrar, and the hosting account.

Roles and Responsibilities: Who Does What

Clear division of labour prevents most disputes. A typical split looks like this:

The most important principle: you should own your domain, hosting, and content, even if the provider manages them day to day.

Common Pitfalls That Delay Projects

• Content arriving late, especially photography and legal text
• Feedback coming from too many people with no single decision-maker
• Changing the scope midway — adding a shop or a booking system after design has started
• Domain or hosting registered in the provider's name
• No plan for who updates the site after launch
• Choosing a platform that cannot grow with the business

A Practical Pre-Project Checklist

Before you approach a designer or developer, have these ready:

1. A one-paragraph description of your business and what the site must achieve
2. A list of pages you think you need
3. Your logo files and any brand guidelines
4. At least some original photography, or a budget decision about sourcing it
5. Confirmation of who owns your current domain, if you have one
6. A named decision-maker on your side
7. A rough timeline and a realistic view of when you can supply content

Working through these phases in order — plan, structure, design, build, launch — keeps a website project predictable. The design is the visible part, but the planning and the technical setup underneath are what determine whether the site launches on time and remains useful afterwards.

If you are working with a limited budget, the short answer is this: choose a ready-made responsive website template when your site is a straightforward brochure, portfolio, or landing page and you can live with its existing structure. Choose a custom website when you need unusual functionality, a distinctive user flow, or a design that must scale with a growing business. For most small budgets, a template gets you online faster and cheaper; custom work buys flexibility you may not need yet.

What You Are Actually Comparing

These two options are not just different price points — they are different products.

A website template is a pre-built design (layout, typography, colour scheme, page structures) that you adapt by swapping in your own text, images, and branding. A custom website is designed and built around your specific requirements, usually by a web designer or developer.

The trade-off is almost always: money and time versus flexibility and uniqueness.

Cost and Time: The Realistic Difference

Exact figures vary widely by provider, region, and complexity, so treat any specific number — including "starting at" prices — as a starting point to verify, not a final budget.

What You Can and Cannot Change in a Template

This is where most budget buyers get surprised. A template is not infinitely editable.

Usually easy to change:

• Text, headings, and images
• Logo and brand colours (within the template's palette system)
• Contact details, social links, and basic SEO fields
• Adding or removing standard sections that the template already supports

Often difficult or impossible without custom work:

• The overall page grid and layout structure
• Adding a page type the template was never designed for
• Complex booking, membership, or e-commerce logic
• Unique interactive elements or animations
• Deep integration with third-party business systems

Before buying, ask directly: "Which parts of this template can I edit myself, and which require a developer?"

When a Template Is the Right Call

A template is usually sufficient when:

• You need a simple brochure site — home, about, services, contact.
• You are building a portfolio where images do the talking.
• You need a single landing page for a campaign or product.
• You want to test an idea before investing in a full build.
• Your budget is genuinely tight and speed matters more than originality.

In these cases, paying for custom design is often money spent on problems you do not have.

When Custom Is Worth the Money

Custom becomes justified when:

• You need functionality a template does not offer — custom calculators, portals, booking flows, or membership areas.
• Your user journey is unusual and a standard layout would confuse visitors.
• Your brand depends on a distinctive look that a widely used template cannot deliver.
• You expect significant growth and need a structure that can expand without a rebuild.
• You need specific integrations with existing business tools.

If two or more of these apply, a template may cost you more in workarounds than a custom build would have cost upfront.

Do Not Forget the Ongoing Side

The purchase price is only part of the picture. Ask about:

• Hosting — who provides it, and what happens if you outgrow it?
• Updates — who applies security and compatibility updates, and how often?
• Maintenance — if something breaks, who fixes it, and is that included?
• Ownership — do you own the design and content if you leave?
• Support — is there a free trial, a support window, or a paid retainer?

A cheap template with no support can become expensive the first time it breaks.

A Short Checklist Before You Commit

Ask any provider — template seller or custom designer — these questions:

1. What exactly is included in the price, and what costs extra?
2. Can I edit text, images, and layout myself? How?
3. Is the design mobile-friendly and responsive by default?
4. Who handles hosting, updates, and security?
5. What happens if I want to change the structure later?
6. Do I own the site and can I move it elsewhere?
7. Is there a trial, refund, or cancellation policy?
8. How long until the site is live?

Bottom Line

On a small budget, start with a responsive template if your needs are standard and your priority is getting online quickly. Move to a custom website only when your requirements genuinely exceed what a template can do — unusual functionality, a unique user flow, or long-term scalability. Match the tool to the job, and verify the ongoing costs before you pay, not after.