Conflict Checks and Engagement Letters Are Billable in Theory

At a mid-sized law firm in Omaha — eight attorneys, two practice groups, a matter history going back fifteen years — the conflict check on a new engagement runs like this: someone pulls up the master spreadsheet, searches for the prospective client’s name and any related entities, cross-checks the opposing-party field, sends an email to the two partners who might remember adjacent matters, and waits. The intake coordinator follows up the next morning. Sometimes the turnaround is same-day. Sometimes a potential conflict surfaces three days in, after the client has already had a substantive call with the partner.

That gap — between the point a prospective client calls and the point the firm actually knows whether it can take the matter — is not a small administrative inconvenience. It’s the window in which the firm has either left money on the table waiting, or moved forward on a matter it should have declined, or done both. The firms that have solved it aren’t running bigger intake teams. They’ve changed where the conflict check lives in the workflow.

Why conflict checks are broken at most mid-sized firms

The core problem is that conflict checks are treated as a clerical task rather than a knowledge task. They are clerical in execution — someone is looking through records — but they require knowledge to do well: knowledge of entity relationships, of adverse parties in past matters, of clients whose interests could conflict in ways that don’t show up if you search only by the exact legal name on the engagement letter.

A spreadsheet with fifteen years of matter history doesn’t carry that relational context. Neither does a manual search through the firm’s document management system unless someone built a very careful index. The result is a conflict check that catches obvious conflicts — the adverse party whose name matches exactly — and misses the harder ones: the entity whose parent company is the other side of an ongoing dispute, the former client whose interests are now adverse to a prospective client on a related question of law.

The time cost is real too. Thirty to forty-five minutes per new matter intake is a reasonable estimate for a check done thoroughly. That time is typically unbilled. The intake coordinator isn’t on the clock for the client. The partner who digs through her memory for adjacent matters isn’t billing that time either. It’s overhead, accepted because the alternative — a conflict that surfaces mid-matter — is much more expensive.

The matter-history-aware conflict pattern

What changes when this is built correctly is that the conflict check draws on structured matter history rather than a spreadsheet search. The firm’s existing matter records — client names, adverse parties, matter types, dates, practice areas — are the input. The pattern runs a search across that corpus when a new intake form comes in: prospective client name, any related entities the intake form identifies, and the nature of the matter.

The output is a conflict report, not a conflict decision. That distinction matters. The report surfaces potential hits: matters where the prospective client or a related entity appeared, matters where the adverse party overlaps, matters where the matter type suggests adjacent interests. It flags the hits by confidence level — exact name match versus related-entity inference versus looser association. The attorney reviews the flagged items and makes the call.

What the pattern doesn’t do is automate the ethical determination. Whether a conflict is waivable, whether a screen is appropriate, whether prior representation creates a current conflict — those are judgment calls that belong to a licensed attorney under professional conduct rules. The tool surfaces the facts; counsel applies the rules.

In practice, for a firm with well-maintained matter history, a check that previously took 30 to 45 minutes runs in a few minutes for most new matters, with the remaining time spent on attorney review of flagged hits rather than on data gathering.

Engagement-letter draft from the same data

The same intake data that feeds the conflict check can produce an engagement-letter draft. This isn’t a complicated observation, but firms rarely close this loop.

A new matter intake form captures the client name, the matter type, the scope of representation, the fee arrangement, the billing contact, and any retainer terms the partner has discussed. All of that goes into the engagement letter. None of it requires the drafting attorney to synthesize anything — it requires someone to move structured information from one place into a document that follows a template the firm has already approved.

The draft produces a letter built from the firm’s standard engagement-letter template, populated with the intake data, flagged in the places where the attorney needs to confirm or adjust (scope language, rate carve-outs, specific matter terms). The partner reviews a draft that’s 80 to 90 percent right rather than starting from a blank template.

The time savings here are modest per matter — fifteen to twenty minutes for a competent drafter who knows the template — but they add up across intake volume, and they shift the partner’s time from assembly to review, which is where legal judgment actually lives.

Where the partner still has to read

Two places require attorney attention that the pattern cannot replace.

The first is the conflict determination. The report can flag a prior representation of a company in the same industry as the adverse party. It cannot evaluate whether that representation creates a material limitation on the current engagement under Rule 1.7. That evaluation requires someone who knows the facts of both matters and understands the applicable professional conduct rules. No conflict check is complete until an attorney has read the flagged hits and signed off.

The second is the scope language in the engagement letter. The intake form captures what the client and partner discussed in the intake call. It does not capture the nuance of what the firm is agreeing to cover and what it is explicitly carving out. Scope disputes are among the most common sources of client-firm friction, and the scope paragraph is the one place in the engagement letter where a draft built from structured intake data requires the partner to read carefully rather than skim.

Flagging both of these explicitly in the workflow — so the partner knows exactly where the draft needs her eyes — is more useful than flagging nothing and hoping she catches it.

What it looks like during a busy intake week

A litigation partner at a mid-sized Omaha firm takes three new matter calls on a Tuesday. Each caller describes the matter briefly; the partner asks for names of related entities and the nature of the dispute.

By the time the partner finishes the third call, the intake coordinator has submitted the intake form for all three. The conflict check runs against the firm’s matter history on submission. Thirty minutes later, two matters come back clean. One flags a prior engagement where the firm represented a company in a related transaction three years ago, and a related entity of the prospective client was an adverse party. That hit goes to the partner for review. She reads the flagged prior matter, concludes the prior engagement is sufficiently attenuated, and documents her determination.

For all three matters, an engagement letter draft is in her queue before end of day. She edits the scope language on two of them, adjusts a rate term on one, and sends all three for client execution by 4:30 p.m.

Under the prior workflow, the conflict check on the flagged matter would have surfaced the next morning, after someone tracked down the partner who handled the prior engagement. The engagement letters would have been drafted by the associate the following day. A week with three new matters would have consumed a morning of intake overhead. Instead, the partner spent forty minutes reviewing drafts and one conflict hit.

For more on how Blue Sage approaches billable-hour recovery for Nebraska law and professional services firms, see the professional services practice.