Shift-Swap Request Drafting Prompt

Start here

Paste the full prompt text (the complete prompt is appended separately) into any ordinary AI chat that accepts text. Then fill in your details under the "Input" block, or reply to the assistant's follow-up questions.

What to paste: the prompt itself, followed by your own details: your name and role, the shifts you want to give up (date, start/end time, role or station, location), any coverage you are asking for, a short reason, who has offered to cover and their confirmation status, known constraints (minimum staff, certifications, overtime rules, blackout dates), your manager's name and preferred channel, the tone you want, and any decision deadline.

Where to paste it: the message box of a normal AI chat. No terminal, account setup or API key is needed.

How to check the output: confirm every date and time appears exactly as you supplied it; confirm anyone offering cover is labelled "offered, not yet confirmed" unless you said otherwise; confirm any coverage gap or constraint is stated openly instead of being hidden or silently solved; and confirm the "approval requested" list names concrete actions rather than a vague "approve this".

Introduction

The prompt helps shift workers write a short, honest swap request that a manager can act on. It separates the shifts affected, who is covering, the gaps you cannot resolve yourself, and the exact approvals you are asking for. It forbids inventing policies, seniority rules, coworker availability or approvals.

See the reference ChatGPT release notes for context on the general-purpose chat workspace.

Prerequisites, permissions and limits

• You need the details above; the prompt will ask for anything missing and labels unknown items [TO CONFIRM].
• A normal AI chat that accepts text is enough. The prompt does not send messages, does not contact anyone, and does not arrange coverage on your behalf.
• It has no access to your real rota, certifications or employer policies, so every constraint it mentions must come from you.
• You still send the message yourself and confirm coverage before relying on it. Anything it writes is a draft, not an agreement.

FAQ

What if I don't have all the details? The prompt asks for the missing items first and waits. It will insert [TO CONFIRM] rather than guess, and the "Before you send" checklist lists what you still have to verify.

Will it claim my manager approved the swap? No. It only names what you are asking for, such as approving the swap, confirming coverage or updating the posted schedule. It never states that anyone already agreed.

Verification note

source reviewed; runtime not tested. The worked example in the prompt is fictional and shows shape only.

Attribution

Original TokRepo prompt, licensed under CC BY 4.0. The reference link retains its own rights.

Complete reusable prompt

You are helping me draft a shift-swap request message for my manager (or scheduler). Use only the details I supply. Do not invent approvals, coverage, policies, or agreements, and do not promise that anyone has already agreed.

First, in your own words, ask me for anything important that is missing. Then wait for my reply before drafting, unless I already gave all required items in the Input block below.

Required inputs

• My name and role/title
• The shift(s) I want to give up: date, start and end time, role/station, location
• The shift(s) or coverage I am asking for, if any
• Why I need the change (keep it brief; I will trim anything too personal)
• Who, if anyone, has already offered to cover: their name and confirmation status
• Coverage constraints I know: minimum staff per station, required certifications, overtime rules, blackout dates
• My manager's name and preferred contact channel
• Tone I want: formal / neutral / casual
• Any deadline for a decision

Second, check coverage risk. For every shift I want to give up, state whether the supplied information shows it will be covered, will NOT be covered, or is UNKNOWN. Flag any constraint that my request may violate. Do not solve it quietly.

Third, produce the message in this format:

1. Subject line: clear and specific (include date and 'shift swap request').
2. Greeting and one-sentence purpose.
3. Bullet list of the exact shifts affected, each with date, time, role, and location.
4. Who is covering, if confirmed, with status ('confirmed' or 'offered, not yet confirmed'). If nobody, say plainly that coverage is not yet arranged.
5. What I am asking the manager to approve, written as a short explicit list (for example: approve the swap, confirm coverage, adjust the posted schedule).
6. One sentence naming any coverage gap or constraint the manager must resolve.
7. A short closing with my contact method and decision deadline.
8. A separate 'Before you send' checklist with the items I must verify or fill in.

Rules

• No invented scheduling policy, no invented seniority or union rules, no invented availability of coworkers.
• Keep the message under 200 words unless I ask otherwise.
• Preserve every supplied date and time exactly; do not convert formats or time zones.
• If a detail is missing, insert [TO CONFIRM] rather than guessing.
• Do not claim the manager has approved anything.

Worked example (fictional, for shape only) Input: Name: Priya; Role: server; Give up: Sat 14 Sep, 17:00-23:00, front section, Main St location; Want: same week off; Cover: Tom said maybe; Constraints: two servers minimum, Priya is only certified keyholder on that shift; Tone: neutral; Deadline: decision needed by Thu 11 Sep. Expected output shape: Subject: Shift swap request - Sat 14 Sep

• Shift to give up: Sat 14 Sep, 17:00-23:00, server, front section, Main St.
• Coverage: Tom offered but is NOT yet confirmed.
• Gap: I am the only certified keyholder for that shift; this needs your resolution.
• Approval requested: approve the swap, confirm keyholder coverage, update the posted schedule.

Pass/fail checks against that example

• Pass only if every date and time matches exactly.
• Pass only if Tom is labelled unconfirmed.
• Pass only if the keyholder constraint appears in the message, not buried or omitted.
• Fail if any policy or approval is invented.
• Fail if the 'approval requested' list is vague, such as 'approve this'.

Finally, list any assumptions you made and any input I still need to supply. Keep this whole response as a ready-to-send draft plus the checklist, not a summary of these instructions.

References and reuse

• ChatGPT release notes

Original TokRepo prompt · CC BY 4.0. Reference documents retain their own rights.