Attendance Occurrence Tracking SOP
Track attendance occurrences under a no-fault point policy, apply points consistently, and exclude protected leave before discipline is triggered. Use it to document each event, update balances, and escalate unclear cases for review.
Trusted by frontline teams 15 years of frontline software
Built for: Manufacturing · Retail · Warehousing · Call Centers · Healthcare Support
Overview
This Attendance Occurrence Tracking SOP template defines how to record an attendance event, determine whether it is protected, apply the correct point value, and update the employee’s balance in a consistent way. It is designed for no-fault point policies where the organization needs a repeatable process for tardies, absences, no-call/no-show events, and other attendance deviations.
Use this template when attendance decisions must be documented, reviewed against a policy matrix, and retained as controlled documented information. It is especially useful when multiple supervisors, HR staff, or site leaders handle attendance and you need the same verification and escalation path at every location. The template also supports protected-leave exclusions so FMLA, ADA-related accommodations, and similar cases are not counted as ordinary occurrences.
Do not use this SOP as a substitute for legal review of leave rights or accommodation obligations. It is not meant for informal coaching-only cultures that do not use points, and it should not be used to bypass a leave-management process or a permit-to-work style approval flow where another procedure governs the absence. If your policy is highly discretionary, this template should be adapted carefully so the documented steps still match actual practice.
Standards & compliance context
- This template supports ISO 9001:2015 documented information practices by creating a controlled record of attendance decisions, exclusions, and revisions.
- Protected-leave checks help the organization avoid counting legally protected absences as ordinary occurrences and support consistent handling of FMLA- and ADA-related cases.
- If attendance events involve hazardous work schedules or restricted duties, the review should align with OSHA-related internal controls and any permit-to-work or fitness-for-duty process that applies.
- The documentation fields can support internal audit trails and corrective action review when repeated attendance deviations indicate a process or staffing issue.
- If your organization uses union rules, state leave laws, or local attendance ordinances, those requirements should be layered into the policy matrix before rollout.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Steps
This section matters because it turns attendance handling into a repeatable sequence with clear ownership, verification, and escalation.
-
Verify the attendance event details
The supervisor verifies the attendance event details in the timekeeping or HR system.
Record the following fields before assigning any points:
- Employee name or ID
- Date and scheduled shift
- Event type: absence, tardiness, early departure, or no-call/no-show
- Actual clock-in / clock-out data, if available
- Any submitted explanation from the employee
-
Check for protected leave or accommodation status
The HR representative reviews whether the attendance event is covered by FMLA, ADA, workers’ compensation, approved leave, or another protected status.
Do not assign points until the review is complete.
-
Apply the point value from the policy matrix
The supervisor applies the point value defined in the attendance policy for the specific occurrence type.
Use only the approved matrix. Do not adjust points based on personal judgment, employee tenure, or department preference unless the policy explicitly allows it.
Examples:
- Full-day absence: apply the policy-defined absence points
- Tardy arrival: apply the policy-defined tardy points
- Early departure: apply the policy-defined early leave points
- No-call/no-show: apply the policy-defined no-call/no-show points
-
Record the occurrence in the tracking system
The attendance coordinator records the occurrence in the HRIS or attendance log.
Include:
- Occurrence type
- Point value assigned
- Policy reference or rule applied
- Supporting documentation reference
- Name of the person who completed the review
-
Update the employee point balance
The HR representative verifies that the employee’s cumulative attendance points were updated correctly.
Confirm that the balance matches the policy calculation and that any prior point removals, expirations, or corrections were applied before finalizing the record.
-
Document the protected leave exclusion
The HR representative documents that the event is excluded from point assessment because it is protected or approved.
Record the applicable reason code, such as:
- FMLA protected leave
- ADA accommodation-related absence
- Approved medical leave
- Other approved leave category
-
Escalate unclear cases for review
The supervisor escalates the case when leave status, documentation, or accommodation coverage is unclear.
Do not assign points until HR, leave administration, or legal review confirms the correct classification.
Escalate immediately if:
- Medical documentation is incomplete
- The employee requests accommodation-related consideration
- The event may involve intermittent FMLA leave
- The event may be tied to a disability-related accommodation
-
Initiate progressive discipline when thresholds are met
The manager initiates the next progressive discipline step when the employee’s point total reaches a policy threshold.
Use the approved discipline sequence defined in the policy, such as:
- Verbal warning
- Written warning
- Final warning
- Termination review
Document the threshold reached, the date, and the reviewer who approved the action.
How to use this template
- The administrator verifies the attendance event details, including date, shift, type of occurrence, and source record, before any point decision is made.
- The reviewer checks for protected leave, accommodation status, or other approved absence documentation and routes uncertain cases to the designated competent person.
- The reviewer applies the point value from the policy matrix and records the rationale when the event falls into a special category or deviation.
- The administrator enters the occurrence into the tracking system, updates the employee point balance, and attaches supporting documentation or exclusion notes.
- The supervisor or HR owner reviews threshold crossings and initiates progressive discipline only after the record is complete and any required escalation has been resolved.
Best practices
- Verify the source record against the timekeeping system before assigning points so a punch error is not treated as an attendance violation.
- Use one policy matrix for all sites that share the same rules, and version-control it as documented information under ISO 9001-style control.
- Document every protected-leave exclusion with the reason code, reviewer, and date so the decision can be defended later.
- Escalate ambiguous cases before the point balance is updated when the event may involve FMLA, ADA accommodation, workers’ compensation, or another protected status.
- Separate tardiness, early departure, no-call/no-show, and full absence into distinct categories so the point value matches the actual deviation.
- Review threshold triggers against the current balance and the rolling window on the same day the occurrence is posted.
- Train supervisors to use the same wording for non-conformance notes so the record stays consistent across departments.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this attendance occurrence tracking SOP cover?
It covers the full workflow for recording an attendance event, checking whether the absence is protected, assigning points from the policy matrix, and updating the employee’s point balance. It also includes documentation for protected leave exclusions and escalation of unclear cases. The template is meant for no-fault point systems where consistency matters more than supervisor discretion.
Who should use this SOP?
HR, attendance administrators, payroll support staff, and managers who are authorized to apply the policy should use it. A competent person should review edge cases involving FMLA, ADA accommodations, workers’ compensation, or other protected leave. If your organization separates attendance administration from discipline, this SOP helps define the handoff.
How often should attendance occurrences be reviewed?
Review should happen each time an attendance event is reported, not in batches that delay action. Point balances should also be checked on a regular cadence, such as daily or weekly, so threshold crossings are not missed. If your policy has rolling windows, the review process should match that cadence.
How does this SOP help with FMLA, ADA, or other protected absences?
The SOP requires a protected-leave check before points are assigned, which helps prevent non-conformance and inconsistent treatment. It also creates a documented exclusion record so the organization can show why an event was not counted. That documentation is important when the absence involves accommodation, intermittent leave, or another legally protected status.
What are the most common mistakes when using an attendance point template?
Common mistakes include applying points before checking protected status, using the wrong point value from the matrix, and failing to record the reason for an exclusion. Another frequent issue is not escalating unclear cases, which leads to inconsistent decisions across supervisors. Missing balance updates can also cause discipline to trigger too early or too late.
Can this template be customized for different attendance policies?
Yes. You can adapt the point matrix, threshold levels, escalation path, and documentation fields to match your policy. Some organizations also add shift-specific rules, no-call/no-show handling, or separate treatment for tardiness versus full-day absence. Keep the verification and exclusion steps intact even when the policy changes.
How does this SOP compare with ad-hoc attendance tracking?
Ad-hoc tracking often depends on memory, email threads, or supervisor judgment, which makes point assignment hard to defend. This SOP creates a repeatable sequence with defined verification, escalation, and recordkeeping steps. That structure reduces disputes and makes audits easier.
What systems can this SOP be paired with?
It can be paired with HRIS, timekeeping, payroll, case management, or ticketing systems that store attendance records and leave documentation. The template works well when the tracking system can log point balances, attach supporting documents, and flag threshold events. If your organization uses separate leave management software, this SOP should reference that handoff.
Related templates
Go deeper on the topic
-
A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
-
Overtime calculation is the process of applying federal, state, local, and contractual rules to hours worked to determine the correct pay — including...
-
Predictive scheduling laws — also called fair workweek laws or secure scheduling — require employers in covered industries to publish employee schedules...
-
Geofencing defines a virtual geographic boundary — a "fence" — around a work location. When an employee's mobile device enters or exits the fence, the...
-
MangoApps AI agents now take action across 21 apps—approving leave, advancing candidates, managing schedules—not just surfacing recommendations.
-
Discover the 5 essential communication platform features every start-up needs—from mobile-first access and security to employee engagement and real-time...
-
Discover how manual performance review processes drain HR productivity, introduce payroll errors, and stall talent strategy — and what automated systems fix.
-
MangoApps AI Experts let you deploy custom, RAG-trained AI assistants across your workforce—no per-seat subscriptions, no IT bottlenecks, full data sovereignty.
Ready to use this template?
Get started with MangoApps and use Attendance Occurrence Tracking SOP with your team — pricing built for small business.
