Website · November 4, 2026 · 6 min read
Keep municipal service pages current: a checklist for departments and web editors
Give staff a clear place to maintain service requirements, fees, forms and application steps. Use AI to prepare a draft from approved documents, then have the department check it before publication.
By Altioras Civic
Key takeaways
- Give each service page a named department owner and link its instructions to the approved policy, fee schedule and form.
- Ask AI to draft individual page fields and list missing answers. Have staff check every requirement and amount against the source.
- Test the published page through to the correct application or payment screen, and record who will update it when the service changes.
Start with a page that sends residents back to the counter
A resident reads the application page, downloads the form and finds a different list of required documents. The page shows an old fee. The Apply button opens a portal without explaining which service to choose. Staff then have to explain the process by phone or at the counter.
Choose one service with that kind of mismatch. Have the department employee who handles applications sit down with the web editor. Work through what a resident needs to know before starting, what they must submit and what happens afterward. Keep the approved policy, current form and fee schedule open beside the page.
This department involvement is part of the website work itself. In its March 2026 project announcement, West Chicago described bringing in staff who regularly assist residents to identify where people struggle online.
Agree on the answers before rewriting the page
Put the service instructions under consistent headings so staff can check one part without hunting through a long paragraph. NYC's web content guide recommends organizing around the user's task, using plain sentences and keeping similar pages consistent. The checklist below is a proposed way to apply those principles to a municipal service page.
Use a title that names the task, such as Apply for a driveway permit. Keep internal notes about approvals and source documents out of the resident's instructions. A department owner should settle conflicting requirements before the web editor publishes a replacement page.
| Page content | What to check | Who reviews it |
|---|---|---|
| Who can apply | Compare eligibility and exclusions with the approved policy. Keep exceptions that affect whether the resident can apply. | Department service owner |
| What to prepare | Compare the document list with the current application form and staff checklist. Explain which items apply only to certain applications. | Employee who checks applications |
| What it costs | Match each amount and effective date to the approved fee schedule. Explain variable charges without inventing an estimate. | Finance and the service owner |
| How to apply | Open the linked form or portal. Confirm the service name, submission route and any required account. | Service owner and web editor |
| What happens next | Check the submission confirmation, review steps and contact route. Publish a turnaround time only if the department has approved it. | Department supervisor |
| Where to get help | Verify the service email or phone, office hours and available alternative application route. | Department service owner |
| Who maintains the page | Record the owner, source links, date checked and next review date in the internal page record. | Web editor and department supervisor |
Sources: NYC Digital Design System — NYC web content style guide
Have AI draft the fields, then check what it left out
Altioras Civic's AI-first approach starts with approved material for this one service. Give a separately approved AI tool the current public instructions, form and fee schedule, identified by document title, version and section. Exclude resident applications and personal information. Ask it to draft the agreed page fields, attach a source reference to each answer and list questions the documents do not resolve.
For example, in a hypothetical permit page, the approved documents might describe an application fee but say nothing about an inspection charge. The draft should mark the inspection-charge question for the department. It must not treat silence as a zero charge or say that inspections are included.
Have the service owner compare every requirement with the cited section. Have Finance check fees against the adopted schedule using the municipality's normal checks, without asking AI to calculate or approve them. The web editor checks the wording and links. Reject unsupported statements, omitted exceptions and promises the department has not approved. A shorter draft is useful only if the resident still receives the instructions needed to apply.
The department approves the final instructions and any translations through its established process. This proposed method uses an external AI tool; staff then review the draft in the CMS.
From approved instructions to a checked service page
- Step 1Gather the sourcesService owner selects the current policy, form and fee schedule.
- Step 2Draft the fieldsAI proposes page text, source references and unanswered questions.
- Step 3Check and approveDepartment checks requirements; Finance checks fees; editor checks wording.
- Step 4Publish and testAuthorized editor publishes, follows the links and records the next review.
Give editors fields they can maintain in Payload
In a proposed Payload CMS build, a developer could define separate fields for eligibility, required documents, application steps, fees and contact details. Add internal fields for the department owner, source references and review dates. Payload's field definitions determine the stored document structure and generate the corresponding editing interface; the municipal service template and its public presentation still have to be designed and built.
Where Versions with Drafts is enabled, staff can save unpublished changes. Developers can configure access rules for different operations. The team must still implement and test who may edit, approve and publish. Turning on drafts does not, by itself, create the municipality's approval process.
Test a fee change with actual editor accounts before accepting the setup. Confirm the draft remains private, the authorized publisher can release it, and the public template displays the right amount and effective date. Any AI import, reminder or check against another system is additional integration or custom work. Teams using another CMS can apply the same content checklist after confirming how that platform handles fields and permissions.
Sources: Payload documentation — Fields Overview; Payload documentation — Drafts; Payload documentation — Access Control
Test the resident's next step and name the next update
After publication, ask a colleague unfamiliar with the draft to find the service, identify what to prepare and follow the application link on a phone. Stop before submitting a real application or payment. Check keyboard use, link labels and the downloadable form as well; structured fields do not replace accessibility testing.
Record the public URL, department approval and date checked. Agree which employee will notify the web editor when a policy, fee, form or portal instruction changes. Check other pages that repeat the same information. Keep the next scheduled review, but update sooner when the service changes.
Start with one page and use the checklist at a working session with its owner. If your team needs help designing the fields, reviewing AI drafts or testing publication, Altioras Civic's Website Modernization & Maintenance service can scope that work with your staff.
References
- NYC Digital Design System — NYC web content style guide (opens in a new tab)
- City of West Chicago — City of West Chicago Launches Digital Modernization Initiative and Invites Public Input (March 13, 2026) (opens in a new tab)
- Payload documentation — Fields Overview (opens in a new tab)
- Payload documentation — Drafts (opens in a new tab)
- Payload documentation — Access Control (opens in a new tab)