---
name: booth-staffing-schedule
description: Builds booth and onsite staffing schedules for trade shows, conferences and user conferences from show hours, staff availability, roles (qualifier, demo, exec, SDR, booth captain) and booked meetings. Enforces minimum role coverage, breaks, maximum shift length and travel constraints, avoids double-booking people who have meetings, and outputs a shift grid, per-person schedules and a list of coverage gaps. Use for booth duty rosters, staff shift schedules, onsite staffing plans or rebuilding a schedule around meetings.
license: MIT
metadata:
  author: eventmarketingsoftware.com
  version: "1.0"
  category: trade-shows-and-field
  source: https://eventmarketingsoftware.com/skills/booth-staffing-schedule
---

# Booth staffing schedule

Turn show hours, a staff list with roles and availability, and any booked meetings into a fair shift schedule that
keeps the booth covered by the right roles at all times, gives everyone breaks, and never puts someone on the booth
when they're in a meeting.

## Intake

If the user has an `event-context.md` file, read it first. Then ask for anything missing in ONE message:

1. Show days and booth hours each day (plus setup and teardown if staff cover them), and the time zone.
2. Booth size, so you can check headcount against space (see benchmarks).
3. Staff list: name, role (qualifier, demo, exec, SDR, AE, booth captain), and availability by day (arrival and
   departure times, sessions they're speaking at, other commitments).
4. Coverage rules: minimum per role at all times (for example 2 qualifiers and 1 demo), peak times needing more,
   maximum people in the booth at once.
5. Booked meetings: person, date, start, end, location (in booth or elsewhere).
6. Preferences: slot length (default 30 minutes), maximum shift length (default 3 hours), minimum break between shifts
   (default 30 minutes), whether execs only cover peak times.

If any rule is missing, use the defaults above and list them as assumptions.

## Connectors (optional)

- **Google Sheets connector:** read availability and meetings; write the grid to a new tab after approval.
- **Slack connector:** send each person their shifts as a direct message or post the grid to the event channel, only
  after showing every message and getting a yes.
- **No connector:** work from pasted text or CSV/XLSX; return a Markdown grid and CSV files.

## Method

```
- [ ] 1. Build the slot grid
- [ ] 2. Block unavailable time and meetings
- [ ] 3. Fill minimum role coverage
- [ ] 4. Add peak coverage and balance hours
- [ ] 5. Insert breaks and enforce shift limits
- [ ] 6. Check coverage and fairness
- [ ] 7. Produce grid, per-person schedules and gaps
```

### 1. Slot grid
Split each show day into slots (default 30 minutes) from booth open to close. Add a 15-minute pre-open slot for the
first shift each day if the user wants a morning huddle.

### 2. Blocks
First clean the inputs: normalize times to 24-hour HH:MM, drop exact duplicate meetings (report how many), and list
anyone with blank or unclear availability as a question rather than guessing. Then mark each person unavailable outside their arrival and departure times, during their speaking sessions and during
booked meetings. Add travel time around meetings held outside the booth (default 15 minutes each side; ask for
large venues). Meetings held in the booth's meeting area still remove the person from floor coverage.

### 3. Minimum coverage
For each slot, assign people to meet the minimum per role. A person counts toward one role per slot. Prefer people
with the fewest assigned hours so far. Booth captain: one per slot if the user wants one, usually a senior marketer.

### 4. Peak and balance
Add extra coverage at peaks (opening hour, breaks between sessions, receptions on the floor) up to the maximum
people in the booth. Balance total booth hours across people with the same role; execs and AEs can carry fewer floor
hours when they hold meetings.

### 5. Breaks and limits
No continuous booth time longer than the maximum shift length. At least the minimum break between shifts. Everyone
gets a meal break on full days. Prefer contiguous shifts over scattered single slots.

### 6. Check
- Every slot meets minimum role coverage, or is listed as a gap with the reason.
- Nobody is on the booth during a meeting, session or outside availability.
- No shift exceeds the maximum length; breaks are respected.
- Headcount per slot never exceeds the maximum in the booth.
- Hours per person are within a fair range for their role; show the min and max.

Run `scripts/check_schedule.py` to verify when code execution is on, or do the same checks in-chat.

### Rebuilding around changes
When meetings are added or someone drops out, keep as much of the existing schedule as possible, change only the
affected slots, and list every change (person, slot, before, after).

## Output

1. **Assumptions:** slot length, shift limits, coverage rules, travel buffers.
2. **Shift grid** per day: rows are slots (`time`), columns are roles, cells list names. Example header:
   `time | qualifier | demo | exec | booth_captain | total_on_booth | meets_minimum`
3. **Per-person schedules:** one block per person with day, shift start and end, role, meetings, breaks. Short
   enough to paste into a message.
4. **Long-format CSV** for checks and sheets: `person, role, date, start, end, activity` where activity is booth,
   meeting, session or break.
5. **Coverage gaps:** date, slot, missing role, suggested fix (who's free, or reschedule a meeting).
6. **Hours summary:** person, role, booth hours, meeting hours, total.

Example output: [references/examples.md](references/examples.md). Headcount and shift-length guidance:
[references/benchmarks.md](references/benchmarks.md).

## Approval gates

- Show every Slack message (or a sample plus the count) and the channel or recipients before sending. Send only
  after a clear yes.
- Don't write to a shared sheet that people are already using without a yes; default to a new tab.

## Script (optional)

```
python scripts/check_schedule.py schedule.csv --min qualifier=2 --min demo=1 --open 09:00 --close 17:00 --max-shift 180 --slot 30
```

Reads the long-format CSV (`person, role, date, start, end, activity`) and reports slots under minimum coverage,
people double-booked (booth and meeting at once), shifts longer than the limit and hours per person. Standard library
only.

## Related skills

booth-staff-briefing (roles and the schedule section of the briefing), pre-show-meeting-outreach (booked meetings),
exhibitor-manual-deadlines (badge allocation, move-in times).

Sample inputs: `assets/sample-staff-availability.csv` and `assets/sample-meetings.csv`.
