Professional liability and Tech E&O for established businesses

Who this page is for

Established professional and technology businesses need an E&O review that begins with the work they perform and the promises they make. A high per-claim limit is useful only when the policy's insured-services definition, claims-made dates, reporting terms, defense provisions, and exclusions fit the exposure.

OnePark Risk can help the business compare an existing program with individually evaluated higher-limit brokerage options, subject to actual placement availability. This process is separate from the site's distinct $1M/$2M cyber and Tech E&O program.

Discuss your professional liability program with a senior broker

Start with a conversation. No application or documents required.

Share five contact details and, if you like, a little context about revenue band, main operating state, and what you want to discuss. A member of the OnePark Risk team contacts you to arrange the next conversation. There is no application, no document upload, and no obligation.

No insurance application or document upload required.

Which professional or technology services are insured?

The professional-services or technology-services definition establishes the work to which the policy's insuring agreement applies. The review should compare that language with websites, proposals, statements of work, invoices, applications, and revenue by service. Accounting, advisory, design, implementation, hosting, managed services, data analytics, software licensing, and support can be treated differently. Work outside the definition is not insured merely because the declarations show a high per-claim limit.

Definitions also need to identify whose work counts. Employees may fit automatically, while independent contractors, subcontractors, acquired entities, joint ventures, and services delivered under another trade name may require specific wording. The policy should be checked for vicarious liability arising from a subcontractor and for whether the subcontractor itself is an insured. New offerings and acquisitions should be reported when the policy requires notice rather than left for an assumption at renewal.

Professional liability generally addresses allegations that defined professional services caused financial loss; Tech E&O applies the same concept to defined technology products or services. Neither label settles coverage. The operative insuring agreement, definitions, exclusions, facts, and applicable law control, so a comparison should quote the relevant wording and identify any activity that remains outside it.

How do customer contracts change the E&O review?

A contract review separates the scope of services from the allocation of liability. A limitation-of-liability clause may cap some damages, while indemnities, warranties, service-level commitments, credits, and carve-outs can create obligations beyond that cap. Counsel should interpret those obligations. The broker's task is to compare them with the policy's insured services, damages definition, contractual-liability exclusion, and any carve-back for liability the business would have had without the contract.

Contractual liability coverage is not a promise that every contractual obligation is insured. An agreement may warrant a particular outcome, accept another party's liability, promise service credits, or impose performance standards that do not qualify as covered damages. The review should identify whether the policy addresses negligent performance, breach allegations, unintentional contractual breaches, or only liability existing independently of the agreement. It should also check exclusions for liquidated damages, penalties, return of fees, and cost to redo the insured's work.

Insurance minimums need their own reading. A customer request for a $5M per-claim E&O limit is different from a $5M annual aggregate, and neither proves that the customer's services or indemnity demand are covered. Certificates summarize insurance but do not amend the form. The contract matrix should record each required amount, basis, duration, and any cyber requirement separately.

What do prior acts, notice, and continuity protect?

Most E&O forms are claims-made, meaning the claim must first be made during the policy period and reported as the policy requires. A retroactive date limits how far back a covered wrongful act may occur; a full-prior-acts provision may remove a stated date but remains subject to other terms. The entity, service, act date, claim date, and report date all matter. A larger current limit does not repair an interrupted retroactive date.

Policies distinguish a claim from a circumstance that might later become a claim. A claim can include a written demand, suit, arbitration, or another proceeding defined by the form. A circumstance notice usually must describe the potential claimant, conduct, alleged harm, and reasons a demand may follow. Timely, sufficient notice can connect a later claim to the earlier policy, but casual correspondence to a broker should not be assumed to satisfy the policy's reporting address and content requirements.

When changing insurers, compare continuity dates, pending-and-prior-litigation dates, prior-knowledge wording, and applications before binding. An extended reporting period, often called a tail, generally extends time to report claims arising from pre-expiration acts; it does not usually insure new work after expiration. Run-off for a sold entity and tail options for the whole policy solve different problems, and their duration and available limit must be stated precisely.

How can defense terms consume or constrain the limit?

Many E&O policies place defense costs inside the per-claim and annual aggregate limits. Legal fees and related expenses then reduce the amount remaining for a settlement or judgment. A $5M per-claim limit with defense inside is not $5M reserved solely for damages. The comparison should show how one claim is defined, whether related claims are combined, which retention applies, and whether defense expense also erodes the annual aggregate.

The duty to defend, a right to defend, and reimbursement of defense costs can produce different control and timing. Panel counsel provisions may require the use of approved firms or rates, while an insured-selected lawyer may need consent. The review should examine advancement of costs, allocation between covered and uncovered allegations, appeals, and whether the retention must be paid before the insurer advances expenses.

Consent-to-settle language determines who approves a resolution. A hammer provision can limit what the insurer pays if the insured refuses a recommended settlement, sometimes to the proposed settlement plus covered expenses incurred to that point or under a stated percentage formula. The exact wording matters. The business should understand decision rights before a dispute, not discover them after defense has already reduced the available aggregate.

Each amount is a per-claim and annual aggregate E&O limit being evaluated, not annual revenue, a cyber limit, or a package recommendation.

When a service failure is also a security event

A technology failure can create customer allegations and the insured's own cyber costs at the same time. For example, a security event may disable hosted software, causing restoration expense and lost income for the provider while customers allege failure to deliver the contracted service. The review should identify whether the Tech E&O part responds to third-party service-failure allegations and whether the cyber part addresses defined response, restoration, privacy, or business-interruption loss.

Combined Tech E&O and cyber forms may use one annual aggregate for both parts, separate coverage-part limits within one policy, or a mixture of headline limits and sublimits. One covered event can be allocated between parts, and payment under one part may reduce the amount left under another. Separate policies can preserve limits but introduce other-insurance, notice, allocation, and defense-coordination questions. Neither structure is automatically preferable.

For a hypothetical professional-services illustration, an advisory firm delivers analysis that a client alleges contains a material error. The review would test whether that advisory work is a defined professional service, whether the engagement's liability cap and indemnity align with policy terms, and how defense erodes the per-claim limit. For a hypothetical software illustration, a flawed deployment coincides with unauthorized access and customer downtime. The review would examine both coverage parts, notices, shared aggregate, waiting period, and allocation without assuming either claim is covered.

What should a higher-limit E&O review produce?

The starting file should include entity and service lists, revenue by service, major contracts, current and prior policies, applications, loss and circumstance history, acquisitions, subcontractor arrangements, and any pending transaction. The broker should create a wording map showing insured services, insured persons and entities, retroactive dates, claims and circumstance reporting, defense, settlement, contractual liability, cyber overlap, exclusions, and each per-claim and annual aggregate amount.

Limit analysis follows scenarios rather than a revenue tier. It should estimate the effect of a major customer dispute, one failure affecting several customers, defense expense, and the possibility of more than one claim during the policy year. Higher-limit options are individually evaluated brokerage placements, subject to actual placement availability. They are not extensions of the site's separate $1M/$2M cyber and Tech E&O program and should not be added to unrelated cyber, D&O, property, or casualty limits.

$10M in annual revenue does not mean $10M of every coverage. Revenue describes the size of the business; each policy limit has to be evaluated against the contracts, loss scenarios, and policy wording that apply to that coverage.

What your senior broker should examine

• Does the insured-services definition include every current professional and technology service, delivery model, and trade name?
• Which limitation-of-liability clauses, indemnities, warranties, and service levels create obligations beyond ordinary negligence?
• Do retroactive dates, continuity terms, acquired-entity provisions, and prior applications preserve the intended prior acts?
• What constitutes a claim or circumstance, where must notice go, and what extended reporting options apply?
• Are defense costs inside the per-claim and annual aggregate limits, and how do panel counsel, consent, and hammer provisions work?
• If one event triggers E&O and cyber allegations, which coverage part responds and is one annual aggregate shared?
• For each higher limit, is the amount per claim, aggregate, primary, or excess, and is it subject to actual placement availability?

Questions businesses ask

Does a higher E&O limit insure every service we provide?

No. The professional-services or technology-services definition controls which work enters the insuring agreement, subject to all other terms. More limit does not expand an omitted service or remove an exclusion.

What is the difference between a claim and a circumstance?

A claim is a demand or proceeding that meets the policy definition. A circumstance is known conduct or an event that might lead to a claim and may be reportable under a separate provision. The policy specifies the content, recipient, and deadline for either notice.

Does an E&O tail cover work performed after cancellation?

Generally, an extended reporting period adds time to report claims arising from acts before the policy ended; it does not insure new post-expiration services. The actual tail endorsement, retroactive date, and run-off terms control.

Should Tech E&O and cyber use one shared annual aggregate?

That depends on the service-failure and cyber scenarios, contracts, and available structures. A shared aggregate can be reduced by either type of covered matter, while separate limits require careful coordination of definitions, notice, and overlapping events.

Are defense costs included in addition to the E&O limit?

Often they are inside and reduce the stated limit, but forms differ. The review should confirm defense treatment, the retention, related-claims wording, counsel provisions, and settlement control rather than infer them from the declarations.

Sources

• Travelers: How does cyber insurance work? — accessed 2026-09-19; supports the explanation that cyber coverage parts may carry different limits, retentions, and first- and third-party functions.
• National Institute of Standards and Technology: Cybersecurity Framework — accessed 2026-09-19; supports the use of structured identification, protection, response, and recovery information when describing technology dependencies.