Public works wants staff to reuse a vetted prompt for drafting standard public-meeting summaries. Which prompt management action fits?

Public works should save the approved prompt so municipal staff can reuse the vetted meeting-summary pattern. Prompt management fundamentals include capturing successful, policy-aligned prompts so teams do not reinvent wording for recurring civic work such as standard public-meeting summaries. Saving the vetted prompt reduces inconsistency, speeds drafting, and keeps staff closer to language that communications or legal stakeholders already accepted.

Saving the prompt as a private draft so individual staff can test the meeting-summary pattern fails because it keeps the vetted prompt private and in draft form rather than making it available as a shared reusable asset, limiting team-wide consistency for standard public-meeting summaries. Placing the approved prompt in review queue so municipal staff await the meeting-summary pattern fails because an already vetted prompt does not need further approval, and holding it in review delays reuse instead of providing staff immediate access to the standard pattern. Copying the approved prompt to a new draft so municipal staff edit the meeting-summary pattern fails because it invites edits that break the standard, reintroduces inconsistency, and negates the value of a vetted municipal prompt that staff should reuse as-is.

Exam caveat: AB-900 Domain 3 covers managing prompts (save, share, schedule, delete). Saving approved prompts is a first-class admin/maker practice. Do not confuse “prompt management” with saving prompts as private drafts, placing approved prompts in review queue, or copying the approved prompt to a new draft to edit—actions that undermine reuse and consistency in Copilot.

Operational check: Place the vetted public-meeting summary prompt in the approved prompt location public works staff can access, name it clearly with version or effective date, confirm it contains no stale fee or policy text, brief staff once on when to use it, and revisit the prompt after the next charter or template change so the saved pattern stays current.