# Remote Team Attendance Checklist

Provided free by Tickin (tickin.pro).

Use this checklist to run attendance for a remote or distributed team across timezones, async schedules, and clear expectations. Work through each group with your team, then save your answers as a written policy.

## Set clear expectations

- [ ] Agree the expected working hours for each person or role in writing
- [ ] State whether hours are fixed, flexible, or fully async so nobody guesses
- [ ] Define core overlap hours when everyone must be reachable
- [ ] List which days count as working days for each region
- [ ] Share where attendance rules live and make sure everyone can find them

## Handle timezones

- [ ] Pick one reference timezone for reporting and cut-offs
- [ ] Record each person's local timezone next to their schedule
- [ ] Convert start and end times to local time so nobody works the wrong window
- [ ] Set a daily cut-off that is fair for people in later timezones
- [ ] Flag holidays and observances that differ by country

## Choose how people clock in

- [ ] Decide the clock-in method: a chat command, a browser page, or a mobile check-in
- [ ] Make sure the method works from any device and any network
- [ ] Define a grace window for a few late minutes before it counts as late
- [ ] Agree how breaks and lunch are logged, if at all
- [ ] Write down what to do when someone forgets to clock in or out

## Keep it fair

- [ ] Document the full attendance policy and share it with the whole team
- [ ] Apply the same rules to every timezone and seniority level
- [ ] Give people a clear, low-friction way to log leave and corrections
- [ ] Review attendance data on a regular schedule, not only when there is a problem
- [ ] Ask the team for feedback and update the policy when it stops fitting