Legal and tax teams can each produce correct advice and still leave the client without a coherent decision. The gap usually appears between workstreams: different versions of the facts, different assumptions about timing and no single record of why one structure was selected over another.
A shared decision log is a simple way to close that gap. It is not a substitute for formal advice. It is the connective record that shows how separate conclusions informed the same business choice.
What the log should capture
The most useful entries are concise. Each records:
- the decision or issue;
- the date and current status;
- the person or body with authority;
- the facts and assumptions that matter;
- the legal and tax implications considered;
- dependencies owned by another adviser or workstream;
- the chosen position and rationale;
- actions, owners and review triggers.
The log should link to source advice and documents rather than reproduce them. Its purpose is to make the relationship between those sources visible.
Begin with one factual baseline
Parallel work becomes unreliable when each adviser is answering a slightly different question. Before comparing alternatives, align on a factual baseline: ownership, entities, cash flows, functions, assets, contracts, jurisdictions, intended timing and commercial purpose.
Unconfirmed facts should remain visibly unconfirmed. A model can proceed on a working assumption, but the decision log should identify who must validate it and whether the final recommendation changes if the assumption is wrong.
This approach avoids a familiar late-stage problem: discovering that the legal documents describe an operating model different from the one used in the tax analysis.
Record alternatives before they disappear
Teams often evaluate several structures before one becomes the working route. Once drafting begins, the rejected alternatives and the reasons for rejecting them can vanish from the active file.
The decision log preserves that reasoning without turning it into a lengthy memorandum. For each material alternative, note the principal benefit, the material constraint and the reason it was not selected.
This record can be especially useful when circumstances change. If timing, ownership or economics move, the team can see whether an earlier alternative should be reconsidered rather than beginning the analysis again.
Make dependencies explicit
Some conclusions cannot be completed within the legal or tax workstream alone. They may depend on accounting treatment, valuation, regulatory approval, financing terms, foreign law or operational capability.
Do not leave those dependencies inside email caveats. Give each one an owner, a required output and a date. The log should also state which decision is blocked—or which risk is being accepted—until the dependency is resolved.
This makes coordination practical. It allows the matter lead to distinguish between a question that is still being analyzed and a question that no one has actually been assigned to answer.
Connect the decision to implementation
The selected structure usually creates follow-up actions across multiple teams. Legal documents may need to be signed in a particular sequence. Tax registrations, elections or documentation may depend on that sequence. Finance systems and compliance controls may need to reflect the new arrangement.
The decision log should therefore continue past selection. Record the conditions supporting the decision and the actions required to keep those conditions true. If a conclusion depends on how the business operates after implementation, identify the owner and the review point.
A modest tool with a high coordination value
The decision log does not need specialized software. A controlled document with clear ownership and links to source materials is often enough. What matters is that both workstreams use it and that changes to material assumptions are recorded.
When the log works, the client can answer a basic but important question: not only “What did our advisers conclude?” but “How did those conclusions come together in the decision we made?”
This note is general information and does not constitute legal or tax advice. The analysis and documentation appropriate to a matter depend on its facts, jurisdictions and applicable requirements.