The AVOID Act's 90-day deadline for contractual impleader claims begins when you serve your answer. That deadline is not the problem. The problem is that the 90 days are only enough time if a specific set of documentation and processes are already in place before service. If they are not, you will spend much of that window reconstructing records and establishing workflows that should have existed already.
The following five preparation points represent the minimum foundation for AVOID Act readiness. Each one corresponds to a category of failure that commonly forfeits impleader rights in the new environment. None of them requires extraordinary resources. All of them require advance work.
1. Accessible subcontractor contracts with confirmed indemnification language
The most fundamental requirement is the ability to retrieve the executed subcontract for any subcontractor, on any active or recently completed project, within 48 hours of being served. This is the threshold question: does a contract exist, and does it contain enforceable indemnification and insurance-procurement language that supports an impleader claim?
If your contracts are stored in project-specific silos, archived at project closeout, or saved in inconsistent formats that make search difficult, you cannot meet this standard reliably. The retrieval problem is a records management problem, not a legal one, and it requires a records management solution.
Enforceability is a separate issue from existence. New York law is specific about indemnification language in construction contracts. Indemnification for the indemnitee's own negligence must be explicitly stated; broad general language will not support it. If your template subcontracts have not been reviewed against this standard recently, that review should happen before you are served, not while the 90-day clock is running.
Use the contract audit playbook to systematically review your subcontract templates and confirm that the indemnification provisions are enforceable. Use the compliance checklist to verify that your contract management infrastructure meets the retrieval standard.
2. Current COIs with verified endorsements for every active and recently completed project
The second preparation point is insurance documentation. For every subcontractor on every active and recently completed project, you need a current certificate of insurance showing at least the required coverage types and limits, along with confirmation that the required endorsements are actually in place on the policy.
"Current" means as of today, not as of project execution. Certificates expire annually, and subcontractors do not always renew on time. A COI file that has not been actively monitored will contain a mix of current and expired certificates, with no reliable indicator of which is which. For a claim that arises on a project that completed 18 months ago, the GC needs to confirm that the sub maintained compliant coverage not just at contract execution but through the relevant policy period.
"Verified endorsements" means more than a certificate that indicates the endorsements were requested. The additional insured endorsement, primary and non-contributory endorsement, and waiver of subrogation endorsement are the core trio required by most construction subcontracts. Confirming that these endorsements exist on the policy, and that the endorsement language meets the contract requirement, requires obtaining copies of the actual endorsements. Relying on the certificate alone does not confirm endorsement language.
The coi-tracking-spreadsheets article covers the specific failure modes of manual COI tracking under AVOID Act deadline pressure and what a more reliable system looks like.
Platforms like TrustLayer automate COI verification across your subcontractor network, flagging expired certificates and coverage gaps against your specific contract requirements so your insurance documentation is ready when the AVOID Act deadline starts.
3. A defined first-48-hours response protocol
The third preparation point is a response protocol: a defined, written process for what happens in your organization in the first 48 hours after service. This is the window in which the foundational decisions about impleader are made or missed.
A functioning response protocol has at least the following components. Someone in the organization is designated to receive new service and immediately notify both defense counsel and the person responsible for impleader review. The notification happens within hours of service, not days. The initial notification includes the complaint, the date of the alleged incident, the location, and the identity of the injured party.
Simultaneously with counsel notification, someone initiates the contract and COI retrieval process. They pull the project from the contract management system, identify the relevant subcontractors, and confirm that the contracts and insurance documentation are accessible. They document what they found and when.
Within the first 48 hours, the response protocol should produce a preliminary map of the contractual chain: who were the relevant subcontractors, which subcontracts govern the relationship, and whether those subcontracts appear to contain the provisions needed for an impleader claim. This map becomes the starting point for defense counsel's evaluation.
Organizations that do not have this protocol in writing are likely to discover the gap the first time they are served, when the absence of a protocol creates exactly the kind of delay that forfeits rights. Building the protocol before service, testing it once with a simulated incident, and maintaining it as part of the operations infrastructure is far less expensive than reconstructing it under deadline pressure.
For a broader framework of the AVOID Act's deadlines and what they require from a process standpoint, the avoid-act-deadlines overview is a useful starting point.
4. Carrier briefing and aligned coverage counsel
The fourth preparation point is alignment with your insurance carriers and coverage counsel. Defense of a Labor Law claim typically involves both defense counsel retained by the carrier and coverage counsel involved in evaluating third-party claim opportunities. The AVOID Act's deadlines require that both parties be aligned on the impleader question before the deadline expires, which means the conversation must begin very early in the case.
Carriers who are not specifically familiar with the AVOID Act framework may not appreciate the urgency of the impleader decision. A defense counsel who knows the deadline but whose instructions from the carrier are unclear about whether to proceed with impleader may let days pass while seeking authorization that never arrives. The result can be a missed deadline that is entirely attributable to internal alignment failure rather than insufficient time.
Briefing your carriers proactively, before a specific claim arises, establishes the baseline that avoids this failure. The briefing should cover the deadline structure (including the distinction between contractual and non-contractual claims), the carrier's role in authorizing impleader decisions, the timeline within which that authorization needs to be provided, and the documentation the carrier expects to receive as part of the impleader recommendation.
The goal is that when a specific claim arises, no one in the chain is encountering the AVOID Act for the first time. Everyone knows the deadline, knows their role, and knows what information needs to move through the chain and how fast. This alignment cannot be created in the middle of a 90-day window; it needs to exist before service.
5. A current readiness self-assessment
The fifth preparation point is an honest evaluation of where your organization currently stands across all of the dimensions above. This assessment is valuable because the gaps that most directly threaten impleader rights are often the ones that have not been formally evaluated because they seemed like routine operations rather than compliance obligations.
The readiness assessment walks through 10 questions covering contract retrieval, COI verification, response protocols, carrier alignment, case law monitoring, and system centralization. The assessment is designed for legal teams and risk managers, and it produces a scored result that identifies where preparation gaps are most acute.
Running the assessment before a claim arrives tells you where to focus preparation efforts. Running it after a missed deadline tells you where the process failed. The first scenario is considerably more useful.
The assessment is available without cost and takes approximately 10 minutes. Organizations that score below the "strong foundation" threshold on the assessment have identifiable preparation gaps that can be prioritized and addressed through the structured framework in the compliance checklist.
The preparation window is finite
The AVOID Act took effect on April 18, 2026. Cases filed after that date carry the new deadline structure. For organizations that have not yet completed the preparation steps above, the window is the period before the next lawsuit arrives.
Prioritizing the five points above, in roughly the order listed, ensures that the most operationally urgent gaps are closed first. Contract retrieval and COI verification are the foundation; response protocol and carrier alignment are the process layer on top; the readiness assessment tells you where to start.
The AVOID Act does not reward good intentions. It rewards preparation that exists when service arrives.