Keeps your system
GMs build schedules in the scheduling system they already use. Rallywise only reads the printed copy.
GMs keep scheduling the way they do now. They add a photo of the week's printed schedule and confirm each person's shifts, so people already working aren't asked to cover and overtime can be skipped.
The GM picks the first day of the week and adds a photo of the printed schedule pinned up in the store.
Rallywise can suggest each person's shifts from the photo. The GM checks them, or fills them in.
Nothing is used until the GM confirms each person's shifts. Then the photo is deleted.
People already on the schedule aren't asked to cover, and the hours feed the optional overtime check.
Without the schedule, a cover request goes to people who are already working that shift, and nobody can tell who's close to overtime until it's too late.
A confirmed week lets Rallywise skip people who are already working and, if the GM chooses, anyone headed into overtime, so the right people get asked first.
GMs build schedules in the scheduling system they already use. Rallywise only reads the printed copy.
No suggested row is used until the GM checks and confirms it.
The photo shows everyone's name, so it's deleted as soon as the GM confirms or discards the schedule.
Confirmed shifts are deleted after the week has passed.
No. It works next to it, using the printed copy your store already posts.
No. The overtime check uses only the hours in the GM's confirmed schedule, and the GM confirms before anyone is booked.
Only the store's GM, and only while the schedule is still a draft.
Their future shifts come off the confirmed schedule automatically.
Founding operators get free setup, a locked $50 rate and a walk-away at week 8.