Tracking Patent Disputes Across Three Continents

Patent litigation rarely stays in one jurisdiction. The intellectual property team at a major Japanese technology conglomerate — a household name in consumer electronics and semiconductor manufacturing — was managing parallel proceedings involving the same patent family in the United States (an ITC investigation and concurrent district court litigation in the Eastern District of Texas), the European Patent Office (opposition proceedings filed by a competitor), and Japan (an invalidity action before the Japan Patent Office). Each proceeding had its own procedural calendar, discovery schedule, and cast of local counsel — and the outcomes were deeply interdependent. A claim construction ruling in Texas could reshape the arguments in Munich; an EPO decision on patent validity could be cited in Tokyo.

The IP team itself was lean but experienced: eight lawyers and patent engineers based primarily in Tokyo, with one liaison in the company's Silicon Valley office. The team had managed parallel proceedings before, but previous cases had involved at most two jurisdictions. This was the first time they faced three simultaneous proceedings involving the same patent family, each at a different procedural stage and each requiring active strategic management. The sheer number of deadlines, filings, and tactical decisions exceeded what any individual team member could track mentally.

The coordination system they had been using was, by the team's own admission, inadequate for the task. A shared Outlook calendar tracked major deadlines — hearing dates, filing deadlines, response periods — but provided no context about what each deadline meant or how it connected to events in other jurisdictions. Email was the primary communication channel with the three sets of local counsel: a patent litigation boutique in Washington, D.C., a leading IP firm in Munich, and a Tokyo-based patent attorney. Important updates were buried in long email threads, and the team frequently found themselves searching their inboxes for information that should have been at their fingertips.

The deputy general counsel, who oversaw the IP function, had heard about Juristic Timeline from a peer at another Japanese technology company during an in-house counsel roundtable. He was initially cautious — the team had limited appetite for learning new tools while managing active proceedings — but the coordination problems were becoming acute. A missed internal deadline on a discovery response in the US case, caught only by luck when an associate happened to re-read a scheduling order the night before, convinced him that the current system was not merely inconvenient but risky.

Juristic Timeline was implemented with a focused scope: the three parallel proceedings would be mapped onto a single chronology, with each jurisdiction represented as a separate track running along a shared time axis. The setup was completed in a single working day. The team began by entering the procedural milestones from each case — hearing dates, filing deadlines, discovery cutoffs, decision dates — and then layered in the strategic context: which deadlines affected other proceedings, where arguments in one jurisdiction could be leveraged in another, and which developments required immediate cross-border coordination.

The visual representation transformed the team's strategic planning. For the first time, they could see all three proceedings in a single view, with the relationships between them made explicit. A deposition scheduled in Texas two weeks before a hearing in Tokyo was immediately visible as both an opportunity and a constraint: the testimony obtained in the US could inform the arguments in Japan, but only if the transcripts were reviewed and translated in time. Under the old calendar system, this kind of cross-jurisdictional planning required someone to manually compare three separate schedules — a task that was often deferred and sometimes forgotten.

The Timeline also served as the team's institutional memory for the dispute. Every significant development — a ruling, a filing, a strategic decision, a change in claim scope — was logged in Timeline with its date, jurisdiction, and a brief annotation explaining its significance. When a new team member joined the IP department midway through the proceedings, she was able to read the complete history of the dispute in Timeline within a day. Under the old system, onboarding a new team member to a complex multi-jurisdictional dispute took weeks of reading email chains and attending briefing sessions.

The cross-jurisdictional visibility proved critical at a decisive moment. The EPO opposition division issued a preliminary opinion that narrowed the scope of the patent claims being contested. Under the previous system, this development might have reached the US counsel days later, after being summarised in an email from Munich and forwarded from Tokyo. Instead, the in-house team flagged the development in Timeline within hours, and the team immediately recognised its implications for the ITC investigation — where the same claims were being asserted with the broader scope. US counsel was briefed the same day and adjusted their claim construction arguments before the next filing deadline. The lead partner at the DC firm later told the in-house team that the speed of the coordination was 'unlike anything I have seen from an in-house IP team.'

Timeline's filtering capabilities proved valuable for the team's regular strategy sessions. Before each monthly coordination call with all three sets of local counsel, the deputy general counsel would filter Timeline to show only developments from the past month and upcoming deadlines for the next six weeks. This filtered view became the standing agenda for the calls, replacing the informal and often incomplete agendas that had previously been assembled from memory and scattered notes. The calls became shorter and more focused — the team spent less time establishing what had happened and more time deciding what to do next.

The discipline of maintaining Timeline also improved the team's relationship with its local counsel. Each firm was given read access to the relevant portions of the timeline and was asked to confirm that their jurisdictional entries were accurate and current. This created a lightweight but effective accountability mechanism: if a local firm's track showed no updates for three weeks, the in-house team noticed immediately and followed up. The Tokyo-based patent attorney observed that the shared timeline 'created a sense that we were all working on one case, not three separate cases that happened to involve the same patent.'

When the ITC issued its initial determination — a partial victory for the company — the in-house team used Timeline to brief the board of directors on the dispute's status. The visual chronology, showing all three proceedings with their current postures and upcoming milestones, communicated the complexity and the company's strategic position far more effectively than the traditional written report. The CEO, who had limited patience for legal briefings, spent fifteen minutes exploring the Timeline and asked three questions — each of which the deputy general counsel answered by clicking on a specific entry. 'This is how I want to see all of our litigation,' the CEO told him afterwards.

The head of IP described Timeline as 'essential infrastructure' for managing multi-jurisdictional patent disputes, comparing it to the project management tools that the company's engineering teams had used for decades but that had never been adopted by the legal department. The team has since rolled out Timeline for all parallel proceedings — currently five active sets across ten jurisdictions — and is exploring its use for patent prosecution tracking, where the coordination challenges between national phase filings are similar in kind, if smaller in scale.

The deputy general counsel, reflecting on the adoption, offered a characteristically understated assessment: 'We did not change how we think about patent strategy. We changed how we see it. And that turned out to be the same thing.'