Define exactly what the assistant may do.

A useful starting scope might summarize an approved public document, draft a routine update from verified facts or suggest a request category for staff review. Name the allowed inputs, output, reviewer and next action. “Help staff with AI” is too vague to evaluate.

A generated suggestion should enter a draft state. The system’s permissions determine whether it can send, publish or update a record. A message saying “please review” is not an approval control if an automated action has already taken place.

Eligibility decisions, enforcement, emergency triage and other consequential actions need a separate assessment of authority, impact and applicable requirements. They do not belong inside a routine drafting pilot merely because the interface looks similar.

Read the industry evidence at its actual scope.

The OECD’s 2025 Governing with Artificial Intelligence report (opens in a new tab) examines 200 use cases across 11 government functions. It identifies uneven maturity and implementation challenges. This is a cross-government research synthesis, not a representative municipal savings benchmark or evidence that a particular local deployment will succeed.

NIST’s July 2024 Generative AI Profile, NIST AI 600-1 (opens in a new tab) describes risks including fabricated outputs, privacy and overreliance. Its suggested actions include checking sources and assessing behavior in relevant conditions. This is risk-management guidance, not a product certification.

The operational model below is Civicfield’s proposed planning approach informed by those references. It is not a study result, a government endorsement or a report of client performance.

Make approval an observable decision.

StepRequired evidence or controlAccountable role
Source selectionApproved material, revision and permission to use the dataService/content owner.
Draft generationSource-linked output, clear draft status and bounded taskAuthorized staff user.
ReviewCheck facts, omissions, tone, destination and appropriatenessReviewer with subject knowledge.
AuthorizationApprove the exact revision and permitted actionNamed authorized approver.
ExecutionAct only on that approved version; re-review material changesPublisher or permitted workflow step.
MonitoringCheck the live result, errors and complaints; provide stop pathOperational owner and backup.

On a small screen, scroll the table sideways to see every column.

Keep generation, factual review and action authorization distinct even if one person holds several roles. The record must show what was approved. If the facts change, an approval for the previous draft should not automatically authorize the replacement.

An authorized reviewer and publisher compare the same marked-up draft and source document before publication, candid close office photograph of their practical review.
Authorizing an exact draft before publication.

Worked example: an internal draft of a service update.

Fictional Cedar Bay example. Staff provide an approved notice stating that a service desk will change location on a specified date. The assistant proposes a web paragraph and a short social version, each linked to the source revision. It has no permission to publish.

The reviewer checks the location, effective date, affected services and assistance instructions against the notice. If the source does not state an opening time, the draft must not invent one. The reviewer either obtains the fact or revises the text to avoid an unsupported claim.

The approver authorizes the exact versions and channels. A publisher checks that the live page and scheduled material match. Later changes follow the correction process. This example defines the controls to test; it claims no measured time saving.

Test failures as deliberately as normal cases.

  • An outdated source conflicts with a newer approved notice: the conflict must be surfaced.
  • A requested fact is missing: the draft must not fill the gap with a plausible invention.
  • A source includes text telling the assistant to ignore its task: treat source text as data, not new authority.
  • A person lacks publication permission: a generated draft must not bypass access controls.
  • A reviewer changes the meaning after approval: require a new decision for the changed version.
  • A connection fails: preserve draft state and prevent a retry from producing duplicate public actions.

Use approved sample data and defined expected behavior. Record correct outputs, errors, review time, rejected drafts and operator confusion. A model’s confidence statement is not a calibrated reliability measure. Check the actual evidence and the complete workflow.

Limit inputs and retain a manual route.

Use only the data authorized for the chosen tool and purpose. Confirm account settings, storage, access, retention and provider terms through the agency’s review process before entering operational records. Begin with approved public or fictional content when that is sufficient for the pilot.

Define who can pause the assistant, what happens to queued drafts and how staff continue manually. Reviewers need enough time and context to disagree with the output. A compulsory approval click with no source visibility encourages a rubber stamp.

Use the pilot planning record and measurement definitions to evaluate whether the bounded assistance is useful. Compare the total work, including verification and correction, before expanding the scope.

A staff member continues an ordinary service task using an organized paper checklist and source binder with a laptop to the side.
Keeping a manual route available.