Schedules that build themselves
Staff send availability from a QR code, and your rules do the rest. You get a finished schedule to approve, for as long as you schedule ahead, not a blank grid to fill.
Swigs Flow builds your staff schedule from availability and your house rules, then keeps every shift covered when someone calls off. Your managers approve. The system does the rest.
The problem
Somebody sits with last week's sheet, a pile of texts about availability and a list of who can't work with who, and rebuilds the next schedule by hand. Game week or a holiday, and it starts over from scratch.
A bartender can't make tonight. Now the manager is scrolling contacts, texting five people one at a time, and hoping someone answers before doors.
Attendance policy lives in a manager's head, so two people who called off the same way can end up treated differently, and staff notice.
A shift moved on Tuesday. Half the staff are still holding the old copy, and somebody turns up for a shift that isn't theirs anymore.
Swigs Flow takes all four off your plate. Here's how.
How it works
Set up once. After that, the system does the building and the chasing, and your managers make the calls.
Your roster, your shift times, what a normal night looks like, who can lead, and your attendance policy. You start from a standard week and we shape it to yours, once, together, as your settings.
A QR code in the back of house and a link in the group chat. Staff tell the system when they can work and ask for time off. You can see at a glance who hasn't answered.
A week, two weeks or a month. Each night is laid out from its usual shape, or from the event you put on the calendar, then every shift is filled by your rules: leads, on-call order, seniority, nights in a row. Anything it can't fill cleanly is flagged, not guessed.
Look it over and change anything: add a shift, move a start time, close a night. Then publish. Staff get a printable schedule or a link, and the system keeps a record of exactly what went out.
Call-offs, cover, time-off requests and changes are handled as they happen, and every message waits for a manager's yes before it goes out.
A call-off, start to finish
The moment that eats a manager's evening, handled in the time it takes to read this.
The week that isn't normal
Every venue has a normal week, and then it has the other ones. Tell the system about them once and the schedule is ready for them.
A game day, a holiday, a private party, a week you are closed. Give it how busy it will be and how the night should look, and the build lays it out that way.
Your usual Wednesday and your usual Saturday are saved as shapes. Change one and every schedule after it follows. Keep a night that worked as a shape for next time.
Build a week, two weeks or a month at a time, starting whenever you like. A Monday you are normally closed can be opened for one night.
Add a shift, move a start time, swap two people or close the day. If the schedule has already gone out, the people affected get a note you approve first.
You set the controls
The agent is the same either way: it reads the call-off, ranks the cover, writes the order. What changes is who says yes. The owner chooses, one kind of decision at a time.
The agent does the work and drafts the decision. A manager reads it and taps yes. This is where every bar starts.
For the calls you want to make yourself: the liquor order over a set amount, a price change, the schedule going out. Your managers see it; only you can say yes.
The agent decides and acts on its own, and tells you what it did. Every action is still recorded with the reasons, and you can turn it back to approval at any time.
| Decision | Manager approves | Owner approves | Fully automatic |
|---|---|---|---|
| Ask for cover when someone calls off | |||
| Send the next schedule to staff | |||
| Approve a time-off request that breaks no rule | |||
| Place the weekly liquor order | |||
| Accept a new par from the buying history | |||
| Change a drink price the Margin Advisor suggests |
Set by the owner, per decision. A manager can always see what the agent did and why, whichever setting is on.
What you get
Staff send availability from a QR code, and your rules do the rest. You get a finished schedule to approve, for as long as you schedule ahead, not a blank grid to fill.
Logged, scored and ranked the moment it comes in, with the ask to the next person already written. You pick a name.
Every text and email waits as a draft until a manager says yes. It does the scheduler's work and leaves the decisions to people.
The published schedule is kept on record. Change a shift afterwards and it is recorded with a name, and a note to each person it affects is written for you to approve.
Count the bar in the order you walk it. Pars show what is short, and the order to each vendor is drafted for you to check.
OperationsLabor by night and by bar, and overtime caught while you build, even when someone's hours are split across more than one bar.
Owner tierRun one bar or several. Share a crew across them or keep them apart: each bar keeps its own rules, and hours split between bars are still added up.
Your leads, your on-call order, your busy nights, your attendance policy. Set up for how your bar already runs.
Most tools give you a grid to fill in. This one fills it, plans around your game days and holidays, then keeps it filled.
Tiers
Three tiers that stack, each one adding to the last. Pick a tab to see what each one does.
Availability comes in, your rules get applied, and your next schedule comes out ready to approve, event nights included. Every call-off is handled the same way whether or not you're in the building.
The same system that runs your staff runs your shelves. Counts get done because they are quick, and orders get placed because they are already written.
What the schedule costs before you approve it, what it cost against what you took, and an AI advisor that reads your sales, your costs and your prices and tells you what it would change. It covers every bar you run, because comparing bars side by side is the point.
Suggestions only. You decide what changes.
A note from the founder
As a bartender, I watched my owner fight the same battle every week: getting the schedule out, chasing call-offs, and getting inventory counted. So I built one system that handles all of it, and automates as much as it can.
The goal was simple: give my boss back the time to run the bar instead of drowning in the busywork.
It asks before it sends anything, because the people on the schedule are coworkers, not ticket numbers.
Questions
About two weeks. Setup is one conversation about how your bars run. Staff then send availability, and your first schedule is built from it. You can keep your current process running alongside until you trust it.
No. Staff use a link and a QR code from their phone. Managers use this website from a phone or a laptop.
Only if you tell it to. Out of the box every text and email is a draft until a manager approves it. An owner can let it act on its own, one kind of decision at a time, and can take that back whenever they like.
You choose, decision by decision. Keep manager approval on everything, send the big calls to the owner, or let it run fully automatic and read what it did afterwards. Whichever you pick, every action is recorded with who or what made it and why.
Any shift, any time. Changes are recorded with who made them, and the system tells you when staff are holding an older copy than the one you changed.
Put the game day, the holiday, the private party or the closure on the events calendar, and the build lays that night out the way you set it. Schedule a week, two, or a month at a time. After it's built you can change any single night, and if it has already gone out, the people affected get a note you approve first.
Either. One bar gets its own week. Several bars can share a crew or keep separate ones; each keeps its own rules, and overtime is caught when someone's hours are split between them.
A flat monthly amount for each bar, by tier, plus a one-time setup that covers the rules conversation and your first schedule built together. No per-employee fees, and nothing longer than month to month. We go through the numbers on the walkthrough.
It's yours. Your roster, schedules and attendance history export whenever you ask.
For labor cost it reads the standard sales export every POS can produce, so there is nothing to integrate. It doesn't run payroll.
Tell us how many bars you run and how you schedule today. We'll walk you through what your first schedule on Swigs Flow looks like.
Or write to hello@swigsflow.com