Product Liability Forms for Engineering Firms

How Engineering Firms should think about occurrence vs claims-made coverage

Occurrence and claims-made are two different ways an Product Liability policy "triggers" — meaning, decides whether a claim is covered.

• Occurrence: the policy responds to claims arising from events during the policy period, regardless of when the claim is filed. A claim filed 5 years after the event is still covered by the policy in effect when the event occurred.
• Claims-made: the policy responds to claims filed during the policy period (regardless of when the event occurred), provided the event happened after the retroactive date. The policy must remain in force for coverage to apply.

For Engineering Firms on professional services firm risks, occurrence is generally preferred for liability lines because losses can take years to surface. Claims-made requires careful retroactive date and tail coverage management.

Tail coverage (ERP) on Engineering Firms Product Liability

Tail coverage on Engineering Firms claims-made Product Liability policies is the safety net for long-tail exposures. professional services firm losses can surface years after the event; without a tail, the claims-made policy in effect when the event occurred (now expired) cannot respond.

The two paths to tail coverage: (1) buy an ERP from the expiring carrier, or (2) get the new carrier to set the retroactive date back far enough to cover prior years. Path 2 is usually cheaper but harder to negotiate; path 1 is always available but more expensive.

How form breadth affects Engineering Firms Product Liability

Some Product Liability lines (notably property and inland marine) offer multiple form breadths:

• Basic: covers named perils only (fire, lightning, vandalism, etc.)
• Broad: adds more perils (sprinkler leakage, falling objects, weight of snow, etc.)
• Special: covers all risks of physical loss except those specifically excluded — broadest and usually preferred

For Engineering Firms, special form is generally the recommendation for property and equipment lines. The premium difference vs broad form is usually small relative to the coverage difference.

Scheduling vs blanketing on Engineering Firms Product Liability

Coverage structure on Engineering Firms Product Liability affects both administrative burden and claim-time response. Scheduled coverage works when inventory is stable and well-documented; blanket coverage works when inventory changes or the engineering firm prefers operational simplicity.

The hidden hazard on scheduled coverage is coinsurance — if individual values are understated and the loss exceeds the listed value, the carrier pays only proportionally. Blanket coverage typically avoids this issue (within the overall limit).

Replacement cost vs actual cash value on Engineering Firms Product Liability

Property and inland marine on Engineering Firms Product Liability can be valued either at replacement cost (RC) or actual cash value (ACV).

• Replacement cost: carrier pays to replace damaged property with new equivalent, regardless of depreciation
• Actual cash value: carrier pays replacement cost minus depreciation — so older property is worth less

RC is almost always preferred for Engineering Firms. The premium difference is usually small; the claim-time payment difference can be enormous, especially on older equipment or buildings. The exception is for items that depreciate quickly and where replacement at depreciated value is acceptable (some inland marine items).

The price-vs-coverage tradeoffs on Engineering Firms Product Liability forms

Engineering Firms Product Liability pricing varies meaningfully with form choices, but the variation usually buys real coverage rather than just adding cost. The standard recommendations (special form, RC, occurrence, blanket endorsements) typically add 10-25% to base premium and produce materially better claim-time outcomes.

Going the other way — basic form, ACV, claims-made, scheduled — saves premium but creates exposure that often shows up at claim time. For most Engineering Firms, the savings don't justify the risk.

Picking the right Product Liability structure for Engineering Firms

Form selection on Engineering Firms Product Liability should follow operational reality, not generic templates. The questions to ask: which contracts require specific form features? Which exposures actually exist in our operation? Where do we have the most claim history? What's the engineering firm's risk tolerance on claim-time disputes?

For most Engineering Firms, the answer is broad form, special form, replacement cost, occurrence, blanket endorsements. This combination handles 80-90% of contractual requirements and exposure types without customization. The exceptions are worth identifying explicitly rather than discovering at claim time.