Guides
UK HR system for multi-site frontline teams: buyer's guide
Campsite · 26 June 2026
Multi-site UK employers with frontline staff need HR systems that work for site managers, not only HQ. Compare architectures, evaluation checklists, and Campsite fit.
Who this guide is for
You operate multiple UK sites with frontline teams: retail, hospitality, care, logistics, cleaning, security, or field services. HQ may have a people team, but site managers run rotas and daily people issues. You need a UK HR system that works at the edge, not only in admin dashboards.
Campsite is one architecture: UK people operations workspace with HR records, hiring, rotas, leave, payroll exports, employment law monitoring, and white-label subdomain per organisation.
See Rota and HR in one system (UK) for unified vs split stack debate.
Multi-site frontline complexity
| Dimension | HQ view | Site manager view |
|---|---|---|
| Headcount | Group total | Today's shift count |
| Compliance | Audit readiness | RTW before rota |
| Hiring | Employer brand | Fill Tuesday bar shift |
| Leave | Policy | Cover this weekend |
| Payroll | Period close | Hours accuracy |
| Communication | All-staff email | Team WhatsApp |
Systems built for 50 desk workers at one address fail when 12 GMs need different permissions and mobile rotas.
Architecture options
| Model | Description | Risk |
|---|---|---|
| HQ HRIS + local spreadsheets | Classic SME pattern | Dual truth |
| HRIS + scheduling app | Best-of-breed | Integration gaps |
| Site-level shadow tools | WhatsApp rotas | Compliance blind spots |
| People operations platform | Campsite-style unified | Change management |
| Enterprise WFM | Scale features | Cost, rollout time |
People teams should pick source of truth explicitly before buying modules.
Requirements matrix for multi-site frontline
Score must-have vs nice-to-have:
| Requirement | Must-have rationale |
|---|---|
| Site-scoped permissions | GM sees own site only |
| Mobile rota publish | Managers on floor |
| Leave vs cover | Avoid understaffing |
| RTW on profile + expiry | Multi-site hiring volume |
| Hiring pipeline | Turnover and seasonal peaks |
| Document storage | Contracts per site role |
| Payroll-ready export | Finance consolidation |
| Audit trail | Cross-site disputes |
| Employment law awareness | UK regulatory change |
| Branded employee experience | Adoption on subdomain |
Campsite maps closely to must-have column for UK frontline multi-site.
UK HR system comparison (categories)
| Category | Multi-site frontline fit |
|---|---|
| Office SME HRIS | Weak rota, manager UX |
| Scheduling-only | Weak HR depth |
| Hospitality ERP | Strong ops, heavy implementation |
| People ops platform (Campsite) | Strong unified |
| Enterprise HRIS + WFM | Strong at scale, expensive |
No category wins all sizes. A 30-site care group differs from a 4-site bakery chain.
Campsite for multi-site frontline (honest)
Strong fit:
- 3 to 100+ sites under one UK employer brand
- Hourly workforce with weekly rotas
- Hiring distributed to site or area managers with HR governance
- Need RTW and contracts on same profile as shifts
- Want employment law monitor for people team cadence
Weaker fit:
- Single site, 10 stable staff
- Global HRIS programme already locked
- Need deep inventory/labour ERP only
- Zero frontline hiring or scheduling
When to look elsewhere
| Scenario | Direction |
|---|---|
| Corporate global Workday/SAP mandate | Enterprise path |
| Labour analytics vs revenue only | Hospitality ERP |
| Micro employer | Lighter HRIS or spreadsheets short term |
| Biometric clocking ecosystem | WFM specialist |
| Franchise legal separation complex | Legal structure first, then software |
Honest comparison protects your rollout budget.
Evaluation checklist (multi-site)
Stakeholders
- People team lead
- Ops/regional managers (2+ in demo)
- Finance payroll owner
- IT/security for subdomain model
Site pilot design
- Pick diverse pilot: busy + quiet site
- Pilot manager is sceptic, not only champion
- Include one payroll cycle
Functional tests
- GM publishes rota without HQ ticket
- RTW expiry visible to GM, not full group payroll
- Hire hourly role with approval chain
- Area manager sees 4 sites, not 40
Compliance
Adoption metrics
- Define: % rotas published in-system week 4
- Define: payroll prep hours vs baseline
Migration checklist (multi-site rollout)
Phase 0: Design
- Site hierarchy and permission matrix
- Naming conventions for roles/locations
- Data owner per region
Phase 1: HQ + pilot site (week 1-2)
- Import employees; dedupe emails
- RTW and contracts uploaded
- Pilot rota live
Phase 2: Wave 1 sites (week 3-4)
- 3 to 5 sites per wave
- Manager training 30 minutes hands-on
- Regional office hours for questions
Phase 3: Remaining sites
- Repeat wave pattern
- Retire shadow spreadsheets per site on schedule
Phase 4: Decommission legacy
- Archive old exports
- Update handbook and audit docs
Read Campsite vs spreadsheets for UK employers if migrating from sheets.
Common mistakes multi-site employers make
HQ picks software without GM trial. Adoption fails silently.
Same permission model all roles. Area manager equals GM equals HR overkill or underkill.
Big-bang 40 sites. Wave rollout reduces support tsunami.
Ignoring payroll mapping early. Finance becomes blocker month 2.
Training PDF only. Managers need live publish practice.
No regional champion. People team cannot scale support alone.
Assuming English-only comms sufficient. Frontline diversity needs clear plain language training.
Operating model after go-live
Software succeeds with operating rhythm:
| Cadence | Activity |
|---|---|
| Weekly | Rota publish audit sample |
| Monthly | RTW expiry review |
| Quarterly | Permission audit |
| Per hire | Onboarding checklist |
| Per law change | Policy update via monitor |
Campsite employment law monitor supports quarterly people team review, not replacement for counsel.
Scenario examples
Retail 22 stores, 280 staff
Pain: rotas in app A, HR in B, RTW email.
Campsite fit: strong if trial proves GM publish and export.
Care 8 homes, 160 staff
Pain: compliance audits, hiring nurses.
Campsite fit: strong with RTW and onboarding emphasis.
Logistics 3 depots, 90 drivers
Pain: rota + HR; less daily shift churn than retail.
Campsite fit: strong to moderate depending rota complexity.
Permission matrix template (multi-site)
| Role | Sites visible | Can publish rota | Can see pay rates | Can hire |
|---|---|---|---|---|
| Group HR | All | No default | Yes | Yes |
| Area manager | Assigned area | Yes | Limited | Yes |
| Site GM | One site | Yes | Site only | With approval |
| Shift lead | One site | View only | No | No |
Fill before vendor demo; reject tools that cannot approximate matrix.
Regional champion model
| Region | Champion duty | Time commitment |
|---|---|---|
| Each area | First-line manager questions | 2 hrs/week rollout month |
| HQ people team | Policy + escalation | Ongoing |
| Finance | Export validation | Payroll week |
Champions reduce people team support tsunami during wave rollout.
Technology adoption curve (frontline)
Expect 20/60/20: enthusiasts, neutral, resistors. Design rollout for neutral majority:
- Short videos under 2 minutes
- Printed one-page "where is my rota"
- Peer buddy at each site (enthusiast pairs with resistor)
Software selection cannot fix resistors alone; ops leadership visibility required.
Disaster recovery and offline scenarios
Frontline sites lose connectivity. Clarify mobile offline behaviour in trial. Managers should know fallback if app unavailable (e.g. call area manager, do not revert to unofficial WhatsApp permanently).
Benchmarks from UK multi-site employers
| Metric | Weak | Strong |
|---|---|---|
| Rota publish before Friday noon | < 80% sites | 95%+ |
| RTW expiry surprises | Any | Zero |
| Payroll corrections | > 5 per period | 0 to 2 |
| Manager weekly admin | > 45 min | < 25 min |
Use benchmarks in vendor business case.
Language and literacy on frontline sites
Training materials above reading age of staff fail. Use:
- Screenshots with circles
- One task per page
- Buddy system first week
Multi-site HR system success is literacy-aware, not feature-rich.
Escalation path poster (site staff room)
Print A4:
- Rota question → GM
- Leave request → system then GM
- Pay question → payroll email
- RTW document → HR email
Reduces people team noise during rollout.
Multi-site rollouts should track leading indicator: percentage of sites publishing rota in-system by Friday 17:00. Lagging indicator: payroll corrections. Fix leading first.
HQ staff visiting sites should use same system as GMs during visits; executives asking "send me the WhatsApp rota" undermines rollout.
Reference links for multi-site buyers
- Rota and HR in one system UK
- Deputy alternative UK HR and scheduling
- Campsite vs spreadsheets for UK employers
FAQ
Can area managers approve leave across sites?
Configure permissions in trial to match delegation policy.
Franchise vs company-owned sites?
Legal entity structure drives access; clarify before import.
Union recognition sites?
Software supports records; collective processes remain negotiated.
Payroll bureau for all sites?
Single export mapping if same bureau; validate columns once.
Mobile data costs for staff?
Manager mobile UX critical; staff rota view lightweight preferred.
How long full rollout?
40 sites often 8 to 12 weeks waved; not one weekend.
Next steps
- Deputy alternative UK HR and scheduling
- StaffSavvy replacement UK employers
- Payroll HR compliance small business UK
- Start a 14-day Campsite trial
Multi-site frontline UK employers fail on permissions and adoption, not missing checkbox features. Choose an HR system site managers will open every Monday, finance will trust every payroll Friday, and auditors can navigate in minutes.