Plan Staffing
plan_staffingCreate a staffing plan based on event city, date, roles, and headcount. Get estimated W-2 rates, lead-time tiers, and compliance flags before submission.
Instructions
CALL THIS FIRST for event staffing requests. Returns a configured-market catalog match, role-level W-2 rate math, estimated totals, tier-based lead-time guidance, and state compliance flags from the event's city, date, roles, and headcount. It does not confirm order coverage or live inventory; a coordinator does that after buyer submission. Use granular tools only for a single rate, date, or state fact. A complete plan may save a non-contact snapshot for 30 days and return plan_id plus continuation. If it returns no plan_id and the buyer needs persistence, call save_staffing_plan once; never save a plan that already has an ID. This tool never accepts or submits contact details, reserves staff, or creates a quote request. Omit roles for the catalog and a suggested mix. Treat totals as planning estimates, not quotes. Branch on status: plan, needs_roles, roles_not_found, or city_not_found; confirm suggestions rather than auto-applying them.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| city | Yes | Event city, name or slug (e.g., 'Chicago'). | |
| roles | No | Roles and headcount. Omit to receive the role catalog and a suggested mix. | |
| attendees | No | Expected attendee count. | |
| event_date | No | Event date as YYYY-MM-DD; legacy recognizable dates are still accepted. | |
| event_type | No | trade-show, conference, festival, concert, sporting-event, corporate, brand-activation, or other. | |
| description | No | Optional free-text event description, echoed into the plan. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tip | No | ||
| event | No | ||
| status | Yes | Discriminator. Branch on this before reading the rest. | |
| message | No | ||
| plan_id | No | Complete plans only. Non-PII plan reference retained for 30 days when Redis persistence succeeds. | |
| lead_time | No | ||
| compliance | No | ||
| next_steps | No | ||
| offer_note | No | Published first-order offer note. Totals remain undiscounted planning estimates. | |
| plan_lines | No | ||
| suggestion | No | Closest known city/role for a miss. Confirm with the user before using it; do not auto-apply. | |
| continuation | No | Complete plans only. Prefilled website handoff; may be present without plan_id when storage fails open. | |
| plan_complete | No | status:plan only. false = one or more requested roles could not be priced and are EXCLUDED from all totals (see unpriced_roles) — resolve them and re-plan before presenting a budget or quoting. | |
| requested_city | No | ||
| staffing_notes | No | ||
| unpriced_roles | No | status:plan with plan_complete:false — the requested lines missing from every total. | |
| available_roles | No | ||
| requested_roles | No | ||
| unresolved_roles | No | ||
| estimated_total_range | No | ||
| overtime_adjusted_total_range | No | Present (non-null) only when daily/weekly OT (or a double-time band) applies to the schedule. |