Swaps & blackouts

Life happens without blowing up the schedule

Volunteers tell the system when they're away and trade dates between themselves. Leads approve — they don't coordinate.

How a swap goes

  1. 1

    Volunteer requests

    They pick the date they can't serve and, optionally, a teammate to trade with.

  2. 2

    Eligible people are offered

    Only volunteers trained for that position and free that day are asked.

  3. 3

    Someone accepts

    First acceptance takes the slot; everyone else's request closes automatically.

  4. 4

    Lead approves

    One tap confirms, and both volunteers get the update by text.

Blackouts that scheduling respects

Set once, honored always

Vacations, school terms and recurring conflicts are excluded before rotations are built.

Trade, don't drop

Swaps keep coverage intact instead of leaving an open position behind.

Everyone stays informed

Requests, approvals and declines all trigger alerts and texts.

One-tap approvals

Leads clear the whole queue from the alert center.

Fairness preserved

Swap history feeds back into future rotations so nobody carries the load.

Guardrails

Position training and background-check status are checked before a swap sticks.

End the Saturday-night group text

Build your roster, generate a year of schedules, and let volunteers see only what matters to them.