Published On: October 26, 2026Categories: Business Insurance8.6 min read

If you run a consulting firm, a lobbying shop, a law-adjacent advisory practice, or a technology services company in the DC metro, your liability picture looks fundamentally different from a retailer or a contractor. Nobody slips on your floor. Nothing you sell catches fire. The risk you carry walks out the door every time a deliverable does — in the form of advice, analysis, a report, a recommendation, or code. Errors and omissions insurance is where that exposure lives, and it’s frequently the most misunderstood line in a professional service firm’s entire insurance program.

What E&O Actually Covers (and What It Doesn’t)

Errors and omissions coverage — sometimes called professional liability — pays for defense costs and damages when a client claims your professional services caused them a financial loss. That’s the core. A management consultant’s engagement produces a restructuring recommendation that the client executes and regrets. A government affairs firm’s advice leads to a missed procurement deadline. A technology services company delivers a system integration that fails at go-live. In each case, the client’s argument is the same: your work cost us money.

A standard commercial general liability policy does not respond to these claims. General liability covers bodily injury and property damage from your business operations — it is not designed for, and typically explicitly excludes, claims arising from the professional services you render. If you’re a professional service firm relying on your GL as your primary liability coverage, that’s a gap worth knowing about before a client decides to test it.

E&O policies are claims-made, which is a structural detail that matters more at renewal time than most firms appreciate. Under a claims-made structure, the policy in force when the claim is reported is the one that responds — not the policy in force when the work was done. That means a claim surfacing today from an engagement you completed several years ago lands on your current policy. The retroactive date on your policy — the cutoff before which prior work isn’t covered — is not a number to accept without thinking. If you’ve carried continuous professional liability coverage, you typically want that retroactive date going back to when your firm started doing covered work. We’ve seen renewal packages come through where the retroactive date quietly shifted forward, which can create a coverage gap for prior work even while the client thinks they’re continuously insured.

The DC Metro Factor: Why the Client Mix Changes the Risk Profile

Firms in Bethesda, McLean, Arlington, and the District itself tend to serve a particular kind of client: federal agencies, federal contractors, trade associations, and well-capitalized private-sector companies. That client profile matters for professional liability in a specific way.

Sophisticated clients have sophisticated legal departments. When something goes wrong on an engagement — or even when a client relationship sours for reasons that have nothing to do with the quality of the work — larger clients are more likely to file a formal claim than a small-business client who might just walk away unhappy. This doesn’t mean every dispute becomes litigation, but it does mean the claim environment around DC-area professional firms is different from markets where clients are smaller or less institutionally resourced. We’ve noticed over the years that firms whose client list includes federal contractors, lobbying clients, or large associations should think carefully about their limits and their deductible — not because claims are inevitable, but because when they come, the adverse party typically has professional representation from day one.

The multi-jurisdiction piece adds another layer. A firm headquartered in Rockville with staff in DC and a contract performance location in Northern Virginia is touching all three jurisdictions simultaneously. Professional liability policies don’t always describe coverage territory in the same terms — some are explicit about US-only coverage, others have broader or narrower language. If you’re a government affairs or technology services firm with any international work, even peripheral international work, that’s worth reviewing with your broker before a claim surfaces in an unexpected location.

Cyber Liability and E&O: Two Policies, One Failure Mode

Here’s something that trips up technology consulting firms in particular. When a data breach or a system failure harms a client, the question of which policy responds — your cyber liability policy or your E&O policy — is genuinely not straightforward. Some carriers write these together on a combined policy; others write them separately in ways that create arguable gaps in the middle.

A scenario: a managed IT services firm in Reston handles network infrastructure for a client. A ransomware event originates from an access point the firm managed. The client suffers operational disruption and claims the firm’s failure to implement adequate security controls caused the loss. Is that a cyber claim? An E&O claim? Both? The answer depends on policy language that varies meaningfully across carriers and forms.

We don’t raise this to suggest you need to worry about every possible scenario in theory — just that this is a real placement decision, not a checkbox. Firms whose work touches technology, data handling, or system infrastructure should review how their professional liability and cyber coverages interact rather than assuming both policies will apply neatly if something goes wrong. The time to understand that is when you’re placing the coverage, not after a client’s attorney has framed the demand letter to slot between your policies.

Our E&O placement work typically involves reviewing exactly these coverage interactions — how the claims-made trigger operates, how the retroactive date is set, and whether there are gaps between adjacent policies.

The Contract Question: When Your Client’s Agreement Changes Your Exposure

Almost every professional services engagement in the DC market is governed by a services agreement. And almost every one of those agreements contains indemnification language that affects how a claim actually flows. The problem is that most firms review those contract provisions with a business lens — what do we have to do, what do we get paid — rather than an insurance lens — does this indemnification clause change our coverage position?

Some indemnification obligations in client contracts are insurable; some aren’t. Some professional liability policies have carve-outs for contractually assumed liability that exceeds what you’d owe at common law. That’s not a standard provision that’s identical across all E&O forms — it’s a variable, and it’s one that can matter if your engagement agreement committed you to a broader duty than your policy anticipates.

This is particularly relevant for firms doing work under federal contracts, where the contract language is often imposed rather than negotiated, and the terms don’t necessarily map cleanly onto standard commercial insurance forms. We’d want to look at the actual contract terms before assuming coverage aligns — not as a legal opinion on the contract, but as an insurance coverage question about whether the policy form and the contractual obligation are speaking the same language.

Policy Limits: What’s Enough and Why the Default Might Not Be

There’s a tendency in professional service firm insurance to anchor on whatever limit the firm carried last year, or whatever limit a client contract requires, and call it done. Neither of those is a rigorous way to think about adequacy.

Client contract requirements set a floor, not a ceiling. If a government contractor requires you to carry a certain limit as a condition of subcontract, that’s a business requirement — it may or may not correspond to the actual loss exposure of the engagement. A large technology services engagement for a federal agency, for example, could produce a claim that dwarfs a standard contract-minimum limit if the system failure causes operational disruption across a significant program.

The per-claim and aggregate limit structure of E&O policies also deserves attention. If your firm runs multiple simultaneous client engagements and you have a policy-year where more than one claim arrives — which happens, particularly in volatile client environments — the aggregate limit is the actual constraint. We typically have the conversation about aggregate adequacy and about whether the deductible structure makes sense given the firm’s size and cash flow. A high deductible can reduce premium meaningfully, but it also means the firm is self-funding the early portion of any defense, which for an active dispute can add up before the claim is anywhere close to resolution.

Multi-Jurisdiction Workforce and the Benefits Angle

One more thread worth pulling for professional service firms with staff across DC, Maryland, and Virginia: the employee benefits side of your program has been changing in ways that affect your compliance exposure as an employer.

Maryland is in the process of implementing a paid leave program that will affect employers with employees in the state. The specifics of the implementation — contribution structures, employer obligations, effective timelines — are evolving and worth reviewing with your broker and your employment counsel rather than relying on general summaries. What’s relevant from a group benefits standpoint is that state-mandated leave programs typically interact with your existing short-term disability coverage, and understanding how they stack — or don’t — is a planning question worth getting ahead of. Employers who’ve already thought through the interaction between state programs and their employer-sponsored benefits tend to have a cleaner answer when HR questions surface.

This matters beyond the benefits program itself: professional service firms whose partners or principals are personally exposed to regulatory penalties for employment compliance failures may carry exposure that intersects with management liability coverage, not just their benefits structure.

The Firm That Doesn’t Think It Has E&O Exposure

We encounter this periodically: a professional service firm that has been operating without professional liability coverage — or with a policy that hasn’t been reviewed in several years — on the theory that they haven’t had a claim and their client relationships are good. Both things can be true right up until they aren’t. E&O claims in the professional services world don’t always track the quality of the work; sometimes they track the quality of the client relationship, or the client’s financial situation, or a change in leadership on the client side that turns a collaborative engagement into a contested one. A firm that’s been in business for a while without a claim has been fortunate — and fortune and coverage are not the same thing.

If this is the conversation you’ve been meaning to have about your own firm’s exposure, we’d be glad to walk through it — 301.468.9600 or info@capitalpointins.com.
The Capital Point Insurance Team