What Is Professional Liability Insurance? Complete Guide 2026

Professional liability insurance covers the financial harm your vendors cause through their work, which is the exposure their general liability policy specifically excludes.

Your vendor’s certificate showed active professional liability at project kickoff. The design defect appeared four years later. By then the vendor had switched carriers twice, and the policy that covered your project no longer exists.

That outcome doesn’t require anyone to make a mistake. Professional liability is written on a claims-made basis, so it responds only while the policy stays active. A certificate confirms coverage at the time somebody issued it, which means verifying at kickoff answers a narrower question than most compliance programs assume.

This guide covers what the coverage handles, which vendors need it, what to require in your contracts, and how to verify coverage that has to survive years past the work it protects.

What Professional Liability Insurance Covers

Nobody gets hurt and nothing gets broken. A professional liability claim comes from a vendor’s advice, their work product, or their professional judgment, and the loss shows up on your balance sheet instead of your property.

What Triggers Coverage

Four situations trigger the coverage:

• Errors in professional work: A structural calculation comes back wrong, a contract gets drafted with a defective clause, or a system architecture can’t handle the load it was designed for.
• Omissions: The vendor leaves out something their professional standard required, like a code requirement an architect failed to incorporate or a disclosure an accountant failed to make.
• Negligent performance: The work falls below the standard a reasonable professional in the field would have met, whether or not the vendor recognized it at the time.
• Negligent failure to deliver: The vendor’s work product fell short of what they were engaged to produce because of an error or omission in performing the service. A pure breach is different, since missing a deadline you negotiated is a contract claim, and the policy responds only where a professional failure caused the shortfall.

Every one of those failures costs you money. An architect’s design error could push your opening date back six months, so you carry the costs on a building you can’t use. Or a consultant’s platform recommendation could burn a quarter of implementation spend before anyone catches a major incompatibility. In both cases, the vendor’s general liability policy doesn’t do anything because nothing was damaged and nobody was hurt.

What Professional Liability Doesn’t Cover

Professional liability answers for financial harm caused by professional services, which leaves four categories uncovered that hiring parties routinely assume the policy handles:

• Bodily injury and property damage: General liability handles both, which is why a vendor performing physical work with a judgment component needs both policies and why neither one alone covers your exposure.
• Intentional acts and knowing violations: A vendor who misrepresented their qualifications or deliberately cut a corner has done the one thing their policy specifically won’t answer for, so the coverage you’re relying on disappears precisely when the vendor’s conduct was worst.
• Fraud and dishonesty: Most forms carve these out while preserving a limited defense obligation until a court establishes the conduct. Once established, the carrier recovers what it spent on defense and you’re pursuing an individual with no insurance behind them.
• Contractual liability beyond the professional standard: Professional liability responds to negligence, not to promises. A vendor who guaranteed a specific result in your contract took on an obligation their carrier never agreed to cover, which means the performance guarantee you negotiated hard for may be uninsured.

The coverage is broadest where your vendor was merely wrong and narrowest where they were culpable, so the failures that feel most deserving of recovery are the ones the policy is least likely to fund. Your indemnification provisions, any bond you require, and the vendor’s own balance sheet have to cover what the policy carves out.

What a $1 Million Limit Buys Now

Among design professionals, the average loss on the first $1 million of professional liability coverage nearly doubled between 2019 and 2023, climbing from $260,000 to $500,000 while claim reporting frequency stayed flat. That means claim severity accounted for the entire increase.

The requirement you wrote into your vendor agreement five years ago now protects you against a materially smaller share of a typical loss. Most standard contract templates haven’t moved, so companies are carrying limits calibrated to a loss environment that ended several years ago.

There’s a second reason the limit buys less than it looks like. Most professional liability policies pay defense costs from inside the limit, so every dollar spent on lawyers is a dollar unavailable to settle the claim. A vendor carrying $1 million who spends $400,000 defending a case has $600,000 left for you.

General liability usually works the other way, with defense paid outside the limit, which is why a $1 million professional liability limit and a $1 million general liability limit are not the same amount of protection. Ask whether a vendor’s policy pays defense inside or outside the limit before you accept the number on the certificate.

Professional Liability vs. General Liability

Your vendor’s liability splits between two coverages that respond to different failures. General liability insurance handles physical damage the vendor causes, while professional liability handles financial loss the vendor’s work causes. Almost every coverage question you’ll face about a vendor comes back to which side of the line their failure falls on.

Here’s how the two policies compare:

Occurrence coverage responds to incidents that happened during the policy period no matter when the claim gets filed. Claims-made coverage responds only while the policy remains active. Two vendors on the same project, both fully compliant with your requirements, will behave completely differently three years after they finish.

The Design-Build Exposure

A design-build subcontractor carries one general liability policy that covers their construction operations while excluding their design work on the same project, which means their concrete placement is insured and their design of that concrete placement isn’t. The certificate gives you no indication of the split, so a sub with $2 million in general liability and a professional services exclusion nobody read passes your compliance check while carrying nothing for the decisions that make them a design-build firm.

What that uncovered half costs is a matter of record. Among insurers writing professional liability for architects and engineers, 82% paid a claim above $1 million in 2025, with 13% paying one between $10 million and $19.9 million, and structural engineering ranked as the highest-severity discipline for 80% of those carriers.

Construction is where you’ll see that split most easily, though it applies anywhere a vendor makes decisions as well as performing physical work. An IT integrator’s general liability answers for the server rack a technician drops, while the same integrator can design an architecture that takes your order system down for three days without damaging anything their policy recognizes. Sorting your vendors by which policy answers for their worst plausible failure tells you how to set insurance requirements by vendor category before the contract goes out.

Professional Liability, E&O, and Professional Indemnity

Professional liability, errors and omissions, and professional indemnity generally describe the same coverage, and the name a vendor uses reflects their industry convention instead of a difference in what the policy does.

Technology firms, financial services companies, insurance agencies, and real estate brokerages call it E&O. Architects, engineers, and consultants call it professional liability. Professional indemnity is the British and Commonwealth term, so it turns up on certificates from vendors with UK, Canadian or Australian parent companies. Healthcare and legal vendors often call it malpractice coverage, which is the same product under the name their own professionals use.

None of that changes what you’re verifying, though. A certificate showing errors and omissions coverage at $2 million per claim gives you what a certificate showing professional liability at $2 million per claim gives you, assuming the policy form and the retroactive date check out.

When the Name Signals a Different Product

Note that technology E&O and standard professional liability are not interchangeable products, because technology E&O forms frequently bundle cyber liability, first-party breach response, and network security coverage that a conventional professional liability form omits entirely.

Where cyber and professional services share a single limit, a breach response can consume the coverage before your professional services claim reaches it. A vendor holding $2 million in combined technology E&O and cyber has considerably less available to you than a vendor holding $2 million in professional liability with cyber written separately.

Ask which structure applies. A vendor whose policy shares limits should carry a higher one, or you should require cyber liability as a separate line with its own limit.

Write your contract requirements around what the coverage must handle instead of what the industry calls it. A requirement naming “professional liability insurance” invites a vendor to argue that their E&O policy doesn’t apply, or to produce a technology E&O form that satisfies the wording while covering something narrower than you intended. Specifying that the vendor maintain coverage for financial loss arising from errors, omissions, or negligent performance of professional services closes that argument before it starts.

Which Vendors Should Carry Professional Liability

Require professional liability from any vendor whose work involves professional judgment, licensed expertise, or a deliverable you’ll rely on to make decisions. The test has nothing to do with whether the vendor wears a hard hat or a suit, and everything to do with whether their mistake would cost you money without breaking anything.

Generally, these seven vendor categories should carry professional liability in almost every engagement:

• Design-build contractors and specialty subs with a design component: Anyone performing delegated design, shop drawing preparation, or engineered systems layout carries an exposure their construction general liability won’t answer for.
• Architects, engineers, and surveyors: These vendors carry the highest claim severity of any category, which makes both the limit and the coverage duration worth setting deliberately.
• IT consultants and system integrators: Their exposure covers architecture decisions, implementation failures, data handling, and the security posture they recommended and you adopted.
• Management and financial consultants: A recommendation you acted on becomes their liability when the recommendation was wrong, though only if the policy exists to respond.
• Staffing agencies placing licensed professionals: The agency’s credentialing, license verification, and placement decisions are professional services in their own right, entirely separate from the malpractice coverage the placed clinician or specialist carries. A facility that verified only the individual’s coverage has confirmed nothing about the agency that vetted them.
• Accountants and financial advisors: Audit findings, tax positions, and valuation opinions all produce claims that arrive years after the engagement closed.
• Marketing and creative agencies: Anything they produce that you publish carries intellectual property, advertising, and regulatory exposure that follows the work into your channels.

Technology limits age faster than any other category. Average ransomware claim costs reached $713,200 in 2025, nearly double the prior year, while incident frequency fell 31%. Severity accounts for the entire move, so an integrator holding a technology E&O limit they set three years ago is holding a number chosen for conditions that no longer apply.

The harder judgment involves the vendor nobody thinks of as a professional. A revenue cycle management firm codes your claims incorrectly and triggers a payer audit. A managed service provider recommends a backup architecture that fails during the outage it was designed for. Neither vendor considers themselves a professional services firm, and the professional services exclusion in their general liability policy applies to them anyway.

Expecting those vendors to raise the issue themselves gets you nowhere. Fewer than half of US small businesses carry professional liability, and 83% of owners can’t correctly describe what the policy covers. Roughly three quarters of them misunderstand general liability as well, and most expect it to respond to a client lawsuit over bad advice. Your requirement has to identify the exposure, because the coding firm and the managed service provider won’t.

Why Claims-Made Coverage Changes Your Compliance Obligation

Professional liability responds only when the policy is active on the day someone files the claim, which means a vendor who carried perfect coverage while performing your work can leave you with nothing years later. Every other coverage in your compliance file behaves the opposite way, and that difference is the single most expensive thing to misunderstand about professional liability.

Rating agencies treat the structure as a cost driver rather than a technicality. AM Best recorded a loss adjustment expense ratio of 17.5 in legal professional liability against 10.5 for commercial casualty, attributing the difference to the claims-made nature of the coverage and to broader social inflation. The same structure that makes these policies workable for carriers is what makes them disappear on you.

The Scenario That Catches Hiring Parties

Imagine your architect completes design work in 2024 carrying $2 million in professional liability, and their certificate goes into your file exactly as your process requires. They retire in 2026 and drop the policy, which nobody tells you about because no one has any reason to. A defect appears in 2027, you file a claim, and no coverage exists to receive it.

Nothing went wrong with your compliance process. You collected the certificate, verified the limits, and confirmed the policy was active when the work happened. The architect also complied with every requirement in the contract, then cancelled a policy they had no obligation to keep. You’re the one left without coverage for that work because a claims-made policy responds to the calendar rather than to the work.

Compare that against the general liability policy from the contractor who built the same project. Under occurrence coverage, the incident happened during the policy period, so the claim responds in 2027 whether or not that contractor still carries insurance. Two vendors, one project, one compliant file each, and completely different outcomes three years later.

Wrap-Up Programs Don’t Cover It

Enrolled subcontractors stop carrying their own general liability and workers’ compensation on a wrapped project, because the master policy handles both. Wrap-up programs exclude professional liability, so every sub performing design or professional services buys and maintains that coverage themselves.

Your design-build subs and delegated design trades still hold their own claims-made policies, still decide when to stop paying for them, and still create the exposure this section describes two years after they demobilize. A general contractor who centralized everything else has centralized nothing here.

Owners sometimes purchase a project-specific professional liability or contractor’s protective professional indemnity policy alongside the wrap, which is a separate placement instead of enrollment. Confirm whether one exists on your project before assuming your design subs are on their own. Our comparison of owner-controlled and contractor-controlled insurance programs covers what enrollment includes.

Retroactive Dates and the Switch Nobody Tells You About

The retroactive date sets how far back a claims-made policy reaches, and coverage stops at that date no matter how long the vendor has been insured. Work performed before it gets nothing.

Vendors switch carriers quite often, chasing price or following a producer to a new agency. A vendor who changes carriers in 2026 can receive a policy whose retroactive date matches the new inception, which erases coverage for the 2023 work they did for you. The limits look identical, the carrier name changed, and the coverage you were relying on no longer exists.

Carriers will usually match the prior date where coverage has been continuous and someone asks for it. That depends entirely on the producer raising the question, and a vendor shopping on price has no idea the question exists. Nothing on the certificate tells you whether anyone asked. Write the retroactive date into your contract as a requirement, then check it on every renewal certificate instead of checking the expiration date alone.

Tail Coverage and How Long to Require It

An extended reporting period, which everyone calls tail coverage, keeps a cancelled policy available for claims filed after it ends. The vendor buys it once, and it covers work already performed within a defined window afterward.

Require it whenever a vendor cancels, non-renews, switches carriers, retires, or dissolves during the period your exposure remains open. That last situation matters most, since a dissolved firm has nobody left to negotiate with and their principals have moved on to other employers.

Setting the duration is where most contracts pick a round number and get it wrong. Tie the requirement to the statute of repose in the state where the work happened for construction and design vendors, or to the applicable statute of limitations for everyone else, which usually covers a shorter period and begins when someone discovers the harm.

Expect resistance, because tail coverage typically costs 150% to 200% of the expiring annual premium as a single payment. A vendor cancelling their policy has usually decided to stop spending on insurance, and the tail is the largest bill they’ll face on the way out. Putting the requirement in the contract before the engagement starts is the only version of this conversation you’ll win, since a vendor already dissolving has no incentive to negotiate.

What a Certificate Tells You and What It Doesn’t

A certificate confirms that coverage existed on the day somebody prepared the document. For occurrence-based general liability, that’s most of what you need. For professional liability, it doesn’t answer the questions that actually determine whether coverage responds.

The certificate won’t tell you whether the retroactive date moved at the last renewal, whether the vendor purchased tail coverage when they switched carriers, or whether the policy cancelled last month for nonpayment. Reading it as proof of continuing coverage is the mistake that turns a compliant file into an uncovered claim. Our explanation of how claims-made and occurrence policies differ covers the mechanics behind both forms.

What to Require in Your Contracts

Your professional liability requirements need five provisions that general liability contracts never contemplate, because the coverage can disappear while the vendor remains fully compliant with everything else you asked for.

Start with limits appropriate to the exposure:

Adjust those against contract value and the size of the decision the vendor influences. A $40,000 engineering study supporting a $12 million build justifies a limit that looks disproportionate to the fee, because the fee has nothing to do with the exposure.

The remaining three provisions handle the timing problem. Require the vendor to maintain coverage for a defined period after completion, tied to the statute of repose where the work happened, or to the applicable statute of limitations for non-construction vendors. Require tail coverage if they cancel, non-renew, switch carriers, or dissolve during that period. Require a retroactive date reaching back to at least the start of your engagement, with written confirmation at each renewal that the date hasn’t moved.

Statutes of repose govern construction and design work. Your exposure to consultants, technology vendors, staffing agencies, and financial professionals follows the applicable statute of limitations instead, which usually covers a shorter period and begins when someone discovers the harm instead of when the vendor finished. Ask your counsel which period applies to each vendor category before you write a number into your template.

The fifth provision makes the other four enforceable. Require annual certificates for the full period instead of the project duration, since most compliance processes stop collecting the moment the vendor’s work ends, which is the exact point at which professional liability starts mattering.

Additional Insured Status Usually Doesn’t Apply

You generally can’t obtain additional insured status on a vendor’s professional liability policy the way you can on their general liability.

Carriers underwrite these policies against the qualifications and claims history of one specific professional, so extending coverage to an unrelated party undermines the basis they priced. Some miscellaneous professional and technology E&O forms do offer a limited endorsement covering your vicarious liability for the vendor’s services, though it never reaches your own professional acts. Ask whether it’s available and expect the answer to be no.

That removes the contractual path you rely on everywhere else. With general liability, an additional insured endorsement places you under the vendor’s policy directly. With professional liability, your protection consists of the limit the vendor bought and how long they keep it in force, which is why the contract provisions above carry the weight that an endorsement would otherwise carry. Our guide to additional insured and named insured status covers how the endorsement works where it is available.

How to Verify Professional Liability on a Certificate

Check the policy form, the retroactive date, the policy period, and the limits. A certificate rarely states the retroactive date unless somebody asked for it, so require it in the Description of Operations box and confirm it falls before the work starts.

What Appears on the ACORD 25

Professional liability rarely gets a dedicated section on the ACORD 25. The producer enters it under “Other” near the bottom of the form, which means the coverage that carries your largest exposure appears in the space designed for whatever didn’t fit above.

Four things belong in that entry:

• Policy form: Marked claims-made or occurrence, and this determines which set of rules governs everything else you check.
• Retroactive date: Establishes how far back the policy goes, so any work you contracted before that date falls outside coverage.
• Effective and expiration dates: Define the current policy period, which is a narrower piece of information than most people treat it as.
• Per claim and aggregate limits: Show what’s available in theory, though the aggregate reflects nothing about claims other clients have already filed against it.

A professional liability entry with no retroactive date shown is incomplete rather than reassuring. Producers omit it regularly, and the omission tells you nothing about whether the date exists or where it falls. Ask for it in writing before accepting the certificate.

What the Certificate Can’t Show You

Four questions determine whether a professional liability policy will respond, and the ACORD 25 answers none of them:

• Whether the retroactive date moved at renewal: The certificate shows today’s date, not last year’s, so a reset that erased coverage for your earlier work looks identical to a date that never changed.
• Whether the vendor purchased tail coverage: Nothing on the form records an extended reporting period, which means a vendor who cancelled and bought tail looks the same as one who cancelled and bought nothing.
• What the policy excludes: Professional liability forms vary far more than general liability forms, and a technology E&O policy might exclude bodily injury arising from the vendor’s work in ways that surprise you when a claim tests it.
• How much of the aggregate remains: A $2 million aggregate that already paid $1.6 million on another client’s claim still prints as $2 million on your certificate.

Few vendors will hand over their policy documents, so rely on your own records and your contract. Comparing each renewal certificate against the one before it will show you if the retroactive date changed. For the rest, require the vendor to buy tail coverage if they cancel or switch carriers, carry a policy that covers your scope of work, and to tell you in writing when paid claims drop their aggregate below your required limit.

The Verification Sequence

Work through these checks on every professional liability certificate before the engagement starts:

1. Confirm the policy form is claims-made: Occurrence-based professional liability exists but is rare, and knowing which form applies determines every other check on this list.
2. Verify the retroactive date predates your engagement: Ask the vendor to have their broker list the retroactive date on the certificate. If the date falls after your work started, then the policy won’t cover that work at any limit.
3. Check the policy period against today: The issue date tells you when somebody prepared the document, not whether coverage survived the months since.
4. Match the named insured to your contracting entity: A policy covering the parent company won’t necessarily respond to work performed by the subsidiary that signed your agreement.
5. Confirm the limits meet your contract: Check both per claim and aggregate, since a vendor working for many clients shares that aggregate across all of them.
6. Verify the carrier’s financial strength rating: A limit only matters if the company behind it can pay.
7. Set the renewal request ahead of expiration: Requesting on the expiration date gives the vendor no time to produce the replacement before coverage lapses in your file.

Our guide to reading a certificate of insurance covers what the rest of the form tells you.

When a Vendor’s Professional Liability Claim Gets Denied

A denial puts you exactly where the vendor’s coverage was supposed to prevent you from ending up, pursuing a business with no insurance for a loss their policy was written to absorb. Somebody still pays the claim, and your options narrow to your own policy, your own balance sheet, or an indemnification provision worth whatever the vendor can actually fund.

The Five Ways a Claim Gets Denied

Each denial traces back to something a verification step would have caught:

• The retroactive date moved: Coverage never reached back to your engagement, so the policy that looked active on your certificate excluded the work it was supposed to cover.
• The policy lapsed before the claim: Claims-made coverage responds only while active, which means a vendor who dropped the policy after finishing your project has nothing to tender when the problem appears.
• The aggregate was exhausted: Other clients filed first, and the $2 million printed on your certificate had already gone out the door before anyone read your claim.
• The conduct fell inside an exclusion: Intentional acts, guaranteed outcomes, and carved-out activities all produce denials, and they tend to appear in the cases where the vendor’s failure was most egregious.
• The vendor reported late: Claims-made policies carry strict notice requirements, so a vendor who sat on your complaint for six months before telling their carrier can forfeit coverage they were otherwise entitled to.

A Denial in Practice

Your facility contracts with a healthcare staffing agency for per diem clinical coverage. The agency’s contract requires $2 million in professional liability, they produce a certificate at onboarding showing exactly that, and your compliance team files it after confirming the limits and the policy period.

Eighteen months into the relationship, a patient files a malpractice action naming both the placed clinician and your facility, alleging the agency credentialed someone whose license had been suspended in another state. The agency tenders the claim to their professional liability carrier.

The carrier denies it. The agency switched carriers fourteen months ago, chasing a lower premium after a broker recommendation. Their new policy carries a retroactive date matching the new inception, and the placement in question happened three months before that date. The certificate your team collected showed $2 million in active professional liability, and every word on it was accurate.

Your facility now defends the action on your own policy. Your recourse against the agency consists of the indemnification provision in your services agreement, enforceable against whatever assets a mid-sized staffing firm holds after their own defense costs.

What You Can Do Before It Happens

None of the five denial paths are invisible, and each one has a contractual answer:

• Require notice of cancellation or material change directly to you: A vendor’s carrier will send it to the vendor. Your contract should require the vendor to forward it within a defined number of days, with a breach provision behind the requirement.
• Verify the retroactive date at every renewal: Checking the expiration date catches lapses. Checking the retroactive date catches carrier switches, which is the failure that produced the denial above.
• Require a dedicated or per-project aggregate: A vendor’s professional liability aggregate covers every client they serve, so claims from other engagements can draw it down before yours arrives. Set your required limit with that in mind, and require the vendor to notify you when paid claims bring the aggregate below it. Project-specific policies do exist for some large engagements,
• Address the exclusions in your indemnification: Intentional acts, guaranteed outcomes, and carved-out conduct fall outside the policy permanently, so your indemnity provision and any bond you require have to reach what the carrier never will.
• Require prompt notice of potential claims: Require the vendor to notify both you and their carrier within a defined number of days of any circumstance that could produce a claim. This protects their coverage from a late-reporting denial and gives you warning before a complaint arrives.

Tracking Professional Liability After the Work Ends

Professional liability is the only coverage in your compliance file that needs to be monitored for years after the vendor finishes, and almost no manual process survives long enough to do it.

Your project closes and the vendor moves off your active list. Their file stops appearing in whatever report your team reviews, because that report tracks vendors currently performing work. Nothing prompts anyone to request a 2029 renewal certificate for design work completed in 2026, and the vendor who quietly drops coverage in 2028 has no reason to mention it. The person who set up the original file has usually moved to another role by then, and their replacement only inherits a spreadsheet with no explanation of why those rows are still there.

How long you need to keep watching depends on where the work happened. More than thirty states have enacted statutes of repose limiting how long anyone can bring a claim against a contractor or design professional, and the Associated General Contractors notes that a latent defect appearing 15 or 20 years after acceptance can still produce liability where no statute of repose applies.

Your monitoring obligation matches whichever window governs the project, not the length of the engagement. That same window should govern the completed operations coverage you require on the general liability side, so both obligations expire on the same date instead of being set independently by two different templates.

Most compliance programs weren’t designed for that timeframe. A process built around active vendors handles renewals well but doesn’t handle completed projects at all, whether it runs on a spreadsheet or on COI tracking software configured only for current work, which is why professional liability lapses go unnoticed until someone files a claim against work nobody has thought about in four years.

CertFocus by Vertikal RMS keeps those vendors in the system after their work ends. Vendors upload their own certificates, trained reviewers check the policy form and the retroactive date instead of the summary printed on the front, and the platform continues requesting renewals for as long as your requirement period lasts. A certificate confirms coverage at the time somebody issued it, which is exactly why the follow-up matters more here than anywhere else in your program.

Where This Leaves Your Compliance Program

Professional liability breaks the assumption every other coverage in your file lets you get away with. You collect a certificate, confirm the policy is active, and move on, which works perfectly for occurrence-based general liability and fails completely here.

The three checks that matter most take almost no time once you know how to make them. Start by confirming the retroactive date predates your engagement, because a policy that doesn’t reach far back enough makes every other check pointless. Then write the coverage period into the contract so the vendor keeps professional liability in force for as long as your exposure stays open. The last check is the one companies skip, which is asking again in year three and year five instead of filing the certificate and closing the project.

CertFocus by Vertikal RMS handles the first and last of those checks, confirming the retroactive date on every certificate and requesting every renewal until your requirement period ends. Request a demo to see how it works.