How to track team availability across time zones

You run people across regions, and the same questions keep surfacing. Who in APAC was actually online yesterday afternoon, their time or yours? Did anyone overlap with the EMEA handoff on Thursday, or did it slip because the two people were never online together? These are pattern questions about time and place: who was online in each region during its own working hours, for how long, and where the regions actually overlap.

Microsoft Teams looks like it should answer this. Every name carries a colored dot. But the dot shows one moment in one place, and across regions it tells you even less.

A teammate who always looks gray from headquarters may be putting in solid hours on their own clock. Someone who is always green at your 4pm may be barely around (a mouse jiggler keeps Teams green). Only the history, read in each person’s local time, shows the pattern behind each.

The answer is to track availability per time zone, openly, from the presence history. The sections below cover why a live dot falls short across regions, what "online during their hours" means, and how to read the record.

One framing first, because it shapes everything below. Presence shows when someone was online in Teams, not what work they did or how hard they worked. Across time zones, read presence as a directional view of when each person and each region is online, and how much. It is a starting point for a conversation, not the whole story.

Why can't a live green dot answer a time-zone question?

A live green dot can't answer it because the dot only tells you whether this person is available in Teams right now, in your current moment. That breaks down across regions for three reasons that compound.

• It is live only. There is no built-in way to ask what the EMEA team looked like at 3pm London time last Tuesday, or whether anyone in APAC was online during their own morning.
• It is one person at a time. You check dots one by one and rebuild the regional picture in your head. Across three or four zones that is guesswork, and it is gone the moment you look away.
• It is anchored to your clock, not theirs. This is the one that quietly defeats a cross-region read. You read a teammate’s dot against your own working hours. Gray at what reads to you as mid-afternoon might be normal evening for them, or a real gap in their morning. A single dot cannot tell those apart, because it does not know whose business hours you are asking about.

So the dot answers "can I reach Mara now." It does not answer "who in Singapore was online during Singapore business hours this week, and for how long," or "when do my New York and Berlin people actually overlap." Those are pattern questions about specific people and regions over time, and a snapshot, read against the wrong clock, cannot answer them.

What "online during their hours" means across regions

Two ideas do most of the work here.

Per-region business hours. "Online during their hours" only means something relative to the hours a region is meant to work.

Say your EMEA group works roughly 9 to 5 Central European Time. The question is whether someone was online inside that window, in that zone, not whether they happened to be online when it suited headquarters. Online time has to be read in each person’s local time, or you are measuring the wrong window.

Overlap windows. The other half is the seam between regions: the stretch where two zones are both inside business hours at the same wall-clock moment. That overlap is where live handoffs and quick syncs happen. If two regions never overlap, every handoff is asynchronous by force, and you want to know that on purpose, not discover it when something slips.

Put those together and a fuzzy worry ("is anyone actually on in APAC?") becomes a pair of answerable questions. Who was online in each region during its own business hours, and for how long? Where do the regions overlap? Here is the shape of it, one region per row, read in each region’s local time:

Read across a row and you can see whether a region held its own window and where it touches the rest of the team. That is the view the green dot cannot assemble, because it has no memory and no notion of whose clock to use. For the broader version of this question on a single team (when are my people actually online, and how much), see how to know when your remote team is available.

How do you read availability per time zone?

You read it from stored presence history, judged against each person’s own local business hours. There is no setting in Teams that hands you presence history, let alone history sorted by region and read in local time. To answer this across zones, something has to do three things together.

Capture and store each change. A collector reads the Teams presence state on a short, regular schedule and records each change it sees between available, away, busy, and offline. That stored stream is what lets you look back at a week or a month instead of squinting at a live dot.

Judge each person in their own time zone. Local time is the step that makes a cross-region read honest. The same presence stream has to be read against each person’s local business hours, not a single company clock. "Online at 10am" should mean 10am where they are.

Get local time wrong and someone working their full day looks like a gap, because you read it against headquarters’ afternoon. Microsoft already keeps each person’s Outlook time zone and working hours, so the local clock is there to read.

Overlay business hours, per user, in local time. With presence stored and anchored to each person’s zone, a business-hours overlay turns the timeline into an answer. You see when each person was online inside their own working window, for how long, and where regions line up at the overlap seam. "Was someone available in every region during business hours" stops being a hunch and becomes a number.

Done this way, the record answers at two levels. Per person, you see when each teammate is online in their own hours, and how much. Across the team, you see the structure: a window that leans on one person, two regions that never meet, an after-hours stretch where nobody is online.

What good looks like for a leader running regions

Once presence is captured and read in local time, the view a distributed-team leader needs is a few specific things:

• Per-person timelines in local time, with a business-hours overlay. Each person’s available, away, busy, and offline strip, drawn against their working window, so "they were online" becomes "they were online during their own working hours," region by region.
• Online-time totals and trends per person and per team. How much each person is online and how that is trending over weeks, rolled up per team, so a window quietly thinning out shows up before a handoff breaks.
• Flags for presence that looks gamed, each showing how it’s calculated. Automatic checks for patterns like hours of unbroken Available or no idle time at all, the kind a mouse jiggler tends to leave, with the calculation visible. A flag is a pattern worth a look, not proof of anything.

The payoff runs both ways. You can see that the APAC evening is thin, that EMEA and the West Coast barely overlap, or that on-call across zones leans on one tired person. Each of those is a schedule you can fix.

The record also corrects the glance, person by person. The teammate who always looked gray from headquarters may turn out to keep a full day on their own clock. The one who was always green at your 4pm may turn out to be rarely around.

Doing this responsibly across regions

Keeping presence history is reasonable. Doing it quietly is the fast way to lose a distributed team, and spreading people across borders only widens the obligations. A few principles:

• Tell your team that presence is kept, in plain language, ideally in a written policy every region can read. Notice laws are a separate check: some places have them, such as Connecticut's prior written notice rule for electronic monitoring, so ask counsel which ones cover your people.
• Start with the window. For a time-zone question, look at the region and the hours first. Presence shows when someone was online, not what they did, so a thin window is a staffing question to raise, not a conclusion about a person.
• Collect the minimum: presence and basic directory fields, nothing more, kept only as long as you need it.
• Mind where people sit. Notice and consent rules differ by jurisdiction and change over time, and some regions you simply should not enroll. Confirm your specifics with your own counsel; this post is general information, not legal advice.

How Presify fits

Presify is a Microsoft Teams presence tracker: it keeps the history of who was online, when, and for how long. Reading that history across time zones is one of the things it is built for. It samples Teams presence (available, away, busy, offline) through the Microsoft Graph presence API on a short, regular interval and stores each change. From that it builds presence timelines, online-time totals and trends, and flags for presence that looks gamed, per person and per team.

For distributed teams, Presify carries a per-user time zone and draws a business-hours band in each person’s local time. "Who was online in each region during its own hours" becomes something you can read, not guess.

The per-user time zone and business-hours band are on every plan. How much history is kept and which flags are included depend on your plan, and the team overlap view is on Pro plans and above.

What we are deliberate about:

• Local time, not a single company clock. Each person’s presence is read in their own time zone, with a business-hours overlay per user. Someone working their full day never reads as a gap just because you are looking from headquarters.
• Five-minute setup, nothing installed. One read-only Microsoft 365 admin sign-in, about five minutes. Nothing is installed on anyone’s device, and there are no screenshots and no keystroke logging, ever.
• 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.
• Tenant-isolated, US-based, scoped responsibly. Your data stays scoped to your Microsoft tenant on US infrastructure, with bounded retention and per-user and workspace-wide deletion. Guest accounts are never tracked, and Presify does not enroll users whose Microsoft 365 location is in the EEA, the UK, Switzerland, or Canada. Every flag shows how it’s calculated, so you can check a pattern before you draw a conclusion.

For a team spread across time zones, the page for Presify for remote and hybrid teams walks through the use cases. It covers who is online, when, and for how long, read in each person’s local time. When you are ready, see how Presify works or start with one Microsoft sign-in. Setup takes about five minutes.