Keeping parallel workstreams aligned across jurisdictions

Once a transaction gets under way, several streams of work run at the same time. Lawyers review documents and draft agreements. Accountants examine financial information. Tax advisers assess consequences. Commercial, technical and people specialists each look at their own part of the business. In a cross-border deal, each of these may be happening in more than one country, in more than one language and across several time zones.

Each workstream can be well run on its own and the transaction can still lose its way, because the streams depend on each other. A finding in one changes the work in another; a decision that one team is waiting for sits unnoticed in someone else's inbox. This article describes practical ways to keep parallel workstreams aligned: mapping them, tracking dependencies, running one issues list and one question log, handling language and time zones, and making decisions at the right moment.

Why alignment is harder than it looks

Most transaction problems are not caused by any single adviser getting something wrong. They come from information that did not travel. Common examples include a legal reviewer who learns late about a financial finding that affects the contract terms, or a tax recommendation that changes the structure after the lawyers have drafted around a different one. Another is a question from the other side answered differently by two people.

Alignment is the work of preventing those failures. It does not need sophisticated tools. It needs a shared picture of who is doing what, a small number of common records, and a predictable rhythm for communication and decisions.

Mapping the workstreams

Start by writing down each workstream, its lead, its scope and its main outputs. A typical map might include:

• Legal, in each relevant jurisdiction — review, documents, approvals and consents;
• Financial — review of historical information, working capital and obligations;
• Tax, in each relevant jurisdiction — consequences of the structure and the steps;
• Commercial — customers, markets, competitive position;
• Operational and technical — sites, systems, key processes;
• People — organisation, key roles, terms, communication and any relocation;
• Integration planning — how the business will run afterwards.

For each workstream, note who leads it, which jurisdictions it covers, what it needs from others and what it delivers. One page is usually enough. The roles behind these workstreams are described in mapping the specialists in a cross-border deal.

Mapping dependencies between workstreams

The map becomes truly useful when you add the arrows between workstreams. A dependency is anything one stream needs from another before it can finish part of its work.

Some dependencies are predictable:

• documents cannot be finalised until key due-diligence findings are understood;
• structure decisions depend on both legal and tax input;
• people plans depend on how the organisation will be combined;
• integration planning depends on what the review has revealed about systems and operations.

Draw these as a simple diagram or list. For each dependency, record who is waiting, who must deliver and what the delivery looks like. Revisit the map whenever the transaction changes shape.

One shared issues list

An issues list records every significant point that needs attention: a finding from the review, a drafting point that cannot be agreed, a missing document, an internal decision that is outstanding. Each entry has a short description, the workstream that raised it, the person who owns it, its status and what happens next.

A single list shared by all workstreams has two benefits. It shows each specialist the points that may affect their own work, and it gives decision-makers one place to see what is open. Keep entries short and factual, close them explicitly when they are resolved and avoid creating parallel lists in different teams.

One question log

Questions from the other side, and the answers given, need their own record. A question log shows:

• the question, who asked it and when;
• which workstream and which internal owner it was assigned to;
• whether the answer needs review by your advisers before it is sent;
• the answer, the supporting documents and the date it was sent.

The log prevents duplicate or inconsistent answers and makes it easy to see what is outstanding. It also becomes a valuable record later, because answers given during the process can matter after signing. Preparing the underlying information in advance, as described in preparing for due diligence: organising company information, makes the log much faster to work through.

A predictable communication rhythm

Workstreams align best when communication follows a rhythm rather than happening ad hoc. Many teams find it useful to have:

• a short regular call for workstream leads to update on progress, dependencies and new issues;
• a written update after each call, listing decisions taken and actions with owners;
• an agreed channel for urgent points that cannot wait for the next call;
• a clear rule about who may speak to the other side, on which topics.

The rhythm should match the stage of the transaction. Early on, less frequent coordination may be enough; during intensive review or negotiation, closer contact is often needed.

Language and time zones

Cross-border transactions add practical friction that is easy to underestimate.

Language

Documents, questions and answers may exist in several languages. Decide early which language is used for the working records — the issues list, the question log, the updates — and how translations of key documents will be prepared and checked. Where a document's legal meaning matters, translation and interpretation should involve qualified people, and it should be clear which version prevails.

Time zones

When teams are spread across time zones, a question raised at the end of one team's day may not be seen until the next day elsewhere. Agree on overlapping windows for calls, set realistic expectations for response times and avoid scheduling decisions in a way that always disadvantages one group.

Escalation and decision points

Not every issue should wait for the next regular call, and not every issue needs the most senior people. A simple escalation rule helps:

• workstream leads resolve what falls within their scope;
• cross-workstream issues go to the person coordinating the transaction;
• issues that affect the objective, the structure or the terms go to the decision-makers named in advance.

It also helps to identify the main decision points in the transaction — moments when the business must decide whether and how to proceed. Preparing a short decision paper before each one, drawing on the issues list and the workstream outputs, leads to clearer and faster decisions. The objective statement described in defining the transaction objective before engaging advisers is the reference point for each of them.

Keeping documents in step

Alignment also depends on everyone working from the same documents. A shared index, a clear folder structure, version discipline and a record of what has been shared with whom all help. When a key document changes — a revised financial summary, an updated organisation chart — notify the workstreams that depend on it rather than assuming they will notice.

Signs that workstreams are drifting

Some signals suggest alignment needs attention:

• the same question is asked or answered more than once;
• workstream leads learn about significant findings indirectly;
• the issues list is growing but few items are closing;
• decisions are being taken informally and not recorded;
• one jurisdiction or workstream is consistently behind and nobody knows why.

None of these means the transaction is in trouble. Each is a prompt to revisit the map, the dependencies and the rhythm before small gaps turn into delays or confusion.

In short

Parallel workstreams stay aligned when there is a shared map of who does what, explicit dependencies, one issues list, one question log, a predictable communication rhythm and clear decision points. Plan for language and time zones from the start, keep documents in step, and watch for early signs of drift. Coordination of this kind supports the specialists; it does not replace their advice.

If you would like help setting up the coordination records for a cross-border transaction, you can talk to Wobridge.