When the town needs to be trusted, the site has to deliver.
Residents do not visit to admire the homepage. They come to pay a bill, read a water advisory, find a council decision, apply for a permit, or reach the right person without guessing department names. Kootenay Made builds the public-facing civic layer around clarity, accessibility, transparency, and the kind of service delivery that holds up under pressure.
Best fit for small and mid-sized municipalities, regional districts, recreation and public service teams, and councils that want more than a locked template: a custom, accessible civic website that earns resident trust and grows with the community.
This category lives or dies on trust, not features.
Kootenay Made positions the municipal website as public trust infrastructure, not a brochure. It is the place residents go in a calm moment to pay a bill, and the place they go in a tense one to find out whether the water is safe or the road is open. We build it resident-first: plain-language service paths, an unmistakable emergency and notice centre, transparent council records, compassionate support routing for vulnerable moments, mobile and assistive-tech accessibility to WCAG 2.2 AA, FOIPPA-aware data handling, and room to add the services the community will need next. A clear civic site quietly tells residents the municipality is competent. That is the entire job.
- 01
Residents arrive with a task, not patience
They need a permit, a payment, a meeting date, a water notice, a road closure, a recreation schedule, a report form, or a phone number. The page wins when the answer appears before the irritation does. Every extra click is a phone call to staff.
- 02
Trust is operational, and it is fragile
A clear civic site quietly signals competence. A confusing one makes even accurate information feel unreliable, exactly when it matters most: during a boil-water advisory, a wildfire evacuation, a contentious rezoning, or a tax deadline. Residents judge the whole municipality by the site.
- 03
Accessibility is a duty, not a feature request
A meaningful share of residents rely on screen readers, captions, keyboard navigation, high contrast, or plain language. Under the Accessible British Columbia Act, removing those barriers is an obligation. A site that locks people out is not just bad design, it is a failure of public service.
- 04
Small teams need clarity they can maintain
Municipal staff cannot babysit a fragile site between budget meetings and emergencies. The system needs reusable service pages, predictable content families, plain-language templates, and editing patterns that protect the experience long after launch.
The systems staff already rely on does the plumbing. KMD wins the decision.
The goal is not to replace every civic system the municipality has invested in. It is to replace the public website layer with a clearer, accessible front door so residents, council, and community partners can actually find and use those services.
Most municipal teams already run capable back-office tools for tax and utility payments, GIS mapping, recreation registration, agenda and minutes management, alert distribution, and records. Those systems are not the problem. The problem is the public website wrapped around them: confusing navigation, buried notices, broken accessibility, and content that only makes sense to staff who already know the org chart.
What the category tool covers
- Emergency and notice distribution for water advisories, road closures, wildfire and flood updates, evacuations, and facility closures
- GIS maps, property tax and utility payments, recreation registration, facility booking, pet licences, permits, and service request intake
- Agendas, minutes, recordings, bylaws, budgets, reports, public hearing notices, and document libraries
- Plain-language routing so residents never need to know department names, software names, or internal process labels to get help
- A custom public site that can grow around local staff capacity, new programs, new notices, and rising public expectations
A platform shaped around how this business actually wins.
- 01
Resident task architecture
Build the site around what people actually need to do: pay, apply, report, register, book, search, contact, attend, read notices, and find support. High-frequency tasks get the shortest path, not the deepest menu.
- 02
Emergency and notice centre
One obvious, trusted place for water advisories, road closures, wildfire and flood updates, evacuation orders and alerts, facility closures, and preparedness guidance. Residents should never have to dig through a news archive when the situation is urgent.
- 03
Council, bylaws, and transparency
Organize agendas, minutes, recordings, bylaws, budgets, reports, public hearings, and elections so citizens can follow the process without knowing internal language. Open, findable records are how a council shows its work and keeps public confidence.
- 04
Permits, forms, and payments
Clear, accessible routes for building permits, business licences, property tax and utility payments, pet licences, service requests, and recreation registration. Payments hand off to secure, PCI-compliant processors, so the municipality is never holding card data it should not touch.
- 05
Community support hub
Compassionate routing for residents who do not know which department or program to search: crisis lines, housing, food, mental health, seniors, youth, newcomers, Indigenous resources, veterans, warming and cooling centres, and local partners. First-class paths, not a footer link.
- 06
Searchable self-service layer
Turn bylaws, forms, guides, fees, master plans, and the questions residents actually ask into a searchable, plain-language self-service layer that reduces call volume without hiding the human contact path for those who need it.
The standard that comes with every Empire build.
- Resident-first sitemap and high-frequency task architecture
- Custom civic homepage with an unmistakable emergency and notice centre
- Council, agenda, minutes, recording, bylaw, budget, and report structure
- Permits, payments, recreation, and service-request routing to secure systems
- Support hub for crisis, housing, mental health, seniors, youth, and newcomers
- Accessibility built to WCAG 2.2 AA: keyboard, screen reader, contrast, captions
- Plain-language content patterns and reusable templates for small teams
- URL inventory, redirect map, and launch QA so records and notices do not vanish
The rules, risks, and trust signals this industry cannot skip.
A site in this category is judged on more than looks. These are the obligations and reassurances I build in by default, so the business stays credible and protected.
Accessible British Columbia Act and WCAG 2.2 AA
Local governments are among the public sector organizations covered by the Accessible British Columbia Act, with accessibility committees and plans expected since 2023. We build to WCAG 2.2 Level AA, the recognized benchmark, so keyboard users, screen reader users, and people who rely on captions, contrast, and plain text can complete real tasks. We also include a working feedback path so residents can report barriers.
FOIPPA and Canadian data residency
Under the Freedom of Information and Protection of Privacy Act, personal information in a public body’s custody or control must generally be stored and accessed in Canada unless an exemption applies. We design forms, hosting, and integrations with that residency expectation in mind, minimize what personal data the public site collects, and flag where a Privacy Impact Assessment belongs. We help you stay aware of the difference between data stored in Canada and data still exposed to foreign legal access.
Plain language and public notice obligations
Municipalities carry statutory duties to publish public notices, bylaws, and hearing information clearly. We structure notices, council records, and service pages in plain language so they are genuinely findable and readable, which serves both the legal obligation and the accessibility one. The right notice should never be buried three menus deep.
Secure payments and PCI DSS
When residents pay property taxes, utilities, or licence fees, card data is handled by PCI DSS compliant payment processors and gateways, not stored on the municipal site itself. That keeps the security and liability burden with specialized providers and protects the municipality from breach exposure on transactions it should never hold directly.
CASL for civic email and alerts
Canada’s Anti-Spam Legislation can apply to municipal electronic messages, especially anything tied to commercial activity. We build alert and newsletter signups with clear consent, accurate sender identification, and a working unsubscribe path, so residents trust your emergency and update channels and the municipality stays on the right side of the rules.
Records, retention, and a clean migration
Bylaws, minutes, notices, and council records often carry retention obligations and long-term public value. A rebuild needs a URL inventory, redirect map, and document strategy so permits, bylaws, public notices, and high-traffic records do not disappear or break links overnight. Continuity of the public record is part of the trust.
See the City of Silvermere concept in the wild.
City of Silvermere is the fictional municipal build that proves the model: resident task architecture for the services people actually need, an unmistakable emergency and alert centre, transparent council and bylaw records, permits, forms, and online payments, and searchable documents, all wrapped in an accessible, plain-language experience.
- Resident task architecture for the top public services
- Emergency and alert centre for advisories and closures
- Council, bylaws, budgets, and transparency
- Permits, forms, and online payments
- Searchable documents and plain-language answers
- WCAG 2.2 AA and FOIPPA-aware by default
City of Silvermere is a fictional concept build created to demonstrate the category. No real municipality, resident data, council, or service outcomes should be implied.
Where the upgrade actually pays off.
- 01
Use custom code to remove the ceiling: if the municipality needs a service hub, alert centre, application flow, map embed, searchable library, or integration, the site can be built for it instead of fought against a rigid template.
- 02
Treat the emergency and notice centre as the single most important page: when a water advisory or evacuation hits, residents should find one obvious place they already trust, not a scramble across social media.
- 03
Make human support civic infrastructure, not a footer link: crisis lines, housing, food, mental health, seniors, youth, newcomers, and Indigenous resources deserve first-class, plain-language paths.
- 04
Build accessibility and continuity in from day one: WCAG 2.2 AA, FOIPPA-aware data handling, and a redirect plan are far cheaper as foundations than as retrofits after a complaint or a broken-link audit.
Build the site this category actually deserves.
Best fit for small and mid-sized municipalities, regional districts, recreation and public service teams, and councils that want more than a locked template: a custom, accessible civic website that earns resident trust and grows with the community.
What owners in this field ask first.
What should a municipal website actually improve?+
It should reduce phone calls and confusion, make high-frequency services easy to complete, keep emergency information unmistakable, make council records findable, meet accessibility obligations, and give a small staff a maintainable structure that does not collapse into a document dump after launch.
How do you handle accessibility and the Accessible British Columbia Act?+
We build to WCAG 2.2 Level AA, the recognized benchmark in Canada: keyboard navigation, screen reader support, sufficient contrast, captions, and plain language. Local governments are covered by the Accessible British Columbia Act and expected to address digital barriers and provide a feedback path, so we bake that in rather than bolting it on after a complaint.
What about FOIPPA, privacy, and where resident data is stored?+
FOIPPA generally requires personal information in a public body’s custody or control to be stored and accessed in Canada unless an exemption applies. We minimize what the public site collects, design forms and hosting with that residency expectation in mind, and flag where a Privacy Impact Assessment belongs. We are not your legal advisor, but we build so the privacy questions are easy to answer.
Can a smaller municipality afford a custom civic website?+
That is exactly the point. We do not need to sell a giant enterprise suite to deliver a serious municipal experience. Scope can start with the public site, resident self-service, the emergency centre, accessibility, and clean handoff, then expand into forms, alerts, payments, maps, or integrations when they make sense.
What happens to our payments, recreation, maps, alerts, and forms?+
The systems that work can stay. We replace the confusing public website layer, then give residents clean, accessible routes into tax and utility payments, recreation registration, alert signups, GIS maps, and document libraries. Card payments hand off to PCI DSS compliant processors, so the municipality is not storing payment data it should not hold.
How do you protect important old pages and records during a rebuild?+
A municipal rebuild needs a URL inventory, redirect map, sitemap plan, document strategy, search checks, and launch QA so permits, bylaws, public notices, and council records do not vanish or break links overnight. Continuity of the public record is treated as part of the project, not an afterthought.
Can the site handle emergency communication people will trust?+
Yes. The public site includes a clear emergency and notice centre with routes for water advisories, road closures, wildfire and flood updates, evacuations, facility closures, and preparedness, plus signup for external alert systems. The goal is one obvious place residents already trust before the pressure hits.
Do we have to worry about CASL for our newsletters and alerts?+
Canada’s Anti-Spam Legislation can apply to municipal electronic messages. We build signups with clear consent, accurate sender identification, and a working unsubscribe path, so your update and emergency channels stay trusted and compliant. The result is higher resident confidence in the messages you send.