A product manager asks Copilot to draft a customer outage update that must sound empathetic, follow a clear timeline with next steps, and avoid inventing technical causes. Which response specification should the manager include in the prompt to reliably control sentiment, coherence, and creativity?

The correct specification works because it maps each control goal to an explicit prompt constraint: empathetic tone directs sentiment, mandated timeline plus next-steps headings enforce coherence and completeness, and restricting creativity to non-factual phrasing prevents hallucination of causes while still allowing polished wording. The alternative that encourages detailed technical speculation fails on creativity control because inferring likely causes violates grounding and risks misinforming customers during an unresolved incident, even though tone and structure are correct. The alternative that permits flexible paragraph flow fails on coherence control because without required headings the model may produce readable but unstructured prose that omits timeline sequencing or accountability for next steps. The alternative that asks for neutral concise wording fails on sentiment control because neutrality suppresses the required empathy and can read as cold during an outage, despite preserving structure and factual safety. Exam caveat: do not choose a plausible prompting tactic simply because it is widely used for marketing or exploratory drafting; score it strictly against all three stated requirements of tone, structure, and factual restraint. Practical check: before sending, verify the draft contains an empathetic opening, distinct timeline and next-steps sections, and no sentence asserting an unverified root cause, revising the prompt if any element is missing.