Blog · Blog

← All posts

Remote Team Attendance Policy Template You Can Copy

5 Nov 2026 · 9 min read · Blog

Remote team attendance policy template: hours, lateness, leave and tracking rules

A developer opens her payslip and finds it two hours short. Her manager fixed a forgotten clock-in by editing the record from memory, and he guessed wrong. She disputes it. He cannot prove his version, and the team now doubts every edited record.

This is an illustrative case, but the cause is common: the policy had no correction workflow. Write the rules first, then add a correction workflow so nobody edits history informally. This remote team attendance policy template does both.

It keeps attendance, hours worked, availability and performance separate, and it tells staff exactly what is tracked. It also shows tracked hours moving into leave, payroll and invoices without becoming a performance score.

The Remote Team Attendance Policy Template

Copy the block below into your handbook. Fill in the [brackets]. Pick one working-hours model and delete the other two.

1. Purpose and scope. This policy covers all [employees and contractors] of [Company] who work remotely. It explains how we record time, handle lateness and leave, and protect your data.

2. Definitions. Present means scheduled, working and reachable in agreed hours. Hours recorded means time captured by the tracker. Performance is judged on outcomes only, such as finished work, quality and deadlines.

3. Working hours (choose one).
Model A, fixed schedule. Work [start time] to [end time], [days].
Model B, core hours plus flex. Be reachable during core hours, [core window] in [named time zone]. Work the rest of your [daily hours] when you choose.
Model C, asynchronous global work. There are no shared hours. Meet agreed deadlines, reply within [reply window], and join [number] meetings a week.

4. Breaks. Take [break length] minutes a day, [fixed at time / flexible]. Pause the timer for longer breaks.

5. Lateness. You are late if you start after [start time] plus [grace minutes] minutes. Tell [manager] before your start if you expect to be late.

6. Missing time. Request missing time within [number] working days and before the payroll cutoff. Give a reason. [Approver] approves or declines.

7. Leave notice. Ask [notice days] days ahead, except in emergencies.

8. What is tracked and who sees it. See the disclosure in the section below.

Fields to fill in

  • Start time and grace minutes
  • Break length
  • Core hours window and its named time zone
  • Notice days for leave
  • Idle pause setting, from 3 to 15 minutes

Attendance in plain words

Attendance asks one question. Was the person scheduled, working and reachable in agreed hours? Hours recorded is a different question: how much time did the tracker capture? Availability is about being reachable, and performance needs outcomes. Mixing these four is how managers end up misusing activity data.

Set Hours, Time Zones and Leave Rules

Remote teams often break policies at the clock. A team in Karachi and a team in Berlin share neither a start time nor a holiday calendar. Say so in the policy.

Add these clauses:

  • Home time zone. Each person's home time zone is listed in their record.
  • Core hours. Shared core hours are written in one named zone, such as [Company reporting zone].
  • Overnight shifts. A shift belongs to the day it starts.
  • Daylight saving. Core hours stay fixed in the named zone. Local start times may move by an hour.

Here is one worked case. A developer in Karachi works for a Berlin client. The policy sets core hours at 10:00 to 16:00 in Europe/Berlin, with a 10-minute grace period. In winter that window is 14:00 to 20:00 in Karachi. She starts at 14:09 and gets no mark. A start at 14:12 is a late mark.

Pakistan does not change its clocks, but Germany does. In summer the same core window opens at 13:00 in Karachi. Her local start moves by an hour, and the rule stays the same. On 3 October, German Unity Day, the client is closed.

She still works, because holidays follow her own country. Her manager waives core hours for that day in advance, so no late mark can happen. On a Pakistani public holiday she is off, and no absence mark applies.

Choose the grace period to match how your people actually start work. Five minutes suits staff who only need to open one app. Ten minutes suits most teams, because a laptop update, a slow VPN or a power cut can cost a few minutes without anyone being careless.

Fifteen minutes suits teams on unreliable connections, but it starts to feel like a free quarter hour. This template uses 10. Count from the scheduled start in the named zone, not from when the laptop wakes. Grace starts fresh each day and never adds up.

A start at 9 minutes is never a mark, and a start at 11 minutes always is.

The first and second late marks in a month need no action. At the third, the manager has a private talk and checks whether the schedule still fits the person. One slip is chance. Two can be a bad week. Three in a month is a pattern worth a conversation. A team with tight client hours can set the trigger at two, but write the number down either way.

If you want a ready wording for pay effects, start from a late coming policy template. Breaks are either fixed or flexible. Pick one and write it down.

Leave rules need four answers. How far ahead must staff ask? Who approves? How many free leave days do staff get each month? Are half days and short leave allowed? Days beyond the free allowance are unpaid, and you can work out the unpaid leave deduction per day from monthly pay.

Public holidays follow each person's country, not the head office. Use your government's official holiday calendar and labour ministry for legal minimums. Protected leave, such as sick or parental leave, must never trigger a late or absence mark.

For staff in Pakistan, check this policy against three sets of rules before you publish it. The first is your province's Shops and Establishments law, such as the Punjab or Sindh versions, or the Islamabad Capital Territory ordinance.

These can set limits on daily hours, overtime, rest breaks and annual leave. The second is the Payment of Wages Act, 1936, together with the applicable Standing Orders. These affect any deduction you attach to lateness or unpaid leave. The third is data protection.

Pakistan has had a draft personal data protection bill, so check its current status with a lawyer before you rely on staff consent alone. Employers elsewhere should check the equivalent rules in their own country.

What Is Tracked and Who Sees It?

Staff should be able to read this section in two minutes. Fill in each line, and never track anything it does not list.

  • Working hours. Recorded while the timer runs. Visible to the employee, their manager and payroll admins.
  • Idle time. The timer pauses after [3 to 15] minutes with no keyboard or mouse. The admin sets the number, and the policy states it. Our note on the employee idle time policy explains how to treat that time.
  • Screenshots. Off by default. Taken only if an admin switches them on, and staff are told first. State the business reason.
  • Retention. Records are kept for [period], then deleted.
  • Employee access. Every employee can view their own records and request a correction.

Idle time and screenshots never decide absence or performance alone. A manager must ask the employee first, and then judge outcomes. A person reading a document or on a call can look idle.

The reason to be this open is trust, and disputes are where its absence shows. A Gallup survey of US employees who work on computers found that only one in five had a great deal of trust in their employer to use employee data responsibly.

The same survey found that just 19% said someone at work had talked with them about the data collected. Those figures are American, so read them as a signal and not as a Pakistani benchmark. Check Gallup's published report for the exact wording and year.

The lesson for any remote team is simple. Staff who are never told what is collected fill the gap with guesses, and guesses turn into disputes.

A plain disclosure line settles those disputes before they start. Take this one: "Screenshots are on for the support team from [date]. They are taken only while the timer runs. Your manager and admins can see them." When an agent asks why a screenshot exists, the manager points to that line and the talk stays short.

Fix Missing Time Without Arguments

Forgotten starts, wrong time zones and missed breaks will happen. Decide the fix now, so it is a routine step and not a dispute.

  1. The employee requests the missing time and says what went wrong.
  2. The named approver approves or declines, usually within [number] working days.
  3. The request must arrive before the payroll cutoff.
  4. Every change is logged with who, when and why.

Nobody edits history informally. If a record is wrong, a request is the only route. Keep the log in a simple format like this sample. The names and dates are made up, so replace them with your own.

Date worked: 12 March
Requested minutes: 40
Reason: Forgot to start the timer after standup
Requested by: A. Khan, 12 March, 15:10
Decision: Approved
Approver: S. Malik, 13 March, 09:45
Payroll cutoff met: Yes

Approved hours should then move through one login. They feed attendance, leave balances, payroll payslips and client invoices, so nobody rebuilds a timesheet on Friday. For agencies and software houses, billable hours support the invoice. They are not a utilization score for discipline.

Clockade is one way to run this flow, with Mac and Windows apps and a Chrome extension. Staff send missing-time requests and admins approve them. The Team plan is $3 per person a month and the Business plan is $6, so cost follows headcount. Start with Clockade.

There are limits. Tracking suits computer-based work, and field or mobile teams need a GPS-first attendance tool. Whatever you use, keep attendance, hours recorded, availability and performance as four separate questions.

Add one rule to the policy and enforce it: idle minutes are never turned into a performance score or a pay deduction. A developer on a client call or reading a spec can show little keyboard activity and still be doing the job. Activity data shows context. Outcomes show performance.

Frequently Asked Questions

How do you define attendance when people work from home on flexible hours?

Attendance means the person was scheduled, working and reachable in the agreed hours. On flexible models, those agreed hours are the core window. Hours recorded are tracked separately.

Should remote staff clock in and out, or are core hours and availability enough?

It depends on how you pay. If you pay by hours or invoice clients by hours, staff should track time. If you pay a fixed salary for outcomes, core hours and availability may be enough.

What should an employee do if they forget to start the tracker?

Request the missing time before the payroll cutoff and give a reason. The named approver approves or declines it. The change is logged.

Can idle time or screenshots decide whether someone was absent?

No. Idle time and screenshots are context, not proof. A manager should ask the employee first and judge outcomes.

How should the policy handle different countries, time zones and public holidays?

Record each person's home time zone and country. Write core hours in one named zone, and apply public holidays by the employee's country. Check legal minimums with official government sources and a local legal review.

Track real hours, not guesses.

Clockade turns your team's tracked time into attendance, leave, payroll and invoices. From $3 per person a month.

Start with ClockadeSee pricing

More from the blog