Blog Product

Coverage across sites, and the gaps a sheet hides

5 min read

A group with three sites and a spreadsheet per site has three rotas that cannot see each other. That is how a floating supervisor ends up rostered in two places on the same Saturday, a leave approval reaches one sheet and not the other, and a gap at the third site stays invisible to the one manager who could have filled it. One invented weekend shows each failure, and what a shared record changes.

Maintained by the TriblockHR Compliance Team. Updated 2 October 2026. This page describes how schedules are scoped across sites in TriblockHR; it states no statutory figure.

How a Saturday goes uncovered

Take an invented group of three cafés, Palm Row Coffee, on one island: the Harbour site, the Mall site and the Airport site. Each has its own manager, and each manager keeps a rota in their own spreadsheet.

The group employs one floating supervisor, Renée, who covers whichever site needs her.

  1. Tuesday. The Harbour manager rosters Renée for Saturday, because Harbour’s own supervisor is off.
  2. Wednesday. The Mall manager, who did not see Harbour’s sheet, also rosters Renée for Saturday, because Mall has a delivery to manage.
  3. Thursday. One of the Airport baristas, Tyrone, has his leave approved for Saturday by head office. The approval is emailed to the Harbour manager by mistake. Airport’s sheet still shows Tyrone working.
  4. Friday. The Airport manager, short one barista, would gladly borrow someone. But nothing tells her she is short, and nothing tells her that Harbour has a spare part-timer who asked for extra hours.
  5. Saturday. Renée goes to Harbour. Mall opens without a supervisor. Airport opens one barista down. Harbour has more staff than it needs.

On Monday, three managers each explain to head office why Saturday went badly, and each explanation is true. Nobody made a careless decision, and nothing in any one sheet would have warned them. Each manager acted sensibly on the sheet in front of them.

What separate sheets cannot show

The failures share a cause: the facts needed to see them were on different sheets.

  • A person in two places. Renée’s double booking existed only across two files. Neither file alone was wrong.
  • A leave clash. Tyrone’s approved leave and his rostered shift were in different places: one in an email, one in a sheet.
  • A gap that could have been filled. Airport’s shortfall and Harbour’s surplus were each visible only to their own manager.

More diligence does not fix this. Each manager would have to open every other site’s sheet every day, and the leave approvals would still be somewhere else. The structure hides the problem.

One record, scoped by site

In TriblockHR, every site’s rota is built on the same record. A schedule carries a name, a date range, a budget and named shift managers, and it is scoped by division, department, employment level and work title. So Palm Row can scope one schedule per café by division, with that café’s manager named as its shift manager.

Each manager still builds their own site’s rota, with the same drag-and-drop grid and the same reusable slots. What changes is that they are all building on one set of people. Renée is one person on the record. When she is placed on a shift at Harbour, that shift exists on the same record the Mall manager is working on.

Publishing notifies the staff on the rota, so the point at which a site’s week is committed is the point everyone sees the same week.

Leave and the roster on the same data

Approved leave and the roster read the same data. When head office approves Tyrone’s Saturday, the approval is on his record. Leave management covers how leave is approved.

That moves the leave clash from something discovered on Saturday morning to something findable on Thursday afternoon, by the person who builds the Airport rota. It does not depend on anyone forwarding the right message.

The argument here is not that software finds every gap by itself. It is that a gap which exists on one record can be found by a person looking at it, where a gap spread across three sheets and an inbox cannot.

What the group still decides

A shared record makes the gaps findable. It does not decide who fills them. Palm Row still needs to settle a few things, in writing:

  • Who owns a floating role. Renée needs one person who decides where she goes each week, so two managers do not both assume they can have her.
  • Who may lend staff, and how. If Harbour has a spare part-timer and Airport is short, can the Airport manager ask directly, or does it go through someone?
  • When rotas are published. If every site publishes by Wednesday, the floating supervisor’s week can be settled by Thursday.
  • Who approves leave for staff who work at more than one site.

Written down once, they also help a new site manager. A manager joining the Mall site in March should not have to learn by Saturday morning that Renée is shared, or that lending staff goes through the area manager.

Those are management decisions. The record supports them; it does not make them.

Each of these rotas is also a cost decision, with its own budget, which a rota carries money before anyone works it covers. Covering a property across shifts and a public holiday is covered on the hospitality page.

Questions

Why do multi-site rotas miss gaps?

With one sheet per site, a person rostered twice, a leave clash or a spare worker elsewhere is only visible across files nobody opens together.

How are schedules scoped to a site?

By division, department, employment level and work title, with named shift managers.

Does approved leave reach the roster?

Approved leave and the roster read the same data, so leave is on the record the rota is built from.

Does the system schedule staff automatically?

No. There is no auto-scheduling. A person builds the rota.

Build every site’s rota on one record, so the gaps are findable before Saturday.

Book a demo

  • SOC 2 Type II attested
  • AES-256 at rest
  • 99.9% uptime
  • Built in The Bahamas