Volunteer Shift Coverage Grid Prompt

Start here

Paste into any ordinary AI chat that accepts text. No terminal or API setup is needed. You supply two things: the prompt below, then your own scheduling material in the same message.

Input to prepare before pasting:

• The event or operating period (dates, location if given)
• A roster: each volunteer's name, any stated role or skill, any stated constraints (for example, can only lift light items, no driving, must be paired)
• Shift definitions: each shift's date, start time, end time, and number of volunteers needed
• Availability notes: each volunteer's stated available and unavailable dates or times, copied as given
• Any fixed assignments already confirmed
• Optional priority rules: which shifts are most critical, and how many backups are wanted per shift

How to paste: put the prompt text first, then your roster, shifts, and availability notes below it in the same message. Start with one real event rather than several at once.

How to check the output: read the coverage grid row by row and confirm every shift appears once, and that each shortfall equals volunteers needed minus confirmed assignments you actually gave. No slot should be filled without a quoted line of your availability text supporting it. Notes like "maybe" or "probably" must stay Unclear and appear under open items. Overlapping shifts for the same person belong in the conflicts section, not in the grid as a solution.

Introduction

This is a reusable prompt for volunteer coordinators. It converts messy availability notes into a coverage grid that separates shifts already covered from those that are short or empty, and then lists the decisions a human scheduler must make. The purpose is not to schedule people, but to make gaps and ambiguities visible before anyone is contacted.

Permissions and limitations

The prompt works only from material pasted into the message. It does not invent people, shifts, skills, or confirmations, and it states nothing about anyone being contacted, confirmed, or scheduled. It does not send, post, or share anything, does not create calendar entries or messages, and does not give legal, medical, safeguarding, or insurance advice; such questions are flagged for the human. Final scheduling, outreach, and any commitment stay with the human scheduler.

If the roster is empty or no shift definitions are given, the correct response is to say so and list exactly what to provide. A blank or flagged slot is a correct result, not a failure.

Example below is fictional and only shows the output shape: Event is a Saturday community repair cafe. Shifts: S1 09:00-12:00 needs 2; S2 12:00-15:00 needs 2. Roster: Ana (electrical), Ben (general), Chloe (general). Availability: Ana free all Saturday morning only; Ben away until 13:00; Chloe says maybe afternoon. S1 would show Ana as an available candidate with one open slot and Status Short; S2 would show Ben available after 13:00, Chloe as Unclear, Status Short.

FAQ

Does the prompt contact or confirm volunteers? No. It only prepares a draft grid. Contacting people and any commitment remain with the human scheduler.

What if availability notes are vague? Vague wording such as "maybe" stays Unclear and is listed under open items with the specific question the scheduler must answer.

What if a shift has no end time or no stated volunteer count? That shift is marked Unclear and the missing value is requested.

Verification note

source reviewed; runtime not tested.

Complete reusable prompt

You are helping a volunteer coordinator build a coverage grid from a roster and availability notes. Work only from the material the user pastes in this message. Do not invent people, shifts, skills, or confirmations.

INPUTS THE USER PROVIDES

• The event or operating period (dates, location if given).
• A roster: each volunteer's name, any stated role or skill, and any stated constraints (for example, can only lift light items, no driving, must be paired).
• Shift definitions: each shift's date, start time, end time, and number of volunteers needed.
• Availability notes: each volunteer's stated available and unavailable dates or times, copied as given.
• Any fixed assignments the user says are already confirmed.
• Optional priority rules: which shifts are most critical, and how many backups are wanted per shift.

YOUR TASK Produce a coverage grid that shows which shifts are covered, which are short, and which are empty. Then produce a short list of decisions the human scheduler must make. Do not assign anyone to a shift unless the availability notes clearly allow it. When availability is vague, partial, or missing, leave the slot open and flag it.

OUTPUT FORMAT

1. Coverage grid, one row per shift in date then start-time order. Columns: Shift ID | Date | Start | End | Volunteers needed | Confirmed (from user's fixed assignments) | Available candidates | Shortfall | Status. Status is one of Covered, Short, Empty, or Unclear.
2. Candidate pool per shift: for each person who appears available, one line naming them and quoting the exact availability text that supports it. If none, write none identifiable from supplied notes.
3. Open slots needing a human decision: numbered list. Each item states the shift, the gap, and the specific question the scheduler must answer.
4. Conflicts and constraints to check: overlaps between shifts, stated constraints that clash with a role, and people whose notes are ambiguous.
5. Follow-up information to collect: a short list of what is missing before a final schedule can be made.

RULES

• Never fill a slot by guessing. A blank or flagged slot is a correct result.
• Never state that anyone has been contacted, confirmed, or scheduled. You are preparing a draft grid for a human to review.
• Quote the user's availability wording when justifying a candidate. Do not paraphrase it into stronger language.
• If two shifts overlap and one person appears available for both, show it as a conflict, not a solution.
• If a shift has no defined end time or no stated number of volunteers, mark it Unclear and ask for the missing value.
• Keep names exactly as supplied. Do not merge similar names unless the user says they are the same person.
• If the roster is empty or no shift definitions are given, say so and list exactly what to provide.

WORKED EXAMPLE Fictional input: Event is a Saturday community repair cafe. Shifts: S1 09:00-12:00 needs 2; S2 12:00-15:00 needs 2. Roster: Ana (electrical), Ben (general), Chloe (general). Availability notes: Ana free all Saturday morning only; Ben away until 13:00; Chloe says maybe afternoon. Illustrative output shape: S1 shows Ana confirmed only if the user listed her as fixed; otherwise Available candidate Ana, one open slot, Status Short. S2 shows Ben as available after 13:00, Chloe as Unclear because maybe is not a commitment, Status Short. Open item: S1 needs one more volunteer; S2 needs a decision on whether to count Chloe and who covers 12:00-13:00.

PASS/FAIL CHECKS BEFORE YOU RETURN

• Pass if every shift appears exactly once and each row's shortfall equals volunteers needed minus confirmed assignments you were actually given.
• Pass if no slot is filled without quoted supporting availability text.
• Pass if vague notes such as maybe or probably stay Unclear and are listed under open items.
• Pass if overlaps between shifts appear in the conflicts section.
• Fail if you invented a name, a skill, a confirmation, or a shift.
• Fail if the grid implies someone was contacted or scheduled.

BOUNDARIES

• Do not send, post, or share anything. Do not create calendar entries or messages.
• Do not give legal, medical, safeguarding, or insurance advice. If the notes raise such a question, flag it for the human.
• Final scheduling, contacting volunteers, and any commitment remain with the human scheduler.

References and reuse

• ChatGPT release notes

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