Advisory work is inherently oral. The value of an advisory relationship lives in conversations — in the back-and-forth of a strategy discussion, in the advisor's response to a client question, in the judgment applied to a specific situation. The documentation of that work is secondary to the work itself, and most advisors treat it as such.
This is a structural mistake, and it is one of the main reasons advisory relationships become fragile over time. When the knowledge produced in an advisory relationship lives entirely in the memories of the participants — what was discussed, what was recommended, what was decided, what the context was — the relationship is one personnel change away from losing everything that was learned. The relationship is not portable. It cannot be re-entered after a pause without significant reconstruction. It cannot be evaluated against its own history. It becomes, in effect, a series of present-tense conversations rather than a coherent, accumulated body of judgment.
Documentation does not replace the oral character of advisory work. It preserves what the oral work produced. The distinction matters. Advisory documentation is not about creating bureaucratic records of meetings or formal deliverable archives. It is about capturing the residue of good judgment so that it is available when the conversation is not happening.
What Advisory Documentation Needs to Accomplish
Before designing a documentation system, it is worth being specific about what advisory documentation needs to do. Four things.
Decision trail: Advisory relationships produce decisions — the client makes choices with the benefit of the advisor's perspective. Those decisions should be recorded: what was decided, what the available options were, what reasoning drove the choice, and who made the decision. This record serves multiple purposes. It prevents revisiting settled questions without acknowledging that the question was already addressed. It provides context when a decision proves correct or incorrect. It gives both parties an accurate account of the engagement's history.
Handoff capability: An advisory relationship should be transferable to a successor advisor without losing the context accumulated during the engagement. This is not primarily about protecting the advisor's value — it is about protecting the client's investment in building the relationship's context. A well-documented advisory engagement enables a successor to enter the relationship with real understanding of the client's situation, the history of the work, and the open questions, rather than starting over.
Re-entry after pause: Many advisory relationships pause. The client's priorities shift, the advisor becomes unavailable for a period, the engagement reaches a natural stopping point before the client is ready to continue. When the relationship resumes, both parties need to be able to reconstruct the context quickly. This is nearly impossible if the engagement's history lives only in memory. It is straightforward if the engagement is documented.
Accountability for both parties: Documentation creates a shared record that both parties can reference when there is disagreement about what was discussed, what was recommended, or what was agreed. This is protective for both the client and the advisor. The client can verify that the advisor's recommendations were implemented as understood. The advisor can demonstrate that recommendations were made and that outcomes reflect client decisions, not advisory failures.
The Advisory Documentation Architecture
The five-component documentation system I use for advisory engagements, which I call the Advisory Documentation Architecture, is designed to accomplish all four of the functions above with the minimum viable overhead for a solo practitioner.
Component One: Decision Log
The decision log is a chronological record of significant decisions made during the engagement. Each entry records: the date, the decision made, the alternatives considered, the reasoning that drove the choice, and who made the decision.
The decision log is the most high-value component of advisory documentation because it directly addresses the most expensive failure mode in advisory relationships: relitigating settled questions. Organizations that do not maintain decision logs spend significant time in meetings that are, in effect, reconstructing the reasoning behind previous decisions. The participants who were not in the original conversation have no reliable account of that reasoning, so they are working from imperfect memory and incomplete information to evaluate decisions that have already been made with better information.
An advisory engagement that maintains a decision log can reference that log when settled questions resurface. This is not about being rigid — decisions can be revisited when new information warrants. It is about doing so with an accurate account of what was previously decided and why, rather than with whatever each participant remembers.
The decision log does not need to be comprehensive. Not every conversation produces a significant decision. The practitioner's judgment about which decisions warrant logging is what determines the log's usefulness. A log that captures major decisions with adequate context is far more valuable than a log that attempts to capture everything and produces a volume of detail that no one reads.
Component Two: Recommendation Register
The recommendation register records advice formally given: the recommendation, the context that prompted it, the date, and the client's response.
The recommendation register accomplishes two things. First, it creates a record that distinguishes advisory input from client decision-making. When the client implements a recommendation and the outcome is positive, the register documents the connection. When the client does not implement a recommendation and the predicted problem materializes, the register documents that as well. This is not about establishing blame — it is about maintaining an accurate account of how advice and decisions related to each other.
Second, it creates a corpus of the advisor's actual recommendations over the course of the engagement. This is valuable for the advisor as well as the client. Reviewing the recommendation register periodically reveals patterns: what kinds of recommendations get implemented, what kinds do not, whether the recommendations are addressing the actual problems or drifting toward what the client wants to hear. These patterns are not always visible in the flow of individual conversations.
The register should be shared with the client. An advisory relationship in which only the advisor knows what recommendations have been made is less accountable than one in which both parties have access to the record.
Component Three: Context Memo
The context memo is a living document that captures the essential background for understanding the engagement: who the key people are and their roles, what the organization's strategic situation is, what the history of the work is, and what the current status of major initiatives is.
Unlike the decision log and recommendation register, which are chronological, the context memo is updated in place. It should reflect the current state of the client's situation, not the history of every change. An older version of the context memo should be archivable — there is value in being able to see how the situation has evolved — but the working version should be the current state.
The context memo is the primary re-entry document. Someone picking up this engagement after a pause — whether a successor advisor or the original advisor returning after a gap — should be able to read the context memo and understand the current state of the engagement. It is the document that makes the relationship portable.
Context memos are also honest documents. If the client's situation has deteriorated since the engagement began, the context memo should reflect that. If the original problem statement has changed, the context memo should be updated. A context memo that is kept accurate is a more useful document than one that reflects how the client prefers to see their situation.
Component Four: Relationship Notes
Relationship notes capture the working dynamics of the advisory relationship — how the client prefers to receive information, what kinds of conversations are most productive, what areas are sensitive, how decisions get made in practice (as opposed to on paper), and who the key internal people are beyond the primary client contact.
These notes are for the advisor's internal use, not for sharing with the client. They capture the practitioner knowledge that accumulates through working with a specific person and organization over time.
Relationship notes are the component that advisors most often fail to capture. The information lives in the advisor's head. It is not written down because it feels too informal, or too personal, or because no one will ask for it. When the advisor steps back from the engagement — even briefly — this knowledge is the first thing to fade.
The practical value of relationship notes is most visible at two moments: when the engagement pauses and resumes, and when the advisor is preparing for a difficult conversation. In both cases, having a written account of how the relationship actually works is more reliable than memory.
Component Five: Open Items Register
The open items register is a list of unresolved questions, pending analyses, and agreed follow-up commitments. It captures what is not yet closed.
Advisory conversations routinely surface questions that neither party can answer in the moment, commitments to revisit topics in light of new information, and areas where further analysis would inform a pending decision. Without a register, these open items live in the conversation and disappear when the conversation ends. They may resurface later when the lack of resolution becomes a problem. They may not resurface at all and the gap they represent quietly damages the engagement's quality.
The open items register should be reviewed at the start of each engagement conversation. This has two effects: it creates accountability for commitments made in previous conversations, and it ensures that the advisor's preparation for each conversation includes what was left unresolved.
Minimum Viable Documentation
The five-component system above is complete. For a solo practitioner managing multiple advisory relationships, maintaining all five components for each engagement may feel like more overhead than the system can sustain.
The minimum viable version of this system for a sole practitioner is three components: a decision log, a context memo, and an open items register. The recommendation register and relationship notes can be added as practice matures or as specific engagements warrant them.
The decision log protects against the most expensive failure mode. The context memo enables re-entry. The open items register prevents the loss of unresolved questions. Together, these three accomplish the essential function of making the engagement's history available to both parties.
What the minimum viable version cannot do is support handoff to a successor advisor as fully as the complete system. The recommendation register and relationship notes are what make that transition navigable. If the engagement is one where continuity matters — long-term advisory relationships with significant institutional knowledge — the full system is worth the additional effort.
The Documentation Practice
Advisory documentation is only useful if it is maintained. A decision log updated once per quarter is better than nothing and worse than one updated after each conversation. A context memo that has not been reviewed in six months is likely inaccurate enough to mislead rather than inform.
The sustainable documentation practice, for a solo practitioner, is a brief administrative period after each client conversation — fifteen to thirty minutes to update the relevant documents with what was discussed, what was decided, what was recommended, and what is now open.
This is not glamorous work. It is the kind of work that gets cut when time is short. The way to protect it is to treat it as part of the delivery of the conversation rather than as overhead that follows it. The client interaction is not complete when the conversation ends. It is complete when the conversation has been documented.
An advisory practice built on this discipline is more sustainable than one that is not. Not because documentation itself produces better advice, but because it creates the conditions under which good advice can be maintained, evaluated, and built on over time. The relationship becomes more than the sum of its conversations. It becomes a body of accumulated judgment — which is, ultimately, what advisory work is for.