New York's AVOID Act Turns Meeting Notes Into Legal Evidence

Here is the scenario construction attorneys are now worried about. A worker gets injured on your site six months after a project closes. You get served. Under the old rules, you had months to investigate — figure out who was responsible, which subcontractors were present, who had what indemnification obligations. You could take a measured approach to third-party impleader.

Under the AVOID Act, effective April 18, 2026, you have days.

That changes everything about what documentation you need to have maintained throughout the project. Not after the lawsuit. Before it.

What the AVOID Act actually does

The AVOID Act amends CPLR Section 1007 in New York, establishing rigid deadlines for filing third-party actions. Jason Kosek and Keith A. Lazere — shareholders at Anderson Kill P.C. who authored a February 2026 analysis of the law in Engineering News-Record — describe it bluntly: attorneys can no longer adopt a wait-and-see approach to impleader.

Instead, comprehensive indemnification analysis, insurance investigation, and liability assessment must happen within days of filing an answer. The practical result, as Kosek and Lazere note, is that the safest course becomes blanket impleader: naming every subcontractor who set foot on the project site, regardless of their apparent connection to the alleged injury.

If you cannot quickly answer who was on site, when, and for what scope of work, you cannot build that third-party complaint in time. Your indemnification rights are at risk not because they don't exist, but because you ran out the clock before you could document them.

What owners now need in every contract

Anderson Kill's recommendation for owners is not to react faster after lawsuits. It is to build documentation requirements into every contract before work begins. The attorneys lay out three specific provisions that belong in every agreement going forward.

The pattern here is consistent: the AVOID Act does not create a new documentation problem. It exposes how much construction teams were relying on memory, informal records, and the assumption that disputes would give them time to piece together what happened.

The Prompt Payment Act: retainage just got simpler

The AVOID Act is not the only law Anderson Kill flags for 2026 contracts. On December 19, 2025, New York amended General Business Law § 757, the Prompt Payment Act, and the change is straightforward: any contract provision requiring retainage exceeding 5% of the total contract sum is void.

Not reduced. Not negotiable. Void.

Courts will not blue-pencil an excessive retainage clause down to 5%. They void the entire provision. If that provision is not severable from your payment terms, you may end up with no retainage protection at all. The attorneys' advice: get retainage language compliant before your next contract is signed and include invoicing provisions that guard against account stated claims.

The documentation gap this exposes

I have watched construction PMs handle documentation the same way for years. Paper logs, shared drives, email threads. Enough to satisfy progress reports, not enough to reconstruct a project's complete attendance history under legal pressure.

The AVOID Act changes the cost of that gap. When your attorney needs to know which electrical subcontractor's crew was on the fourth floor on a specific Tuesday three years ago, the answer has to exist in searchable, timestamped records — not in somebody's memory.

Meeting notes, site visit logs, coordination call transcripts. Every one of them is now a potential exhibit in a third-party complaint that needs to be filed within days. If they were never written down, or if they exist on a cloud platform that the subcontractor's team can access and modify, or if they are distributed across twelve email chains — you have a discovery problem before litigation even begins.

Local, structured, searchable records — meeting by meeting, party by party — are what the AVOID Act's compliance timeline actually requires. The contract provisions Anderson Kill recommends (the comprehensive schedule, the centralized database, the immediate delivery of subcontracts) all depend on someone actually capturing that information contemporaneously.

A note-taking tool that sends your meeting audio to a third party is a liability in this context, not just a privacy concern. The records of who said what in a coordination meeting could be discoverable. You want those records to live where you control them.

Frequently asked questions