Resident services platform
ClerkSite: resident task design ↗
Explore clear paths to records, requirements and visit preparation.
A public website residents can use and staff can run.
Plan the resident experience and publishing operation together: WordPress or Drupal, content migration, accessible forms and documents, multilingual workflows, hosting, training and support.
Resident experience
Staff publishing example
Resident services platform
Inspect the work.
Explore clear paths to records, requirements and visit preparation.
ClerkSite: a clearer county clerk experience ↗
County clerk services. Follow the workflow from the first step through the result.
Each example identifies its relationship, source and limitations. Founder prior-role work, separate ventures and synthetic demonstrations are distinguished from company client delivery.
Problems we can help solve
- Replace a difficult website or publishing workflow
- Make documents and online tasks accessible
- Connect service discovery, requests and reporting
Agree what ready means.
Acceptance is defined for your engagement. Examples of checks to agree before work begins:
Deliverables, timing, team availability, integrations and support coverage are confirmed in the written scope.
The optional staff workflow is a synthetic, in-browser demonstration. It is not a deployed municipal CMS, client delivery or a production publishing system.
Shape the scope
- A task-based site structure and accessible page designs
- WordPress or Drupal CMS roles, publishing workflows and editor training
- A content inventory, migration plan and redirect checks
- An agreed managed-hosting plan, including WP Engine where appropriate, launch checks and support responsibilities
- Your priority resident tasks and departmental content owners
- The current website, document inventory and integrations
- Publishing roles, review needs and procurement requirements
ClerkSite
Explore the demonstration
Publish a meeting notice
Change the draft, review the exact text, then publish it to the preview. Editing after review requires another review. Reloading resets the scenario.
Draft ready for review.
Resident preview
Council meeting details are being prepared.
Check a migration mapping
The fictional source /departments/public-works/trash must map to /services/waste in this agreed inventory. This check compares the mapping with that inventory; it does not make a live HTTP request.
- An editor completes an agreed draft, review and publishing task
- The migration inventory reconciles to its destinations and redirects
- Priority resident journeys are tested, with findings and retests recorded
- The receiving team reviews the runbook and agreed support responsibilities
Evidence for this kind of work
Synthetic planning sample
Migration and redirect plan ↗
Inspect source-to-destination mapping and proposed acceptance checks.
Planning guide
Ownership and handover guide ↗
Use the questions to define accounts, training, restore responsibilities and coverage.
Choose a starting scope
- 01Software, CMS and platform deliveryBuild a public website, application or internal platform. Modernize what your team already uses.
- 02Research, design and accessibility deliveryUnderstand a service, prototype an improvement and implement accessible experiences with test evidence.
- 03Data, dashboards and connected operationsConnect sources, reconcile the data and make decisions traceable through dashboards, maps or APIs.
What happens next
Bring the problem, desired outcome and timing. We confirm fit, access requirements and a proposed scope before commitment.
Discuss a public-service project ↗The first conversation identifies the decisions, constraints and evidence needed for a useful brief. The proposal then names deliverables, responsibilities, acceptance criteria and a fixed price for the agreed scope.