City communications wants leadership to pick among Copilot message variants in one place. What should they do?
Select an answer to reveal the explanation.
Short Explanation
Too many message drafts floating around? Consolidate Copilot variants on a city communications Page so leadership can pick. One page for comparison beats a maze of private chats.
Full Explanation
City communications often generates several Copilot message variants; leadership needs a side-by-side choice surface. Consolidating Copilot message variants on a city communications Page for leadership to choose is correct because Pages gather alternatives in one shared artifact where executives can compare tone, accuracy, and channel fit without hunting private threads. Municipal campaign messaging—emergency alerts, budget explainers, service changes—benefits from deliberate selection before anything ships.
Sending each variant in a separate private chat with no shared comparison fails decision hygiene; leaders cannot efficiently weigh options or leave durable selection notes. Publishing every draft variant publicly before leadership reviews any of them fails message control and can seed conflicting resident expectations. Discarding all variants and writing nothing for the campaign fails the communications mission; the need for a message remains even when drafts need curation.
Exam caveat: consolidating drafts for leadership choice is not public release—selection and factual clearance must precede posting to social, web, or media channels. Operational check: place all variants on the communications Page, mark factual claims that need ops confirmation, capture leadership’s chosen variant in writing, and publish only the cleared selection through authorized channels.