The prompt
Score 10 of 10, Excellent
Use it when A new or changed policy is about to be announced, and managers need to understand it and be ready for their team's questions before it goes out.
- {{organization}}
- {{lead_time}}
- {{policy}}
- {{reason}}
- {{dates}}
- {{employee_announcement}}
- {{hr_contact}}
Full prompt and why it works
Prompt
Write a briefing for managers at {{organization}} about the policy change below, to send {{lead_time}} before employees are told, so that every manager can explain the change the same way, answer the first questions their team asks and know what to pass to HR. Managers will read it between other work and come back to it when someone stops them in the hallway, so it has to be quick to scan. The policy, new or changed (the text, or the old and new versions): """ {{policy}} """ Why it is changing, as leadership has agreed to explain it: {{reason}} Dates: {{dates}} The announcement employees will receive: """ {{employee_announcement}} """ HR contact for questions and escalations: {{hr_contact}} Use these headings: 1. What is changing and when: four sentences at most, then a short before and after table if a new rule replaces an old one. 2. Why: the reason as agreed, in words managers can repeat. 3. What you need to do, and by when: a checklist. 4. Questions your team is likely to ask: 6 to 8, each with a short answer taken from the policy. For example: "Does this apply to people already on a flexible schedule?" followed by the policy's answer. That example shows the form only. 5. What to send to HR: individual situations, requests for exceptions, anything touching pay, health, accommodations or legal rights, and anyone upset enough to raise a complaint. 6. What not to say: guesses about future changes, promises of exceptions, and personal views on the decision presented as the company's. Keep it under 600 words. The tone should be plain and practical, like one manager briefing another. Make sure the briefing and the employee announcement say the same thing. Do not add rules, examples or answers that are not in the policy. If the two differ on a fact, such as a date or who is covered, list each difference at the top under "Fix before sending" rather than choosing one. If the policy does not answer one of the likely questions, keep the question and write [ASK HR] as the answer.
Variables
- {{organization}}
- Your organization or the part of it the policy covers.
- {{lead_time}}
- How far ahead managers hear, for example "two working days".
- {{policy}}
- The policy text, or the old and new versions side by side.
- {{reason}}
- The reason leadership has agreed to give, in a sentence or two.
- {{dates}}
- When it is announced and when it takes effect.
- {{employee_announcement}}
- The message employees will receive, pasted in full.
- {{hr_contact}}
- Who managers go to, for example "your HR business partner".
Why it works
- Who it's for. It is written for managers who will be stopped in the hallway with questions, so the answers come from the policy and the escalation points are spelled out.
- What good looks like. The briefing must match the employee announcement, and any difference is listed for fixing before either goes out.
- If unsure. A likely question the policy does not answer keeps its place with an [ASK HR] answer, so managers do not improvise policy.