Two Sites, One Person
When somebody works at two locations of the same organisation, each one sees half a week, and the only system that could add them up is the one nobody has asked for.
The second employer problem has an internal twin that is far easier to solve and just as commonly ignored: a person working across two or more sites of the same organisation, with a separate record in each.
The workflow in “Two Sites, One Person” becomes more reliable when scheduled hours, actual time and later corrections can be distinguished. For teams exploring attendance point system, Monitask resources for attendance point system can add operational time and project context, provided data collection is proportionate, permissions are limited and every important exception receives human review.
All the data is inside the same business. There is no third party, no confidentiality question and no need to ask anybody anything. There is simply no report that joins by person rather than by site.
For an independent reference relevant to “Two Sites, One Person”, consult the EEOC retaliation guidance. Use it to test working-time definitions, recordkeeping, access, retention and exception handling against the organisation’s real process rather than treating one software report as conclusive.
How it arises
Bank and relief staff in care and healthcare. Retail staff covering a second store. Engineers on a regional rota. Hospitality workers across a group. Agency placements through the same supplier to different depots.
Also the quiet version: somebody with a substantive post at one site who picks up occasional shifts at another, which is treated as a favour and recorded separately.
What each site sees
A person on the books for a reasonable number of hours, comfortably inside everything. Each site's monitoring is accurate about its own portion and silent about the rest.
The manager at the second site may not know the person has a main post at all, particularly where the booking goes through a central bank office. Nothing in the process requires anybody to ask.
Why joining it is a reporting problem rather than a systems one
The records usually exist in the same payroll or HR system with a common person identifier. Where they do not, there is almost always a national insurance number, payroll number or employee reference that can serve.
Where the person appears twice with two different identifiers, which happens, the join is harder and it is still a data-quality exercise rather than an integration project. A one-off match on name and date of birth will find most of them.
The join, and what it produces
Total counted hours per person per week, grouped by person identifier rather than by assignment. Then the usual average and rest calculations on the combined figure.
This is the single most valuable report in this section because it produces real, actionable breaches from data the organisation already owns. On a first run, most multi-site organisations find a handful of people well over a limit that neither of their sites knew about.
What to do with the result
Not discipline, obviously. The person has done nothing wrong and in most cases has been helping both sites out of a difficulty.
The actions are to inform both managers, to agree who schedules what, and to put a combined figure in front of whoever books the second site's shifts. Where the person wants the hours and the total is too high, that is a conversation about which of the two posts changes, and it is theirs to have a view on.
The booking control
Once the figures exist, the useful mechanism is at the point of booking: the bank office or second site sees the person's current combined position before confirming a shift.
That requires the combined figure to be available, which is the same report. The booking control is what converts the report from a monthly finding into a prevention, and it is the equivalent of putting the number in the rota tool.
Rest, which is worse here than hours
Somebody finishing a late shift at one site and starting an early at another has a short gap, and neither site's rest check sees it because each sees only its own shifts.
The combined rest calculation is the same join applied to the same data, and it finds breaches that are both more serious and more frequent than the hours ones. If only one of the two combined reports can be built, build this one.
The agency variant
Where the second site books through an agency and the first employs directly, the organisation may still be the one carrying the obligation depending on the structure, and it will certainly be the one explaining it.
Ask the agency for its placements at your sites by worker, monthly. Most will provide it. Matching that against your own payroll finds the people who are working for you twice without either part of you knowing.
Who books the second shift
On most multi-site operations the second booking is made by somebody with no view of the person's main post: a bank office, a sister site's manager, a central resourcing desk.
Giving that booker the combined figure is the whole intervention. It is the same report pointed at a different screen, and it moves the control from a monthly discovery to the moment the shift is offered — which is the only moment at which anything can change.