The AVOID Act establishes a 60-day deadline for a defendant to file a first third-party complaint asserting non-contractual claims, such as contribution and common-law indemnification. Unlike the contractual deadline, which runs from a fixed and verifiable event (the date the defendant serves its answer), the non-contractual deadline runs from a different and more ambiguous trigger: the date on which the defendant "becomes aware" that the proposed third-party defendant may be liable.
The legislature did not define "becoming aware." That omission is not unusual; courts routinely fill statutory gaps through interpretation. But in this instance, the gap is load-bearing. The meaning of "becoming aware" will determine when the 60-day clock starts for a significant category of third-party claims in New York construction and premises litigation.
Why the distinction between contractual and non-contractual claims matters
Before examining the awareness standard, it helps to understand why the AVOID Act uses two different triggers at all.
Contractual claims, such as indemnification based on a written contract and claims for failure to procure insurance, arise from documents. When a defendant is served with a complaint, it can look at its contracts with subcontractors or vendors and determine within days or weeks whether contractual impleader rights exist. The deadline appropriately runs from answer service because the relevant information is in the defendant's possession or readily obtainable.
Non-contractual claims work differently. Contribution under CPLR Article 14 and common-law indemnification arise from the facts of the accident, not from documents. A general contractor defending a Labor Law § 240 claim may not know at the time it answers which specific subcontractor's employees were working on the scaffold, who controlled the work zone, or whether another trade's negligence contributed to the injury. That information emerges through discovery, witness interviews, incident reports, and OSHA records.
The legislature recognized this dynamic by decoupling the non-contractual deadline from the answer date. A defendant cannot be expected to file a contribution claim against a party it does not yet know may be liable. The "becoming aware" standard attempts to give defendants a fair window to act once they have the information needed to make an impleader decision.
What courts are likely to consider when defining "becoming aware"
Because "becoming aware" is undefined in the statute, courts will look to several interpretive sources: the text of the statute itself, legislative history, analogous standards in other procedural contexts, and practical considerations about what information a defendant reasonably needs before it can assess third-party liability.
The discovery rule analogy
The closest doctrinal analogy is the discovery rule applied in statutes of limitations. Under the discovery rule, a limitations period begins to run when the plaintiff knew or should have known of the injury and its connection to the defendant's conduct. New York courts have developed substantial case law on what "knew or should have known" means in various contexts, and much of that reasoning may apply to the "becoming aware" standard.
The most important question the discovery rule analogy raises is whether "becoming aware" is purely subjective, meaning the defendant's actual knowledge, or objective, meaning when a reasonably diligent defendant in the same position would have known. Courts applying discovery rules generally use an objective standard: the period runs from when the party knew or should have known with reasonable diligence. Applying that framework here would mean that a defendant who had access to information pointing to a third party's potential liability, but failed to investigate, could be found to have "become aware" earlier than its actual awareness.
What qualifies as awareness
Even under an objective standard, courts will need to define what quantum of information triggers awareness. Several candidates exist along a spectrum.
At one end, awareness might require only that the defendant know the identity of the proposed third-party defendant and that the third party was present at the project or incident. Under this reading, a general contractor "becomes aware" of a subcontractor's potential liability when it first knows the sub was on the job site.
At the other end, awareness might require something closer to a formed belief that the third party's conduct was a proximate cause of the plaintiff's injury. Under this reading, the clock would not start until the defendant had enough information to evaluate causation, not merely presence.
The more defendant-friendly reading is likely the one courts adopt for the simple reason that it gives "becoming aware" a meaning distinct from mere awareness of the third party's existence. If the legislature had intended the clock to start when the defendant first identifies a potential impleader target, it could have said so. The word "may be liable" in the statute supports a causation-based reading: awareness that a party "may be liable" implies some basis for believing liability is possible, not merely that the party exists.
Multiple potential third-party defendants
One of the most practically significant questions under the "becoming aware" standard is whether it runs separately for each potential third-party defendant. In a large construction case, there may be fifteen subcontractors whose work is potentially relevant to the plaintiff's injury. As discovery proceeds, new information may emerge about different parties' involvement at different times.
If the standard runs separately for each party, a defendant could potentially file timely third-party complaints against some parties while arguing that the clock has not yet started for others whose liability only emerged later. This interpretation has practical appeal: it would allow the AVOID Act's 60-day framework to function as designed across the complex multi-party cases it was drafted to address.
The alternative reading, in which the clock starts for all potential third-party defendants when the defendant first becomes aware of the general category of third-party liability, is harder to administer and may lead to defendants filing prematurely against parties whose liability is speculative at the time of filing. Courts are unlikely to favor an interpretation that rewards premature impleader.
Proof issues at the "becoming aware" boundary
Whatever standard courts adopt, defendants who invoke the "becoming aware" trigger will face evidentiary obligations. If a defendant argues that the 60-day period runs from a specific date later than the answer date, it must be able to demonstrate what information it had, when it received that information, and why earlier information did not constitute awareness.
This creates a documentation obligation that parallels the substantive defense. Defendants should maintain records of:
- The date on which investigation of each potential third-party defendant began
- The specific documents, reports, or testimony that informed the awareness determination
- Internal communications reflecting the point at which counsel concluded that impleader was warranted
These records serve a dual purpose: they establish the timeline for the awareness defense, and they demonstrate the reasonableness of the defendant's impleader decision if the timing is later challenged.
Interaction with the 12-month hard cap
Even if a defendant successfully argues that the "becoming aware" clock did not start until late in the case, the 12-month hard cap measured from the answer date operates as a backstop. Once 12 months have passed from the date the defendant served its answer, a third-party complaint requires written consent of both the plaintiff and the court, regardless of when awareness occurred.
This means that in cases with complex facts and many potential third-party defendants, the "becoming aware" standard provides flexibility within the first 12 months but does not eliminate the need to make impleader decisions before the hard cap expires. Defendants who anticipate awareness issues should treat the 12-month mark as a firm planning deadline even before the awareness trigger is established.
For a full overview of how the deadlines interact, see all AVOID Act deadlines explained. To track whether your organization has the systems in place to monitor awareness triggers as they arise, the readiness assessment covers the documentation and workflow dimensions that this standard demands.
The "becoming aware" standard is one of the statute's most consequential interpretive questions, and the answers will emerge case by case. For a preview of the questions most likely to be litigated in the courts' early engagement with the AVOID Act, see the article on early case law trends. For the complete annotated text of CPLR § 1007, including the non-contractual trigger provision, see the full law.