Bobadilla v. The Email Chain
On documented conversations, attorney client privilege, and the call you should have made first.
There is a specific kind of corporate instinct that feels responsible and occasionally isn't. It's the instinct to document. To write it down, send the follow up, confirm in writing, create the record. In most situations this is exactly right. In some situations it is the most expensive thing you will do all year.
The moments when people most want to send an email are often the moments when sending an email is most dangerous. Something sensitive surfaces. A situation gets sticky. Someone does something that needs to be addressed. And instead of picking up the phone, someone opens a new message, types out what they know, copies three people, and hits send.
Now there's a record. Now there's a chain. Now there's a thread that proves awareness, establishes a timeline, and documents exactly who knew what and when. It felt responsible. It may have just moved you from one legal category to a significantly more expensive one.
What Documented Awareness Actually Costs
Take employee complaints as an example, because it's the one I've watched play out more times than I can count. An employee raises an issue. A manager receives it. The manager, trying to do the right thing, sends an email to HR documenting what was said. Maybe they copy their own manager. Maybe they reply all. The intention is good. The instinct is reasonable. The result is that the employer now has a written record proving they knew about the complaint, when they knew, and who else knew.
In employment law the difference between negligence and willfulness is not a technicality. It's the difference between a company that failed to prevent something and a company that knew about it and failed to act. That distinction can be worth hundreds of thousands of dollars. Sometimes more. And the thing that moves a company from the first category to the second is often a well-intentioned email sent by someone who thought they were handling it responsibly.
This is not an argument against documentation. It's an argument for thinking clearly about what you're documenting, when, and what that document might mean to someone who reads it later in a context you didn't anticipate.
The Culture Problem
Corporate culture has a complicated relationship with meetings and documentation. There are meetings that exist to generate agendas, agendas that generate notes, notes that generate follow up emails, and follow up emails that generate reply chains that eventually include people who weren't at the original meeting and aren't entirely sure why they're being copied. Most of this is harmless. Some of it is quietly generating a record that nobody is actively managing and nobody has fully thought through.
The instinct to document everything is not inherently wrong. Contracts should be documented. Decisions should be documented. Commitments should be documented. But there is a meaningful difference between documentation that serves your business and documentation that exists because hitting reply felt like doing something. The email chain that reconstructs a sensitive conversation in writing, copies people who didn't need to be included, and sits in six inboxes indefinitely is not the same thing as a well-maintained contract file.
The question worth asking before you type anything is not whether to document. It's what this document will look like to someone who reads it without your context, your intentions, or your relationship with the people involved.
The Cone of Silence
This is where having a lawyer changes everything.
Attorney client privilege protects confidential communications between a lawyer and their client made for the purpose of seeking or providing legal advice. It belongs to the client. It covers the conversation about what a situation means legally and what to do about it. The call you make to your lawyer before you do anything else happens inside that protection. The email you send to your leadership team about the same situation does not.
What this means practically is that the phone call to your lawyer is categorically different from any other call you could make in that moment. You can say the scary thing out loud. You can describe the situation fully, including the parts that are embarrassing or uncertain or not yet resolved. You can ask the question you're afraid to ask. None of it creates a record that exists outside that conversation. The advice you receive, the plan you build, the decision you make about how to proceed, all of that happens before anything is in writing. Before anything is documented. Before anyone else knows what you know.
That is an enormous operational advantage and most founders don't have access to it because they don't have a lawyer they can call.
What Integration Actually Changes
Outside counsel can give you privilege too, technically. But the advice is choppy and limited because the context isn't there. You're explaining your business, your people, your history, and your problem all at once to someone who is trying to help you in a crisis they've just been introduced to. The advice you get is shaped by what you manage to convey in a compressed conversation with someone who has no baseline understanding of how your business actually works.
An integrated lawyer already has the context. They know your contracts, your team, your risk tolerance, your communication style, and the history of decisions that led to the current situation. When something goes sideways they can see the practical ripple effect of every available option. They answer the questions you should have asked but didn't, because they already know enough about your business to know what you're missing. They ask better questions because they have historical context. The conversation is a genuine thought partnership instead of an emergency briefing with a near stranger.
That difference is most visible in the moments when something has just happened and you have about thirty minutes before you need to decide how to respond. Those moments go very differently depending on whether you're calling someone who knows you or someone who doesn't.
Pick Up The Phone: A Practical List
These are the situations where your first move should be a call to your lawyer, not an email to your team, not a text to a trusted friend, not a Google search, and not a reply to whatever just landed in your inbox.
Someone on your team raises a complaint about another employee or about management, formally or informally, in passing or in a meeting. Before you document it, before you respond, before you tell anyone else, make the call.
A key employee resigns and you suspect they're headed to a competitor. The window for protecting your business interests is short and what you do in the first few hours matters significantly. Make the call before you send any communication to that employee or anyone else.
You receive anything from another party's lawyer. A cease and desist, a demand letter, a notice of any kind. Do not respond. Do not forward it to your team with commentary. Make the call.
You discover or suspect that an employee has been stealing, whether money, time, clients, or confidential information. The sequence of steps matters enormously and the wrong first move can compromise your options. Make the call.
A customer or vendor tells you verbally something that contradicts what your contract says. Before you respond, before you confirm anything in writing, before you agree to adjust your position, make the call.
You're mid-negotiation and realize you've already agreed to something verbally that you shouldn't have. Before you say anything else, before you send a recap email, make the call.
You're about to hire someone with a non-compete, a former employee of a direct competitor, or someone you've had a prior personal or financial relationship with. Before you extend the offer, make the call.
Something happens that might be a data breach. Even a small one. Even one you're not sure about. The notification windows in data privacy law are shorter than most founders realize and the clock starts when you knew or should have known. Make the call.
You're approached about an acquisition, a partnership, or an investment and the other party asks you to keep it confidential before you've agreed to any terms. Before you say yes to the confidentiality, before you share anything, make the call.
A situation arises that you don't have a name for yet. Something feels wrong or off or legally significant and you can't fully articulate why. That instinct is data. Make the call.
The Call You Should Have Made First
Understory exists to be that call. Not the lawyer you engage after the crisis is already documented, the chain already sent, the record already created. The one you call before you open the email.
When you have an integrated legal relationship, the cone of silence is available to you in real time. The advice is informed by context. The plan is built before anything is in writing. And the sticky situations that would otherwise generate panicked email chains and expensive consequences get handled the way they should have been handled from the beginning.
Pick up the phone. Say the scary thing out loud. Figure out what it means before you put it anywhere it can be read without you.
That's what the relationship is for.
- m
