How to Build Payroll-Ready Attendance Rules in 5 Procedures | EasyClocking by WorkEasy Software

How to Classify an Absence as Excused or Unexcused

beginner · 30 minutes per event

This procedure applies consistent definitional criteria to every employee absence event in a workday. Executed by the direct manager or HR coordinator at the time of the absence report, it produces a documented, timestamped classification decision ready for enforcement review and payroll processing.

1. Receive the Absence Notification
Prerequisites
- Written attendance policy with defined excused and unexcused absence categories approved by HR leadership
- List of organization-approved absence reasons (e.g., FMLA, jury duty, bereavement, personal illness with notice)
- Documentation requirements defined (e.g., doctor's note threshold for absences of 3 or more consecutive days)
- Access to the employee's time and attendance record for the current period
Confirm the employee reported the absence before or within the policy's notification window. Most attendance policies define a cutoff, such as one hour before the scheduled shift start. Check the time-and-attendance system, manager voicemail, text messages, and any other approved notification channels for the employee's message.
Record the following in the attendance log:
- Date and time the notification was received
- Channel used (phone call, text, app notification, email)
- Whether the notification arrived within the policy window or after it
If no notification was received by the policy deadline, do not classify the event here. Route it to the No-Call/No-Show procedure instead. The notification timestamp is the first data point the classification depends on, so capture it before doing anything else.
Expected outcome: A timestamped record of when and how the employee reported the absence, confirming whether the notification arrived within the policy window.
2. Record the Employee's Stated Reason Verbatim
Write down the employee's stated reason for the absence exactly as communicated. Do not paraphrase, summarize, or interpret. If the employee said "I have a doctor's appointment for my back," record that phrase, not "medical appointment."
Verbatim documentation matters for two reasons:
- It preserves the employee's own characterization of the event, which protects both the employee and the organization if a dispute arises later.
- It prevents managers from unconsciously upgrading or downgrading reasons based on their relationship with the employee, which creates inconsistency across shifts and locations.
Enter the verbatim reason in the attendance system's notes or reason field alongside the notification timestamp from the previous step. If the employee provided the reason verbally, note that it was a verbal statement and record the date and time of the conversation.
Expected outcome: The employee's exact stated reason is recorded in the attendance log alongside the notification timestamp.
3. Match the Stated Reason to the Approved-Reasons List
Cross-reference the employee's stated reason against the policy's excused-absence category list. Your organization's list typically includes categories such as:
- Protected leave (FMLA, ADA accommodation, state-mandated sick leave)
- Jury duty or court subpoena
- Bereavement within the policy's defined relationship and duration limits
- Personal illness or injury reported with timely notice
- Pre-approved personal time off
If the stated reason maps clearly to one of these categories, note the matching category code. If the reason does not match any approved category, or if the match is ambiguous, flag the event for HR review before assigning a classification. Do not force a match. An ambiguous reason flagged for review is better than a wrong classification that gets corrected after payroll runs.
EasyClocking by WorkEasy Software applies this matching logic automatically when an absence event is logged, flagging events for manager review when the stated reason does not align with an approved code in the system's rule engine.
Expected outcome: The stated reason is matched to a specific approved-absence category code, or the event is flagged for HR review due to ambiguity.
4. Apply the Notice-Timing Rule
Even when the stated reason qualifies as excused, the timing of the notification matters. Review the timestamp from Step 1 against the policy's notification deadline.
Apply one of three classification paths:
1. Excused (timely notice): The reason matches an approved category and the employee notified within the policy window.
2. Excused, late notice: The reason matches an approved category, but the employee notified after the deadline. This is a distinct classification, not the same as unexcused. It may carry a lesser consequence under the progressive discipline schedule.
3. Unexcused: The reason does not match an approved category, regardless of notice timing.
The "excused, late notice" category is the one most organizations skip, and skipping it forces managers into a binary choice that does not reflect the actual situation. An employee with a legitimate reason who called 15 minutes late is not the same as an employee who offered no qualifying reason at all. Maintaining this third category produces fairer, more defensible records.
Expected outcome: The event is assigned one of three classifications: Excused, Excused (Late Notice), or Unexcused.
5. Request Documentation if the Threshold Is Met
Check whether the absence triggers a documentation requirement under the attendance policy. Common thresholds include:
- Absences of three or more consecutive days require a doctor's note or medical documentation.
- Bereavement absences beyond the standard allowance require documentation of the relationship and the event.
- Jury duty requires a copy of the summons or court documentation.
If the threshold applies, notify the employee in writing of the documentation requirement and the due date. Use the same channel the employee used to report the absence when possible, and follow up with a written record (email or system notification). Record the documentation request date and the due date in the attendance log.
Do not change the classification based on pending documentation. The classification stands as assigned in Step 4 until documentation is received or the due date passes. If documentation is not provided by the deadline, the event may be reclassified per the policy's documentation-failure rule.
Expected outcome: The employee is notified of any documentation requirement with a clear due date, and the request is logged in the attendance record.
6. Enter the Classification into the Attendance System
Log the completed classification in the time-and-attendance system with the following data points:
- Employee name and ID
- Date of absence
- Notification timestamp
- Stated reason (verbatim)
- Matched category code
- Classification: Excused, Excused (Late Notice), or Unexcused
- Documentation requested (yes/no) and due date if applicable
- Classifying manager's name
This record is the single source of truth for enforcement, payroll, and any future audit or dispute. If your system supports reason codes, use the code rather than free text for the classification field so reporting and pattern analysis can run automatically. EasyClocking by WorkEasy Software stores each classification as a coded, timestamped event that feeds directly into payroll sync and the sick-leave pattern screen at pay-period close.
Expected outcome: A coded, timestamped classification record exists in the attendance system with all required data fields populated.
7. Notify the Employee of the Classification in Writing
Send the employee a brief written confirmation of the classification decision within one business day. The notice should include:
- The date of the absence
- The classification assigned (Excused, Excused with Late Notice, or Unexcused)
- Any documentation requirement and its due date
- The policy's appeal or dispute process, if one exists
Written notification serves two purposes. First, it gives the employee the opportunity to dispute an incorrect classification before it affects payroll or triggers discipline. Second, it creates a paper trail showing the employee was informed, which is essential if the classification later contributes to a progressive discipline action. Deliver the notice through the organization's standard communication channel (email, system notification, or printed memo delivered in person with a signature line). Document delivery in the attendance log.
Expected outcome: The employee has received written confirmation of the classification, and delivery is documented in the attendance file.

Download the procedure above

How to Define and Apply Tardiness Rules Across Shifts

intermediate · 2 weeks including validation period

This procedure establishes shift-specific tardiness thresholds and embeds them in the attendance system so every late arrival is captured consistently. Executed by HR in collaboration with operations managers during policy setup or shift-schedule changes, it produces a configured tardiness rule set validated against real clock-in data.

1. List All Active Shift Start Times
Prerequisites
- Current shift schedule with defined start times for all locations and roles
- Draft attendance policy with a tardiness definition (e.g., arrival more than X minutes after scheduled start)
- Manager roster with shift assignments confirmed
- Time-and-attendance system access with rule-configuration permissions
Pull the current shift schedule and document every unique start time across all locations, departments, and roles. Include rotating schedules, split shifts, and any seasonal or project-based shift variations that are active or planned for the next quarter.
Organize the list in a simple table:
- Location
- Department or crew
- Shift name or identifier
- Scheduled start time
- Days of the week the shift runs
This inventory is the foundation for every tardiness rule you configure. If a shift start time is missing from this list, late arrivals on that shift will not be flagged, and you will discover the gap only when a manager reports inconsistent tardiness data. For multi-location employers, collect this information from each site's operations manager and verify it against the scheduling system. Do not assume all sites run the same schedule.
Expected outcome: A complete inventory of every active shift start time across all locations and roles, documented in a single reference table.
2. Define the Tardiness Grace Period
Confirm the policy's grace-period threshold and document it as a single, organization-wide standard. The grace period is the number of minutes after the scheduled start time during which a clock-in is not flagged as tardy. Common grace periods range from zero to seven minutes.
Factors to consider when setting the threshold:
- Operational reality: On a construction job site, workers may need a few minutes to badge in after arriving at the gate. On a manufacturing floor, clock-in devices may be located away from the workstation. A zero-minute grace period in these environments generates false positives that erode manager trust in the system.
- Rounding rules: If your payroll uses rounding (e.g., nearest quarter-hour), align the grace period with the rounding increment to avoid conflicts between what the attendance system flags and what payroll pays.
- Consistency: Use one grace period for the entire organization unless a documented operational justification exists for a shift-specific exception. Inconsistent thresholds invite favoritism claims.
Document the chosen grace period in the attendance policy and in the system configuration notes.
Expected outcome: A single, documented grace-period threshold is established and ready for system configuration.
3. Set the Tardy-to-Absent Conversion Boundary
Define the minute-mark at which a late arrival converts from a tardiness event to a half-day or full-day absence. Without this boundary, managers make inconsistent judgment calls on employees who arrive very late, and the attendance record becomes unreliable for both discipline and payroll purposes.
Common conversion rules:
- More than 60 minutes late without prior approval equals a half-day absence.
- More than half the shift duration late equals a full-day absence.
- Arrival after the midpoint of the shift, with no prior communication, triggers the no-call/no-show procedure instead of the tardiness procedure.
Write the conversion rule into the attendance policy and map it to the corresponding event codes in the system. This boundary is the handoff point between the tardiness enforcement procedure and the absence classification procedure. If your policy does not define it, a 90-minute late arrival sits in a gray zone that neither procedure covers cleanly.
Expected outcome: A documented conversion rule defines exactly when a late arrival becomes a half-day or full-day absence, with corresponding event codes mapped.
4. Configure Tardiness Rules in the Attendance System
Enter each shift start time and the tardiness threshold into the time-and-attendance system so late clock-ins are auto-flagged. For each shift in your inventory from Step 1, configure:
- The scheduled start time
- The grace period (from Step 2)
- The tardy-to-absent conversion boundary (from Step 3)
- The event code the system assigns when a clock-in falls outside the grace window
EasyClocking by WorkEasy Software configures shift-specific tardiness rules during implementation, including grace periods, tardy-to-absent conversion thresholds, and the progressive discipline triggers that surface in manager dashboards. If your system supports rule inheritance, set the grace period at the organization level and override it only for shifts with documented exceptions.
After configuration, run a spot check by pulling a recent week's clock-in data and verifying that the system correctly flags late arrivals against the new rules. Correct any misaligned shift-start-time mappings before moving to the validation step.
Expected outcome: Every active shift has a configured tardiness rule in the attendance system, and a spot check confirms correct flagging on recent clock-in data.
5. Map Tardiness Events to the Progressive Discipline Schedule
Confirm how many tardiness events within a rolling period trigger each level of the progressive discipline schedule. A typical structure looks like this:
- 3 tardy events in a rolling 90-day period: verbal warning
- 5 tardy events: written warning
- 7 tardy events: final written warning
- 9 or more tardy events: termination review
Document whether tardiness events and absence events count on the same progressive schedule or separate schedules. If your policy includes a tardiness-to-absence conversion rule (e.g., 3 tardy events equal 1 absence occurrence), document that conversion explicitly and configure it in the system. Mixing tardiness and absence counts on the same schedule without a written conversion rule creates inconsistency that undermines enforcement and opens the organization to discrimination claims.
Record the discipline thresholds, rolling-period length, and conversion rules in the attendance policy and in the system's discipline-trigger configuration.
Expected outcome: The progressive discipline thresholds for tardiness are documented, configured in the system, and aligned with (or separated from) the absence discipline schedule.
6. Distribute the Tardiness Rule Reference Card to Managers
Create a one-page reference card that summarizes the tardiness rules for every shift and distribute it to all direct managers before the policy effective date. The card should include:
- Each shift's start time and the grace period
- The tardy-to-absent conversion boundary
- The progressive discipline thresholds and the rolling-period length
- The tardiness-to-absence conversion rule, if applicable
- The contact for HR escalation questions
Distribute the card through a channel managers actually use: a printed laminated card posted near the time clock on a shop floor or warehouse dock, a pinned message in the manager communication channel, or a PDF attached to the policy announcement email. The goal is zero ambiguity on the rules before the first tardiness flag fires. Managers who learn about the rules from the system alert rather than from the reference card will handle the first few events inconsistently.
Expected outcome: Every direct manager has received and acknowledged the tardiness rule reference card before the policy effective date.
7. Validate the Rule Set with a Two-Week Audit
Run a two-week parallel audit comparing the system's tardiness flags against manual manager logs. During this period, ask each manager to record tardiness events independently (on paper or in a spreadsheet) alongside the system's automated flags.
At the end of the two-week window, compare the two data sets:
- Identify events the system flagged that the manager did not record (potential false positives from misconfigured shift times).
- Identify events the manager recorded that the system missed (potential gaps in shift-time coverage or grace-period configuration).
- Calculate the match rate and investigate every discrepancy.
Correct any configuration errors and re-run the comparison for the affected shifts. Do not begin enforcement actions based on system flags until the match rate between system and manager records is consistent. EasyClocking by WorkEasy Software supports this validation step through exception reports that surface flagged events alongside the raw clock-in timestamp, making discrepancy investigation straightforward.
Expected outcome: System-generated tardiness flags match manual manager records at a consistent rate, and all configuration discrepancies have been resolved before full enforcement begins.

Download the procedure above

How to Enforce a Tardiness Policy Using Progressive Discipline

intermediate · 2 hours per disciplinary action

This procedure applies consistent, documented disciplinary responses when an employee accumulates tardiness events within a rolling review period. Executed by the direct manager with HR support, it produces a signed disciplinary record that creates an audit-ready enforcement trail.

1. Pull the Employee's Tardiness Event Log
Prerequisites
- Tardiness rule set configured per the Define and Apply Tardiness Rules procedure
- Progressive discipline schedule documented in the attendance policy (verbal, written, final, termination)
- Employee's current tardiness event count for the rolling period pulled from the attendance system
- HR business partner notified before any written or higher-level action
Retrieve the employee's rolling-period tardiness count from the attendance system. Do not rely on manager memory or informal notes. The system record is the single source of truth for discipline decisions.
Review the log for the following:
- Total tardiness events within the current rolling period
- Dates, clock-in times, and duration of each tardy event
- Any prior discipline actions already issued during this rolling period
- Any pending classification disputes or documentation requests that might affect the count
If any event in the log is still in a pending or disputed status, resolve it with HR before proceeding. Issuing discipline based on a count that includes a disputed event creates a procedural vulnerability. EasyClocking by WorkEasy Software surfaces rolling-period tardiness counts on the manager dashboard, including the discipline level each employee has reached, so the data pull takes seconds rather than requiring a manual report build.
Expected outcome: A verified, current tardiness event log with no unresolved disputes, ready to determine the applicable discipline level.
2. Identify the Applicable Discipline Level
Match the employee's event count to the progressive discipline schedule. If the policy states that five tardy events in a rolling 90-day period trigger a written warning, and the employee has five confirmed events, the applicable level is a written warning.
Check two additional items before proceeding:
- Prior discipline in this cycle: If the employee already received a verbal warning at the three-event threshold, the next action is the written warning. Do not repeat the verbal warning.
- Discipline level skip requests: If a manager believes the situation warrants skipping a level (e.g., jumping from verbal to final), that decision requires documented HR approval before the meeting. Inconsistent level-skipping is one of the most common sources of legal exposure in attendance enforcement.
Record the identified discipline level and the supporting event count in your meeting preparation notes. You will present both to the employee in the meeting.
Expected outcome: The correct progressive discipline level is identified and documented, with any level-skip requests routed to HR for approval.
3. Schedule a Private Meeting Within 48 Hours
Schedule a face-to-face meeting with the employee within 48 hours of the threshold being reached. Delays beyond 48 hours weaken the connection between the events and the discipline, and they create the impression that enforcement is inconsistent or retaliatory when it eventually happens.
Choose a private location: a closed office, a conference room, or an area away from the shop floor, warehouse dock, or job-site trailer where other employees cannot overhear. On a construction site or in a manufacturing plant, this may mean scheduling the meeting before or after the shift rather than during a break in a shared space.
Document the meeting date, time, and location in the attendance file. If a witness or HR representative will attend (required for written-level actions and above at most organizations), confirm their availability before notifying the employee.
Expected outcome: A private meeting is scheduled within 48 hours, with the date, time, location, and attendees documented in the attendance file.
4. Present the Tardiness Record to the Employee
Open the meeting by presenting the employee's tardiness event log. Show the specific dates, clock-in times, and tardiness durations for each event in the rolling period. Give the employee a printed or on-screen copy so they can review the data.
After presenting the record, give the employee the opportunity to provide context. Listen and document any information the employee offers. Common responses include:
- A disputed event the employee believes was classified incorrectly
- A personal or family circumstance the employee had not previously disclosed
- A scheduling or transportation issue affecting a specific set of dates
If the employee raises a dispute about a specific event, note it and inform the employee that the disputed event will be reviewed. Do not reduce the discipline level during the meeting based on an unverified dispute. If the review later removes the event from the count and drops the employee below the threshold, the discipline action can be rescinded with documentation.
Expected outcome: The employee has reviewed the tardiness record, and any context or disputes raised by the employee are documented in the meeting notes.
5. Issue the Disciplinary Action in Writing
Complete the discipline form with the following information:
- Employee name, ID, and department
- Dates and details of each tardiness event in the rolling period
- The attendance policy section that defines the progressive discipline threshold
- The discipline level being issued (verbal warning, written warning, final warning)
- The improvement expectation: what the employee must do to avoid the next level (e.g., zero additional tardy events within the next 30 days)
- The consequence if improvement does not occur
Read the form to the employee or allow the employee to read it independently. Answer any questions about the content. EasyClocking by WorkEasy Software generates pre-populated discipline notices from the attendance module, pulling the event dates and policy references directly from the system record so the manager's preparation work is minimal.
Expected outcome: A completed discipline form is ready for signature, with all event data, policy references, and improvement expectations documented.
6. Obtain the Employee's Signature or Document Refusal
Ask the employee to sign the discipline form. The signature confirms receipt of the notice, not agreement with the discipline. Make this distinction clear to the employee verbally and in the form's language.
If the employee refuses to sign:
1. Note the refusal on the form with the date and time.
2. Have the witness (if present) sign the form confirming the employee was presented with the document and declined to sign.
3. Provide the employee with a copy of the unsigned form.
File the signed (or refusal-documented) form in the employee's attendance record. This document is the audit trail that proves the discipline was issued, communicated, and documented, regardless of whether the employee signed it. Without this step, a later dispute becomes a credibility contest between the manager and the employee, with no written record to resolve it.
Expected outcome: The discipline form is signed by the employee or documented as refused, filed in the employee's attendance record, and a copy is provided to the employee.
7. Set a 30-Day Follow-Up Date
Before closing the meeting, schedule a follow-up check-in for 30 days after the discipline date. The purpose of the follow-up is to review the employee's tardiness record in the intervening period and document either improvement or continued issues.
Record the follow-up date in the attendance file and in the manager's calendar. At the follow-up meeting:
- If the employee had zero tardy events in the 30-day window, document the improvement in the attendance file. Verbal acknowledgment of improvement reinforces the policy's fairness framing.
- If additional tardy events occurred, assess whether the next discipline threshold has been reached and re-enter this procedure at Step 1.
The 30-day check-in closes the loop on each discipline action. Without it, discipline actions accumulate in the file without any record of whether they produced the intended behavioral change, and managers lose the ability to distinguish between an employee who improved and one who did not.
Expected outcome: A 30-day follow-up date is scheduled, documented in the attendance file, and entered in the manager's calendar.

Download the procedure above

How to Respond to a No-Call/No-Show Event

intermediate · 4 hours including contact attempts and documentation

This procedure executes a documented, timestamped response when an employee fails to report to a scheduled shift without prior notice. Executed by the direct manager within the first two hours of the missed shift, it produces a no-call/no-show record with contact-attempt documentation and escalation status.

1. Confirm the Absence at Shift Start
Prerequisites
- Policy definition of no-call/no-show (e.g., absent with no contact within 1 hour of shift start)
- Policy definition of job abandonment trigger (e.g., 3 consecutive no-call/no-shows)
- Emergency contact information accessible to the manager
- HR contact available for same-day escalation
Verify that the employee has not clocked in and has not contacted the manager, HR, or any other approved notification channel by the policy's notification deadline. Check the time-and-attendance system for a clock-in record, and check voicemail, text messages, and any team communication tools the organization uses.
Also check with the employee's direct coworkers or crew lead. In warehouse, construction, and manufacturing environments, an employee may have told a coworker they would be late or absent without contacting the manager directly. If the employee contacted a coworker but not the manager, this is a notification-procedure violation, not a no-call/no-show. Handle it through the absence classification procedure instead.
Document the time you confirmed the absence, the channels you checked, and the result of each check. This timestamp is the anchor for everything that follows.
Expected outcome: A confirmed, timestamped record that the employee did not clock in and did not contact the manager or HR by the policy deadline.
2. Attempt Direct Contact with the Employee
Call the employee's primary phone number. Document the time of the call, the outcome (no answer, voicemail left, busy signal, reached the employee), and the content of any message you left.
If you reach the employee:
- Record the employee's stated reason for the absence.
- Inform the employee that the event is being classified as a no-call/no-show because no notice was provided by the policy deadline.
- If the employee provides a reason that may qualify as excused (e.g., emergency hospitalization), note it and inform the employee that reclassification will be reviewed by HR upon documentation.
If you do not reach the employee, send a text message or leave a voicemail that includes: the date, the fact that the employee was expected for a scheduled shift, and a request to contact the manager or HR as soon as possible. Document the message content and delivery timestamp. Do not send threatening or accusatory messages. The tone should be factual and concerned.
Expected outcome: A documented contact attempt with timestamp, outcome, and message content recorded in the attendance log.
3. Contact the Emergency Contact if the Employee Is Unreachable
If the employee has not responded within two hours of the shift start, contact the listed emergency contact. This step serves two purposes: it verifies the employee's safety, and it creates a documented good-faith effort to reach the employee before escalating.
When speaking with the emergency contact:
- Identify yourself by name and role.
- State that the employee was expected for a scheduled shift and has not been reachable.
- Ask only whether the employee is safe and whether the emergency contact can relay a message. Do not discuss discipline, attendance history, or policy consequences with the emergency contact.
Document the time of the call, the name of the person you spoke with, and the outcome. If the emergency contact is also unreachable, document the attempt and proceed to the classification step. EasyClocking by WorkEasy Software auto-logs no-call/no-show events and triggers a manager notification workflow, ensuring the contact-attempt record is captured in the attendance file without manual entry.
Expected outcome: A documented emergency-contact attempt with timestamp and outcome, confirming a good-faith safety check before further escalation.
4. Classify the Event as No-Call/No-Show
Enter the event in the attendance system with the NCNS event code. Attach the following to the record:
- Date and shift the employee missed
- Timestamp of the absence confirmation (Step 1)
- Direct contact attempt log (Step 2): time, channel, outcome, message content
- Emergency contact attempt log (Step 3): time, person contacted, outcome
- Any stated reason provided by the employee if contact was made
The NCNS classification is distinct from an unexcused absence. An unexcused absence means the employee communicated but the reason did not qualify. A no-call/no-show means no communication occurred at all. Keeping these categories separate allows the progressive discipline schedule and payroll to treat them differently, which most policies require.
If the employee later contacts the manager with a reason that may qualify for reclassification (e.g., they were in the hospital), flag the event for HR review but do not change the code until HR completes the review.
Expected outcome: A coded NCNS record exists in the attendance system with all contact-attempt documentation attached.
5. Notify HR of the Event
Send HR a written summary of the no-call/no-show event on the same day it occurs. The summary should include:
- Employee name, ID, shift, and location
- Date and time of the missed shift
- Contact-attempt timeline and outcomes
- Any context or reason the employee provided if contact was made
- The employee's NCNS count for the current rolling period
- Whether the event brings the employee to or near the job-abandonment threshold
HR needs this information to assess whether the event triggers additional obligations, such as FMLA notice requirements, ADA interactive process considerations, or state-specific leave protections. A single no-call/no-show may have an explanation that qualifies for protected leave. HR cannot make that assessment without same-day notification.
Email or use the organization's HR case-management system. Do not rely on a verbal mention at a later meeting.
Expected outcome: HR has received a same-day written summary of the NCNS event with all relevant data for assessment and escalation.
6. Issue a Written NCNS Notice Upon the Employee's Return
When the employee returns to work, deliver a written notice of the no-call/no-show event and the applicable discipline level before the employee begins the shift. Do not wait until the end of the day or the next pay period.
The notice should include:
- The date and shift of the NCNS event
- A statement that no notification was received by the policy deadline
- The discipline level being applied per the progressive discipline schedule
- The employee's current NCNS count for the rolling period
- A reminder of the job-abandonment threshold and its consequences
Give the employee the opportunity to provide context or dispute the classification. If the employee provides documentation that supports reclassification (e.g., hospital discharge papers), forward the documentation to HR for review. Do not reclassify the event on the spot. Obtain the employee's signature or document their refusal, and file the notice in the attendance record.
Expected outcome: The employee has received and acknowledged (or refused) a written NCNS notice with the applicable discipline level, filed in the attendance record.
7. Evaluate the Job-Abandonment Trigger
Review the employee's NCNS count against the policy's job-abandonment threshold. Most employer policies define job abandonment as two or three consecutive no-call/no-show shifts. The specific number must be defined in the written attendance policy and applied consistently.
If the employee has reached the threshold:
1. Escalate to HR immediately. Do not proceed with termination without HR review and approval.
2. HR should verify that all NCNS events in the consecutive sequence are properly documented with contact attempts.
3. HR should confirm that no pending reclassification requests, FMLA applications, or ADA accommodation requests affect the count.
4. If HR approves the job-abandonment determination, follow the organization's termination procedure, including the final pay and benefits notification requirements under applicable state law.
If the employee has not reached the threshold, document the current count in the attendance file and note how many additional consecutive NCNS events would trigger the abandonment review. This information helps the manager recognize the escalation point if another event occurs.
Expected outcome: The employee's NCNS count is evaluated against the job-abandonment threshold, and either an HR escalation file is opened or the current count is documented with the remaining trigger distance noted.

Download the procedure above

How to Audit Sick-Leave Usage and Sync Finalized Attendance to Payroll

advanced · 3 hours per pay-period close

This procedure identifies potential sick-leave abuse patterns in a rolling period and ensures all classified attendance events are finalized, approved, and transmitted to payroll without manual correction. Executed by HR and payroll coordinators at every pay-period close, it produces a clean, audit-ready attendance-to-payroll data file.

1. Pull the Period's Absence and Tardiness Event Log
Prerequisites
- All absence events for the period classified per the Classify an Absence procedure (excused, unexcused, NCNS)
- Sick-leave abuse signal criteria defined in policy (e.g., Monday/Friday pattern, post-holiday clustering, frequency exceeding a defined threshold per rolling period)
- Payroll system integration or export format confirmed with the payroll team
- Manager approval of all time records for the period complete
Export all classified attendance events for the pay period from the attendance system. Filter the export by event type (excused, excused with late notice, unexcused, NCNS, tardy) and by employee. The export should include:
- Employee name and ID
- Event date and type
- Classification code and reason
- Manager who classified the event
- Documentation status (received, pending, not required)
- Discipline actions issued, if any
This export is the raw data set for both the sick-leave pattern screen and the payroll sync. If your attendance system allows scheduled exports, configure the report to run automatically on the day after the pay-period cutoff. EasyClocking by WorkEasy Software generates this export automatically at pay-period close, formatted for direct transmission to your payroll system.
Review the export for completeness. If any employee's time record is missing or incomplete, flag it before proceeding. An incomplete data set transmitted to payroll creates retroactive corrections that are more expensive to fix than a same-day hold.
Expected outcome: A complete, filtered export of all attendance events for the pay period, ready for pattern screening and payroll sync.
2. Run the Sick-Leave Pattern Screen
Screen the period's sick-leave events against the abuse-signal criteria defined in the attendance policy. Common policy-defined signals include:
- Day-of-week pattern: Sick calls on Mondays or Fridays at a rate significantly above the employee's baseline or the team average.
- Post-holiday clustering: Sick calls on the day before or after a company holiday or the employee's scheduled vacation.
- Frequency threshold: Sick-leave occurrences exceeding the policy's defined limit within a rolling period (e.g., more than a set number of occurrences in 90 days) without a qualifying medical condition on file.
- Post-discipline clustering: Sick calls in the days immediately following a disciplinary event.
A pattern flag is not a finding of abuse. It is a signal that opens an investigation. Do not adjust pay, change the classification, or initiate discipline based on a pattern flag alone. Flag the employee's record for HR review and move on to the next step. EasyClocking by WorkEasy Software runs this pattern screen automatically, surfacing flagged employees in a dashboard view that HR can review without building manual pivot tables.
Expected outcome: Employees whose sick-leave usage matches defined abuse signals are flagged for HR investigation, with no pay or classification changes made at this stage.
3. Escalate Flagged Cases to HR for Investigation
For each flagged employee, open an investigation file in the HR case-management system. The file should include:
- The employee's sick-leave event log for the rolling period
- The specific pattern signals triggered (day-of-week, post-holiday, frequency, post-discipline)
- The employee's overall attendance record for context
- Any prior discipline actions on file
HR owns the investigation from this point. The investigation process typically includes:
1. Reviewing whether the employee has a qualifying medical condition on file (FMLA certification, ADA accommodation, or state-mandated sick-leave protection) that explains the pattern.
2. Meeting with the employee to discuss the pattern and give the employee the opportunity to provide context or documentation.
3. Documenting the investigation findings and determining whether the pattern constitutes abuse per policy or is explained by a protected condition.
Do not delay the payroll sync while waiting for investigation outcomes. The classification that exists at the time of the payroll cutoff is the classification that transmits. If the investigation later changes a classification, process the correction in the next pay period as an adjustment.
Expected outcome: An HR investigation file is opened for each flagged employee, with the sick-leave pattern data and supporting context documented.
4. Confirm Manager Approval on All Time Records
Verify that every employee's time record for the pay period carries a manager-approved status in the attendance system. This is the hard gate before payroll export. No record transmits without manager approval.
Check for the following common approval gaps:
- Employees who transferred between departments or crews mid-period, where neither the old nor the new manager approved the full record.
- Managers who are themselves absent and have not delegated approval authority.
- Records with open exception flags (missing punches, unresolved disputes, pending documentation) that prevent the manager from approving.
For each unapproved record, contact the responsible manager directly. If the manager cannot approve before the payroll cutoff, escalate to the manager's supervisor or HR for emergency approval. Document any emergency approvals with the approving authority's name and the reason the primary manager was unavailable.
EasyClocking by WorkEasy Software enforces the manager-approval gate automatically, preventing payroll export until all records in the period carry approved status.
Expected outcome: Every employee's time record for the pay period has a documented manager approval, with no unapproved records remaining before payroll export.
5. Reconcile Unresolved Classification Disputes
Identify any attendance events still in "pending" classification status. These are events where the employee disputed the classification, where documentation is still outstanding, or where the manager flagged the event for HR review and the review has not been completed.
For each pending event, determine the appropriate resolution path:
- Documentation pending but due before payroll cutoff: Contact the employee and request immediate submission. If the documentation arrives and supports reclassification, update the event code before export.
- Documentation past due: Apply the policy's documentation-failure rule. Most policies convert a pending-documentation event to unexcused if documentation is not received by the deadline.
- HR review pending: If the review cannot be completed before payroll cutoff, transmit the event with its current classification and process any reclassification as a next-period adjustment.
Document the resolution of each pending event, including who made the decision and on what basis. Zero pending events at the time of payroll export is the target. Every pending event that transmits unresolved creates a retroactive correction in the next period.
Expected outcome: All pending classification events are resolved or documented for next-period adjustment, with zero unresolved events blocking the payroll export.
6. Export the Finalized Attendance Data to Payroll
Transmit the approved, classified attendance file to the payroll system in the required format. Depending on your integration setup, this may be:
- A direct API transmission to payroll software (such as ADP, QuickBooks, Gusto, or another system in the platform's integration library)
- A scheduled file export in CSV, XML, or the payroll provider's proprietary format
- A manual upload to the payroll system's import portal
Before transmitting, run a final validation check:
- Total employee count in the export matches the active employee roster for the period.
- Total hours and absence codes are present for every employee.
- No records show blank classification codes or missing manager approvals.
Document the transmission timestamp, the file name or API confirmation ID, and the total employee count transmitted. EasyClocking by WorkEasy Software supports direct integrations with over 20 payroll systems, transmitting approved time data without manual file handling for supported platforms.
Expected outcome: The finalized attendance data file is transmitted to payroll with a documented timestamp and confirmation ID.
7. Verify Payroll Receipt and Flag Discrepancies
Confirm that the payroll system received and accepted the transmitted attendance file. Check for:
- Import confirmation: Most payroll systems generate a receipt confirmation or import log. Pull this log and verify the employee count and record count match what you transmitted.
- Import errors: Look for rejected records, field-mapping errors, or unrecognized codes. Common issues include new employees not yet set up in payroll, event codes that do not map to a payroll pay code, and date-format mismatches.
- Discrepancy count: Any records rejected by payroll must be corrected and re-transmitted before the payroll processing deadline.
For each import error, determine whether the fix is in the attendance system (e.g., a missing employee record) or in the payroll system (e.g., an unmapped pay code). Coordinate with the payroll team to resolve errors same-day. Document every error and its resolution in the payroll sync log.
When the import is clean and confirmed, the pay-period attendance cycle is closed. File the transmission log, import confirmation, and any error-resolution notes as the audit record for the period.
Expected outcome: Payroll receipt is confirmed, all import errors are resolved and documented, and the pay-period attendance-to-payroll cycle is closed with a complete audit record.

Download the procedure above

Not Ready for a Quote? Start Here.

How to Classify an Absence as Excused or Unexcused

1. Receive the Absence Notification

2. Record the Employee's Stated Reason Verbatim

3. Match the Stated Reason to the Approved-Reasons List

4. Apply the Notice-Timing Rule

5. Request Documentation if the Threshold Is Met

6. Enter the Classification into the Attendance System

7. Notify the Employee of the Classification in Writing

How to Define and Apply Tardiness Rules Across Shifts

1. List All Active Shift Start Times

2. Define the Tardiness Grace Period

3. Set the Tardy-to-Absent Conversion Boundary

4. Configure Tardiness Rules in the Attendance System

5. Map Tardiness Events to the Progressive Discipline Schedule

6. Distribute the Tardiness Rule Reference Card to Managers

7. Validate the Rule Set with a Two-Week Audit

How to Enforce a Tardiness Policy Using Progressive Discipline

1. Pull the Employee's Tardiness Event Log

2. Identify the Applicable Discipline Level

3. Schedule a Private Meeting Within 48 Hours

4. Present the Tardiness Record to the Employee

5. Issue the Disciplinary Action in Writing

6. Obtain the Employee's Signature or Document Refusal

7. Set a 30-Day Follow-Up Date

How to Respond to a No-Call/No-Show Event

1. Confirm the Absence at Shift Start

2. Attempt Direct Contact with the Employee

3. Contact the Emergency Contact if the Employee Is Unreachable

4. Classify the Event as No-Call/No-Show

5. Notify HR of the Event

6. Issue a Written NCNS Notice Upon the Employee's Return

7. Evaluate the Job-Abandonment Trigger

How to Audit Sick-Leave Usage and Sync Finalized Attendance to Payroll

1. Pull the Period's Absence and Tardiness Event Log

2. Run the Sick-Leave Pattern Screen

3. Escalate Flagged Cases to HR for Investigation

4. Confirm Manager Approval on All Time Records

5. Reconcile Unresolved Classification Disputes

6. Export the Finalized Attendance Data to Payroll

7. Verify Payroll Receipt and Flag Discrepancies

How These Procedures Connect

Next steps