When you open a second branch, you copy the roster file and give it to the new manager. By the fifth branch, each manager has changed the file in their own way. Shift codes mean different things. Nobody in head office can see which branch is short on Saturday. A crew member who helps at two branches ends up on two shifts at the same time.
This guide is for chains of shops, restaurants, clinics, pharmacies and service teams with several sites. It assumes you already know how to build one good roster. If not, start with how to make a shift roster.
The problems that only appear with many branches
- Different formats. Each branch invents its own codes and layout, so head office cannot compare them.
- Shared staff. People who work at more than one branch are booked twice, or not at all.
- Hidden hours. Each branch counts only its own hours, so nobody sees that one person worked too many in the week.
- Late branches. Some branches publish on Thursday, others on Sunday night.
- No single view. Head office learns about a gap from a customer complaint.
Step 1: Decide what is central and what is local
Branch managers know their own floor best. Head office knows the rules and the whole picture. Split the work so each side does what it knows.
| Set once, for every branch | Set by each branch |
|---|---|
| Shift codes, times and breaks | Who works which shift |
| Your limits for rest between shifts and weekly hours | The cover needed on each day |
| The weekly deadline to publish | Local events, deliveries and busy days |
| Leave approval steps and attendance rules | Day-to-day changes and call-outs |
| Who may see and change each roster | Requests to borrow staff from another branch |
Your limits must also follow the law on hours and rest. Check the current DOLE rules or ask a payroll specialist before you fix them for every branch.
Step 2: Use one set of shift codes
If "AM" means 6:00 to 15:00 in one branch and 7:00 to 16:00 in another, every report that adds up shifts is wrong. Agree on one list of codes for the whole company. When a branch needs a different time, give it a new code. Do not reuse an old code with new times.
Step 3: Give each branch roster one owner
Make one person responsible for each branch roster each week, usually the branch manager or a scheduler. Give them a named backup for when they are away. Limit access so each manager can change only their own branch. A manager who can edit every branch will, sooner or later, change the wrong one.
Head office or an area manager can see all branches. Seeing is not the same as changing. Keep change rights local unless someone is covering for an absent manager.
Step 4: Plan for shared and floating staff
Most chains have people who work at more than one site: relief crew, area supervisors, a pharmacist who covers two branches. They cause most of the double bookings.
- Give each person one home branch, even if they float.
- When they work at another branch, check their shifts at every branch, not only the one you are building.
- Count their weekly hours across all branches against your limit.
- Check the rest gap when a late shift at one branch is followed by an early shift at another.
- Write down which branch asks for them first when two branches need them on the same day.
Step 5: Run one weekly calendar
A shared calendar gives every branch the same rhythm, and makes a late branch easy to spot. For example:
- Early in the week: each branch confirms its cover needs and approved leave.
- Midweek: requests to borrow staff go to the other branch manager.
- Before the deadline: each branch builds and checks its roster.
- On the deadline: every branch publishes, and head office checks which ones did not.
Pick days that suit your trade. A restaurant group may publish earlier than a clinic. What matters is that every branch uses the same days.
Step 6: Set a rule for borrowing staff
When one branch is short and another has spare people, the fix is obvious. The process often is not. Agree a simple rule: the branch that needs help asks the other branch manager, not the crew member directly. The lending manager agrees, and the borrowing branch adds the shift to its roster. This stops crew members from being pulled in two directions, and it keeps both rosters correct.
Step 7: Give head office one view
Once a week, head office or the area manager should be able to answer these questions without a phone call:
- Which branches have published next week, and which have not?
- Where are the open slots, by branch and day?
- Who is over the weekly hours limit, counting all branches?
- Which branches had the most late starts and no-shows last week?
- Where did overtime cost the most?
If the answers need five spreadsheets, the rosters are not really one system yet.
Step 8: Review the week
After each week, compare the roster with what happened. Look at late starts, no-shows and overtime by branch. A branch that always runs over may need more cover in the plan. A branch with many call-outs may need a talk about its patterns. Share what works: if one manager has a good way to plan weekends, others can copy it.
How Workforce Pinas handles many branches
In Workforce Pinas, each legal employer has its own sites, and each site has its own weekly roster. Shift templates belong to the whole organisation, so every branch uses the same codes. A role can apply to one site, so a branch manager sees only their branch. The system refuses two shifts that overlap for one person, at any site. The weekly hours warning counts shifts at every site, and the roster warns you when a person belongs to another site.
If two managers change the same roster, the second change stops and the page shows the latest version. The attendance report exports by site and date range. See employee scheduling, the page for retail and restaurants, or ask us for a demo.
