Broadcasts go to every connected shifter at once. The first acceptable response wins. To maximize the odds of someone good claiming it:
Be specific about role
If the shift is for a server, mark it as a server shift. Shifters filter by role; "any role" broadcasts get fewer claims because nobody's sure if they qualify.
Set a fair rate
Connected shifters know your usual rates. Lowballing a broadcast underperforms. If it's a difficult shift (overnight, holiday, last-minute), bump the rate.
Use the description
Two sentences are enough: "Friday brunch service, 9am-1pm. Solo bar shift, you'll be running the floor with one server. Recent brunch experience preferred."
Mark flexible if it's flexible
Open windows ("anytime between 5pm and 7pm to start") attract more claims than fixed-time-only.
Send within ~24 hours of when you need it filled
Broadcasts to fill three weeks out generally don't get claimed quickly because shifters can't yet predict their availability. For "next Friday" or sooner, broadcasts are far more responsive than targeted requests because you cast a wider net.
When NOT to broadcast
- High-skill or high-trust shifts (you want the right person, not the fastest claimant). Send targeted instead.
- Shifts you're saving for a specific person.