Scoped policy resolution
Resolve rules through employee override, organisation scope and tenant default using approved workforce dimensions.
Configuration & control · Configuration is the product
Fit the system to your policy—without creating a custom codebase.
Configure attendance, leave, payroll, approvals, permissions and notifications around the way your organisation actually works, while keeping every policy scoped, dated and reviewable.
Illustrative product interaction Grounded in supported product behaviour
Policy resolverIllustrative · effective-dated
Apply a late-mark rule to Chennai factory employees without changing office staff.
Resolved outcome
Chennai plant default
10-minute grace · 3 late marks → half day
Effective 01 Oct 2026Factory workforce rule
Night-shift handling · swipe rounding
Effective 01 Oct 2026Operations G4 rule
Overtime eligibility · manager approval
Effective 01 Sep 2026Employee override
Temporary grace extension
Expires 31 Oct 2026Why this matters to the Head of HR
Growing businesses do not all operate the same late-mark rule, leave year, overtime window or approval chain. HR leaders need control after go-live—not a new engineering request every time policy changes.
Use this page as a product-evaluation path: start with the operating problem, inspect the representative interaction, then verify the exact policy and output in the live product.
Policy Configuration capabilities
Designed around the full operating workflow.
Configure the module around your structures, policies, ownership and approval model—not a generic process diagram.
Effective dates
Introduce future changes without overwriting the historical policy that applied to an earlier transaction.
Preview before activation
See which policy resolves for a selected employee and date before making it active.
Guided administration
Start with the required settings and activate deeper controls as operational maturity grows.
Conditional workflows
Route transactions using amount, leave days, department, grade, location, employment type, tenure and other approved conditions.
Roles and data scope
Give system and custom roles access to the relevant module, action and organisational data scope.
Connected operating workflow
Follow the action from policy to owner to downstream result.
The exact screens differ by module, but the operating principle remains the same: the applicable rule, current owner, status, effective date and history stay visible.
Less dependence on vendor engineering Faster policy changes after go-live Defensible historical policy context
Policy Configuration workflow
- Describe the policy changeOwner, status and history remain visible.
- Configure scope and effective dateOwner, status and history remain visible.
- Preview the resolved policyOwner, status and history remain visible.
- Approve and activate with historyOwner, status and history remain visible.
Product proof and boundaries
Evaluate the operating behaviour—not only the feature name.
These examples are illustrative product patterns grounded in the supported product material. Use the live product to validate the exact screen, policy and output required for your organisation.
Supported pattern
Previewable policy resolution
See the rule, workforce scope and effective date before activation.
Verify in demo
Describe the policy change
Use a representative employee, workforce group and effective date. Follow the transaction through owner, status and downstream impact.
Current boundary
Scope honestly before committing.
Configuration supports approved product actions and policy dimensions; unsupported edge cases still require transparent scoping.
A working view, not a static report
Give the team clear status and exception signals.
The example measures below are illustrative. Definitions and thresholds should be configured around the operating cadence and evidence your team uses.
ScopedBy employee and organisation
DatedHistory preserved
PreviewedBefore activation
GovernedBy role and approval
Connected modules
View all modules Policy Configuration works better when its inputs and outputs stay connected.
Time & 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.
ExploreLeave Management
Configure eligibility, accrual, balance-year, sandwich, clubbing, carry-forward, comp-off and encashment rules for different employee populations through one policy resolver.
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.
ExploreWorkflow Automation
Create structured, conditional workflows for employee changes, requests, letters, payroll inputs and cross-functional HR processes.
Explore
Questions about implementation
Bring this context into the demo Evaluate Policy Configuration in your policy context.
Use your actual workforce groups, approval paths and edge cases during product evaluation.
Is configuration the same as customisation?
No. Configuration uses the standard product’s governed settings and rule model. Customisation introduces customer-specific code. duoHR is positioned to handle policy variation through configuration wherever the current product supports the rule.
Can an administrator see which rule will apply before launch?
Yes. The policy model is designed around scoping, effective dates and preview so an authorised administrator can check the resolved rule for a representative employee and date before activation.
Explore Policy Configuration
See Policy Configuration configured around your organisation.
Bring one representative workflow or current process challenge. The demo will show the operating path, controls and connected outcomes.