Attendance for Remote and Field Teams: A Practical Policy

When people don't sit in the office, attendance changes from "were you here?" to "were you working, and what got done?"

#Allow remote check-in

In **Work › Organisation › Settings**, switch on **Allow remote check-in** and save. Staff can check in from anywhere; the time is recorded as usual.

If only some staff are remote, consider separate organisations or clear rules on who may check in remotely.

#Pair check-ins with outcomes

Attendance alone says little about remote work. Add: - A **daily stand-up** message in the team chat: yesterday, today, blockers. - **Weekly report packs** with the numbers that matter — calls made, visits completed, tickets closed. See [weekly reporting templates](/blog/weekly-reporting-template-teams).

#Field staff

- Add **customer sites or branches** as geofences if visits must be verified. - Use chat to share photos of completed work. - Use **approvals** for travel expenses with receipts attached.

#Respect privacy

- Check location **at check-in**, not all day. - Be transparent about what's recorded. - Don't require cameras on all day — it hurts trust and bandwidth.

#A sample policy

1. Check in by 09:15 (remote check-in allowed). 2. Post your daily plan in the team chat by 09:30. 3. Be reachable during core hours (11:00–16:00). 4. Submit the weekly report by Friday 17:00. 5. Check out at the end of the day.

#Frequently asked questions

How do I track attendance for work-from-home employees?

Allow remote check-in and pair it with daily updates and weekly reports that show outcomes.

Can field staff check in at customer sites?

Yes. Add customer sites as office locations with a radius, or allow remote check-in.

Is tracking location all day necessary?

No. Checking location at check-in plus outcome reporting is usually enough and respects privacy.