A late-coming policy should define when lateness starts, how late arrivals are recorded, and what happens when the pattern continues. A fair policy uses measurable rules for fixed shifts, rostered shifts, flexible hours and approved leave while allowing documented exceptions.
What the policy must decide | Choose the rules | Policy template | Genuine delays | Repeated lateness | System requirements | Rollout checklistA workable policy connects scheduled start times, first clock-in records, late marks, approvals and escalation notes so the people administering attendance can review the same record. The policy should be adapted to the employer's working arrangements rather than copied as a universal rule.
What a late-coming policy must decide
A late-coming policy defines late arrival against the employee's scheduled start time and keeps it separate from absence or early departure. It should also state who it covers, how exceptions work and which record proves the attendance event. A sample late-coming policy uses the first recorded punch after a grace period to define late arrival and treats leaving early as a separate matter.
Set the scope
State whether the policy covers the employee groups governed by the organization's attendance rules. Add instructions for fixed shifts, rostered shifts, flexible hours, field work, multiple locations and approved leave.
Approved leave should not be treated as a late arrival when the leave record covers the relevant start time. A late arrival means the employee arrived after the policy's stated threshold. An absence means the employee did not attend the scheduled work period, while early departure means the employee left before the approved end time. Keep these categories separate in the policy and attendance records.
Make the rule measurable
Identify the scheduled start time, the first accepted punch, the attendance source and the person responsible for reviewing a disputed record. The first punch is the earliest accepted clock-in event for a work period, such as a device punch or approved mobile check-in.
Consistency matters across branches and shifts. If one manager rounds a 09:04 arrival down while another records it as late, employees receive different treatment for the same event and attendance reports become difficult to review.
Choose the rules before writing the template
Choose the grace period, late-mark count, regularisation process and escalation point before publishing the policy. The policy components identified in the brief's reference material include working hours, grace periods, notification procedures, frequency limits, attendance records and disciplinary actions. No single number of minutes, free late marks or deduction method is correct for every employer, shift pattern or jurisdiction.
A grace period is a stated interval after the scheduled start time during which an arrival is treated according to the policy's chosen rule. State whether the interval is measured in calendar minutes, scheduled minutes or another clearly defined unit, and say whether an arrival at the exact boundary is on time or late.
- Grace period: enter the approved interval as [number of minutes] and define the boundary rule.
- Free late marks: decide whether a limited number of late arrivals may be recorded without immediate escalation. A free late mark should still appear in the attendance record.
- Counting period: specify whether late marks are counted per week, month, roster cycle or another approved period.
- Absence threshold: state when a late arrival becomes another attendance category, if the employer uses such a category, and who reviews that decision.
- Cancellation and correction: explain when a late mark can be cancelled, corrected or regularised and which approval is required.
Do not imply that a late mark automatically creates a pay deduction. Any payroll treatment should be reviewed for the employer's applicable rules and written separately from the attendance measurement rule where necessary.
Late-Coming Policy Template for Employees
Use the following structure as a starting template, then replace every bracketed field with a decision approved for the organization. Customize the fields for shifts, locations and working arrangements instead of applying one rule across every team.
Purpose
Purpose: [Organization name] uses this policy to define late arrival, record attendance consistently and explain how repeated lateness is reviewed.
Scope and definitions
Scope: This policy applies to [employee groups] working at [locations] under [fixed shifts, rostered shifts, flexible hours or field-work arrangements]. The effective date is [date], the version is [version number], and the policy owner is [role or department].
Definitions: The scheduled start time is the start recorded for the employee's approved shift. Late arrival means the first accepted punch occurs after [scheduled start time plus grace period]. Absence, approved leave and early departure are recorded as separate attendance categories.
Notification and exceptions
Notification: An employee who expects to be late must notify [manager, duty supervisor or attendance contact] through [approved channel] before [time or shift event], unless an emergency prevents advance notice. Notification does not automatically approve the late arrival or remove the need for a clock-in record.
Exceptions: An employee may request regularisation when [approved reasons] apply and submits [supporting information] to [approver] within [time limit]. Regularisation is an approved correction or classification of an attendance event; it is not an automatic exemption.
Counting rules and responsibilities
Counting rules: Late marks are counted over [defined period]. [Number] late marks may be recorded before [review or escalation]. The organization will state whether late marks are cancelled by approved leave, corrected attendance data or an approved regularisation request.
Responsibilities: Employees record attendance and report expected delays. Managers review shift records and discuss recurring patterns. HR or the designated policy owner maintains the policy, reviews escalations and checks consistent application across teams.
Escalation, review and acknowledgement
Escalation: The review sequence is [manager conversation], [written caution], [formal warning or other approved action]. Before a consequence is applied, the employee receives notice of the relevant attendance records and an opportunity to provide the information allowed by the policy.
Review: This policy will be reviewed when shift timings, attendance rules, locations or recording methods change. Record the review date, reviewer and approved version.
Employee acknowledgement: I acknowledge that I received and understood the policy: [employee name], [signature or electronic acknowledgement], [date].
How to handle genuine delays and exceptions
Genuine delays should follow a documented request and approval process rather than an informal manager decision. Transport problems, emergencies, weather-related delays, official duty and field work can be listed as policy considerations, but none should become an automatic exemption unless the employer chooses to define it that way.
Require the employee to report the delay through the stated channel when reasonably possible. The report should include the employee, scheduled shift, expected arrival, location, reason category and time of notification. State what supporting information may be required and handle sensitive information through the organization's own process.
Assign approval to a named role, such as the shift manager or HR reviewer. The approver should record the decision as approved, declined or awaiting information, with the decision time and a short reason. Use the same approval route for comparable cases across departments.
Regularisation should not erase the original event. Keep the first punch, the request, the approval and the final attendance status together. That sequence lets HR distinguish a corrected record from a late arrival that was recorded accurately and not approved for regularisation.
Escalation for repeated lateness
Repeated lateness should move through a clear sequence from an early manager conversation to written caution and, where approved, a formal warning. The policy must state the counting period, notification steps and records reviewed before each stage.
- Review the pattern: confirm the scheduled shifts, first punches, approved leave, regularisation decisions and any corrected records.
- Hold a manager conversation: explain the pattern using specific dates or shift records, ask whether a scheduling or reporting issue exists, and record the outcome.
- Issue written caution when the threshold is met: identify the relevant rule, attendance period and expected change. Give the employee the notice required by the organization's process.
- Refer for formal review: HR or the designated reviewer checks the records and confirms that the proposed action follows the published sequence.
- Monitor the next review period: use the same counting rules and record approved exceptions without changing the rule retrospectively.
Managers should avoid relying on memory or isolated complaints. An attendance record that shows the scheduled shift, first punch, late-mark status, approval history and manager notes gives the employee and reviewer a common factual basis.
Review the policy when shift timings, locations, attendance devices or attendance-to-payroll workflows change. A rule written for one location may need a controlled update before it is used for mobile teams or a different time zone.
Policy Rule Versus Attendance-System Requirement
Every policy decision needs a matching attendance record, responsible person and review action. Manual registers, app-based records and biometric records can all be considered, but the right method depends on the workplace, devices, locations, connectivity and operating rules.
For context, OnPay's tardy-policy guide is presented within a product ecosystem that includes payroll, time tracking, reporting, PTO management and scheduling. Paycor's employee time-and-attendance material describes an employee app alongside time-and-attendance and scheduling software. These examples do not establish that one method fits every workplace.
| Policy decision | Record required | Responsible person | Review action |
|---|---|---|---|
| Grace period and first punch | Scheduled start, boundary time, shift identifier and first accepted punch | Policy owner and system administrator | Test an on-time arrival, boundary arrival and late arrival |
| Late-mark count | Late status, counting period and employee or shift identifier | Manager or HR reviewer | Check that the same period and category are used across teams |
| Regularisation and approvals | Original event, request reason, supporting information, approver and decision | Named approver | Confirm the final status preserves the original record |
| Notification | Message time, reporting channel, expected arrival and recipient | Employee and receiving manager | Compare notification records with the first punch |
| Warning stage | Relevant attendance events, notice, response and outcome | Manager and HR | Confirm the published escalation sequence was followed |
What to verify before choosing a method
For a manual register, check who enters the record, how corrections are approved, how records are retained and how separate shifts or locations are reconciled.
For an app-based record, verify supported devices, location rules, offline handling, correction permissions, shift assignments and report exports. The workflow should remain understandable to employees and supervisors.
For a biometric device or face-punch workflow, verify the supported hardware, enrollment process, location coverage, shift handling, exception process and data controls. Do not assume that a biometric method fits every workplace or working arrangement.
For attendance-to-payroll workflows, verify which approved attendance fields can be handed to the next process and who reviews them first. The objective is a traceable record from scheduled shift to attendance status, not an automatic promise about payroll or compliance outcomes.
Rollout Checklist for Managers and HR
Roll out the policy only after the rules, records and responsibilities have been approved and tested. A controlled launch uses version control, an effective date, supervisor briefing, employee acknowledgement and sample attendance events.
- Approve the policy owner, scope, version number and effective date.
- Confirm the grace period, late-mark counting period, exception categories and escalation sequence.
- Configure schedules, locations, shift types, attendance categories and approval roles.
- Brief supervisors on first punches, notifications, regularisation and employee conversations.
- Share the final policy with employees and collect the required acknowledgement.
- Test an ordinary late arrival, an approved exception, a disputed punch and repeated lateness.
- Review attendance reports regularly for inconsistent treatment across branches, teams and locations.
Use the checklist and template as a starting point, then align the final policy with the organization's working arrangements, attendance records and approval process.
Frequently asked questions
What should a late-coming policy include?
A late-coming policy should define the scheduled start time, grace period, first punch, late-mark counting period, notification process, exceptions, responsibilities and escalation steps. It should also explain how records are corrected, approved and reviewed.
How should a company define the grace period?
The company should choose a measurable interval that fits its shifts and operating rules, then state exactly how the interval is calculated. The policy should clarify whether an arrival at the boundary is on time or late and apply the same rule to comparable employees.
How many late marks should an employee be allowed?
There is no universal number that fits every employer. Set the count and review period in line with the organization's approved attendance rules, record every late mark, and explain when a manager conversation or further review begins.
When should late arrival become a half-day or absence?
The policy should state whether and when a late arrival changes to another attendance category, using a defined threshold and approval process. Employers should review any related pay or leave treatment for the applicable jurisdiction rather than treating one approach as universal.
How should genuine delays be regularised?
The employee should report the delay through the approved channel and submit any required supporting information within the stated time. A named approver should record the request, decision and final attendance status while preserving the original punch and notification records.
