Give the public answer a responsible owner.
A website team can manage templates without knowing whether a permit instruction or program deadline is correct. The department responsible for the service needs to own the facts. A content owner coordinates that relationship and ensures there is a next review or update action.
Digital.gov’s account of website management at GSA (opens in a new tab) describes the problems caused by unclear responsibility and the work of defining an accountable role. It concerns federal website management, not a staffing rule for every municipality. The model below is a practical starting point to adapt with your team.
Verify the underlying facts using the source-check worksheet. When preparation capacity is the bottleneck, compare content operating models.
Assign decisions, not just job titles.
| Responsibility | Decision or evidence | Backup to identify |
|---|---|---|
| Service fact owner | Confirms hours, requirements, locations and effective changes. | Another authorized subject-matter reviewer. |
| Content editor | Prepares clear text, links, visuals and accessible alternatives. | An editor with access to the same source record. |
| Approver | Authorizes the exact version and intended channels. | An explicitly authorized alternate approver. |
| Publisher | Publishes or schedules the approved revision and checks the live result. | Someone with appropriate publishing access. |
| Website/content lead | Resolves ownerless content and coordinates standards and review priorities. | A named escalation owner for unresolved decisions. |
On a small screen, scroll the table sideways to see every column.
One person can hold several responsibilities in a small team. Record when the same person performs both checks so the process remains honest. Where an agency requires independent review, access and staffing need to support that requirement.
Use one record that follows the update.
For a changing public fact, record the item, source, responsible service, affected pages and channels, proposed revision, fact reviewer, approval decision and publication check. Make the relationship between the source and each public version clear.
The content calendar workbook provides the detailed revision and source-check fields. Use it after deciding who is authorized to perform those steps. A workbook can record a decision; it does not grant a role permission to approve or publish.
Use the content audit to find pages with missing owners or uncertain facts before assigning an editorial calendar.

Set review triggers as well as dates.
A regular review date helps, but it should not be the only way information changes. Add triggers such as a new service policy, an amended deadline, a venue change, a staff departure or an organizer cancellation. Give the person receiving a trigger a clear route to the content owner.
Choose review frequency according to how quickly the information changes and the effect of an error. Record why a review is needed. A changed date stamp is not evidence that someone verified the service facts.
Digital.gov’s content lifecycle guidance (opens in a new tab) provides context for maintaining information after creation. Your review record should identify the actual source checked and the resulting action.
Agree on the urgent path before an urgent change.
Identify who can authorize a time-sensitive update, the alternate when that person is unavailable, which channels are appropriate and what happens when the source is incomplete. A faster workflow still needs an accountable decision and a record of the version published.
If a previously published detail is wrong, use a correction workflow that tracks every affected version. Urgent service information should use the agency’s approved communication procedure; a routine content service does not establish emergency-response authority.
Make reassignment part of normal operations.
When someone changes roles, transfer their owned items, pending approvals, scheduled posts and review tasks. Confirm the alternate has the required access. Remove the departed person’s access through the approved administration process and check for services tied to their account.
Review the governance record when a new channel, service or supplier is added. To choose communication priorities, use the social media strategy guide. For prepared materials or support implementing the agreed process, explore government content and social support.

Set review frequency from risk and change, with an owner.
Use consequence and likelihood of change to choose a review priority. A wrong eligibility instruction or imminent deadline deserves different attention from a stable background description. Assign a responsible source owner, the change triggers and a planned next check. There is no universal interval that makes every government page current.
A service owner should notify the content team when a policy, fee, contact route, form or location changes. A planned check catches changes that did not arrive through that route. Review translated pages, linked documents and scheduled versions as dependencies of the fact, not independent items that can be left behind.
The audit review model records priority, evidence and action. A source-verified change, an unchanged fact check and an editorial rewrite are different events. Preserve those meanings when using public date labels.

