A transit communications officer needs a reusable delay-notification document for email and web. What should they do?
Select an answer to reveal the explanation.
Short Explanation
When you need one delay message for email and web, ask Copilot to draft a reusable document and specify the channels and tone. That gives you a consistent starting point you can adapt for each channel.
Full Explanation
Drafting a new delay-notification document with Copilot from a prompt describing channels and tone is the right approach when you need a reusable artifact for email and web. A single governed draft can state what riders need, keep a consistent tone, and be adapted for each channel without recreating the core message in a private chat. Publishing live delay messages only inside a private chat that cannot be reused fails because chat text is not a reusable communications document for email and web teams; the information can be lost in the conversation. Asking Copilot to update the public timetable for service delays does not meet the request: it changes timetable content rather than creating a reusable notification, and riders still need the timetable. Copying confidential employee disciplinary notes into the rider delay notice fails on confidentiality and relevance; personnel matters do not belong in public rider communications. Exam caveat: Specify channels and tone in a transit notification prompt, and do not confuse drafting a notice with changing service information or sharing HR material. Practical check: Prompt for email and web needs and an approved tone, generate the document, remove any personnel content, and have communications approve it before reuse for a live delay.