Employee monitoring for distributed teams
A focused guide to transparent visibility, proof of work and workforce analytics.
Operations across a gap with no overlap
One exchange costs a day. Four exchanges cost four days.
Fifty notes for teams whose halves are never awake at the same time. Not a guide to remote work, which assumes an overlapping hour and designs for it. A working account of the harder case: a gap with nothing in it, work that moves only by handover, and a unit of time that is not the hour but the night.
When an asynchronous team needs a shared operational record, employee monitoring software can connect tracked hours, activity patterns and project context without adding another status meeting. That evidence makes the handover more useful while keeping the surrounding conversation focused on outcomes.
For a second perspective on the surrounding workflow, consult Atlassian's Confluence workspace; it shows how a widely used platform structures the same coordination problem.
What was being doneElapsed
A question with one unambiguous answer
A question that needed one clarification first
A decision needing agreement from both halves
An incident opened an hour before the handover
A piece of work finished and handed over clean
Two people arguing their way to a shared view
six things · ten nights · one that no number of nights settles
One team's own week, logged as it went.
50notes, each one a thing that goes wrong or a thing that helps
6parts, grouped by where in the relay the difficulty sits
10nights that one ordinary week cost the team in the panel above
1thing in that same week that no number of nights settles
The figures in this collection are practical illustrations drawn from operational scenarios, not universal benchmarks. Use them to frame questions about handovers, workload and visibility, then adapt the process to the team's actual hours, responsibilities and local requirements.
Six places the difficulty sits
Every note belongs to one of them. The cost line on each card is what that part of the relay takes out of a week, stated in nights rather than in hours.
The gap
Measuring the gap
How big the gap actually is, how to state it so people can compare windows, and what one crossing costs.
Costs: one night per exchange
Across the night
What crosses the night
What survives a handover, in what state, and the difference between handing over finished work and handing over a puzzle.
Costs: one night, if it is left well
The day
The shape of a day at either end
The first hour is reading what happened while you slept. The last hour is writing what the next person needs.
Costs: two hours of every day
Asking
Asking well, because a question costs a day
How to put a question so that one answer finishes it, and what makes an answer need a second crossing.
Costs: one trip if the question is whole
When it breaks
When something breaks
Incidents that span a handover, what the person waking up actually needs, and the things that genuinely cannot wait.
Costs: the handover lands mid-incident
What no relay settles
What no relay settles
The residue: what needs two people thinking at once, what that costs, and when the arrangement is wrong for the work.
Costs: no number of nights
One team's own week, logged as it went
Three panels, all of them drawn from the same week on the same team. Nothing here is a benchmark and nothing is divided by anything: the numbers are a record, not a target.
One ordinary week on one team, and what each thing cost in nights
What was being doneElapsed
A question with one unambiguous answer
Asked at 16:40, read at 09:10 their time, answered before their lunch
A question that needed one clarification first
The clarification was one sentence and cost two further nights
A decision needing agreement from both halves
Nobody disagreed with anybody; the argument took four passes to converge
An incident opened an hour before the handover
Handed over live, with the diagnosis half finished and the notes thin
A piece of work finished and handed over clean
The only row that cost nothing beyond the night it had to wait
Two people arguing their way to a shared view
It needs both of them present at once, and no number of nights supplies that
six things · ten nights · one that no number of nights settles
Six things, ten nights, and one that no number of nights settles. The strip is not drawn to scale and cannot be: every night is the same length, while the work between them is minutes against fifteen hours. Nothing here divides the one by the other, because the resulting fraction reads as idleness when the fact is that there was nobody awake to do it. One team's own week, logged as it went.
Where everybody's working day sits, all of it stated in one time zone
Two engineers and a designer
The half that holds most of the product work and all of the client calls
Two engineers and the person who runs support
Twelve and a half hours later, which is the whole of the problem
The person who manages both halves
Shifted early on purpose, which buys an hour with one half and none with the other
The contractor who covers Fridays
Overlaps the second half almost exactly and the first half not at all
four people · no minute of the day when all of them are awake
Four groups, and no minute of the day when all of them are awake. The manager's shifted start buys an overlap with one half and nothing with the other, which is the usual outcome of shifting one person. One team's own hours, stated in a single zone so that the windows can be compared; what any other team looks like differs by where its people are.
Questions asked in one week, and what each answer cost in round trips
Can we ship the import without the audit flag?
What did the client actually agree to on Tuesday?
Asked without saying which client, then without saying which call
Is the staging database safe to reset?
Asked of somebody who had to ask somebody else
Which of the two approaches did we settle on?
The answer existed in a message nobody could find, so it was re-argued
Are you happy for me to merge this?
Should we tell the client before or after the fix?
A question with two answers, neither of them wrong, asked as though it had one
six questions · seven round trips beyond the first
Six questions, seven round trips beyond the first. Five of those seven were caused by how the question was put rather than by the distance: a missing noun, a wrong addressee, an answer that already existed. Distance makes a badly formed question expensive; it does not make it badly formed. One team's own week, logged by the person who asked.
01 / 06one night per exchange
Measuring the gap
How big the gap actually is, how to state it so people can compare windows, and what one crossing costs.
- The Unit Is the Night, Not the Hour
- Stating Everybody's Hours in a Single Time Zone
- The Overlap That Is Not Really There
- What One Crossing Actually Costs
- The Half-Hour at the Edge of Two Days
- Shifting One Person's Day, and What It Buys
- Counting Crossings Instead of Estimating Hours
- The Week the Clocks Change
- Writing the Gap Down Where People Can See It
02 / 06one night, if it is left well
What crosses the night
What survives a handover, in what state, and the difference between handing over finished work and handing over a puzzle.
- What Survives a Handover and What Does Not
- Handing Over Work That Is Actually Finished
- Handing Over Something Half Built
- Handing Over Something Waiting on an Answer
- The State Work Has to Be Left In
- The Handover Note, and What Belongs in It
- What Not to Hand Over at All
- The Thing That Keeps Coming Back
- Handing Something to Somebody Not Expecting It
03 / 06two hours of every day
The shape of a day at either end
The first hour is reading what happened while you slept. The last hour is writing what the next person needs.
- The First Hour: Reading What Arrived Overnight
- The Last Hour: Writing What the Other End Needs
- What Belongs in the Middle of the Day
- The Price of the Two Hours, Stated Honestly
- Keeping the Writing Hour When the Day Overruns
- The Meeting Somebody Stayed Up For
- Being the Person Who Sits Between the Halves
- When One Half's Day Is Longer Than the Other's
04 / 06one trip if the question is whole
Asking well, because a question costs a day
How to put a question so that one answer finishes it, and what makes an answer need a second crossing.
05 / 06the handover lands mid-incident
When something breaks
Incidents that span a handover, what the person waking up actually needs, and the things that genuinely cannot wait.
- When It Breaks an Hour Before the Handover
- What to Write Before You Sleep
- Who May Be Woken, and Who Decides That
- What Genuinely Cannot Wait Until Morning
- The Decision Only the Sleeping Half Can Make
- Handing Over an Incident That Is Still Running
- Reconstructing What Happened Overnight
- On-Call When the Team Spans a Gap
06 / 06no number of nights
What no relay settles
The residue: what needs two people thinking at once, what that costs, and when the arrangement is wrong for the work.
- Two People Thinking at the Same Moment
- Trust, and What a Relay Does Not Build
- Noticing That Somebody Is in Trouble
- Judging Work You Have Never Watched Being Done
- Deciding Without Ever Having a Conversation
- Work That Should Not Be Split Across the Gap
- Saying Out Loud That the Gap Is the Problem
- What a Relay Is Actually Good For
The short version
The unit is the night, and almost everything follows from that
One exchange costs a day. A question that needs a clarification costs three. A decision that needs genuine agreement costs four or five, and a conversation that needs two people thinking together costs nothing at all, because it does not happen. Everything worth doing about this is about reducing the number of crossings, not about making each crossing faster.
Software field guides
Three ways to compare the tools around asynchronous work
Each guide uses a different scope and layout, from a focused monitoring shortlist to a broader operations catalog.
Time tracking for asynchronous teams
Compare timers, timesheets, billing and handover context.
Workforce operations platforms
A wider catalog spanning analytics, scheduling, HR and payroll workflows.