Plants, stores and offices need different shifts and leave calendars, while corporate HR needs one monthly readiness view.
Multi-location policy governance
Let locations operate differently without losing central HR control.
Apply calendars, shifts, leave, overtime, payroll and approval policies to the right locations while keeping one employee and reporting foundation.
Representative operating scenario Current boundaries stated clearly
Operating lensIllustrative interaction
Operating readiness by location
Local execution with central visibility.ChennaiReady
Pune11 exceptions
Bengaluru2 approvals
Controlled location variation
Resolve the right rule for the right workforce.4Holiday calendars
6Shift policies
3Payroll groups
Group payroll readiness
Stop discovering missing location inputs on payroll day.8/10Sites closed
94%Inputs ready
17Open actions
Who this page is for
For multi-location businesses that need local rules and central governance in the same HRMS.
The operating problem
What usually breaks before the software conversation begins.
Use these symptoms to determine whether the issue is data, policy, ownership, monthly closure or an unsupported product requirement.
01
Local workbooks become the real policy source.
02
Corporate HR cannot see which locations are ready for payroll.
03
A policy update is copied manually across branches.
04
Leadership reports use inconsistent location definitions.
A practical operating approach
Resolve the policy first, then automate the cycle.
The exact product setup is validated during discovery and demonstration. The sequence below keeps the rule, owner and downstream result connected.
Model the organisation
Represent entities, locations, departments, employee groups and reporting relationships consistently.
Map legitimate variation
Apply the correct local calendar, shift, leave and approval policy.
Retain central status
Track exceptions, approvals and closure readiness by location.
Use shared reporting definitions
Compare headcount, absence, overtime and payroll readiness without manual consolidation.
Connected product scope
View the full product The outcome depends on more than one isolated feature.
Review the upstream source, policy resolver, approval path and downstream output together.
Core HR
Centralise employee records, organisation structures, dated lifecycle changes and policy scope so downstream attendance, leave, payroll, performance and access decisions use the same governed foundation.
ExplorePolicy Configuration
Configure attendance, leave, payroll, approvals, permissions and notifications around the way your organisation actually works, while keeping every policy scoped, dated and reviewable.
ExploreTime & Attendance
Apply configurable rules to punches, shifts and work patterns, explain why each day resolved as it did, and close exceptions before they become payroll corrections.
ExplorePayroll
Connect effective-dated salary structures, attendance and leave inputs, earnings, deductions, reimbursements, recoveries and statutory calculations in a payroll run that can be reviewed and rolled back before finalisation.
Explore
Evaluation questions
Bring this use case into a demo Confirm the exact policy, evidence and product boundary.
The answers below reflect the supplied product source. Customer-specific commitments still require live-product and commercial validation.
Can policies be scoped by location?
Yes. Location is one of the documented organisational dimensions used for policy resolution.
Can one employee have a temporary override?
Employee-level override is described where configured, with effective dates preserving history.
Can HR compare readiness across sites?
The website positions location-level attendance and payroll status as an operating view; exact dashboards should be confirmed in the product demo.
Multi-location policy governance
Validate this use case with one real policy or transaction.
Bring a representative employee, location, shift, payroll month or output. We will shape the walkthrough around the exact operating case.