Discover and audit
Owner · Kimply teamWe measure the site you have before we touch it.
- WCAG 2.1 AA accessibility audit of the current site
- Inventory of every page, PDF, and form
- Search Console and GA4 baseline
- Interviews with department leads
A five-stage method for redesigning public-sector websites. Every stage has one accountable owner, a fixed list of deliverables, and a written record your team can audit.
LAST UPDATED: NOVEMBER 2026
01 · Stages and deliverables
We measure the site you have before we touch it.
Every requirement is written down and approved before a line of code.
Accessible, mobile-first templates your staff can update without a developer.
Plain-language pages that residents understand and search engines can find.
A clean cutover, trained staff, and a plan for what comes next.
02 · Who does what
City staff time is limited. This split keeps your team in the approval seat without doing the heavy lifting.
| Work | Kimply | Your team |
|---|---|---|
| Accessibility audit | Leads and delivers | Provides site access |
| Requirements and sitemap | Drafts the spec | Reviews and approves each decision card |
| Design and development | Builds and tests | Reviews at set milestones |
| Content rewrites | Writes and optimizes | Fact-checks department details |
| Launch and redirects | Plans and executes | Approves go-live date |
| Ongoing updates | Trains staff, optional support | Owns day-to-day updates |
03 · Why it works
Requirements are written, reviewed, and approved in Crema Spec. Nothing gets built on a guess.
Every approval is logged with its reason. That record supports procurement, audits, and council questions.
Writers start at the audit, not the week before launch. Pages ship accurate, plain, and searchable.
Your staff can update the site without a developer, and they leave training with a style guide.
04 · Forward-deployed engineering
Before our team automated a single workflow, we read the inbox. Every exception and rule was captured first.
We bring the same depth to a city website audit. Every page, PDF, and form gets counted before anything moves.
05 · FAQ
Forward-deployed engineering puts engineers inside a customer's team so they build where the work happens. Kimply embeds for about 90 days, builds the fix, then turns it into a repeatable product. We call it embed, build, productize.
We test the current site against WCAG 2.1 Level AA, inventory every page, PDF, and form, and record search and analytics baselines. You get a prioritized list of issues before any redesign work begins.
Your team does. Every requirement is written as a decision card in Crema Spec, sized for a 25-minute review, and logged with its reason once approved.
Yes. We inventory, clean up, and migrate content, and we rebuild key PDFs as accessible web pages where possible. A redirect map keeps old links working.
Yes. Sites are built on a CMS your staff can run without a developer, and every launch includes training and a content style guide.
Next step
Send us your RFP or scope. We will map it to the five stages and show you the plan.