Turn Your Staff Rules into Clear Policies for Breaks, Swaps, Call-Outs and Phones
You get a one-page staff policy table covering breaks, shift swaps, call-outs and phone use, with one-sentence rules, a consequence for each, and flags to fix.
Prompt
Act as an operations manager who has written staff handbooks for restaurants, cafes and small retail shops.
Your job: turn my existing staff rules into clear policies on four topics: breaks, shift swaps, call-outs and phone use. I will paste my current rules, notes or old handbook text right after this prompt. If I paste nothing, first ask me these questions in one message and wait for my answers:
1. What type of business is it, and how many staff?
2. How long are typical shifts, and what breaks do staff get now?
3. How do swaps and call-outs work today, and what goes wrong most?
4. What is your current rule on phones during shifts?
Rules:
- Each policy is one sentence, under 30 words, written to the staff member as "you".
- Every policy has a stated consequence, stepped from first to repeat offense.
- Use exact numbers wherever timing matters (hours of notice, minutes of break).
- Keep the intent of my rules; label any rule you add as "Suggested".
- Plain words a 16-year-old new hire understands on first read.
Output format:
1. Table: Topic | Policy | Consequence
2. Flags: vague, contradictory or hard-to-enforce rules, each with a suggested fix
3. A two-line acknowledgment for staff to sign
End with one line noting that break and scheduling laws vary by location, this is not legal advice, and I should check local labor law or an employment lawyer before publishing.Example output
Tips and common edits
Why this works
- One-sentence policies under 30 words keep rules readable for new and young hires on a shift.
- Requiring a stepped consequence for every rule removes guesswork and makes enforcement consistent across managers.
- The Flags section catches vague or conflicting rules you already have before staff exploit or misread them.
Use this when your rules live in group chats, sticky notes or an old handbook. Paste them into ChatGPT, Claude or Gemini, or answer its four questions. Know your shift lengths and current break setup.
Common edits
- Add topics like uniforms, tip pooling or clocking in late to the four covered here.
- Ask for a Spanish version of the table for bilingual staff.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Build a Weekly Staff Shift Schedule Around Peak Hours and Availability
Get a one-week shift schedule plus an hour-by-day coverage grid, with labor hours totaled against your budget and every understaffed hour flagged.
Design a Loyalty Punch-Card Program That Protects Your Margins
Get two loyalty reward structures compared by true cost per returning visit, a recommended program with card wording, anti-abuse rules and a 90-day tracking plan.
Plan a Local Event or Community Partnership That Brings In New Customers
Get three event ideas matched to your space and budget, a cost breakdown, a ready-to-send partner outreach message and a four-week prep timeline.
Write a Polite Email to a Supplier About a Late, Short or Damaged Delivery
Get a firm, friendly supplier email that lists the exact shortfall and its impact, asks for one remedy by a set date, and includes a follow-up line.
Turn Health Inspection Notes into a Ranked Fix Plan with Owners and Deadlines
Paste your inspection report or notes and get every finding ranked by risk and cost, with an owner, a deadline, prevention checks and when to call a pro.
Write Restaurant Menu Item Descriptions From Your Ingredients and Cooking Methods
You get a menu table with a description under 25 words for each dish, its word count, allergen codes, and a short list of items to confirm with the kitchen.