A factory and corporate office share one HRMS but use different shifts, grace periods and late-mark consequences.
Attendance policy configuration
Configure attendance rules around the workforce you actually employ.
Model grace periods, lateness consequences, swipe modes, workday thresholds, location rules and regularisation controls without creating a customer-specific product fork.
Representative operating scenario Current boundaries stated clearly
Policy resolverIllustrative · effective-dated
Resolve a 09:11 punch for an employee whose shift begins at 09:00.
Resolved outcome
Late mark recorded
Punch is one minute beyond grace
No payroll impact yetLate mark · 1 of 3
Third late mark becomes half day
Decision is explainableScheduled shift resolved
09:00–18:00 · 45-minute break
Work date: 29 Sep 2026Chennai office policy
Geo-fence: warn outside location
Policy preview availableWho this page is for
For HR and operations teams evaluating whether an HRMS can support unusual attendance policies across employee groups, locations and shifts.
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
One global rule creates incorrect outcomes for legitimate workforce differences.
02
Policy changes depend on the vendor or engineering team.
03
Managers cannot explain why a day became late, half-day or absent.
04
Attendance exceptions reach payroll after the cut-off.
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.
Scope the policy
Apply rules by location, employee group, department, grade, employment type or an approved employee override.
Set the effective date
Preserve the historical rule while making the new policy active from the correct date.
Preview the resolution
Check which policy will apply to a representative employee and date before activation.
Operate the exception cycle
Route regularisation and approvals with the owner, status and history visible.
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.
Policy 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.
ExploreShifts & Rosters
Create shift patterns, publish rosters, manage changes and connect planned schedules to attendance, overtime and payroll.
ExploreWorkflow Automation
Create structured, conditional workflows for employee changes, requests, letters, payroll inputs and cross-functional HR processes.
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 different locations follow different attendance policies?
Yes. The public product positioning supports policy scoping by organisational dimensions such as location, employee group, department, grade, business unit and employment type.
Can an administrator preview which rule will apply?
The product material describes policy preview and effective-dated resolution before activation.
Does duoHR perform biometric matching?
No. Device data can be consumed, but biometric matching, facial recognition and buddy-punch detection are not presented as current native capabilities.
Attendance policy configuration
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.