Join for free

Draft a team policy or process announcement

Author: AILesson7 min setupTested with:ChatGPTReviewed: 2026-08-28

Quick answer

Explain an approved workplace change with accurate scope, actions, exceptions, support, and feedback routes. Provide: Approved change facts, Required actions and support, Communication constraints. Expected result: A clear announcement plus manager briefing, employee checklist, open questions, and consistency review.

1

Add your context

Your text stays in this browser. AILesson Prompts does not send it to a model or server.

2

Your prompt

Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt

Draft a team policy or process announcement from only the approved information below.

Change facts:
[change]

Actions and support:
[actions]

Communication constraints:
[delivery]

Separate approved policy, implementation guidance, rationale, examples, and unresolved decisions. State who is affected, what changes and stays the same, effective and transition dates, required actions in chronological order, exceptions, accessibility or accommodation route, help contact, escalation, and where the authoritative policy lives. Never invent authority, legal interpretation, disciplinary consequence, exception, deadline, benefit, system behavior, or reason. Do not expose personal cases. Use respectful plain language and explain practical impact before background. If a fact needed for safe compliance is missing, label it as a blocker rather than guessing. Produce the main announcement, a manager consistency brief, a recipient checklist, anticipated questions with only confirmed answers, and a pre-send accuracy check.
Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.

From input to outcome

A worked example

See how concrete context turns this recipe into a usable result

Actual input

Approved change facts
Approved by Operations Director on 20 August. From 15 September, the 28-person Customer Operations team must record shift swaps in ShiftHub instead of email. Applies to permanent and temporary team members in Shanghai and Shenzhen. Existing schedule, pay, overtime approval, leave policy, and manager approval for swaps do not change. Reason that may be shared: one current record is needed to reduce missed handoffs. Transition 1–14 September: email requests are accepted but coordinators copy approved swaps into ShiftHub. From 15 September, a swap is not final until the manager approves it in ShiftHub. Emergency illness follows the existing call-in process, not this workflow. No disciplinary consequences have been approved. Policy page wording is still under review.
Required actions and support
Employees attend a 20-minute demo or watch the recording by 12 September, submit swaps in ShiftHub, and verify approval before changing shifts. Managers review requests within one working day when possible; this is a service aim, not a guarantee. Workforce Coordinator Lina owns rollout and keeps the approval record. IT Help handles access problems through the internal help portal. Staff needing accessibility support contact People Support privately; details must not be sent to managers. If ShiftHub is unavailable, contact the duty manager; the approved temporary fallback has not yet been defined and is a launch blocker. Chinese and English quick guides are planned.
Communication constraints
Email from Lina to the team, friendly and direct, under 450 words, with headings. Managers receive a separate five-point brief and must not improvise exceptions or consequences. Questions go to a shared operations inbox; private accommodation questions go only to People Support. Do not call the change legally required or promise zero scheduling errors. Do not mention any employee incident.

Example output

Subject: Shift swaps move to ShiftHub on 15 September

What is changing From 15 September, Shanghai and Shenzhen Customer Operations team members, including permanent and temporary colleagues, must submit shift swaps in ShiftHub. A swap is final only after manager approval appears there. This gives the team one current record and helps reduce missed handoffs.

What is not changing Your schedule, pay, overtime approval, leave policy, and the requirement for manager approval remain unchanged. Emergency illness continues through the existing call-in process.

What to do By 12 September, attend the 20-minute demo or watch the recording. For a swap, submit the request in ShiftHub and check that approval is recorded before changing shifts. During 1–14 September, email is still accepted and coordinators will copy approved swaps into ShiftHub.

Help and questions Use the internal help portal for access problems. Send general questions to the shared Operations inbox. Contact People Support privately for accessibility support; do not send personal details to your manager. If ShiftHub is unavailable, contact the duty manager. The temporary fallback is not yet approved, so Lina will confirm it before launch. The authoritative policy-page link is also pending.

Manager brief: apply the rule to permanent and temporary members in both cities; approval remains required; do not invent exceptions or consequences; aim to review within one working day without promising it; route private accessibility matters to People Support.

Recipient checklist: complete training by 12 September; use ShiftHub from 15 September; wait for recorded approval; retain the emergency call-in route; use the correct help channel.

Confirmed Q&A: Does email count after 15 September? No, based on the approved change. Does pay or leave policy change? No. What happens during an outage? Contact the duty manager; the temporary fallback is unresolved. Pre-send blockers: approve outage fallback, publish policy link, confirm demo/recording links, and verify both language guides.

Why this works

  1. 1

    Separating policy from guidance prevents local examples from becoming accidental rules

  2. 2

    A manager brief and open-question list reduce inconsistent answers during rollout

Check the result

  • Can each affected person tell whether the change applies and what to do by when?

  • Do the announcement, manager brief, checklist, and FAQ use the same approved rules?

  • Are exceptions, accommodations, unresolved items, support, and authoritative sources explicit?

Use it with confidence

Frequently asked questions

Practical answers about when to use this recipe, what to provide, and where human review still matters

What should I prepare before using “Draft a team policy or process announcement”?

For “Draft a team policy or process announcement,” prepare Approved change facts, Required actions and support, and Communication constraints. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Draft a team policy or process announcement” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A clear announcement plus manager briefing, employee checklist, open questions, and consistency review—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Draft a team policy or process announcement”?

The published test record for “Draft a team policy or process announcement” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

More ways to explore

Where this recipe fits

Text promptsPeople, hiring & developmentFor managers

Keep the work moving