A 09:11 punch must be evaluated against a 09:00 shift, a ten-minute grace period and a three-late-mark threshold.
Attendance exception control
Turn late punches into explainable policy outcomes—not monthly disputes.
Configure grace-in and grace-out windows, repeated-lateness consequences, half-day or loss-of-pay thresholds and approval paths with a visible decision trail.
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 organisations that need consistent late-mark treatment across shifts, locations and employee groups.
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
Late-mark logic is maintained in spreadsheets or payroll notes.
02
Employees and managers cannot see why a consequence was applied.
03
Repeated lateness is handled inconsistently.
04
Corrections are submitted after attendance closure.
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.
Configure the shift context
Resolve the scheduled shift and work date before evaluating the punch.
Apply the grace and threshold
Use the approved late window and repeated-lateness policy.
Record the decision
Retain why the day became late, half-day or another supported status.
Route regularisation
Send correction requests through the configured approval workflow before payroll input closes.
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.
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.
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.
ExploreWorkflow Automation
Create structured, conditional workflows for employee changes, requests, letters, payroll inputs and cross-functional HR processes.
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 repeated late marks trigger a consequence?
The product material describes configurable lateness thresholds and repeated lateness leading to half-day, full-day or loss-of-pay treatment.
Can punch times be rounded?
The documented scope includes 5, 15 or 30-minute rounding with up, down or nearest options.
Is every decision explainable?
The source material describes a decision ledger and policy preview for attendance outcomes.
Attendance exception control
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.