Vicarious Liability for Subconsultants
When a design firm prime contracts and subcontracts portions of the work, the owner's agreement is generally with the prime. An owner alleging a design error will typically look to the prime, whether the error originated in the prime's own work or in a subconsultant's. Professional liability policies commonly cover the insured's vicarious liability for subconsultants. What they generally do not do is cover the subconsultant itself. The subconsultant is not an insured under the prime's policy, so the prime's coverage responds to the prime's liability and then the prime, or its carrier through subrogation, looks to the subconsultant and its policy for recovery. That makes the subconsultant's own coverage the prime's practical protection. A subconsultant without professional liability coverage, with inadequate limits, or with a retroactive date postdating the work is an uncollectible indemnity, which means the prime's own policy bears the loss alone.
- The prime is generally answerable to the owner for the whole design
- Professional liability typically covers the insured's vicarious liability for subconsultants
- The subconsultant is normally not an insured under the prime's policy
- A subconsultant with no coverage or inadequate limits leaves the prime carrying the loss
What to Require From Every Subconsultant
The requirements are straightforward and the enforcement is where firms slip. Each should be in the subconsultant agreement, verified before work begins, and confirmed at each renewal during the project. Professional liability coverage at a limit proportionate to the subconsultant's scope and to the project's exposure, not simply a round number. A retroactive date on or before the date their work begins, which is what makes claims made coverage meaningful. Confirmation that coverage will be maintained for a stated period after completion, since design claims surface years later and a subconsultant that drops coverage after the project leaves nothing to recover against. Indemnity language matched to the standard of care rather than a broader warranty, because professional liability policies generally do not cover liability assumed under a contract that exceeds the professional standard of care. An indemnity that promises more than negligence based liability may be uninsurable in the part that exceeds it. Certificates and, for significant scopes, confirmation of the actual policy form are the verification step. A certificate alone does not reveal a retroactive date problem.
- Professional liability limits proportionate to scope and project exposure
- A retroactive date on or before the start of their work
- A commitment to maintain coverage for a stated period after completion
- Indemnity tied to the standard of care, not a broader warranty
- Verification before work starts, and again at each policy renewal during the project
Joint Ventures Need Their Own Answer
A joint venture is a separate legal entity, and that single fact creates the issue. Many professional liability policies cover the named insured and, often, its liability for joint ventures only to the extent of its interest, or only where the joint venture has been declared. Some exclude joint ventures entirely unless specifically endorsed. The result is that two firms with good individual policies can form a joint venture with no coverage for the joint venture itself. A claim naming the joint venture then faces a threshold coverage question before anyone reaches the merits. Three approaches are common. The joint venture can buy its own project specific professional liability policy, which is the cleanest answer for a significant venture and often what an owner requires. Each partner can endorse its own policy to cover its participation in the named joint venture, which requires both carriers to agree and each firm's limits to be adequate. Or the parties can rely on individual policies covering their respective scopes, which works only where the scopes are genuinely separable and the joint venture itself is unlikely to be named, which is rarely the case. Whatever the approach, declaring the joint venture to both carriers before work begins is the non negotiable step.
- A joint venture is a separate entity and may fall outside both partners' policies
- Some forms cover joint venture liability only to the extent of interest, or only if declared
- Options include a project specific policy for the venture, endorsements on each partner's policy, or reliance on separable scopes
- Declare the joint venture to both carriers before work begins
Delegated Design and Specialty Subcontractors
A related exposure arises when design responsibility is delegated to a trade contractor. Curtain wall, structural steel connections, precast, fire protection, and mechanical systems are commonly designed by specialty contractors or their engineers, with the design professional reviewing submittals rather than performing the design. The coverage question is the scope of the design professional's own responsibility. Reviewing a submittal for general conformance with design intent is a narrower duty than designing the element, and the contract should say so clearly. Where the contract is vague, the design professional may be argued into responsibility for a delegated design it never performed. The practical steps are to define delegated design scopes explicitly in the contract, state the review standard in the contract and on the submittal stamp, require that delegated design be performed and sealed by a licensed professional, and require that the delegated designer carry professional liability coverage. A trade contractor whose engineer has no coverage leaves the shortfall somewhere, and that somewhere is usually the prime design professional.
- Define delegated design scopes explicitly rather than leaving them implied
- State the submittal review standard in both the contract and the stamp language
- Require delegated design to be sealed by a licensed professional
- Require professional liability coverage from the delegated designer
Limits, Aggregates, and Project Specific Options
Practice policies are written on an annual aggregate shared across every project the firm has ever done. One significant claim, or several moderate ones, can consume the aggregate and leave the firm exposed on everything else in progress. That is the argument for project specific professional liability on large or unusual projects: a dedicated limit for that project, typically with a term extending through completion and a discovery period after, that does not erode the practice policy. Owners on major projects frequently require it. For a joint venture, it also resolves the entity coverage question in the same instrument. For firms relying on their practice policy, the aggregate is worth examining against the total portfolio of work in progress rather than against any single project. A firm whose largest project exposure approaches its annual aggregate is carrying concentration risk even if no claim has arrived.
- Practice policy aggregates are shared across all projects and all prior work
- Project specific coverage provides a dedicated limit that does not erode the practice policy
- Project specific terms generally run through completion plus a discovery period
- Compare the aggregate against total work in progress, not against one project
Frequently Asked Questions
This article is for general information and is not a substitute for policy language or professional advice.