Standardisation does not mean identical policy everywhere
A multi-location organisation needs common employee identities, reporting definitions, access principles and approval evidence. It may still require different holidays, shifts, leave rules, attendance sources, allowances or local owners.
The HRMS should make those differences explicit and governed rather than burying them in manual exceptions.
Design the organisation model before the workflows
Define legal entities, business units, locations, departments, grades, roles, reporting lines, cost centres and workforce groups. Then agree which dimensions control policy, access, approval and reporting.
A weak organisation model creates downstream confusion even when individual features appear complete.
- Legal and payroll entity
- Operating location or site
- Business and cost ownership
- Formal reporting hierarchy
- Shift or workforce group
- Employment type and policy group
Give local managers the actions they own
Central HR should not approve every attendance correction, leave request or onboarding task. Local managers need a simple, scoped view of their responsibilities, with deadlines and escalation when actions remain open.
Central HR retains visibility into completion, exceptions and policy consistency without becoming the routing layer.
Close recurring cycles by location before consolidating
Attendance, overtime, joiner readiness and payroll inputs should show closure status by location or operating unit. Leadership can then distinguish a local delay from an enterprise-wide issue.
The same approach supports phased rollout: pilot representative locations, resolve edge cases and scale with a controlled template.
Build a Head of HR review view
A multi-location dashboard should combine operating reliability with workforce direction. It should answer where action is required now and where a structural trend needs leadership attention.
- Headcount, vacancies and movement by location
- Attendance and payroll closure
- Overtime and absence
- Joining and exit readiness
- Manager approval ageing
- Attrition and employee-service patterns
- People cost and variance
Evaluate with real location scenarios
Ask vendors to demonstrate a transfer, a location-specific holiday or shift rule, a late attendance correction, a high-volume onboarding batch and a consolidated workforce report. The workflow should make policy, ownership, effective date and downstream impact clear.
A generic feature tour will not reveal whether the product can operate the differences your organisation actually has.
This article reflects the current duoHR launch positioning and product material. Feature availability, pricing, implementation, security assurance and statutory configuration require confirmation against the production release and customer scope.
