30 Claude Prompts for Employee Handbooks
Paste your actual policies and Claude drafts the section, in plain language employees will read. Not "give me some advice".
In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
Core Policies & Code of Conduct
5 promptsCode of Conduct Section
1/30You are an HR policy writer who drafts code of conduct sections for employee handbooks. <context> The company needs a code of conduct section covering expected workplace behavior, professionalism, and consequences for violations. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Company size and setting: [PLACEHOLDER: 85 employees, hybrid office and remote] - Core values to reflect: [PLACEHOLDER: respect, accountability, directness] - Behaviors to explicitly address: [PLACEHOLDER: harassment, discrimination, substance use at work, use of company property] - Reporting channel: [PLACEHOLDER: HR email [email protected] or anonymous ethics line] </inputs> <task> Draft a code of conduct section (400 to 600 words) covering expected behavior, the specific issues listed, how to report a concern, and general consequences for violations, in plain language. </task> <constraints> - This is a draft for HR and employment counsel to review before publishing, it is not final legal policy language - Cover every behavior listed in inputs, none skipped - Use plain, direct sentences, avoid legal jargon where a plain phrase works - State the reporting channel clearly and prominently </constraints> <format> A formatted policy section with a short intro, 4 to 6 labeled subsections, and a closing reporting statement. </format>
Drafts a full code of conduct section covering expected behavior, named issues, and how to report concerns, flagged for legal review.
Pro tip: Always route this section through employment counsel before publishing; code of conduct language carries real legal weight in disciplinary cases.
Anti-Harassment and Non-Discrimination Policy
2/30You are an employment policy specialist who drafts anti-harassment and non-discrimination sections for handbooks. <context> The company needs a clear anti-harassment and non-discrimination policy section, including protected categories and the complaint process. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Jurisdiction(s) of operation: [PLACEHOLDER: California and Texas] - Protected categories to list: [PLACEHOLDER: race, color, religion, sex, sexual orientation, gender identity, national origin, age, disability, veteran status] - Complaint process: [PLACEHOLDER: report to direct manager, HR, or the anonymous ethics line; investigation within 10 business days] - Non-retaliation commitment: [PLACEHOLDER: yes, explicit] </inputs> <task> Draft an anti-harassment and non-discrimination policy section covering the definition of harassment and discrimination, the protected categories, the complaint process with the stated timeline, and a clear non-retaliation statement. </task> <constraints> - This is a draft only; anti-harassment policy language must be reviewed by employment counsel for the specific jurisdictions listed before publishing, since requirements vary by state - List every protected category given, do not shorten the list - State the investigation timeline exactly as given - Include the non-retaliation statement as its own clearly labeled paragraph </constraints> <format> A formatted policy section with definition, protected categories list, complaint process steps, and non-retaliation statement. </format>
Drafts the anti-harassment and non-discrimination policy with protected categories and complaint timeline, flagged for jurisdiction-specific legal review.
Pro tip: List every state you operate in in the inputs; several states (like California) require specific language this draft alone won't cover, counsel needs to add it.
Attendance and Time-Off Policy
3/30You are an HR policy writer who drafts attendance and time-off sections for employee handbooks. <context> The company needs a section explaining attendance expectations, how to request time off, and what counts as an unexcused absence. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Standard work hours: [PLACEHOLDER: 9am to 6pm, core hours 10am to 4pm for hybrid staff] - Time-off request process: [PLACEHOLDER: submit in the HR system at least 5 business days in advance for planned leave] - Sick leave notice: [PLACEHOLDER: notify manager before start of shift, same day is fine] - Unexcused absence definition: [PLACEHOLDER: no notice given and no approved leave on file, 3 in a rolling 90 days triggers a check-in] </inputs> <task> Draft an attendance and time-off section covering standard hours, the request process for planned leave, the notice process for sick leave, and what triggers an unexcused-absence check-in. </task> <constraints> - Use the exact hours, timelines, and thresholds given, do not round or approximate - Separate planned leave and sick leave into clearly distinct subsections - Keep tone informative, not punitive </constraints> <format> A formatted policy section with 3 labeled subsections: Standard Hours, Requesting Time Off, Sick Leave and Attendance. </format>
Drafts the attendance and time-off section with your exact hours, request process, and unexcused-absence threshold spelled out.
Pro tip: Give it your real rolling-window threshold (like 3 in 90 days); a vague policy here is the top cause of inconsistent manager enforcement.
Conflict of Interest Policy
4/30You are a corporate governance and HR policy writer who drafts conflict of interest sections for handbooks. <context> The company needs a conflict of interest policy covering outside employment, financial interests, and gifts from vendors or clients. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Areas to cover: [PLACEHOLDER: outside employment or moonlighting, financial interest in a competitor or vendor, hiring or supervising relatives, gifts from vendors] - Disclosure process: [PLACEHOLDER: disclose in writing to HR before accepting outside work or a gift over $100] - Gift threshold: [PLACEHOLDER: gifts under $100 in value are acceptable without disclosure, over $100 must be disclosed and may need to be declined] </inputs> <task> Draft a conflict of interest section covering each area listed, the disclosure process, and the specific gift threshold, with 1 short example per area to make it concrete. </task> <constraints> - Cover all 4 areas listed, each as its own labeled subsection - Use the exact dollar threshold given - Examples must be realistic and specific, not vague ("a situation that could be a conflict") </constraints> <format> A formatted policy section with 4 labeled subsections, each with 2 to 3 sentences of policy plus 1 example. </format>
Drafts the conflict of interest policy across outside work, vendor gifts, and family hiring, with a concrete example per area.
Pro tip: Ask for the examples to be industry-specific to your company; generic conflict-of-interest examples don't stick with employees the way a realistic one does.
Disciplinary Process and Progressive Discipline Policy
5/30You are an employment policy specialist who drafts disciplinary process sections for handbooks. <context> The company needs a section explaining how performance and conduct issues are addressed, including the steps of progressive discipline. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Discipline steps: [PLACEHOLDER: verbal coaching, written warning, final written warning, termination] - Exceptions for immediate termination: [PLACEHOLDER: theft, violence, harassment, gross misconduct] - Employment type note: [PLACEHOLDER: at-will employment, this process is not a guarantee of any specific number of steps] - Documentation requirement: [PLACEHOLDER: manager documents each step in the HR system within 3 business days] </inputs> <task> Draft a disciplinary process section listing each step of progressive discipline in order, the exceptions that allow skipping straight to termination, the at-will employment note, and the documentation requirement for managers. </task> <constraints> - This is a draft only; at-will language and disciplinary process wording must be reviewed by employment counsel before publishing, since it can affect legal protections - List discipline steps in exact order given - State the at-will note clearly, do not imply discipline steps are guaranteed before termination - Include the exceptions list prominently, not buried </constraints> <format> A formatted policy section: ordered steps list, exceptions list, at-will note, and documentation requirement, each labeled. </format>
Drafts the progressive discipline policy with ordered steps, termination exceptions, and the at-will note, flagged for counsel review.
Pro tip: Never publish the at-will language without employment counsel sign-off; poorly worded discipline steps can accidentally create an implied contract in some states.
Benefits & Compensation Sections
5 promptsBenefits Summary Page
6/30You are a total rewards specialist who writes clear benefits summary sections for employee handbooks. <context> The handbook needs a benefits summary page giving employees a plain overview of what's offered, with detail deferred to the plan documents. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Benefits offered: [PLACEHOLDER: medical/dental/vision (company pays 80% of premium), 401k with 4% match, $1,000 annual learning stipend, 20 PTO days, 10 paid holidays] - Eligibility: [PLACEHOLDER: full-time employees, benefits start day 1] - Where to find full plan details: [PLACEHOLDER: the benefits portal at cedarco.com/benefits or HR] </inputs> <task> Write a benefits summary section listing each benefit with a 1-line description, the eligibility rule, and a pointer to where employees find full plan documents for legal detail. </task> <constraints> - List every benefit given, none omitted - State clearly that this summary does not override the official plan documents - Keep each benefit description to 1 line, save detail for the plan documents </constraints> <format> A table with columns: Benefit, Summary, Eligibility, plus a closing note on where to find full plan documents. </format>
Builds a plain-language benefits summary table with eligibility rules, pointing employees to the full plan docs for legal detail.
Pro tip: Always add the note that plan documents govern over the summary; benefits summaries are informational, the signed plan documents are the legal source of truth.
PTO and Holiday Policy Table
7/30You are an HR policy writer who documents time-off accrual and holiday policies for employee handbooks. <context> The handbook needs a clear table showing how PTO accrues, carries over, and which holidays are observed. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - PTO accrual: [PLACEHOLDER: 20 days per year, accrued 1.67 days per month, starting day 1] - Carryover rule: [PLACEHOLDER: up to 5 unused days carry into next year, rest is forfeited] - Paid holidays (list): [PLACEHOLDER: New Year's Day, MLK Day, Memorial Day, Juneteenth, Independence Day, Labor Day, Thanksgiving + day after, Christmas Eve, Christmas Day] - Floating holiday: [PLACEHOLDER: 1 floating holiday per year, employee's choice] </inputs> <task> Build a PTO accrual table (monthly accrual rate, annual total, carryover rule) and a separate holiday calendar table listing each observed holiday, plus a note on the floating holiday. </task> <constraints> - Use the exact accrual rate and carryover figures given - List every holiday given, in calendar order - State the carryover forfeiture rule plainly, don't soften it into vague language </constraints> <format> Two tables: "PTO Accrual" and "Paid Holidays", plus a 1-sentence floating holiday note. </format>
Builds the PTO accrual table and full holiday calendar with the carryover rule stated plainly, no vague language on forfeiture.
Pro tip: State the carryover cap explicitly rather than "unused PTO may be forfeited"; ambiguity here is the top source of year-end HR tickets.
Compensation and Pay Cycle Explainer
8/30You are an HR and payroll specialist who writes plain-language pay policy sections for handbooks. <context> The handbook needs a section explaining how and when employees get paid, without disclosing individual salary information. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Pay frequency: [PLACEHOLDER: biweekly, every other Friday] - Pay method: [PLACEHOLDER: direct deposit only] - Overtime eligibility note: [PLACEHOLDER: non-exempt employees earn 1.5x for hours over 40/week; exempt employees are salaried] - Where pay questions go: [PLACEHOLDER: [email protected]] </inputs> <task> Write a compensation and pay cycle section explaining pay frequency, pay method, how overtime eligibility works for exempt vs non-exempt staff, and where to direct pay questions. </task> <constraints> - Do not include or invent any individual salary figures, this section is about process only - State the exempt/non-exempt overtime distinction accurately as given - This is a draft; overtime and exempt/non-exempt classification language should be confirmed against current federal and state wage law by counsel before publishing </constraints> <format> A formatted policy section with 3 short labeled parts: Pay Schedule, Overtime Eligibility, Pay Questions. </format>
Writes the pay cycle and overtime eligibility section in plain language, without touching individual salary data, flagged for wage-law review.
Pro tip: Confirm your exempt/non-exempt classifications with counsel before this ships; misclassification is one of the most commonly litigated wage issues.
Parental and Family Leave Policy
9/30You are a benefits policy writer who drafts parental and family leave sections for handbooks. <context> The company needs a parental and family leave section covering paid leave duration, eligibility, and how it interacts with any legally required leave. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Paid parental leave: [PLACEHOLDER: 12 weeks fully paid for birthing and non-birthing parents] - Eligibility: [PLACEHOLDER: employed 6+ months, full-time] - Interaction with legal leave: [PLACEHOLDER: runs concurrently with any state or federal family leave entitlement, does not add on top of it] - Return-to-work process: [PLACEHOLDER: notify HR 30 days before intended return date] </inputs> <task> Draft a parental and family leave section covering leave duration and pay, eligibility, how it interacts with legally required leave, and the return-to-work notice process. </task> <constraints> - This is a draft only; how company leave interacts with state and federal leave law (FMLA and state equivalents) varies by jurisdiction and must be reviewed by employment counsel before publishing - State the eligibility requirement exactly as given - Be explicit that leave runs concurrently, not additively, with legal leave, since that is a common point of employee confusion </constraints> <format> A formatted policy section with 4 labeled parts: Leave Duration, Eligibility, Relationship to Legal Leave, Returning to Work. </format>
Drafts the parental leave section covering duration, eligibility, and how it stacks with legal leave, flagged for jurisdiction-specific counsel review.
Pro tip: Explicitly state whether company leave runs concurrently or in addition to legal leave; this is the single most common parental-leave misunderstanding among new parents.
Retirement and Perks Overview
10/30You are a total rewards specialist who writes retirement and perks sections for employee handbooks. <context> The handbook needs a section covering the retirement plan and smaller perks, distinct from the core health benefits summary. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Retirement plan: [PLACEHOLDER: 401k, company matches 100% of the first 4% of salary contributed, vests immediately] - Additional perks: [PLACEHOLDER: $1,000 annual learning stipend, $50/month wellness stipend, free lunch on Fridays, 1 paid volunteer day per year] - Eligibility for retirement plan: [PLACEHOLDER: eligible after 30 days of employment] </inputs> <task> Write a retirement and perks section explaining the 401k match structure and vesting, eligibility timing, and each additional perk with a 1-line description. </task> <constraints> - State the match formula and vesting schedule exactly as given - List every perk given, no omissions - Keep perk descriptions to 1 line each </constraints> <format> A formatted section: a short paragraph on the 401k, followed by a bulleted list of additional perks. </format>
Writes the retirement plan explainer (match, vesting, eligibility) plus a clean bulleted list of every smaller perk.
Pro tip: State the vesting schedule explicitly even if it's immediate; employees often assume matches vest over time unless told otherwise.
Onboarding & New Hire Sections
5 promptsNew Hire Welcome Section
11/30You are an employer branding and HR writer who drafts the welcome section that opens an employee handbook. <context> The handbook needs an opening welcome section that sets tone, introduces company history briefly, and orients a brand-new employee. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Founded and short history: [PLACEHOLDER: founded 2015, started as a 3-person design studio, now 85 people across 2 offices] - Mission statement: [PLACEHOLDER: helping small manufacturers modernize their operations without enterprise software complexity] - Tone: [PLACEHOLDER: warm but not overly casual] - CEO or founder name for sign-off: [PLACEHOLDER: Priya Nair, Founder] </inputs> <task> Write a welcome section (250 to 350 words) that welcomes a new employee, gives a brief company history, states the mission, and explains how to use the handbook (that it's a reference, not a one-time read), signed by the founder. </task> <constraints> - Use the exact history and mission facts given, no invented milestones - Keep tone matching the input (warm but not overly casual), avoid excessive exclamation points - Include a line explaining the handbook is meant to be referenced ongoing, not just read once </constraints> <format> A formatted welcome section, 3 to 4 paragraphs, with a signature line. </format>
Writes the opening welcome section of the handbook, real company history and mission included, signed by your founder.
Pro tip: Keep the history to 1 to 2 real facts; a welcome section that reads like a full company timeline delays getting to what the new hire actually needs.
First 30/60/90 Day Onboarding Checklist
12/30You are an onboarding program manager who builds structured new-hire checklists for handbooks. <context> The handbook needs a 30/60/90 day onboarding checklist so new hires and their managers know what should happen by each milestone. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Role type: [PLACEHOLDER: general, applies to most departments] - Day 1 to 30 milestones: [PLACEHOLDER: complete HR paperwork, IT setup, meet team, complete compliance training, shadow 3 meetings] - Day 31 to 60 milestones: [PLACEHOLDER: own first small project, complete department-specific training, 30-day check-in with manager] - Day 61 to 90 milestones: [PLACEHOLDER: full workload, 90-day performance check-in, set goals for next quarter] </inputs> <task> Build a 30/60/90 day checklist with each milestone assigned to its window, split into a "New Hire" column and a "Manager" column showing who owns each item. </task> <constraints> - Include every milestone given, placed in the correct 30-day window - Every item must have an owner (New Hire or Manager), not left blank - Keep each checklist item to one short action phrase </constraints> <format> A table with columns: Window, Item, Owner, grouped by Day 1 to 30, Day 31 to 60, Day 61 to 90. </format>
Builds the full 30/60/90 day onboarding checklist with clear owners, so new hires and managers both know what's expected when.
Pro tip: Assign every item an owner explicitly; checklists without an owner column are the most common reason onboarding steps get missed.
Equipment and IT Setup Policy
13/30You are an IT operations and HR liaison who documents equipment and account setup policy for new hires. <context> The handbook needs a section explaining what equipment new hires receive, how accounts get set up, and who owns equipment return. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Standard equipment provided: [PLACEHOLDER: laptop, monitor, headset, and a $200 home office stipend for remote staff] - Account setup timeline: [PLACEHOLDER: email and core system access provisioned 3 business days before start date] - Equipment ownership: [PLACEHOLDER: company property, must be returned within 5 business days of last day] - Who to contact for issues: [PLACEHOLDER: [email protected]] </inputs> <task> Write an equipment and IT setup section covering what's provided, the setup timeline, the ownership and return policy, and the support contact. </task> <constraints> - Use the exact equipment list and timelines given - State the return policy and window plainly, including that it's company property - Keep the support contact line prominent and easy to find </constraints> <format> A formatted policy section with 3 labeled parts: What You'll Receive, Setup Timeline, Equipment Return. </format>
Writes the equipment and IT setup section covering what's provided, the timeline, and the return policy on exit.
Pro tip: Make the return-on-exit window explicit; unreturned equipment is one of the most common offboarding disputes HR handles.
Probationary Period Policy
14/30You are an employment policy specialist who drafts probationary or introductory period sections for handbooks. <context> The company wants a section explaining the introductory period new hires go through, what's evaluated, and what happens at the end of it. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Introductory period length: [PLACEHOLDER: 90 days] - What's evaluated: [PLACEHOLDER: job performance, attendance, fit with team] - Benefits during this period: [PLACEHOLDER: full benefits still apply from day 1, this period does not delay benefits] - At-will note: [PLACEHOLDER: employment remains at-will before, during, and after this period] </inputs> <task> Draft a probationary/introductory period section stating the length, what's being evaluated, that benefits are unaffected, and the at-will note, ending with what a successful completion looks like. </task> <constraints> - This is a draft only; language implying guaranteed employment after the introductory period must be avoided, and the section should be reviewed by employment counsel before publishing to protect at-will status - State clearly that benefits are unaffected, since this is a common employee misconception - Use the exact period length given </constraints> <format> A formatted policy section, 4 short paragraphs, ending with a 1-sentence note on what happens after successful completion. </format>
Drafts the introductory period policy, clarifying benefits aren't delayed and preserving at-will language, flagged for counsel review.
Pro tip: Never imply the introductory period is a guarantee of continued employment after it ends; that wording has created at-will disputes for other companies.
Company Culture and Values Section
15/30You are a culture and internal communications writer who drafts the values section of employee handbooks. <context> The handbook needs a section explaining the company's core values with concrete behavioral examples, not just abstract words. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Core values (3 to 5): [PLACEHOLDER: Respect, Accountability, Directness, Curiosity] - One behavior example per value: [PLACEHOLDER: Respect = assume good intent in written communication; Accountability = own mistakes without deflecting in retros; Directness = give feedback to the person, not around them; Curiosity = ask "why" before proposing a fix] - How values connect to performance reviews: [PLACEHOLDER: values are one of 3 review criteria alongside impact and growth] </inputs> <task> Write a values section listing each value with its definition and the specific behavior example given, plus a closing note on how values connect to performance reviews. </task> <constraints> - Use the exact behavior example for each value, do not replace with generic examples - Keep each value's writeup to 2 to 3 sentences - Avoid abstract statements with no behavioral anchor </constraints> <format> A formatted section with one labeled subsection per value (definition + example), plus a closing paragraph on performance review connection. </format>
Writes the values section with a concrete behavior example per value, tied directly to how performance gets reviewed.
Pro tip: Insist on a real behavior example per value, not just a definition; values without a concrete example are the section employees skip.
These prompts give you the what. Tutorials give you the why.
Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. 300+ tutorials and growing.
Remote & Flexible Work Policies
5 promptsRemote Work Eligibility Policy
16/30You are an HR policy writer who drafts remote work eligibility sections for handbooks. <context> The company needs a section explaining which roles are eligible for remote work, the approval process, and any location restrictions. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Eligible role types: [PLACEHOLDER: engineering, design, and marketing roles; not eligible: on-site operations and reception] - Approval process: [PLACEHOLDER: manager approval, documented in the HR system] - Location restrictions: [PLACEHOLDER: must reside in a state where the company is registered to run payroll, currently CA, TX, NY, WA] - Review cadence: [PLACEHOLDER: eligibility reviewed annually with manager] </inputs> <task> Draft a remote work eligibility section stating which roles qualify, the approval process, the location restriction and why it exists (payroll registration), and the review cadence. </task> <constraints> - This is a draft; location restrictions tied to payroll and tax registration should be confirmed with legal/payroll before publishing, since operating in a new state can create tax obligations - List the eligible and ineligible role types exactly as given - State the location restriction and its reason plainly, not as an unexplained rule </constraints> <format> A formatted policy section with 3 labeled parts: Eligible Roles, Approval Process, Location Requirements. </format>
Drafts the remote eligibility policy with role types, approval steps, and the payroll-driven location restriction explained plainly.
Pro tip: Confirm your current payroll-registered states with finance before publishing this; a wrong state listed here can lead an employee to relocate somewhere the company can't legally pay them.
Hybrid Schedule and Core Hours Policy
17/30You are an HR policy writer who documents hybrid work schedules for employee handbooks. <context> The company needs a section explaining the hybrid schedule: which days are in-office, core collaboration hours, and flexibility around the edges. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - In-office days: [PLACEHOLDER: Tuesday and Thursday required, other days flexible] - Core hours: [PLACEHOLDER: 10am to 4pm local time, all employees expected to be reachable] - Flexibility outside core hours: [PLACEHOLDER: start and end times can shift as long as core hours and 8-hour days are met] - Exception process: [PLACEHOLDER: request a schedule exception through manager, reviewed case by case] </inputs> <task> Write a hybrid schedule section covering required in-office days, core hours, flexibility outside core hours, and how to request an exception. </task> <constraints> - Use the exact days and hours given - Distinguish clearly between what's fixed (in-office days, core hours) and what's flexible - Keep the exception process short and clear, not bureaucratic-sounding </constraints> <format> A formatted policy section with 3 labeled parts: In-Office Days, Core Hours, Requesting an Exception. </format>
Writes the hybrid schedule section, drawing a clean line between what's fixed (in-office days, core hours) and what flexes.
Pro tip: Be explicit about which parts are truly fixed vs flexible; ambiguity here is what causes managers and employees to interpret "hybrid" completely differently.
Home Office Stipend and Equipment Policy
18/30You are an HR and finance policy writer who documents remote work stipends and equipment rules. <context> The handbook needs a section explaining the home office stipend, what it can be used for, and how reimbursement works. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - One-time setup stipend: [PLACEHOLDER: $500, for desk, chair, monitor within first 60 days] - Ongoing stipend: [PLACEHOLDER: $50/month for internet, added to paycheck] - Reimbursement process: [PLACEHOLDER: submit receipt in the expense system within 30 days of purchase for the one-time stipend] - Excluded items: [PLACEHOLDER: no furniture beyond desk/chair, no personal electronics not used for work] </inputs> <task> Write a home office stipend section covering the one-time and ongoing stipend amounts, what they can be spent on, the reimbursement process and deadline, and excluded items. </task> <constraints> - Use the exact dollar amounts and deadlines given - List excluded items clearly so employees don't submit ineligible expenses - Separate the one-time stipend process from the ongoing monthly stipend clearly </constraints> <format> A formatted policy section with 3 labeled parts: One-Time Setup Stipend, Ongoing Internet Stipend, What's Not Covered. </format>
Writes the stipend policy with exact dollar amounts, reimbursement deadlines, and excluded items spelled out to cut down expense disputes.
Pro tip: List excluded items explicitly; most stipend confusion comes from what's NOT covered, not what is.
Communication Norms Policy
19/30You are a remote work operations specialist who documents communication norms for distributed teams. <context> The handbook needs a section setting expectations for async vs synchronous communication, response times, and which tool is used for what. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Tools and their use: [PLACEHOLDER: Slack for quick async questions, email for external/formal communication, video calls for real-time discussion and 1:1s] - Expected response time: [PLACEHOLDER: Slack within 4 business hours, email within 1 business day] - Meeting-free time: [PLACEHOLDER: no internal meetings on Wednesdays] - Time zone expectation: [PLACEHOLDER: overlap at least 4 hours with your team's core hours, regardless of your base time zone] </inputs> <task> Write a communication norms section covering which tool to use for what, expected response times, meeting-free time, and the time zone overlap expectation. </task> <constraints> - Use the exact tools, timings, and response windows given - State response times as expectations, not hard SLAs, unless the input frames them otherwise - Keep the tool-to-use-case mapping as a clear list, not prose </constraints> <format> A formatted policy section: a tool-use table (Tool, Use Case, Response Time) followed by 2 short paragraphs on meeting-free time and time zone overlap. </format>
Writes the async/sync communication norms with a tool-to-use-case table and clear response-time expectations for distributed teams.
Pro tip: Frame response times as expectations, not contractual SLAs, unless you actually intend to enforce them that strictly.
Travel and Expense Policy for Remote Employees
20/30You are a finance and HR policy writer who drafts travel and expense sections for remote and distributed teams. <context> The handbook needs a section covering when remote employees travel for work (offsites, client visits) and how expenses are reimbursed. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Covered travel occasions: [PLACEHOLDER: company offsites (twice a year), client visits when required by role, team meetups] - Booking process: [PLACEHOLDER: book through the company travel portal, or submit for reimbursement with receipts if booked independently] - Expense categories covered: [PLACEHOLDER: flights (economy), hotel (up to $250/night), meals (up to $75/day), ground transport] - Reimbursement deadline: [PLACEHOLDER: submit within 14 days of travel] </inputs> <task> Write a travel and expense section covering which travel is company-covered, the booking process, the expense categories with their limits, and the reimbursement deadline. </task> <constraints> - Use the exact dollar limits and deadlines given - Present expense categories and limits as a table, not a paragraph - State the booking process options clearly (portal vs independent booking) </constraints> <format> A formatted policy section: 2 short paragraphs on covered travel and booking, followed by an expense limits table (Category, Limit). </format>
Writes the travel and expense policy for remote teams with exact per-category limits in a table and the reimbursement deadline stated.
Pro tip: Put the reimbursement deadline in bold or its own line; late submissions past the deadline are the most common expense-policy dispute.
Compliance & Workplace Standards
5 promptsWorkplace Safety Policy
21/30You are a workplace safety and HR policy writer who drafts safety sections for employee handbooks. <context> The company needs a workplace safety section covering general safety expectations, incident reporting, and emergency procedures for its office locations. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Office locations: [PLACEHOLDER: Austin, TX and San Francisco, CA] - Incident reporting process: [PLACEHOLDER: report any injury or near-miss to your manager and HR within 24 hours] - Emergency procedures: [PLACEHOLDER: fire evacuation routes posted by each exit, designated assembly point in the parking lot] - Safety contact: [PLACEHOLDER: office manager at each location] </inputs> <task> Draft a workplace safety section covering general safety expectations, the incident reporting process and timeline, emergency procedure basics, and the safety contact per location. </task> <constraints> - This is a draft; workplace safety requirements (OSHA and state equivalents) vary by location and must be reviewed by legal/EHS staff before publishing - Use the exact reporting timeline given - List both office locations and note the safety contact structure applies per location </constraints> <format> A formatted policy section with 3 labeled parts: General Safety, Incident Reporting, Emergency Procedures. </format>
Drafts the workplace safety section with incident reporting timeline and emergency basics, flagged for OSHA/EHS compliance review.
Pro tip: Route this section to whoever owns EHS or facilities compliance, not just HR; safety requirements often need location-specific detail this draft won't have.
Data Security and Acceptable Use Policy
22/30You are an IT security and HR policy writer who drafts acceptable use sections for employee handbooks. <context> The company needs a section covering acceptable use of company systems, password and device security expectations, and what happens with company data on personal devices. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Required security practices: [PLACEHOLDER: multi-factor authentication on all accounts, company-managed password manager, no company data stored on personal cloud drives] - Personal device policy: [PLACEHOLDER: personal devices allowed for email/Slack only, must have a passcode and remote wipe enabled] - Prohibited actions: [PLACEHOLDER: sharing login credentials, installing unapproved software on company laptops, using public wifi without VPN for sensitive systems] - Reporting a security incident: [PLACEHOLDER: report suspected phishing or a lost device to [email protected] immediately] </inputs> <task> Draft a data security and acceptable use section covering required security practices, the personal device policy, prohibited actions, and how to report a security incident. </task> <constraints> - List every required practice and prohibited action given, none omitted - State the incident reporting instruction as "immediately", not a delayed window - Keep language specific and actionable, not generic ("be careful with data") </constraints> <format> A formatted policy section with 4 labeled parts: Required Practices, Personal Devices, Prohibited Actions, Reporting an Incident. </format>
Drafts the acceptable use and data security policy with specific required practices and prohibited actions, not vague security advice.
Pro tip: List prohibited actions as a specific bulleted list; a security policy that only states principles gets ignored more than one with concrete rules.
Social Media and Confidentiality Policy
23/30You are a corporate communications and HR policy writer who drafts social media and confidentiality sections for handbooks. <context> The company needs a section on employee social media use and protecting confidential information, without overreaching into employees' personal speech rights. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Confidential information examples: [PLACEHOLDER: unreleased product plans, financial results before public announcement, customer data, internal strategy discussions] - Personal social media guidance: [PLACEHOLDER: employees may identify as working at the company but should note views are their own; do not post confidential information] - Company account posting: [PLACEHOLDER: only marketing and designated spokespeople post on official company accounts] - Note on protected activity: [PLACEHOLDER: this policy does not restrict employees discussing wages, hours, or working conditions with each other] </inputs> <task> Draft a social media and confidentiality section covering what counts as confidential information, personal social media guidance, who can post on official accounts, and the note on protected activity. </task> <constraints> - This is a draft; social media policies must not be written or applied in a way that restricts legally protected employee discussions (such as wages and working conditions), and should be reviewed by employment counsel before publishing - Include the protected activity note explicitly, do not omit it - List confidential information examples exactly as given </constraints> <format> A formatted policy section with 4 labeled parts: Confidential Information, Personal Social Media, Company Accounts, Your Rights. </format>
Drafts the social media and confidentiality section including the required protected-activity carve-out, flagged for counsel review.
Pro tip: Never drop the protected-activity note; a social media policy that appears to bar discussing pay or conditions with coworkers can violate labor law even if that wasn't the intent.
Anti-Retaliation and Reporting Policy
24/30You are an employment policy specialist who drafts anti-retaliation and internal reporting sections for handbooks. <context> The company needs a section making clear employees can report concerns without fear of retaliation, and how reports are handled. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Reporting channels: [PLACEHOLDER: direct manager, HR, skip-level manager, or the anonymous ethics line at cedarco.com/ethics] - What counts as retaliation: [PLACEHOLDER: demotion, termination, exclusion, negative review, or schedule changes because someone made a good-faith report] - Investigation commitment: [PLACEHOLDER: HR acknowledges reports within 3 business days and investigates promptly] - Consequence for retaliation: [PLACEHOLDER: subject to disciplinary action up to termination] </inputs> <task> Draft an anti-retaliation section covering the reporting channels, a definition of retaliation with examples, the investigation commitment and timeline, and the consequence for retaliating against a reporter. </task> <constraints> - This is a draft only; anti-retaliation protections have both federal and state-specific dimensions and should be reviewed by employment counsel before publishing - List every reporting channel given - State the investigation timeline exactly as given - Make the consequence for retaliation explicit, not implied </constraints> <format> A formatted policy section with 4 labeled parts: How to Report, What Retaliation Looks Like, Our Commitment, Consequences. </format>
Drafts the anti-retaliation policy with reporting channels, a concrete definition of retaliation, and consequences stated plainly.
Pro tip: Give concrete retaliation examples (demotion, exclusion, schedule changes), not just the word "retaliation"; vague definitions are harder for managers to self-police against.
State-Specific Policy Addendum Outline
25/30You are an HR compliance specialist who identifies where a national employee handbook needs state-specific addenda. <context> The company operates in multiple states and needs to know which handbook sections likely require a state-specific addendum, before legal drafts the actual addendum language. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - States of operation: [PLACEHOLDER: California, Texas, New York, Washington] - Handbook sections already drafted: [PLACEHOLDER: sick leave, harassment policy, meal and rest breaks, final pay on termination, marijuana/drug policy] - Purpose of this output: [PLACEHOLDER: an internal checklist for legal, not the addendum text itself] </inputs> <task> Build a checklist mapping each drafted section to the states listed, flagging which section/state combinations commonly require distinct state-specific language (based on general knowledge of how these topics tend to vary by state), for legal to verify and draft. </task> <constraints> - This output is a research starting point only, not legal advice or final compliance language; every flagged item must be confirmed and drafted by employment counsel licensed in that state - Do not draft actual addendum legal language, only flag where it is likely needed - Be explicit that laws change and this list should be verified against current statutes before relying on it </constraints> <format> A table with columns: Handbook Section, State, Likely Needs Addendum (yes/no/unsure), Note, plus a closing disclaimer line. </format>
Builds a starting checklist flagging which handbook sections likely need state-specific addenda, for counsel to verify and draft, not a substitute for legal review.
Pro tip: Treat this strictly as a starting checklist for your legal team's to-do list, never as the actual compliance language; state employment law changes often and requires a licensed review in each state you operate.
Most people use 10% of Claude. Tutorials unlock the rest.
AI Academy: 300+ hands-on tutorials on Claude, ChatGPT, Midjourney, and 50+ AI tools. New tutorials added every week.
Handbook Structure & Rollout
5 promptsEmployee Handbook Table of Contents
26/30You are a publications editor who structures employee handbooks for clarity. <context> Before assembling the final document, the team needs a full table of contents mapping every section that should exist in the handbook. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Sections already drafted: [PLACEHOLDER: welcome, code of conduct, anti-harassment, attendance, benefits summary, PTO policy, remote work eligibility, hybrid schedule, safety, data security, anti-retaliation] - Sections still needed: [PLACEHOLDER: acknowledgment form, glossary of terms] - Target format: [PLACEHOLDER: digital PDF and intranet page] </inputs> <task> Build a full table of contents ordering all drafted and still-needed sections logically (welcome and culture first, policies grouped by theme, acknowledgment last), and flag which sections are still missing. </task> <constraints> - Include every section listed, drafted or not - Group related policy sections together (e.g. all leave-related sections adjacent) - Clearly mark each section as "Drafted" or "Needed" in the output </constraints> <format> A numbered table of contents with columns: Section, Status (Drafted/Needed). </format>
Builds the full handbook table of contents, grouping related policies logically and flagging which sections still need drafting.
Pro tip: Run this early in the project; reordering an outline is far cheaper than reorganizing a finished 40-page handbook.
Plain-Language Policy Summary Page
27/30You are a plain-language writing specialist who condenses dense HR policy into a quick-reference summary for employees. <context> The full handbook is long. The company also wants a 1-page plain-language summary hitting the policies employees ask about most, with a pointer to the full section for detail. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Top policies employees ask about (5 to 6): [PLACEHOLDER: how PTO accrues and carries over, remote work eligibility, how to report a concern, the 401k match, parental leave length, expense reimbursement deadline] - Source detail for each (short facts): [PLACEHOLDER: PTO 20 days/yr, 5 day carryover; remote eligible by role, manager approval; report via manager/HR/ethics line; 401k 100% match on first 4%; 12 weeks paid parental leave; expenses due within 14 days] </inputs> <task> Write a 1-page "quick answers" summary with each of the 6 questions as a heading, a 1 to 2 sentence plain-language answer using the source facts, and a note that full detail lives in the named handbook section. </task> <constraints> - Use only the facts given, do not invent additional policy detail - Keep each answer to 1 to 2 sentences, this is a quick reference, not the full policy - Order questions by how often employees likely ask them (most common first) </constraints> <format> A 1-page document with 6 question headings, each followed by a short plain-language answer. </format>
Builds a 1-page plain-language quick-reference answering the top 6 policy questions employees actually ask, pointing to the full sections.
Pro tip: Pull the actual most-asked questions from your HR ticket history if you have it; a summary built on real questions gets used far more than one built on guesses.
Interactive Handbook Index Page
28/30You are a front-end developer who builds simple, searchable index pages for internal HR documentation. <context> The company wants a single HTML page that serves as a clickable index of every handbook section, for the internal intranet, since employees currently can't find sections in the PDF. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Sections and their category grouping: [PLACEHOLDER: Getting Started (Welcome, Onboarding Checklist), Policies (Code of Conduct, Anti-Harassment, Attendance), Benefits (Benefits Summary, PTO, Retirement), Remote Work (Eligibility, Hybrid Schedule), Compliance (Safety, Data Security, Anti-Retaliation)] - Brand color: [PLACEHOLDER: #0F766E teal with white background] </inputs> <task> Build a complete, self-contained HTML index page with a search box (client-side JavaScript filtering the visible list by text typed) and the sections grouped into labeled category cards as given. </task> <constraints> - Single HTML file, inline CSS and inline JavaScript only, no external dependencies - The search box must filter section names live as the user types, using plain JavaScript - Group sections under the exact categories given, each as its own card - Must be legible on mobile as well as desktop </constraints> <format> A complete, live-previewable HTML document (starting with <!DOCTYPE html>) with working client-side search. </format>
Generates a live, self-contained HTML handbook index page with working client-side search, so employees can find a section without hunting through a PDF.
Pro tip: Test the search box with a partial word (like "leave") after Claude builds it; confirm the filter matches substrings, not just exact section names.
Handbook Acknowledgment Form
29/30You are an HR compliance specialist who drafts handbook acknowledgment forms. <context> Every employee needs to sign an acknowledgment confirming they received and read the handbook, for the company's records. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Handbook version/date: [PLACEHOLDER: version 2026.1, effective August 2026] - Key statements to include: [PLACEHOLDER: employee received and had opportunity to read the handbook, understands policies may change with notice, understands employment remains at-will, knows where to direct questions] - Signature fields needed: [PLACEHOLDER: employee name, signature, date, employee ID] </inputs> <task> Draft an acknowledgment form with the key statements as a short numbered list an employee reads and confirms, followed by the signature fields. </task> <constraints> - This is a draft; the exact at-will and policy-change language should be reviewed by employment counsel before use, since acknowledgment forms can have legal weight in disputes - Include every key statement given as its own numbered item - Keep the form to 1 page </constraints> <format> A formatted 1-page form: numbered acknowledgment statements followed by a signature block with the fields listed. </format>
Drafts the 1-page acknowledgment form with the at-will and policy-change statements employees sign, flagged for counsel review.
Pro tip: Store signed acknowledgments in your HR system indefinitely, not just for the current handbook version; they matter most in disputes that surface years later.
Handbook Rollout Announcement Email
30/30You are an internal communications specialist who announces new or updated employee handbooks to staff. <context> The company is rolling out an updated handbook and needs an email to all employees announcing it, explaining what changed, and asking for acknowledgment. </context> <inputs> - Company name: [PLACEHOLDER: Cedar & Co] - Handbook version/date: [PLACEHOLDER: version 2026.1, effective August 2026] - Key changes from last version: [PLACEHOLDER: updated remote work eligibility, added parental leave detail, revised PTO carryover cap from 3 to 5 days] - Action required: [PLACEHOLDER: read the updated sections and sign the acknowledgment form in the HR system by September 1, 2026] - Where to ask questions: [PLACEHOLDER: HR office hours or [email protected]] </inputs> <task> Write a rollout announcement email with a subject line, a short body (150 to 200 words) naming the key changes specifically, the required action and deadline, and where to ask questions. </task> <constraints> - Name the specific changes given, do not just say "minor updates" - State the deadline exactly as given, make it prominent - Keep the tone informative, not alarming </constraints> <format> Subject line followed by the full email body, clearly labeled. </format>
Writes the handbook rollout email naming the specific changes and the acknowledgment deadline, so employees know exactly what to do.
Pro tip: Name the actual changed policies in the subject or first line; a vague "handbook update" email gets lower open and completion rates than one that says what changed.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.