Risk transfer in New York construction has always depended on two things: the language in your subcontracts and the certificates of insurance in your files. What changed on April 18, 2026 is the speed at which that language and those files need to be actionable. Before the AVOID Act, a general contractor with imperfect documentation could often recover: locate the missing contract, track down the endorsement, get coverage counsel and defense counsel aligned, and file the third-party complaint before anyone lost their rights. The AVOID Act takes that recovery time away. If your documentation is not ready when service arrives, it may not be ready before your impleader rights expire.
This article describes how the AVOID Act has raised the floor on pre-litigation risk transfer, what contract and COI practices now constitute the minimum standard of care, and how to build a vendor onboarding process that meets that standard.
What pre-litigation risk transfer means
Risk transfer is the practice of shifting financial exposure from the party who faces direct liability to the party who is actually responsible for the underlying condition or activity that caused harm. In the construction context, the primary mechanisms are:
-
Contractual indemnification: The subcontractor agrees to indemnify the GC and owner for claims arising from the sub's work. When an injured worker sues the GC under Labor Law § 240, the GC's third-party claim against the sub for contractual indemnification is the vehicle through which that liability is transferred to the party whose employee was injured.
-
Additional insured coverage: The subcontractor procures a commercial general liability policy and endorses it to name the GC and owner as additional insureds. When the claim is paid, the sub's carrier pays on behalf of the additional insured, so the GC and owner are indemnified through insurance rather than through a direct payment from the sub.
-
Primary and non-contributory status: The sub's policy responds before the GC's own insurance, so the GC's carrier is not required to contribute to the defense or indemnification.
All three mechanisms depend entirely on documentation that must exist before the claim arises. There is no way to retroactively create an enforceable indemnification clause, compel a sub's carrier to add an additional insured endorsement after the policy period, or establish primary and non-contributory status after the claim is tendered.
The AVOID Act has added a fourth dependency: the documentation must be accessible and reviewable within the impleader window. A valid indemnification clause that cannot be located within 90 days of service is, for practical purposes, useless.
What has changed under the AVOID Act
Before the AVOID Act, the documentation gap between "we have a subcontract somewhere" and "we can file a third-party complaint tomorrow" could often be bridged with time and effort. Defense counsel would issue a records demand, the sub would produce its copy of the contract, and the parties would sort through the paperwork over weeks or months. The litigation schedule was flexible enough to absorb that delay.
Under the AVOID Act, that flexibility is gone. The relevant deadlines are:
The 90-day window for contractual claims is the most directly affected by documentation readiness. If a GC cannot locate the relevant subcontract within the first two weeks of that window, it loses a third of the available time to investigation and document recovery before it can begin the substantive impleader analysis. On a complex multi-subcontractor project, that loss is not recoverable.
The practical effect is that the standard of care for pre-litigation risk transfer now includes not just having the right contract language and the right COI, but having them organized and accessible in a way that supports a response measured in days, not weeks.
The indemnification clause: what the standard of care requires
New York construction contracts require careful indemnification drafting. General Obligations Law § 5-322.1 voids agreements that purport to indemnify a party for its own negligence in a construction contract. Enforceable indemnification must be limited to claims arising from the sub's own work, acts, or omissions. The standard of care for indemnification language includes:
Scope: The clause must cover the categories of claims you will face. Bodily injury to the sub's employees, property damage caused by the sub's operations, and claims arising from regulatory violations by the sub are the core coverage areas for Labor Law purposes.
Limitations: The clause must not attempt to indemnify for the indemnitee's sole negligence. Partial indemnity structures, where the sub indemnifies for its proportionate share of liability, are generally enforceable and are the safer drafting approach where any doubt exists.
Survival: The clause should survive the completion of the work, the expiration of the contract term, and the termination of the contractual relationship. Claims often arise years after the work is complete.
Defense obligation: Separate from indemnification, the clause should require the sub to defend the GC and owner from and against claims covered by the indemnity, not just to indemnify after a final determination. The right to a funded defense is practically significant in construction litigation, where defense costs are substantial.
Accessibility: The clause must be in a form you can produce. A signed original or a signed copy held in your contract management system is sufficient. An unsigned draft, an email exchange without a final executed agreement, or a verbal understanding is not.
The COI standard: what the AVOID Act implicitly requires
The certificate of insurance is the document that proves the sub's insurance-procurement obligations have been satisfied. Under the AVOID Act framework, a COI that is current, properly endorsed, and accessible within 48 hours of service is a minimum requirement for preserving your additional insured and failure-to-procure claims.
The specific elements that must be in your COI file for each active subcontractor:
Current certificate. The COI must be in force during the policy period that covers the date of the alleged injury or damage. A COI that expired before the incident provides no coverage for that claim.
Additional insured endorsement. The endorsement, not just the certificate face, must name the GC and owner as additional insureds. A COI that states "additional insured per contract" without an actual endorsement may or may not be enforceable depending on how the underlying policy is written. The endorsement itself is the proof.
Ongoing and completed operations. Additional insured status for ongoing operations covers claims that arise while the sub's work is being performed. Completed operations covers claims that arise after the work is complete, which is where most construction tort claims are asserted. You need both.
Primary and non-contributory language. The endorsement must specify that the sub's coverage is primary and that the GC's and owner's coverage is non-contributory. Without this language, your own insurer may be required to contribute to the defense and indemnification.
Notice of cancellation. The COI should confirm that your organization will receive notice before the sub's coverage is cancelled or materially reduced.
Platforms like TrustLayer automate the collection and verification of COI endorsements across your subcontractor base, tracking completed operations coverage, primary and non-contributory language, and expiration dates against your specific contract requirements so that your COI file is compliant before a claim arrives.
Vendor onboarding as the gating mechanism
The most efficient way to ensure that your documentation meets the AVOID Act standard is to make contract execution and COI delivery a condition of onboarding. A subcontractor who begins work without a signed contract and without delivering a compliant COI creates a risk exposure that the AVOID Act makes materially harder to remedy after the fact.
A compliant vendor onboarding protocol includes the following gates.
Gate 1: Executed subcontract before mobilization. No subcontractor should begin work before the governing subcontract is executed by both parties. The subcontract should contain the indemnification and insurance-procurement clauses described above. An unsigned draft, a letter of intent, or a handshake agreement does not satisfy this requirement.
Gate 2: Compliant COI before mobilization. The sub should deliver a COI and all required endorsements, reviewed against the contract's insurance requirements, before mobilization. If the COI is deficient in any respect, the sub should be required to obtain the correct endorsement before starting work.
Gate 3: COI renewal at expiration. Annual COI renewals should be tracked and collected automatically, not on demand. A subcontractor whose COI expires during an active project period must provide a renewal before the expiration date, not after.
Gate 4: Contract storage at execution. The executed subcontract should be filed in your contract management system at the time of execution, indexed by project and subcontractor name, in a format that is accessible to your legal and risk management functions without a search.
For organizations with large subcontractor bases, implementing these gates requires a combination of process discipline and, increasingly, technology. The same infrastructure that supports vendor compliance under normal operating conditions is the infrastructure that protects your impleader rights under the AVOID Act when a claim arrives.
The interaction with insurance carrier relationships
Pre-litigation risk transfer under the AVOID Act is not solely an operational problem; it also requires coordination with your insurance program. Carriers who are providing coverage for your construction operations need to understand the AVOID Act framework because their claims handling processes must align with the impleader deadlines.
Specific carrier coordination points include:
Coverage confirmation speed. When a claim is tendered and impleader is being evaluated, coverage counsel needs to confirm whether the third-party claims fall within the coverage provided before the deadline. Building an expectation into your carrier relationship that coverage analysis will be completed within 30 days of tender, not 60 or 90, is a concrete step that protects your ability to file before the deadline.
Additional insured tender. When you have viable additional insured claims against a subcontractor's carrier, the tender should be made early in the impleader window, before the deadline, so that the sub's carrier has the opportunity to accept the tender and participate in the defense. Late tender does not forfeit the claim, but it creates unnecessary friction.
Reservation of rights. If your carrier issues a reservation of rights on coverage for the third-party claims, coverage counsel and defense counsel need to know immediately. The AVOID Act deadline does not pause while coverage disputes are resolved.
For more on the insurance dimension of AVOID Act compliance, see the industry analysis at insurance carriers. For the broader compliance framework that puts pre-litigation risk transfer in context, see the compliance checklist.
Building the risk transfer standard into project operations
The AVOID Act has effectively defined a minimum standard of care for pre-litigation risk transfer that applies throughout the project lifecycle, not just when a claim arrives. Meeting that standard requires treating contract execution and COI management as litigation-readiness functions from the first day of any project.
The organizations that will consistently preserve their impleader rights under the AVOID Act are those that have made compliant vendor onboarding a non-negotiable condition of doing business, that maintain current and accessible COI files as a matter of course, and that have built a response protocol that can activate within 48 hours of service. These are not extraordinary measures. They are the operational baseline that the AVOID Act now requires.
The contract audit playbook provides the methodology for auditing your current contracts against this standard. The readiness assessment provides a scored diagnostic for measuring where your organization stands across all ten dimensions of AVOID Act compliance.