Verified against ChatGPT · 2026-08-13
Draft an employee handbook policy section that a manager could actually apply consistently
Produces one handbook policy section at a time, written for consistent day-to-day application by managers who aren't HR specialists, flagged as a first draft pending HR and legal sign-off.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Draft one section of our employee handbook on the topic below. Write it so a manager who isn't an HR specialist could apply it consistently in a real situation, not so it merely reads well. HANDBOOK TOPIC Requesting and approving unplanned sick leave. COMPANY CONTEXT 60-person company, mostly remote, managers across 4 different states. SITUATIONS THIS POLICY NEEDS TO HANDLE Employee calls in sick the morning of an important client meeting; employee has taken 5 unplanned sick days in one month. EXISTING PRACTICE (IF ANY) Currently just handled case-by-case by each manager with no consistent standard. DRAFTING APPROACH Write the policy around the real situations described, since a handbook section that only covers the easy, obvious case and stays silent on the messy realistic ones is the section managers end up calling HR about anyway, defeating its purpose. State the rule for each situation as something a manager could apply without judgment calls beyond what the policy itself gives them — if a decision genuinely requires judgment, say explicitly whose judgment (the manager's, HR's, or legal's) rather than leaving it ambiguous who decides. Where the existing practice differs from what you're drafting, note the gap explicitly rather than silently changing established practice — a handbook that contradicts what people already understand to be true creates confusion and potential unfairness claims from anyone who acted on the old understanding. Keep the tone plain and direct — a handbook section is reference material an employee or manager reads once and needs to apply correctly months later without re-reading the whole thing, not a document meant to be read for tone. WHAT NOT TO DO Do not state a specific legal minimum (like a required number of leave days, notice period, or accommodation standard) as if it's settled — these vary by jurisdiction and change, and stating one as fact risks the handbook being wrong the moment it's published or in a different state or country. Mark any such number as "[confirm minimum with legal/HR for applicable jurisdiction]" instead of asserting a specific figure. OUTPUT FORMAT 1. The policy section (heading, plain-language text, one worked example for the trickiest situation named). 2. A short list of any specific legal minimums or figures flagged for HR/legal confirmation. 3. A note on any gap between this draft and existing practice, if one was described. 4. A closing line stating this is a first-draft handbook section pending HR and legal review, and it should not be added to the handbook or relied upon by managers or employees until a qualified lawyer has confirmed it against applicable employment law.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
A handbook policy drafted from the topic name alone tends to cover the easy, textbook version of the situation and stay silent on exactly the messy real cases that prompted someone to want a written policy in the first place — requiring the actual real situations as input and instructing the model to write the policy around them, including a worked example for the trickiest one, is what keeps the draft from being technically about the right topic while being practically useless the first time a manager hits an edge case. Insisting that every rule be applicable "without a judgment call beyond what the policy gives" — or explicit about whose judgment it is when one is unavoidable — targets a specific and common handbook failure where vague language ("managers should use discretion") gets written in because it sounds reasonable, but in practice produces inconsistent enforcement across managers, which is the exact problem multi-state or multi-manager companies write handbooks to prevent. Flagging the gap between the draft and existing informal practice matters because handbooks don't get written into a vacuum — employees and managers already have some shared understanding of how things work, and a new written policy that silently contradicts that understanding, rather than naming the change explicitly, creates a fairness problem for anyone who reasonably relied on the old norm. The prohibition on stating specific legal minimums as settled fact is the highest-stakes safety rule here: employment law thresholds (leave entitlements, notice periods, accommodation standards) are jurisdiction-specific and change over time, and a model asserting a specific number with confidence risks the handbook being factually wrong from the moment it's adopted in exactly the area — mandatory minimums — where getting it wrong creates real legal exposure.
What you get back
Unplanned Sick Leave. If you're unable to work due to illness, notify your manager as early as possible before your shift or scheduled meetings begin — a text or Slack message is sufficient; you do not need to provide a doctor's note for absences of [confirm minimum with legal/HR for applicable jurisdiction] days or fewer. Worked example: if you call in sick the morning of an important client meeting, notify your manager immediately so they can arrange coverage; the sick leave itself is still approved under this policy regardless of meeting timing. Flagged for legal/HR: minimum documentation threshold, and any state-specific paid sick leave requirements across your 4 states. This is a first draft pending HR and legal review — do not add to the handbook until confirmed by a qualified lawyer.
Verified against
ChatGPT GPT-5.1 · 2026-08-13
Changelog
- 2026-08-13 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
