City fee-schedule language changes after council adoption. A clerk’s saved Copilot prompt still cites the old wording. What should the clerk do?

When city fee-schedule language changes after council adoption, a clerk’s saved Copilot prompt that still cites the old wording is an outdated control and must be corrected. The clerk should update the prompt with the new fee-schedule language and re-save it for reuse so subsequent drafts quote the adopted rates and phrasing. Prompt libraries are living municipal assets: when the authoritative fee ordinance or posted schedule changes, the saved instructions that cite those fees must change in lockstep to prevent Copilot from regenerating obsolete amounts for residents and counter staff.

Leaving the outdated saved prompt unchanged so Copilot keeps quoting obsolete fees fails accuracy and resident trust; staff would continue publishing wrong amounts after council action. Sharing the obsolete prompt citywide so every desk repeats the old fee language amplifies the error across departments. Deleting Microsoft 365 entirely because one prompt needs a wording update fails proportionality—the fix is a targeted prompt edit and re-save, not abandoning the tenant productivity suite.

Exam caveat: updating and re-saving the prompt does not automatically correct documents already generated from the old version; clerks must also refresh templates, posted PDFs, and in-flight drafts that may still carry pre-adoption language. Confirm the effective date of the new fee schedule before cutting over the prompt.

Operational check: after re-save, run the prompt against a sample fee inquiry, compare every cited amount and label to the council-adopted schedule, and spot-check that older saved prompt versions are retired or clearly marked superseded in the shared prompt library.