Two entities in two countries move in step. Neither move, on its own, would land in any report. The pair does, because coordinated timing across a border is one of the small handful of signals that survives translation between legal systems that otherwise cannot be usefully compared. It is a cheap read to run once the timeline exists; the expensive part is building the timeline in the first place.
We log cross-country events on a single timeline per person. The visualization is unimpressive; what it surfaces is not. A person's company in one country files a change of registered office on a Tuesday and an entity in another country files an officer change on the Wednesday, three times in eighteen months, across years that would otherwise look unrelated. That pace is not coincidence; the two entities are being run by people who talk to each other and act on the same calendar.
Timing also reveals advisors; advisors and corporate services firms have signature patterns. They file in batches; they reuse templates. They send their clients identical instructions on identical days. When two people who are publicly unconnected show the same filing pace in the same offshore country in the same month, they likely share an advisor, and that advisor is the connecting node.
We do not always need to know which advisor. Knowing that two people share one is sometimes enough to reframe a counterparty question. It moves a relationship from "they happen to be in the same industry" to "they are being run by the same set of hands."
Timing analysis is cheap once you have the timeline. The expensive part is building the timeline in the first place across registries with inconsistent date formats and uneven update frequencies. That work compounds; after the first hundred people, the engine has enough normalized history to run timing queries in seconds. The first hundred took a long time.
A single entity moves in one country and it is a filing. Two entities in two countries move in the same direction inside a short window and the pace itself becomes the finding. Timing is the field most cross-border tools underweight, because they are built to compare state at a moment rather than motion across a period.
Once you start reading timing as a signal in its own right, patterns show up that the structural view misses. A registered office change in one country a fortnight before a new director in another. A wind-up in one place inside the same quarter as an incorporation in an adjacent one. The individual actions are unremarkable. The synchronisation is the read.
The general lesson, useful outside the private-client context, is that coincidences in time are informative. Most systems treat two events as independent unless someone tells them otherwise. Watching for the interval, rather than the events, is a cheap habit that changes what you can see.