A fair way to track remote work hours

Here is the tension every leader of a remote or hybrid team runs into. You need some honest visibility: are people reachable during the hours you cover, is the team staffed when a customer calls, can you answer a coverage question with something better than a hunch. At the same time, almost nobody wants to install spyware on their colleagues, and almost nobody wants to work somewhere that does. The fear of being seen as Big Brother is real and well founded, because the heavy-handed tools on the market really do break trust.

So the question is not "monitor or do not." It is how to get the visibility you genuinely need in a way that is fair. This post is our answer, because building Presify forced us to think hard about where the line is.

What "fair" actually looks like

Fairness is not a vibe. It comes down to a short set of principles you can hold yourself to.

• Be transparent. Tell people. The biggest difference between fair monitoring and creepy monitoring is whether the team knows it is happening. If you would be uncomfortable saying out loud what you keep, that is the signal.
• Collect the minimum. Capture the least that answers your actual question. To know whether the team is reachable during coverage hours, you do not need screen recordings, keystrokes, or a per-minute activity feed. More data is not more insight, it is more liability.
• Measure reachability, not keystrokes. Decide what you are trying to know. For most teams it is coverage and availability, not "is this person typing right now," and the second question is both harder to answer honestly and easier to game.
• Treat the data as a starting point, not a verdict. Any signal tells you what happened, not why. The moment monitoring becomes a gotcha, you have lost the team.
• Give any legally required notice. Depending on where your people work, you may have specific notice or consent obligations. Plan for that up front.

That last point deserves a flag: this post is general information, not legal advice. Notice and consent rules vary by jurisdiction and change over time, and they can turn on facts specific to your organization. We go deeper on the US picture in is it legal to track employee Teams status, but for your situation, confirm with your own counsel.

Why heavy monitoring is the wrong tool for most teams

Screenshot capture, keystroke logging, and "productivity scores" promise certainty. In practice they deliver three problems.

First, they measure the wrong thing. A keystroke or mouse-movement score rewards activity-theater: the person who jiggles the mouse and keeps a doc open scores well, while the person who thinks for twenty minutes before writing three good sentences scores badly. You end up optimizing for looking busy, which trains your team to perform for the meter.

Second, they erode trust, and trust is most of what makes a remote team work. The day someone discovers their screen is being photographed is the day they stop believing the relationship runs on good faith. That cost shows up in retention and in how candidly people talk to you, not on a dashboard.

Third, the more intrusive the method, the more obligations tend to come with it. Recording screen content or capturing keystrokes is a different category from reading a status your platform already computes, and the rules that attach to it are heavier. The intrusive tool is the one most likely to create a notice or consent problem for you.

None of this means the vendors are villains. There are narrow, regulated situations where intensive monitoring is genuinely required. But for an ordinary team that just wants to know it is reachable and covered, that machinery is the wrong size for the problem, and its costs dwarf what it buys.

Where presence history fits

There is a much lighter signal that answers the reachability question without surveilling the work itself: Microsoft Teams presence, kept over time. Teams already computes a presence state for each person, the colored dot that reads as available, away, busy, or offline. What it does not do is remember: the dot shows you now, and only now. Presence history is that same state recorded as it changes, so you can look back and see when the team was reachable across a week or a month instead of guessing.

The narrowness is the point. Presence history is read-only: no agent on anyone's machine, no screenshots, no keystroke logging, ever. It tells you when someone was reachable in Teams, a coverage and availability signal. It is not a productivity score and cannot tell you what someone was doing or how well. It answers "was the team reachable," not "was this person working hard." That fits the fair principles cleanly: the lightest signal that answers a real question, easy to disclose, pointing you toward a conversation rather than a verdict.

A short checklist for doing it fairly

If you want a defensible, low-drama approach, this is the whole thing:

1. Decide the one question you need answered. For most teams it is coverage and reachability.
2. Tell your team, in plain language, what you keep and why, in a written policy.
3. Collect the minimum that answers it. Skip screen and keystroke capture unless you have a specific reason.
4. Keep it only as long as you need it.
5. Use it as context for a conversation, never as a silent scorecard.
6. Confirm any notice or consent obligations for the places your people work, with your own counsel.

Follow those six and you land in the same defensible posture most thoughtful organizations do, without the trust cost of the heavy tools.

How Presify is built for exactly this

We built Presify to be the fair option, so the principles above are wired into the product, not left to your good intentions.

• Read-only and minimal. Presify reads presence (available, away, busy, offline) through the Microsoft Graph presence API on a short, regular interval, plus the basic directory fields it needs to label and scope users. It never touches message content, chats, calls, files, or calendars.
• No agent, no screenshots, no keystrokes. Setup is a one-time, read-only Microsoft admin consent. There is nothing to install on anyone's device, and no screen capture or keystroke logging in the product, ever.
• Reachability, not a productivity score. Presify stores each presence change and builds timelines, online-time trends, and anomaly flags. The anomaly flags always show the math behind them, so a flag is something you can read and question, not a black-box judgment.
• Bounded retention, US-based, tenant-isolated. Your data is scoped to your Microsoft tenant and processed on US infrastructure. History is trimmed automatically by your plan, and per-user and workspace-wide deletion are built in. Guest users are excluded, and we do not monitor users in the EEA, the UK, Switzerland, or Canada. More detail lives on the security page.
• Evidence for a conversation. Presence history describes what someone's status showed, not why. We treat it as a starting point, not a verdict, and we recommend telling your team that presence is being kept.

If reachability and coverage are what you want to answer fairly, that is the whole job Presify is built to do. Read the broader case on Presify for remote and hybrid teams, see how Presify works, or start with one Microsoft sign-in.

This article is general information, not legal advice. It does not address your specific circumstances, and laws differ by jurisdiction and change over time. Consult your own attorney before acting on it.