Approve and publish.
And the email each person receives.
Part 4 of 17 · 1 min 24 s
Transcript
What the narration says, word for word (translated from the Spanish voice-over).
In this video: how a week gets approved and published, and what each person on the team receives.
The month is composed in full, but it isn't published in full. It's approved and published week by week, because that's how the work actually goes: what's close gets locked, what's further out keeps moving. Approving is the first signature. The week is marked approved and stops moving when the month is regenerated: the engine respects it.
Publishing is the second, and it's the one that speaks to the team.
On publish, each person receives only their own shifts by email, not the schedule of twenty people. They also get a calendar file, which puts those shifts on their phone, reminder included.
If something has to change later and be republished, Batuta first says how many people's hours changed, and who they are. Nobody gets an email that isn't theirs. And the published week is recorded exactly as it was published. What the team saw stays saved.
Want to see this with your own venue's shifts and staff? Write to us at usebatuta.com.
Recorded on a demo restaurant: invented names, no real person's data. There is no pilot running yet, so you will not see customer results here.