Draft an employee-facing FAQ for {{change: e.g. our return-to-office transition, our new hybrid policy}}.
Inputs:
- The change: {{paste — what, when, who, why}}
- The official talking points: {{paste leadership messaging}}
- Concerns Slack channels / employee surveys have surfaced: {{paste}}
- What's NOT changing: {{paste — to anchor uncertainty}}
Output FAQ with these question categories:
## The basics
Q: What is changing? Q: When? Q: Who does it apply to? Q: Who doesn't it apply to?
Answer in plain language with the date and the scope.
## What this means for my day-to-day
The 5–8 specific operational questions: parking, lunch, meeting blocks, equipment, dress code, commute reimbursement, etc.
## What if my situation is different
Disabilities. Caregiving. Distance. Health concerns. Religious observance. Each with the specific path to request an exception and the person to email.
## What this does NOT mean
The misreadings to head off: "is my job at risk if I push back," "is this layoffs in disguise," "is the policy in writing or can it shift back."
## What you're hearing on Slack
The 2–3 questions you've seen in non-official channels that the official FAQ avoids. Answer them honestly. If the answer is "we don't know yet," say so.
## How decisions get made if this isn't working
The review cadence, the criteria, who decides if the policy changes.
Tone:
- Direct. No leadership-platitude language.
- Acknowledge the friction before the rationale.
- Answer the question that was asked, not the question you wish was asked.
Hard rule: if the FAQ doesn't address the most-upvoted Slack question, the FAQ is theater. Address it or the policy review will land in town hall instead.internal-commspolicychange-management