Distributed teams
Your team is spread out. The record is not.
Hours, activity and attendance are read on each person's own local day and land on one board. You stop waiting for a status update to find out where a project actually is.
Free for two seats, no card.
One working day, 6 places
09:00 to 17:30 local, standard offsets
09:41UTC
- DEBerlin10:41Germany, inside the working day
- ESMadrid10:41Spain, inside the working day
- HKHong Kong17:41Hong Kong, outside the working day
- USNew York04:41United States, outside the working day
- BRSão Paulo06:41Brazil, outside the working day
- ZAJohannesburg11:41South Africa, inside the working day
3 of 6 inside their working day
The shared record
One board, however far apart the desks are
Six regional exports, reconciled at the end of the month, and by then the answer is history. Every seat reports into one page instead: who is working, on what, right now — without waiting for a standup, a status update or a manager in the room to notice.
- Today
- Insights
- Activity board
- Live screens
- Team
- Agents
- Integrity
- App categories
- Reports & digests
- Capacity
- AKAria K.Figma92Active
- JMJon M.Terminal78Active
- SDSara D.Slack61Active
- RPRavi P.Notion34Idle 11m
- LMLena M.Teams55In a call
- TVTomas V.Off shift0Off
- Every hour on its own local day
- Hours and activity are attributed to the worker's own local day, so a 19:00 start in Manila reads as that person's evening rather than a hole in your Tuesday afternoon.
- It goes in without a fight
- Consent, redaction and an on-screen indicator mean nobody is recorded without knowing it, and the same record opens for the person it describes. There is nothing to discover later and object to.
- Employees and contractors, one roster
- One board carries both — focus, attendance and output — whichever country the seat is in and whichever contract it sits under.
The whole argument, in one line
Distance should change where the work happens, not what you can see of it.
Every hour lands on the board on the day it happened, in the time zone it happened in. Nothing waits for a weekly roll-up, and nothing is reconstructed from memory on a Friday.
Two-way visibility
The record points both ways
A team that decides it is being watched rather than measured will slow the whole thing down. So the record opens from both ends: the same five artefacts, read by a manager and by the person they describe. Nobody has to take our word for what is collected.
- The board
- A manager opensWho is working, on what, right now, across every seat wherever it happens to be.
- That person opensThe same day back in their own view: what was recorded of them, hour by hour.
- Captures
- A manager opensPeriodic screen captures on a cadence you set, blurred on the device before anything leaves it.
- That person opensSees each capture of them, and can send a specific one back to be reviewed.
- Applications
- A manager opensPer-app deny-lists are applied on the device, before anything is transmitted.
- That person opensNamed applications never enter the record at all, on any machine.
- Who looked
- A manager opensOpening someone else's record is itself an entry in the hash-chained audit log.
- That person opensCan see that their data was read, and when it was read.
- Consent
- A manager opensThe roster carries every person's consent status and the policy version they hold.
- That person opensKnows which version of the policy they accepted, under the rules of their own country.
- Today
- Insights
- Activity board
- Live screens
- Team
- Agents
- Integrity
- App categories
- Reports & digests
- Capacity
- LMLena M.After-hours load · rising86High load
- RPRavi P.No-break streak · rising79High load
- AKAria K.Context switching · rising74High load
- SDSara D.Workload trend · rising61Elevated
- JMJon M.Context switching48Elevated
- TVTomas V.No-break streak · tracking off28Steady
Capacity
Distance hides overload
In one building, the person who has not stopped is visible from across the room. Distributed, nobody walks past their desk. This page does the walking past — every week, on every seat.
- 01Load against a band, not a leaderboardEach seat is read against a healthy range, so the two people carrying the team show up while that is still a scheduling problem rather than a resignation.
- 02Counted on their day, not yoursHours land on the worker's own local day, so an evening in one region does not arrive on your Monday morning looking like overtime.
- 03Coverage, not just totalsA headline figure can look complete while a rota is two seats short at 02:00 in one region. Only a local-day reading shows that gap at all.
Where you hire
The same rollout is not legal everywhere
A headcount in a new country stops at “legal need to look at it”, and then waits. 32 jurisdictions are written up and sourced here, grouped by how much has to happen before you switch anything on: the instruments that govern, the control that answers each duty, and the part no vendor can do for you.
Prior approval required4
A works council, union or regulator has to agree before monitoring is switched on. Without that agreement it is not a risk, it is a hard stop.
Specific practices restricted3
The law or the regulator treats some monitoring, usually continuous screen capture or keystroke logging, as off the table regardless of consent.
Consultation required6
Employee representatives must be consulted or negotiated with before deployment. They may not have a veto, but skipping the step is itself the offence.
Notice and proportionality19
Monitoring is lawful with advance written notice, a documented lawful basis and a proportionality test. The paperwork is the requirement.
Compliance is a property of your deployment rather than of any product, and none of these pages will tell you otherwise. Of the 6 places on the clock at the top of this page, 5 have a page here. Hong Kong does not, and it is not filled in with a guess: a plausible summary of a labour code nobody checked is worse than no page at all. Read the index, or ask us what we know about a country that is not listed.
Straight answers
The questions we would ask in your position
Every answer here is the one you would get on a call. Open as many as you like; they stay open, so two can be held side by side.
Activity is read per local day rather than against a head-office clock. That is what makes a gap visible: aggregate coverage can read 98% while a rota is two seats short at 02:00 in one region, and only a local-day view shows it.
That depends almost entirely on how it arrives, which is why the controls are two-way. Employees get a self-view of what was collected and a route to appeal a specific capture, access to their data is itself recorded, and per-app privacy deny-lists keep named applications out of the record entirely. Teams that roll this out as something people can inspect get a very different reception from teams that roll it out quietly.
Per-app deny-lists apply on the device before anything is transmitted, so named applications never enter the record. Combined with capture policies scoped to working hours, what is collected is an explicit decision rather than everything that happened on the laptop.
macOS is live today, along with a VS Code companion. Windows, Linux and a browser extension are in beta, and a mobile app for deskless teams is planned. The product pages carry the current status for each rather than listing everything as shipped.
The rules differ per jurisdiction, and so does the product: consent, notice and retention are applied per country with a record of which policy version each person accepted. That record is the thing an authority asks for. What the data may be used for, particularly for automated evaluation, is a policy you set deliberately.
Point it at one team for a week.
Create the account, put the agent on a handful of desks, and leave it alone. On Friday you read the week instead of reconstructing it: hours against their projects, focus and idle per person, and the timesheets already filled in.
Free for two seats. No card, and no sales call to sit through.