Waiving a Conflict of Interest: What the Record Should Actually Contain

Every conflict waiver letter I've read looks the same on the surface. There's a paragraph explaining the conflict, a paragraph saying the firm believes it can represent both matters diligently, a signature line, and a date. And for years that felt like enough, right, because nobody ever went looking behind it. Then a malpractice claim shows up eighteen months later, or a former client's new lawyer sends a letter asking the firm to withdraw, and the first thing anyone does is pull the file to see what the waiver actually rested on. And what they usually find is one signed page and basically nothing else. No record of when the conflict was first spotted, no record of who caught it, no record of what alternatives were discussed before the client agreed to waive, nothing showing the firm actually screened the matter afterward the way the letter promised it would. That gap between "we have a signed waiver" and "we have a record that would hold up" is where firms actually lose these fights, and I want to walk through what should be sitting in that file instead, because I've built the system a few hundred firms now use to run this exact process and I've talked to enough of them about the moments it saved them to know where the weak points usually are.

A waiver letter is one page of a much longer record

Here's the thing that gets missed constantly. Bar rules generally require that a waiver be based on informed consent, and informed consent is not a legal conclusion you assert in a letter, it's a factual claim about what happened before the letter was written. Did the client actually understand the nature of the conflict. Was the conflict fully disclosed, not summarized. Did someone at the firm actually check whether this was a concurrent conflict, meaning both clients are current, or a former client conflict, meaning the rules and the remedies are different. And critically, when did the firm find out about the conflict in the first place, because a waiver drafted six weeks after the firm quietly noticed the overlap and kept working the file anyway reads very differently than one drafted the day the conflict was flagged.

This is actually the exact reason conflict checks in Casely run automatically the moment a name gets typed into intake, across the firm's entire contact and matter history, not as a manual search someone has to remember to run in a separate tab. Because the timestamp on that automatic check becomes part of the record. It's not "we believe we caught this early," it's a system generated entry showing the exact moment the name was typed and the exact moment the match surfaced. That single data point ends up mattering more than people expect when a waiver gets challenged later.

What a defensible waiver file actually needs

Let me be very honest about this part, because I've sat with managing partners going through their old files after a scare, and the pattern is always the same. The letter is fine. Everything around the letter is missing. So when I think about what the record should actually contain, it's not one document, it's a sequence of facts that any reasonable person, or any bar counsel, could reconstruct without asking the attorney to remember what happened eight months ago.

That last item is the one firms skip most often, and it's usually the one that matters most if things go sideways, because a firm that says "we screened the conflicted attorney" but can't show when the screen actually took effect in the system is making a claim it can't back up.

The sequence that should exist before the letter is ever drafted

If you walk through how this should actually happen in order, it looks something like this, and honestly most of the malpractice exposure I've seen traces back to a step in this sequence getting skipped or done out of order.

Notice that the letter is near the end of that sequence, not the whole of it. If a firm's actual process is "draft letter, get signature, move on," they've built a record with a hole in the middle of it, because there's no evidence the analysis and the conversation happened before the consent was requested.

The part that keeps mattering after the signature

This is where I think most conflict waiver processes actually fail, not at the drafting stage but afterward, because a waiver usually comes with a promise, something like "the conflicted attorney will be screened from this matter," and that promise needs to be enforced, not just written down. If the wall is just a note in a shared drive telling people not to talk to a certain colleague about a certain file, that's not a wall, that's a suggestion, and a suggestion doesn't hold up when someone gets deposed about it.

That distinction, a hidden button versus a blocked API call, is the difference between an ethical wall a firm can describe in a letter and an ethical wall a firm can actually prove existed when someone asks. In Casely this is enforced at the server, meaning role based permissions decide what a screened attorney can see and do across documents, matters, notes, and trust activity, and that decision doesn't depend on the person remembering not to click into a file.

Why this compounds as a firm grows

A five attorney firm can mostly get away with a weak process here because the number of overlapping clients is small enough that someone usually notices, and so the risk stays low even when the record is thin. That stops being true almost immediately once a firm scales past a certain size, and this is something I hear from firms constantly once they've been running on Casely for a year or two, which is that the volume of contacts and matters grows fast enough that manual conflict awareness just becomes unreliable, not because anyone got careless but because nobody can hold thousands of prior clients in their head while reviewing a new intake.

That last number is the one I'd point to if I were explaining this to a partner who's still doing conflict checks by asking around the office, because "did anyone here work with this person before" is not a search, it's a hope, and hope is not something you want sitting in a malpractice file next to a waiver letter.

Where firms actually get exposed

The scenario I've heard described most often by firms after the fact isn't a firm that missed an obvious conflict, it's a firm that caught the conflict, handled it reasonably, and then couldn't prove any of it two years later because the proof lived in someone's memory or in an email thread that got archived and forgotten. The waiver letter survived. The context around it didn't. And bar counsel, or opposing counsel in a disqualification motion, doesn't care that the firm probably did the right thing, they care what the record shows, and a record that's just a signature with no timeline behind it reads as thin no matter how careful the actual work was.

So when I talk to firms about this, the advice isn't really "get better at conflicts," most firms are already careful, it's "make sure the carefulness leaves a trail," because the trail is the only thing anyone outside the room will ever see. A conflict check that timestamps itself the moment a name is entered, a waiver scope that's specific instead of boilerplate, a wall that's enforced at the system level instead of by memory, and an access log that can be pulled on demand, that's not extra paperwork, that's the actual defense if this ever gets tested. And so yeah, that is basically the whole case for it.