Guides

Employee Attendance Policy Template and Guide

An attendance policy is the document everyone points to when something goes wrong: a late arrival, a missed shift, a disputed hour. Written well, it is also the reason most of those things do not go wrong. Below you will find what a good policy covers, how to write one in an afternoon, and an employee attendance policy template you can copy and adapt.

  • 16 min read
  • 3,219 words
ShareTelegramXLinkedIn
Illustration of an attendance policy checklist beside an attendance dashboard with a weekly chart, a schedule calendar and a location privacy badgeGuides

What is an employee attendance policy?

An employee attendance policy is a written set of workplace rules covering working hours, punctuality, time recording, absence reporting, leave, overtime approval and how attendance problems are handled. It tells employees what is expected of them and tells managers how to respond, so the same situation gets the same answer regardless of who is on duty.

It is different from an employment contract, which sets individual terms such as salary and contracted hours, and from a leave policy, which sets entitlements. The attendance policy is operational: it describes how the working day actually runs.

Important: the template and guidance on this page are a practical starting point, not legal advice. Rules on working hours, breaks, overtime, sick leave, notice, disciplinary procedures and employee monitoring differ between countries and regions and change over time. Adapt the policy to the laws that apply to your business and, where possible, have it reviewed by a qualified HR or employment law professional before you use it.

Why every business needs a written attendance policy

Small teams often run on unwritten rules until the first disagreement. A written attendance policy prevents that disagreement, or at least settles it quickly.

  • Consistency: two managers apply the same grace period and the same absence procedure.
  • Fairness: employees know the rules in advance instead of discovering them when they break one.
  • Payroll accuracy: clear rules on clock-ins, breaks, corrections and overtime make the hours you pay easier to check.
  • Evidence: when a pattern of lateness or absence has to be addressed, a policy and consistent records make the conversation factual.
  • Onboarding: new employees learn how the working day runs in ten minutes instead of ten weeks.
  • Trust: a policy that states what attendance data is collected, and what is not, reassures staff who are asked to use an app on their own phone.

What should an attendance policy include?

An attendance policy should include your working hours and schedules, how time is recorded, what counts as late or absent, how to report an absence, how no-shows are handled, how records are corrected, how schedule changes, leave and overtime are approved, who is responsible for what, how attendance data and location checks are handled, and what happens when the policy is not followed. Use this checklist when writing or reviewing yours:

  • Purpose and scope: who the policy covers, including part-time and shift staff
  • Working hours and schedules: where schedules are published and how far in advance
  • Time recording: the method, what to record, and that nobody records time for someone else
  • Punctuality and grace periods: what counts as late and as leaving early
  • Absence reporting: who to tell, how, and by when
  • No-shows: what counts as one and what happens next
  • Breaks: paid and unpaid breaks and how they are recorded
  • Schedule changes and swaps: who approves them and how they are recorded
  • Overtime: when approval is needed and how it is requested
  • Corrections: how a missed or wrong record is fixed, and time limits for asking
  • Leave: how planned leave is requested and approved
  • Responsibilities: what employees and managers each must do
  • Attendance data and privacy: what is collected, when, who can see it, and how long it is kept
  • Follow-up on repeated issues: a fair, stepped process
  • Review: when the policy will next be reviewed

How to create an employee attendance policy in 8 steps

You can draft a solid policy in an afternoon if you decide the rules first and write second.

  • Step 1: List the situations you actually face. Late arrivals, sick calls, missed clock-outs, swaps, overtime requests. Your policy should answer each one.
  • Step 2: Check the legal minimums. Confirm working-time, break, overtime, sick leave and monitoring rules for each country or region where you employ people.
  • Step 3: Decide your operating rules. Grace periods, notice times, correction deadlines and who approves what. Write the numbers down.
  • Step 4: Choose one time-recording method. Two methods in parallel always disagree. Decide what the official record is.
  • Step 5: Write it plainly. Short sentences, one rule per paragraph, no legal jargon. Many employees will read it in a second language.
  • Step 6: Ask two or three employees and a manager to read it. Every question they ask is a gap in the text.
  • Step 7: Share it and ask for acknowledgement. Explain it in a short team meeting, give everyone a copy and record that they received it.
  • Step 8: Apply it consistently, then review it. Revisit the policy after three months and at least once a year, and whenever the law or your operations change.

Punctuality, lateness and grace periods

A late employee policy works best when it separates three things: the definition of late, the reporting duty, and the response to a pattern.

Define late precisely: “recording the start of work more than [5] minutes after the scheduled start.” A grace period absorbs normal variation, but it should be the same for everyone on the same shift. Posts that cannot be left uncovered, such as security or reception, may need no grace period at all.

Set a reporting duty: an employee who knows they will be late tells their manager before the shift starts. Lateness that was reported in advance is operationally very different from lateness that was not, and your policy should treat it differently.

Respond to patterns, not single events. One late arrival after a transport strike is not a performance issue. Repeated unreported lateness is. Records that show the scheduled start, the actual start and whether the lateness was reported make this distinction easy.

Absence reporting and no-shows

Absence rules should be simple enough to follow at six in the morning with a fever. State who to contact, by which channel, and by what time. A message to a team group chat is easy to miss, so name a specific person or a specific channel.

Define a no-show, sometimes called a no-call no-show, as missing a scheduled shift without notifying anyone in advance. Say what happens after one: a same-day contact attempt, a conversation on return and a record of the outcome. Be careful with rules that treat a number of consecutive no-shows as resignation or job abandonment; whether and how that is allowed depends on local law, so confirm it before you write it in.

For sick leave, state what evidence is required and after how many days, but keep it within what your local law permits. Many countries restrict what an employer can ask about an employee’s health.

Clock-in and clock-out rules and attendance corrections

Name the one official way to record time, for example Slide In and Slide Out in the SlidesClock app, and require employees to record the start and end of every shift themselves. Recording time for a colleague should be explicitly prohibited. If you use location, workplace network or device checks, say so and explain why.

Mistakes will happen: a flat battery, a forgotten Slide Out, a start recorded at the wrong site. Your policy should give a way to fix them. The employee asks for a correction with the correct time and a reason, within a set period such as two working days. A manager approves or declines it. The original record is kept alongside the correction, so anyone reviewing it later can see both. For more on keeping these records honest without surveillance, see how to reduce employee time theft.

Schedule changes, overtime approval and leave requests

Schedule changes: say where the schedule is published, how much notice you aim to give, and that swaps between employees must be approved and updated in the schedule before the shift. A swap that only exists in a chat thread will show one person absent and another working an unscheduled shift.

Overtime: say whether overtime must be approved in advance, who approves it, and how it is requested. Make clear that time worked is recorded accurately either way. Our guide on how to track employee overtime explains why recorded extra time and approved overtime should be kept separate.

Leave: say how and how far in advance planned leave is requested, who approves it, and that approved leave is not counted as absence. If you run rotating shifts or overnight work, our guide to shift attendance covers how rest days and night shifts should be handled in records.

Manager and employee responsibilities

A policy that only lists employee duties feels one-sided and usually fails. Give managers clear obligations too.

A simple split of attendance responsibilities. Adapt it to your team structure.
AreaEmployeeManager
SchedulesCheck the published schedule and raise conflicts earlyPublish schedules on time and record every change
Time recordingRecord their own start and end of work, every shiftMake sure the recording method works at every site
Lateness and absenceReport before the shift starts, through the named channelRespond consistently and record the outcome
CorrectionsRequest corrections promptly, with a reasonReview corrections quickly and fairly; never edit silently
Overtime and leaveRequest in advance where possibleDecide promptly and never approve their own requests
PrivacyUse attendance tools only as intendedAccess attendance data only for work purposes

Privacy considerations for GPS and location-based attendance

If your attendance system checks location, your policy must say so plainly. Employees are rightly cautious about installing an app that uses location on their own phone, and data protection laws in many regions require you to tell people what you collect and why.

State four things. What is checked: for example, GPS position against the workplace area, the workplace network, or the registered device. When: only at the moment the employee records the start or end of work. What is not collected: no tracking during breaks, after work or on days off, and no movement history. Who can see the data and how long it is kept.

Choose tools that make those promises true. SlidesClock checks location only at Slide In or Slide Out, when a workplace policy requires it, and does not run background location tracking. Read more about GPS attendance and privacy and how SlidesClock handles security.

Free employee attendance policy template

Copy the template below and replace everything in [square brackets] with your own details. Delete any clause that does not apply, and check every clause against the law where your employees work before you share it. SlidesClock users can name “the SlidesClock app (Slide In and Slide Out)” as the attendance method in section 3.

[COMPANY NAME]
EMPLOYEE ATTENDANCE POLICY
Effective date: [DATE]    Version: [1.0]    Policy owner: [NAME, ROLE]

1. PURPOSE
This policy explains how working time is scheduled and recorded at [Company Name], what we expect from everyone on punctuality and attendance, and how absences, corrections, schedule changes, leave and overtime are handled. It applies the same rules to everyone so that attendance is fair, predictable and accurately paid.

2. SCOPE
This policy applies to all employees of [Company Name], including full-time, part-time, temporary and shift employees, at all locations. Where this policy differs from an employment contract, a collective agreement or the law, the contract, agreement or law applies.

3. SCHEDULES AND TIME RECORDING
3.1 Work schedules are published in [attendance app / location] at least [7] days in advance.
3.2 Employees must record the start and end of every shift themselves using [attendance app or method]. This is the official attendance record.
3.3 Employees must not record time for anyone else, or ask anyone to record time for them.
3.4 Unpaid breaks are [scheduled as part of each shift / recorded by the employee]. Paid breaks are: [details or "none"].

4. PUNCTUALITY
4.1 Employees should be ready to work at the scheduled start time.
4.2 Recording the start of work more than [5] minutes after the scheduled start counts as late. Recording the end of work more than [5] minutes before the scheduled end counts as leaving early.
4.3 An employee who expects to be late must tell [manager / named contact] by [phone call / message in the attendance app] before the shift starts.

5. ABSENCE REPORTING
5.1 An employee who cannot attend a scheduled shift must tell [named contact] by [channel] at least [2] hours before the shift starts, or as soon as possible in an emergency.
5.2 The employee should say when they expect to return and keep their manager updated if that changes.
5.3 Evidence for sickness absence may be requested after [number] days, in line with applicable law.

6. NO-SHOWS
6.1 A no-show is missing a scheduled shift without notifying [named contact] before it starts.
6.2 After a no-show, the manager will try to contact the employee the same day and will meet the employee on their return to understand what happened.
6.3 Repeated no-shows are handled under section 12 and applicable law.

7. CORRECTIONS TO ATTENDANCE RECORDS
7.1 If a start or end of work was missed or recorded incorrectly, the employee must request a correction in [attendance app or method] within [2] working days, giving the correct time and the reason.
7.2 A manager reviews and approves or declines the correction. The original record is kept alongside the correction.
7.3 Managers must not change attendance records without a documented reason.

8. SCHEDULE CHANGES AND SWAPS
8.1 Any change to a published schedule, including a swap between employees, must be approved by [manager role] and updated in [attendance app or method] before the shift.
8.2 [Company Name] will give as much notice of schedule changes as operations allow, and at least [number] hours where possible.

9. OVERTIME
9.1 Overtime must be approved by [manager role] [in advance, except in emergencies].
9.2 Employees request overtime in [attendance app or method], stating the date, the hours and the reason.
9.3 All time worked is recorded accurately. Overtime is paid or compensated in line with the employee's contract and applicable law.
9.4 No one may approve their own overtime.

10. LEAVE
10.1 Planned leave is requested in [attendance app or method] at least [14] days in advance, where possible.
10.2 Leave is approved by [manager role] based on the employee's entitlement and team cover. Approved leave is not counted as absence.

11. ATTENDANCE DATA AND PRIVACY
11.1 [Company Name] records the times employees start and end work, and [location / workplace network / registered device] checks made at those moments only, to confirm attendance at the workplace.
11.2 We do not track employees' location during breaks, outside working hours or on days off.
11.3 Attendance data is used only for scheduling, attendance, payroll and related HR purposes, is accessible to [roles], and is kept for [period], in line with applicable law.
11.4 Questions about attendance data can be sent to [contact].

12. REPEATED ATTENDANCE ISSUES
12.1 Repeated unreported lateness, early leaving or absence will first be discussed informally with the employee to understand the cause.
12.2 If the pattern continues, [Company Name] may follow its [disciplinary or performance procedure], applied consistently and in line with applicable law.
12.3 Absences protected by law or approved in advance are not treated as attendance issues.

13. RESPONSIBILITIES
13.1 Employees: follow this policy, record their own time accurately and report absences promptly.
13.2 Managers: publish schedules on time, apply this policy consistently, review requests promptly and never approve their own requests.

14. REVIEW
This policy will be reviewed by [date] and at least once a year.

ACKNOWLEDGEMENT
I have received and read the [Company Name] Employee Attendance Policy.
Employee name: ______________________  Signature: ______________________  Date: __________

Common attendance policy mistakes

Most attendance policies fail for the same few reasons. Check yours against this list before you share it.

  • Copying a template without checking local law, especially on sick leave, notice periods and dismissal.
  • Zero-tolerance rules that treat a single transport delay the same as a pattern of unreported lateness.
  • Rules for employees with no matching duties for managers.
  • No correction process, so mistakes are fixed informally or not at all.
  • Two time-recording methods running in parallel with no rule about which one is official.
  • Using location checks without telling employees what is collected and when.
  • Writing the policy once and never reviewing it.

How SlidesClock helps you apply an attendance policy consistently

A policy is only as consistent as the way it is applied. SlidesClock puts the rules your policy describes into the daily workflow, so the same rule is applied every time.

Employees Slide In and Slide Out on their own phone, with the time taken from the server. Each workplace can check GPS position, the workplace network or a registered device at that moment only, which lets your privacy clause be literally true. Work schedules hold the start and end times, grace periods, rest days and unpaid breaks your policy defines, so lateness and early leaving are measured the same way for everyone. Reminders are planned from the roster.

Leave requests and overtime requests are filed and decided in the app, and a reviewer cannot decide their own request. Attendance corrections keep the original record beside the change and are available on Premium; reports and exports start on Standard. The free plan covers up to 5 employees at one location, which is enough to run your new policy with a real team. Start tracking attendance with SlidesClock, or compare plans on the pricing page. If you are setting up a small team, our guide to attendance tracking for small teams walks through the first week.

Frequently Asked Questions

What should an employee attendance policy include?

Working hours and schedules, how time is recorded, what counts as late or absent, how to report absences, no-shows, corrections, schedule changes, overtime and leave approval, manager and employee responsibilities, attendance data and privacy, and how repeated issues are handled.

How do you write an attendance policy for a small business?

List the situations you face, check local legal minimums, decide your rules and numbers, choose one official way to record time, write plainly, test the draft with a few employees, share it with an acknowledgement, and review it after three months.

What is a reasonable grace period for lateness?

Many businesses use about 5 to 10 minutes, and roles that cannot be left uncovered may use none. The right value depends on the role; what matters most is that it is written down and applied to everyone on the same shift.

What is a no-call no-show?

Missing a scheduled shift without notifying the employer beforehand. A policy should define it, set out the follow-up, and avoid automatic consequences that may not be lawful where you operate.

Can an attendance policy require GPS check-ins?

In many places it can, if employees are told what is collected, when and why, and if data protection rules are followed. Checking location only at clock-in and clock-out, rather than tracking all day, is easier to justify and to explain.

Is this attendance policy template legally binding?

No template is legal advice. Adapt it to the employment and data protection laws where your employees work, and have it reviewed by a qualified professional where possible before you use it.

Keep going on slidesclock.com

Related reading

More practical guides on attendance & verification

Start Work. Just Slide.

Start free for up to 5 employees at 1 branch. Upgrade when your team grows.