A public-health writer juggles Copilot chats for a heat-advisory campaign and a vaccine-clinic campaign. What rename practice best prevents mix-ups?

In concurrent municipal campaigns, Copilot chat titles are the primary way staff distinguish workstreams at a glance. Rename each conversation to name the campaign it supports—for example, heat advisory or vaccine clinic—so you can reopen the right thread without reading its message history. Campaign-specific labels reduce the risk of mixing messaging, citations, and deadlines between unrelated outreach tracks, and make overnight handoffs safer when multiple writers share Copilot history. Keeping both chats titled “Chat” fails because identical default labels erase campaign identity and invite mix-ups between heat-advisory and vaccine-clinic content. Giving both chats the generic title “Public health” also fails: the department name is shared, so the title does not distinguish the concurrent campaigns. Using generic labels and relying on the latest message fails because a recent message may not clearly identify the campaign, and reviewers must inspect conversation content to tell the threads apart; that is slower and more error-prone than clear titles. Exam caveat: renaming improves discoverability, but it does not enforce access controls or prevent content from being pasted into the wrong chat. Titles are navigation aids, not security boundaries, so sensitive drafts still need correct permissions and review. Practical check: confirm that each title uniquely identifies its campaign in Copilot history, then spot-check that heat-advisory and vaccine-clinic prompts are in the matching threads. A simple convention, such as campaign plus date or product, can help overnight reviewers use consistent titles.