Hybrid team coverage: a record of who's online, not a hunch
Ask most hybrid managers whether their team held coverage last Tuesday afternoon and you get a version of the same answer: "I think so." "Pretty sure people were around." "Nobody flagged a gap, so probably." That is not a measurement. It is a hunch dressed up as one, and it is what a surprising number of staffing decisions actually run on.
The hunch is understandable. In an office you absorbed coverage passively: empty desks, the room going quiet at 3pm, the feel of the team thinning out. Hybrid took that ambient signal away and replaced it with nothing. So you reconstruct coverage from memory and a few Teams dots and call the result a sense of the team. It is better than blind, but it is still a guess, and guesses are a poor basis for telling someone the late window is uncovered or deciding whether you need another hire.
This post is about replacing that guess with a record: Teams presence tracked over time, so you can see who was online, when, and for how long, and read coverage off the pattern instead of a glance. The glance is worse than it looks, because the green dot shows one moment, not the whole story. Someone can sit green all afternoon and barely be around, and the person who always looks yellow may be the one quietly holding the late window.
One boundary before the how-to. A presence record tells you when people showed as online in Microsoft Teams, and for how long. It does not tell you how hard anyone worked or what they produced, because presence isn't productivity. It is a directional read, and a starting point for a conversation about how the team is set up, not a judgment on a person.
What "coverage" actually means for a hybrid team
Coverage is not "is everyone online all day." It is narrower and more useful: during the hours you have committed to cover, is someone online to handle what lands?
That definition has three moving parts worth naming:
- The window. The hours that matter to you. Often core hours, a support window, an on-call shift, or the overlap where two regions can actually hand off.
- The threshold. How many people need to be online in that window for it to count as covered. Sometimes one. Sometimes two for redundancy. Rarely everyone.
- The reality. Who was actually online, when, and for how long across that window, over the days and weeks you care about.
Guesswork fails on the third part. You can usually state your window and threshold from memory. What you cannot reconstruct from memory is the reality: who was actually online across the Thursday late window for the last month. That is a pattern question, and memory stores impressions, not patterns. The value of a presence record is that it remembers the reality so you do not have to.
Why the green dot won't give you the number
Microsoft Teams looks like it should answer this. Every name carries a colored dot. But the dot is built for one moment, and coverage is a question about time.
The dot tells you one person's status right now. It is live only, so there is no way to ask what the team looked like last Tuesday at 4pm. It scrolls away, so even watching it gives you one frame and no record. And it is one person at a time, so you cannot see the whole team across a window at once. You end up checking dots one by one and rebuilding the picture in your head, which is exactly the guesswork you are trying to escape.
So the dot answers "can I reach Sam now," not "did we hold the late window every day this month." For the deeper version of this gap, including what each state means and where the dots stop being reliable, we wrote a full leader's guide: how to know when your remote team is available.
From guess to number: the presence record
A presence record is what you get when something samples each person's Teams status on a short, regular interval and stores each change it sees, so presence becomes a timeline instead of a dot. Once you have that, the fuzzy hunch resolves into a few concrete things a manager can read:
| Guesswork question | What the record gives you |
|---|---|
| "Were people around Tuesday afternoon?" | A per-person presence timeline for that window |
| "Is the late window actually covered?" | Online time rolled up per team across the window |
| "Is anyone's green dot too good to be true?" | A flag, with its math shown, for presence that looks gamed, such as Available for hours with no break |
| "When do my two regions overlap?" | A coverage view showing where regions are online together |
The shift is from impression to record. Instead of "I think the team held coverage," you have a timeline and an online-time number that either show the window was held or show exactly where it thinned. And it cuts both ways: the same record that surfaces a thin window also shows who has been quietly holding it, credit a glance at the dot never gives. Either way, it is a starting point for a conversation, not a conclusion about anyone.
Track it in the open
Here is where this earns or loses your team's trust. A presence record is a form of accountability, and it works best in the open.
The fair version is a transparent, two-way record. You tell your team, in plain language, that presence is tracked and what it is used for. The same record holds you accountable too: if it shows on-call leaning on one person, that is your scheduling problem to fix, not their failing. A flag is a prompt to ask, not a conclusion to act on. Done this way, the record is something everyone can see, including the people it describes.
The version that backfires is the quiet one: collecting the same data without telling anyone, then producing it as a gotcha. That is the fast way to lose a hybrid team, and depending on where your people work, it can also skip a notice the law requires. Same data; the difference is whether people were told.
So the rule we keep coming back to: tell your team presence is tracked. If you would be uncomfortable saying out loud what you record, that discomfort is the signal, not the workaround. We go deep on the principles, the minimum-collection rule, and the legal notice side in a fair way to track remote work hours. That piece is general information, not legal advice, and your own counsel should confirm your specifics.
The light way to put a number on coverage
Most monitoring software installs an agent on every laptop and records screens and apps, and some log keystrokes. You do not need any of that to answer a coverage question, and none of it would tell you whether the late window held. The lightest signal that answers the question is presence over time: Teams already computes a status for each person, so a presence tracker just samples that status on a regular interval and records the changes.
A defensible, low-drama approach is short:
- State the window you need covered, and the threshold for "covered."
- Tell your team, in plain language and ideally in writing, that presence is tracked and why.
- Collect the minimum: presence and basic directory fields. No screen capture, no keystrokes.
- Keep it only as long as you need it.
- Read the record as a starting point for a conversation, never as a silent scorecard.
- Confirm any notice or consent obligations for where your people work, with your own counsel.
Follow those and the coverage question stops being a hunch and becomes a number you can defend, without rolling out software to every laptop.
How Presify keeps the record
Presify is a Microsoft Teams presence tracker, and coverage is one view on the record it keeps. It reads Teams presence (Available, Away, Busy, Offline) through the Microsoft Graph presence API on a short, regular schedule, stores each change, and builds presence timelines, online-time trends, and anomaly flags, per person and rolled up per team. The output is a record a manager can share with the team openly: who was online, when, and for how long, and whether the team held coverage during the hours that matter.
What we are deliberate about:
- Read-only and minimal. Presify reads presence plus the basic directory fields it needs to label and scope users. It never touches message content, chats, calls, files, or calendars.
- About five minutes, nothing installed. Setup is one read-only Microsoft sign-in by an admin. Nothing is installed on anyone's device, and there is no screen capture or keystroke logging in the product, ever.
- Directional, not a productivity score. Six anomaly flags surface presence that looks gamed, like a status that stays Available for hours with no break, and each one shows its math, so a flag is something you can read and question, not a black-box judgment. We recommend telling your team that presence is tracked.
- Bounded retention, US-based, tenant-isolated. Your data is scoped to your Microsoft tenant and processed on US infrastructure, with retention trimmed automatically by your plan and per-user and workspace-wide deletion built in. Guests are excluded, and Presify automatically excludes people whose Microsoft directory location is in the EEA, the UK, Switzerland, or Canada.
If your answer to "who's online, and when?" is still "I think people are around," Presify replaces the hunch with the record: who's online, when, and for how long, with flags for presence that looks gamed and a coverage view on top. The page for Presify for remote and hybrid teams walks through the use cases. When you are ready, see how Presify tracks Teams presence or start with one Microsoft sign-in. Setup takes about five minutes, and nothing gets installed.
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.