100 Best Claude Employee Handbook Prompts for Event Planners

Direct Answer

The best Claude prompts for employee handbook for event planners are designed to give you a complete, role-based, ready-to-use handbook framework. They cover on-boarding, safety, vendor and client policies, data handling, incident response, and performance processes in clear, actionable formats that you can deploy immediately.

Introduction

This page is a practical prompt library for creating an employee handbook specifically for event planners. It helps HR and operations teams assemble consistent policies that scale across multiple events and venues.

Whether you manage a single conference or a portfolio of weddings and corporate gatherings, these prompts provide concrete language, templates, and checklists you can adapt to your organization’s needs.

How to Use These Claude Prompts

• Replace all placeholders like [industry], [audience], [product], [constraints], [data], [tone], and [format] with your specifics.
• Add or remove constraints to fit your policy standards and legal requirements.
• Ask for specific output formats such as bullet lists, template pages, or checklists, and request an executive summary when needed.
• Validate outputs by cross-checking with local labor laws and venue regulations.
• Consider running prompts in batches to cover onboarding, safety, vendor, and incident workflows separately.

100 Best Claude Employee Handbook Prompts for Event Planners

1. Introductory handbook overview: Role: You are a human resources policy architect. Task: Draft an executive summary for the employee handbook for event planners. Context: Include purpose, audience, scope, and access. Output: A concise overview in bullet list format with five items. Constraints: No jargon, suitable for non-technical readers, 60 to 90 words.
2. Role definitions for events: Role: Policy writer. Task: Define core event planning roles (event manager, vendor liaison, on-site supervisor, safety lead, registration coordinator) with responsibilities and clear escalation paths. Context: Use a table-like structure in plain text. Output: A structured list with role, primary responsibilities, and reporting lines. Constraints: Each role has 2–3 bullets.
3. Work hours and shifts: Role: HR advisor. Task: Establish standard work hours, shift patterns, overtime rules, and holiday coverage for event seasons. Context: Include part-time and full-time staff. Output: A policy section with bullet points and an example schedule for a two-week event cycle. Constraints: Include at least two sample shift templates.
4. Code of conduct for events: Role: Ethics policy specialist. Task: Create a code of conduct section covering professionalism, client interaction, vendor relations, and conflicts of interest. Context: Realistic scenarios for training. Output: A list of 8 to 12 rules with brief explanations. Constraints: Rules should be easy to enforce.
5. Safety and incident reporting: Role: Safety lead. Task: Outline safety policies for events, including incident reporting timelines, emergency contacts, and drill schedules. Context: Applicable to indoor and outdoor events. Output: A policy document with sections and a quick-reference card. Constraints: Include at least one flowchart-like step sequence in text.
6. Vendor management policies: Role: Procurement writer. Task: Define vendor onboarding, risk assessment, contract adherence, and performance reviews. Context: Include sample vendor scorecard. Output: A policy section with checklists and a sample scorecard. Constraints: 6–8 criteria.
7. Client communication guidelines: Role: Communications lead. Task: Establish preferred channels, response times, and escalation for client inquiries. Context: Include templates for emails and notes. Output: A guideline with 5 templates and a quick-reference table. Constraints: Use professional tone.
8. Onboarding new staff: Role: HR trainer. Task: Create a 30-day onboarding plan for event staff including training modules, shadowing, and feedback loops. Context: Align with handbook sections. Output: A numbered 30-day plan with milestones. Constraints: Include a simple checklist.
9. Documentation standards: Role: Documentation specialist. Task: Standardize how to document policies, training records, and incident reports. Context: Include naming conventions and storage locations. Output: A filing scheme with example file names and retention periods. Constraints: Use consistent tags.
10. Attendance and punctuality policy: Role: Compliance officer. Task: Define attendance rules, punctuality expectations, and consequences for violations. Context: Include examples for shift-based events. Output: A policy section with examples and a reminder template. Constraints: Include a one-page summary.
11. Pay and billing guidelines: Role: Payroll policy designer. Task: Outline payment terms for staff, vendors, and freelancers, including reimbursements and expense reporting. Context: Provide sample expense form. Output: A policy section with three example scenarios and a glossary. Constraints: Must satisfy local labor laws.
12. Equipment handling policy: Role: Operations lead. Task: Create guidelines for equipment use, storage, transport, and returns. Context: Include checklists for setup and teardown. Output: A policy section with 6 checklists. Constraints: Add a safety reminder.
13. Travel and lodging policy: Role: Travel coordinator. Task: Draft travel policies for staff attending offsite events, including booking procedures and per diems. Context: Consider multi-city events. Output: A policy page with booking steps and sample itineraries. Constraints: Include a travel approval workflow.
14. Code of ethics for vendors: Role: Compliance auditor. Task: Define ethical expectations for vendor interactions and gifts. Context: Include red flags and audit steps. Output: A 6-point ethics code with examples. Constraints: Simple language.
15. Data handling and privacy: Role: Data protection officer. Task: Outline data collection, storage, access, and deletion policies for attendee information. Context: Include examples of compliant data practices. Output: A policy section with roles and responsibilities. Constraints: Include a quick data flow diagram in text.
16. Emergency procedures: Role: Safety director. Task: Create step-by-step emergency procedures for different incident types. Context: Include communication trees and assembly points. Output: A ready-to-train procedure guide. Constraints: Include runbooks for two scenarios.
17. Accessibility policy: Role: Inclusion officer. Task: Ensure events comply with accessibility standards for venues, materials, and registration. Context: Include accommodations checklist. Output: A policy page with 8 accessibility requirements. Constraints: Cite relevant guidelines.
18. Conflict resolution: Role: HR mediator. Task: Provide a process for resolving disputes between staff, volunteers, and vendors. Context: Include mediation steps and escalation paths. Output: A flowchart-like list with 7 steps. Constraints: Use neutral language.
19. Remote work guidelines: Role: Ops manager. Task: Establish expectations for remote coordinators supporting events, including communication and time tracking. Context: Applicable to hybrid teams. Output: A policy section with two example schedules. Constraints: Include accountability measures.
20. Performance review framework: Role: HR strategist. Task: Build a lightweight annual review framework tailored for event planners, with goals linked to event outcomes. Context: Include rating scales and feedback prompts. Output: A template set for managers and staff. Constraints: 4 to 6 prompts per review.
21. Training and certification policy: Role: Training lead. Task: Document required trainings, certification renewals, and tracking methods. Context: Include renewal reminders. Output: A policy page with a training tracker template. Constraints: Include 3 example certificates.
22. Harassment policy: Role: Compliance officer. Task: Provide a zero-tolerance harassment policy with reporting paths and protection for reporters. Context: Include anonymous reporting options. Output: A policy section with escalation steps. Constraints: Include sample reporting form.
23. Dress code policy: Role: HR administrator. Task: Define event-specific attire standards, safety considerations, and client expectations. Context: Include examples by role. Output: A dress code list with visuals described in text. Constraints: 6 items.
24. Leave and time-off: Role: HR generalist. Task: Outline leave policies, accrual, and request processes for event calendars. Context: Include blackout periods during peak seasons. Output: A policy section with an approval flow. Constraints: Include sample forms.
25. Workplace safety reminders: Role: Safety coach. Task: Create a concise safety reminder set for daily briefs before events. Context: Include quick checks for first aid, emergency exits, and PPE. Output: A 1-page safety reminder with 12 bullets. Constraints: Actionable and easy to scan.
26. Venue access policy: Role: Operations supervisor. Task: Document venue access rules for staff, volunteers, and vendors, including credentialing. Context: Include badging templates. Output: A policy page with access levels and checklists. Constraints: Simple language.
27. Client data handling: Role: Data steward. Task: Define how client data is collected, stored, and deleted when projects end. Context: Include retention schedules. Output: A policy section with a data lifecycle diagram in text. Constraints: Include a deletion checklist.
28. Event-day decision log: Role: Event manager. Task: Create a standard decision log format for on-site decisions during events. Context: Include date, time, decision owner, and rationale. Output: A template log with 12 fields. Constraints: Use simple language.
29. Vendor performance reviews: Role: Procurement lead. Task: Establish quarterly vendor performance review process with criteria and scoring. Context: Include sample review form. Output: A scoring rubric and example filled form. Constraints: 4–6 criteria.
30. Incident response playbook: Role: Security coordinator. Task: Build a playbook for common incidents during events, with roles and recovery steps. Context: Include post-incident reporting. Output: A structured playbook with checklists. Constraints: 2 example incidents.
31. Sustainability policy: Role: Sustainability officer. Task: Define eco-friendly practices for events, waste reduction, and supplier selection. Context: Include a sustainable procurement checklist. Output: A policy page with 10 practices. Constraints: Include measurement ideas.
32. Language and communication policy: Role: Communications lead. Task: Specify inclusive language guidelines and client-facing communication norms. Context: Include templates and examples. Output: A policy page with 5 templates. Constraints: Avoid jargon.
33. Crisis communications plan: Role: PR lead. Task: Draft a crisis communications outline for events, including message approval and media handling. Context: Include a sample holding statement. Output: A plan with 6 sections. Constraints: Plain-text templates only.
34. Attendance tracking method: Role: Operations analyst. Task: Propose a simple attendance tracking method for on-site teams and volunteers. Context: Include a weekly reporting format. Output: A method description with forms. Constraints: 2 sample forms.
35. Training schedule templates: Role: Training coordinator. Task: Create reusable training schedule templates for different event sizes. Context: Include onboarding and refresher sessions. Output: Three templates with fill-in fields. Constraints: Include duration estimates.
36. Recruitment guidelines: Role: HR recruiter. Task: Define the recruitment flow for event roles, including posting, screening, interviews, and offers. Context: Include interview scorecards. Output: A policy page with flow steps. Constraints: 5 validation points.
37. Remote vendor coordination: Role: Project manager. Task: Outline best practices for coordinating remote vendors across time zones. Context: Include communication cadences. Output: A policy page with a weekly plan. Constraints: 3 example schedules.
38. Confidentiality policy: Role: Compliance officer. Task: Create a confidentiality agreement guideline for staff and vendors. Context: Include breach remedies. Output: A policy section with a sample clause. Constraints: Plain language.
39. Safety briefing templates: Role: Coordinator trainer. Task: Provide ready-to-use safety briefing templates for on-site teams. Context: Include role-specific briefings. Output: Five briefing templates with checklists. Constraints: Include a one-page summary.
40. Equipment inventory process: Role: Inventory control lead. Task: Describe how to track equipment from receipt to return. Context: Include audit-ready records. Output: A process document with forms. Constraints: Monthly cycle.
41. Volunteer engagement policy: Role: Community manager. Task: Outline guidelines for engaging volunteers, recognition, and complaints handling. Context: Include a volunteer handbook appendix. Output: A policy page with 7 bullets. Constraints: Include recognition ideas.
42. Work-product ownership: Role: Legal counsel. Task: Define ownership and rights for event deliverables created by staff and freelancers. Context: Include IP caveats. Output: A policy section with examples. Constraints: Plain language.
43. Health and wellness guidelines: Role: HR wellbeing lead. Task: Propose health and wellness resources for event teams, including mental health support. Context: Include confidential reporting. Output: A policy page with 5 resources. Constraints: Include contact details.
44. Remote access policy: Role: IT lead. Task: Define secure remote access for event planning teams, including MFA and device controls. Context: Include incident reporting for access issues. Output: A policy section with steps and examples. Constraints: Include enforcement notes.
45. Badge printing standards: Role: Credentialing coordinator. Task: Document badge design, data fields, privacy considerations, and reuse policies. Context: Include printable templates. Output: A badge standard page with 4 templates. Constraints: Include accessibility notes.
46. Client onboarding checklist: Role: Account manager. Task: Create a client onboarding checklist for new events, including kickoff meeting goals. Context: Include stakeholder map. Output: A checklist with 20 items. Constraints: Clear owner assignments.
47. Post-event evaluation: Role: Event analyst. Task: Define a post-event survey framework, data analysis plan, and reporting steps. Context: Include executive summary template. Output: A structured evaluation plan. Constraints: Include three KPIs.
48. Budget policy for events: Role: Finance liaison. Task: Establish budget approval, tracking, and variance reporting for events. Context: Include example reports. Output: A policy page with a budgeting flow. Constraints: Include sample dashboard view.
49. Ethics in tipping and gifts: Role: Compliance officer. Task: Clarify rules around tipping, gifts, and hospitality from vendors. Context: Include audit questions. Output: A policy section with examples. Constraints: Neutral tone.
50. Incident learning repository: Role: Knowledge manager. Task: Create a central repository for incident learnings with categories and search tags. Context: Include tagging conventions. Output: A structure guide and sample entry. Constraints: 8 tags max.
51. Data retention policy: Role: Data steward. Task: Define how long different data types are kept after events and how to dispose securely. Context: Include disposal methods. Output: A retention schedule and disposal workflow. Constraints: Comply with laws.
52. Catering and food safety: Role: Safety lead. Task: Provide food safety standards for event catering, including temperature controls and storage. Context: Include vendor responsibilities. Output: A policy page with 6 checks. Constraints: Include training reference.
53. Travel risk assessment: Role: Risk manager. Task: Create a travel risk assessment for staff traveling to events, including emergency plans. Context: Include mitigation actions. Output: A risk matrix and action list. Constraints: Use plain language.
54. Client privacy policy: Role: Privacy officer. Task: Outline how attendee and client data is stored, shared, and deleted. Context: Include consent language. Output: A privacy policy section with examples. Constraints: Include a data subject rights summary.
55. Remote work equipment policy: Role: IT administrator. Task: Define allowed devices, maintenance, and replacement cycles for remote work. Context: Include loaner equipment process. Output: A policy page with 4 device categories. Constraints: Include security tips.
56. Attendance escalation flow: Role: Operations analyst. Task: Create an escalation flow for persistent attendance issues. Context: Include manager notifications. Output: A multi-step flow with decision points. Constraints: 7 steps.
57. Venue risk management: Role: Event risk lead. Task: Document venue-specific risks and mitigations, including weather contingency. Context: Include checklists. Output: A risk register for a typical venue. Constraints: 10 items.
58. SOP library structure: Role: Knowledge architect. Task: Propose folder structure and naming conventions for event-related SOPs. Context: Include example file names. Output: A library map with categories and tags. Constraints: 5 top-level folders.
59. Employee recognition policy: Role: People manager. Task: Define recognition programs, eligibility, and nomination workflows. Context: Include sample messages. Output: A policy page with 4 recognition ideas. Constraints: Simple language.
60. Data breach response: Role: Security officer. Task: Provide a rapid breach response plan for personal data. Context: Include notification timelines. Output: A concise playbook with steps and owners. Constraints: 6 steps.
61. Workload balancing guidelines: Role: Ops lead. Task: Create guidelines to balance workloads during peak event periods. Context: Include staffing tools. Output: A policy section with two balancing methods. Constraints: Include example scenarios.
62. Accessibility onboarding: Role: Inclusion lead. Task: Ensure new-hire onboarding materials meet accessibility requirements. Context: Include checklist and alternative formats. Output: A compliance-ready onboarding guide. Constraints: 5 accessibility checks.
63. Cultural sensitivity policy: Role: Diversity officer. Task: Define expectations for respectful behavior and cultural awareness at events. Context: Include training prompts. Output: A policy page with 6 scenarios. Constraints: Include coaching tips.
64. Event-day vendor liaison: Role: Vendor manager. Task: Provide a protocol for on-site vendor coordination, check-in, and issue resolution. Context: Include a contact tree. Output: A step-by-step protocol. Constraints: 8 steps.
65. Host communications guideline: Role: Host liaison. Task: Create guidelines for host communications with attendees, speakers, and sponsors. Context: Include timing and tone notes. Output: A guideline page with 5 templates. Constraints: Use consistent branding.
66. Parking and transportation policy: Role: Operations coordinator. Task: Define parking, shuttles, and transit allowances for events. Context: Include signage and staff instructions. Output: A policy section with maps. Constraints: Include cost details.
67. Language translation policy: Role: translator lead. Task: Establish translation/interpretation policies for multilingual events. Context: Include vendor coordination. Output: A policy page with 3 service models. Constraints: Include turnaround times.
68. Media consent policy: Role: Compliance officer. Task: Draft media release and consent guidelines for attendees and participants. Context: Include usage rights. Output: A policy page with consent templates. Constraints: Plain language.
69. Incident reporting form: Role: Compliance admin. Task: Create a standardized incident report form for on-site events. Context: Include fields for date, time, people involved. Output: A fillable form in plain text. Constraints: Should be copy-paste ready.
70. Asset disposal policy: Role: Assets manager. Task: Define how to retire and dispose of event assets, including data sanitization. Context: Include documentation steps. Output: A disposal policy with checklists. Constraints: Include sign-off.
71. Airport transfer policy: Role: Travel coordinator. Task: Document procedures for airport transfers and delays during events. Context: Include contact list. Output: A policy page with 3 scenarios. Constraints: Include refund guidelines.
72. Conflict of interest disclosure: Role: Compliance officer. Task: Create a simple COI disclosure process for staff and vendors. Context: Include annual reminder. Output: A policy section with form templates. Constraints: 2 forms.
73. Confidentiality exception policy: Role: Legal counsel. Task: Define what information may be shared in emergency situations and to whom. Context: Include safeguarding notes. Output: A policy page with 5 exceptions. Constraints: Clear language.
74. Social media guidelines: Role: Communications lead. Task: Establish approved social media channels, posting cadence, and crisis rules. Context: Include examples of approved posts. Output: A guideline page with 6 templates. Constraints: Include monitoring tips.
75. Refund and cancellation policies: Role: Finance liaison. Task: Document event-related refunds, cancellations, and penalties. Context: Include customer communication templates. Output: A policy page with 4 scenarios. Constraints: Transparent terms.
76. Event accessibility testing: Role: QA lead. Task: Propose testing steps to verify accessibility of venues, apps, and materials. Context: Include checklists and pass criteria. Output: A test plan with 8 items. Constraints: Collaborative run-through required.
77. Catering allergy policy: Role: Safety lead. Task: Define allergy handling procedures for catering staff and kitchens. Context: Include label requirements. Output: A policy page with 5 allergy workflows. Constraints: Include supplier guidance.
78. Volunteer hours reporting: Role: Volunteer coordinator. Task: Create a system for tracking volunteer hours and shifts. Context: Include approval steps. Output: A simple timesheet template. Constraints: 2 example entries.
79. Non-disclosure reminders: Role: Legal assistant. Task: Add periodic NDA reminders and renewal prompts to the handbook. Context: Include sample notices. Output: A policy section with reminder templates. Constraints: Clear language.
80. Event data analytics policy: Role: Data analyst. Task: Specify data collection for analytics and reporting while protecting privacy. Context: Include dashboards. Output: A policy page with data categories. Constraints: Include sampling notes.
81. Post-event cleanup duties: Role: Operations lead. Task: Define cleanup responsibilities and waste disposal procedures after events. Context: Include checklists. Output: A duty matrix with owners. Constraints: 8 items.
82. Safety training cadence: Role: Training manager. Task: Schedule recurring safety trainings aligned with events calendar. Context: Include attendance tracking. Output: A training calendar with reminders. Constraints: Annual refresh.
83. Incident follow-up actions: Role: Safety officer. Task: List required follow-up actions after any incident, including root cause analysis. Context: Include responsible party. Output: A remediation plan with timelines. Constraints: 5 actions.
84. Background check policy: Role: HR leader. Task: Specify when and how to conduct background checks for event staff and vendors. Context: Include consent requirements. Output: A policy page with checklists. Constraints: Compliance notes.
85. Equipment return policy: Role: Inventory manager. Task: Detail the return process for rented and borrowed equipment. Context: Include inspection criteria. Output: A return procedure with form templates. Constraints: 4 steps.
86. Emergency contact directory: Role: Admin. Task: Create a centralized emergency contact directory for events. Context: Include on-site posting guidelines. Output: Directory template with access roles. Constraints: Updated monthly.
87. Event badge privacy: Role: Compliance specialist. Task: Explain privacy considerations for attendee badges and QR codes. Context: Include data minimization notes. Output: A policy page with badge design tips. Constraints: 4 privacy tips.
88. SLA for internal teams: Role: Ops manager. Task: Define service level agreements between planning teams and on-site teams. Context: Include response times and ownership. Output: An SLA document with metrics. Constraints: 3 examples.
89. Crisis drill schedule: Role: Training coordinator. Task: Plan quarterly crisis drills for event teams. Context: Include debrief protocol. Output: A drill calendar with checklists. Constraints: 4 drills.
90. Vendor breach protocol: Role: Security officer. Task: Outline steps if a vendor experiences a data or security breach. Context: Include notification tasks. Output: A incident workflow with owners. Constraints: 6 steps.
91. Remote collaboration norms: Role: Project manager. Task: Establish norms for remote collaboration tools and etiquette. Context: Include meeting templates. Output: A norms page with examples. Constraints: 5 rules.
92. Workplace accessibility audit: Role: Accessibility auditor. Task: Provide a simple audit checklist for handbook readers with disabilities. Context: Include remediation suggestions. Output: An audit report template. Constraints: 7 items.
93. Privacy-by-design: Role: Data protection officer. Task: Integrate privacy considerations into every handbook section. Context: Include a mini-checklist. Output: A privacy-by-design page with examples. Constraints: 6 steps.
94. Event sponsorship guidelines: Role: Sponsorship lead. Task: Define sponsor interactions, branding permissions, and payments. Context: Include conflict checks. Output: A policy page with 5 sponsor rules. Constraints: Clear approval path.
95. Remote incident communication: Role: Communications lead. Task: Draft a protocol for communicating incidents that occur remotely during events. Context: Include notification templates. Output: A workflow with 6 steps. Constraints: Include public disclosure notes.
96. Post-event debrief template: Role: Program manager. Task: Create a standardized debrief template to capture learnings. Context: Include stakeholder feedback prompts. Output: A fillable template with sections. Constraints: Include rating scale.
97. Legal hold policy: Role: Legal counsel. Task: Define when to issue legal holds during event investigations. Context: Include notification workflow. Output: A policy page with 4 steps. Constraints: Clear language.
98. Employee data access: Role: IT administrator. Task: Specify who has access to employee records and how access is granted and revoked. Context: Include audit logs. Output: An access control policy with steps. Constraints: Include revocation timing.
99. Event risk register: Role: Risk manager. Task: Build a living risk register for typical events with likelihood and impact scores. Context: Include mitigations. Output: A template with 12 entries. Constraints: Regular updates.
100. handbook versioning policy: Role: Policy architect. Task: Establish versioning, change control, and publishing processes for the handbook. Context: Include update logs and approval steps. Output: A versioning guide with templates. Constraints: 3 approval milestones.

Best Practices

• Write prompts that specify the exact audience and role so the output matches your handbook sections.
• Request structured outputs (bullets, checklists, templates) to ease integration into your document editor.
• Include compliance and risk angles to ensure policies meet legal and safety standards.
• Save prompts as reusable templates and tailor them per event or department to maintain consistency.

Common Mistakes to Avoid

• Using generic or vague prompts that produce broad policies beyond your jurisdiction.
• Omitting audience and role details which makes outputs misaligned with handbook sections.
• Not enforcing a consistent output format, causing messy integration into the handbook.
• Overloading prompts with too many requirements in one go, reducing clarity and usefulness.

FAQ

What makes a prompt good for an employee handbook for event planners?

A good prompt is specific about roles, policies, outputs, and audience, and yields ready-to-use sections, checklists, or templates that can be directly inserted into a handbook.

How should I customize prompts for different events?

Adjust placeholders for venue type, staff size, compliance requirements, and brand voice, and request examples tailored to those variables.

Can these prompts cover safety and legal requirements?

Yes, prompts include safety procedures, incident response, vendor compliance, data privacy, and conflict of interest sections aligned with typical event operations.

What output formats do prompts produce?

Prompts can output bullet lists, templates, checklists, narrative policies, or structured tables suitable for handbook editors.

How can I ensure prompts stay up to date?

Create a versioning plan, store prompts in a changelog, and schedule periodic reviews aligned with policy changes or new regulations.

Are these prompts suitable for onboarding new HR staff?

Yes, many prompts generate onboarding templates, role definitions, and initial training plans that help new HR staff ramp quickly.