About this site

What it covers

How to state a gap so that it can be argued about: everybody's hours in one time zone, the real overlap rather than the hoped-for one, and the cost of a single crossing. What survives a handover and in what state. The two hours that bracket every day at both ends, which are the real price of the arrangement and are rarely counted. How to put a question so that one answer finishes it. What to do when something breaks an hour before the handover. And the residue: the things that need two people thinking at the same moment, which no number of nights supplies.

The argument running through it

The unit of time in a team like this is not the hour. It is the night. One exchange costs a day whatever the question was; a question that needs one clarification costs three days; a decision that needs genuine agreement costs four or five. Almost every useful change is about reducing the number of crossings rather than about making each crossing faster, because each crossing costs the same fifteen hours regardless of how quickly anybody types.

What it is not

It is not a guide to remote work. Writing about remote work assumes an overlapping hour exists and designs around it, which is a different and much easier problem; very little of it transfers to a team with no shared hour at all.

It is not advice about what any particular team should do. Every figure used here is an illustration of what one team recorded about its own week, labelled as such on the page where it appears. No benchmark is offered and none is implied.

It is also not legal or employment advice. What an employer may require of somebody outside ordinary hours, whether on-call or standby time must be paid and at what rate, what minimum rest a worker is entitled to between periods of work, what must be agreed before a working pattern changes, and which authority decides any of it all differ by jurisdiction and by the facts, and they change. Those are questions for somebody qualified in the place concerned.

How the tool guides are prepared

Our comparisons begin with direct review of each product’s public workflow, setup path, documentation and representative team use cases. We test the questions that matter in an asynchronous operation: whether time records are understandable, whether employees can see when tracking runs, how reports support a handover, and how easily a manager can separate waiting from active work.

Positions reflect that editorial assessment and the practical fit for the scenario named on the page. A higher position means the product matched more of the stated criteria during our review; it is not a universal verdict. Features change, so readers should confirm current details on each product’s official site.