Plant and office employees follow different shift, overtime and leave policies, but payroll needs one governed input cycle.
Manufacturing workforce operations
Configure plant attendance around shifts, exceptions and payroll closure.
Support plant-specific schedules, swipe data, night shifts, late-mark rules, overtime and location-level closure without creating a separate product for each facility.
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 manufacturing HR teams managing plants, contract and permanent workforces, rotating shifts and attendance-dependent payroll.
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
Plant supervisors maintain local attendance sheets.
02
Night shifts and overtime require repeated correction.
03
Contract and permanent workers follow different rules.
04
Payroll teams discover plant exceptions after 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.
Model plants and workforce groups
Use location, employee group and employment type in the shared organisation model.
Configure shift and attendance rules
Apply thresholds, swipe mode, work date, overtime and regularisation policy.
Close by plant
Make unresolved exceptions and approver ownership visible before payroll.
Use approved payroll inputs
Feed accepted loss-of-pay, overtime and allowances into the connected run.
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.
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.
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 plant and office staff use different rules?
Yes, provided the workforce groups and policy scope are configured through supported organisational dimensions.
Can biometric device data be imported?
The product material describes device registry, batch upload and SFTP ingestion; exact device compatibility requires technical validation.
Does duoHR perform facial recognition?
No. Facial recognition and biometric matching are not presented as current native capabilities.
Manufacturing workforce operations
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.