Draft
Template
Build a policy or process update template
Get a fixed anatomy for every policy announcement — what, why, who, what to do, by when, where to learn more.
The prompt
Build a reusable template for announcing policy and process updates.
Context: we send these [several times a quarter] from [HR / Operations / IT]. Every update has the same anatomy: what’s changing, why, who it affects, what to do, by when, where to learn more.
Audience: affected employees who need to act, and everyone else who needs to be aware.
Tone: clear, direct, and supportive.
Must include:
– A one-sentence summary block at the top
– Fixed sections: “What’s changing”, “Why”, “Who this affects”, “What you need to do” (numbered, with dates), “By when”, “Questions?”
– An FAQ block with three placeholder questions
– A CTA button to the full policy
Constraints: under 250 words in sample form before the FAQ; headings identical every time.
Output: the template with each section in place, sample content marked [like this], and a short note on what changes per update versus what stays fixed.
Works in
CoAuthorHow to use
Keep the headings identical every time. Employees learn where to look, and approvals get faster.
The prompt
Build a reusable template for announcing policy and process updates.
Context: we send these [several times a quarter] from [HR / Operations / IT]. Every update has the same anatomy: what’s changing, why, who it affects, what to do, by when, where to learn more.
Audience: affected employees who need to act, and everyone else who needs to be aware.
Tone: clear, direct, and supportive.
Must include:
– A one-sentence summary block at the top
– Fixed sections: “What’s changing”, “Why”, “Who this affects”, “What you need to do” (numbered, with dates), “By when”, “Questions?”
– An FAQ block with three placeholder questions
– A CTA button to the full policy
Constraints: under 250 words in sample form before the FAQ; headings identical every time.
Output: the template with each section in place, sample content marked [like this], and a short note on what changes per update versus what stays fixed.
