Insurance Documents to Collect Before Awarding Subcontract Work

Awarding subcontract work is the wrong moment to discover that the insurance file is incomplete.

By then, the start date is on the schedule. The superintendent expects a crew. Accounting has a vendor to set up. A missing endorsement or a certificate issued to the wrong entity is no longer an administrative detail. It is a decision that someone has to make under time pressure.

The better sequence is simple: use the proposed subcontract and other written project requirements to define the insurance request, collect the records, review them, and then make the award decision under your company's process.

That sequence does not require one universal document checklist. It requires a checklist that matches the work.

Start with the agreement, not last year's email

A roofing subcontractor, a design consultant, a hauler, and a small interior trade do not necessarily belong in the same insurance workflow. The contract, project requirements, trade, and your risk-transfer program determine what to request.

Open the proposed subcontract, owner instructions, and other written requirements expected to govern the work. Identify the insurance provisions that are expected to apply to this subcontractor. Note the required coverage types and limits, the parties that must receive evidence, and any endorsement requirements. Check whether the project has owner-specific instructions that differ from your usual company standard.

Requirements affecting payment, work authorization, public work, safety, or owner approval vary by contract, law, and risk program. Put those rules in the award workflow, but do not invent a universal stop-work or payment rule from a COI checklist.

The collection request should point back to the written requirement. "Please send your insurance" creates a guessing game. "Please send the records listed in Section 8 for the Oak Street project" gives the subcontractor and broker something concrete to follow.

Build the file the contract calls for

Many pre-award files begin with a certificate of insurance. Depending on the agreement, the file may also need copies of endorsements addressing additional insured status, waiver of subrogation, or primary and noncontributory wording. Project-specific forms may apply. Some contracts call for evidence tied to a particular location or operation.

Treat each item as its own review point. A certificate and an endorsement are not interchangeable.

The ACORD 25 states that the certificate is issued as a matter of information, confers no rights on the certificate holder, and does not amend or alter the listed policies. It is evidence of coverage information at the time it was issued. Policy terms and endorsements control.

That distinction matters before award. If the agreement requires additional-insured status, listing your company in the certificate holder box does not create it. The policy must provide the status or an endorsement must do so. A sentence in the description box cannot rewrite the policy.

Review identity before limits

A certificate can display familiar limits and still belong to the wrong legal entity.

Compare the named insured with the party signing the subcontract. Trade names, parent companies, affiliates, and similarly named entities can create confusion. If the names differ, resolve the relationship rather than assuming they are interchangeable.

Then confirm the producer and subcontractor contacts. A renewal request sent to an employee who left six months ago will not become more effective because the tracker says "requested."

Record the project or work scope associated with the review. That detail becomes useful later when the same subcontractor works under a different agreement or an owner asks for the historical file.

Read the certificate as a review starting point

Once identity is settled, compare the listed coverage information with the subcontract requirements. The review may include:

• policy types required by the agreement
• effective and expiration dates
• limits shown for each required line
• certificate holder name and address
• project or location wording requested in the instructions
• endorsements that must be collected separately

Do not turn this into a coverage opinion. A certificate does not show every policy term, condition, or exclusion. When a question depends on the policy, endorsement language, or application of coverage to an operation, send it to a qualified insurance professional and review the actual documents.

A clean review note should say what was checked, which requirement was used, what remains missing, and who owns the next step. "COI good" is too vague to help the person who inherits the file.

Keep safety approval in its own lane

Insurance records are one part of subcontractor onboarding. Safety qualifications, licensing, training records, site access, permits, and trade-specific controls may be separate parts of the award process.

Do not use a COI as a substitute for those reviews. A current certificate says nothing about whether a crew has completed project orientation, whether a hot-work permit is in place, or whether a license is valid for the work.

The teams responsible for insurance records and safety may exchange status, but each should document its own decision. That separation avoids a dangerous shortcut: treating one green check as approval of everything.

Make collection easy, then preserve the response

The subcontractor should know exactly where to send the file and what information belongs with it. A no-login upload link is useful because it removes account creation from a task that may happen once or twice a year.

Inside COI Compass, a team can import its subcontractor roster, send no-login upload links, set renewal reminders, and keep each certificate and follow-up in the record history. Its AI can draft ACORD 25 fields for human review. A person still checks the draft against the document and the applicable requirements.

The history matters as much as the current file. Save the original submission, corrected versions, endorsements received, review notes, and exception decisions. When someone asks why a subcontractor was approved, the answer should come from the record rather than one employee's memory.

Bring exceptions into the award meeting

Some files will still be incomplete when the award meeting starts. Do not hide that behind a generic pending status.

Name the missing item. Identify the contract requirement. State who can decide whether an exception is allowed, and record the decision. If the exception is temporary, assign an owner and due date for the corrected record.

The team may decide to delay award, change the work plan, seek advice, or proceed under an approved exception. That response belongs to the contract, law, company policy, and risk program. The COI review supplies facts; it does not make the decision by itself.

Before the next award meeting, choose one pending subcontract and reconstruct the file. Can another reviewer see the signed requirements, every document received, the review result, and any open exception without opening someone else's inbox? If not, the collection process is not finished.

Sources

• ACORD certificate FAQ
• New York DFS approved ACORD 25 (2025/12)
• COI Compass product page