Vendor COI tracking for property managers: what a certificate proves and what to check instead

Where certificate time goes

Ask a property management coordinator about vendor insurance and you will hear a familiar story. A plumber or a roofing crew is needed on a property this week. The vendor's insurance agent emails an ACORD 25. Someone opens it, compares it with the company's vendor requirements, notices that the additional insured box is marked but no endorsement is attached, and writes back. Two days later a corrected certificate arrives, still without the endorsement.

Commercial managers do the same work for tenants. The lease says what the tenant must carry, the tenant sends an ACORD 25 for liability and often an ACORD 28 for its property coverage, and someone checks both against the insurance clause. Association managers do it for the association's vendors, and residential managers also track renters insurance across their units.

Property management systems help with part of this. Yardi Breeze, for example, stores insurance expiry dates on the vendor record and warns staff before they pay a vendor whose insurance has expired. That warning comes at payment time, often after the work is done, and an expiry alert does not check endorsement wording. Some dedicated COI services read endorsements too, so compare what your current tools check with the checks your staff still do by hand. The minutes go into reading PDFs against a requirement sheet and chasing endorsements, across hundreds of vendors whose policies renew at different times of year.

What a certificate proves, and what it does not

The ACORD 25 certifies that the listed policies were issued to the named insured for the policy period shown. In Texas, an approved certificate that is properly issued confirms that the policy has been issued or coverage bound (Insurance Code section 1811.151). That has value. It is also a snapshot on the day of issue, and the form itself warns that the limits shown may have been reduced by paid claims.

Most of what managers assume beyond that needs a second look. The certificate's header says it is issued as a matter of information only, confers no rights on the certificate holder and does not amend, extend or alter the coverage. Texas section 1811.152 and Delaware's Certificates of Insurance Act (18 Del. C. 4503) put the same rule into law. ACORD describes its 27 and 28 evidence forms the same way: certificates for parties with a financial interest in the property, typically lenders, issued as a matter of information only.

Holder versus additional insured

Being named as certificate holder gives a property manager a copy of the evidence and nothing more. Additional insured status, which lets the owner entity and the management company claim under the vendor's liability policy, comes from the policy's additional insured provisions or an endorsement. The ACORD 25 says so in its IMPORTANT box: if the holder is an additional insured, the policy must have additional insured provisions or be endorsed, and a statement on the certificate does not confer rights in place of the endorsement.

So the endorsement or policy wording is the document to read. Check that it covers the right entities and the work the vendor does. Its form number should also match a form listed on the policy. A scheduled endorsement lists additional insureds by name, so the owner LLC and the management company need to appear on it. Some vendors carry a blanket additional insured endorsement in place of a list of names. Blanket wording describes the class of people it covers, so read that description against your own relationship with the vendor. For contractors, ask whether the endorsement covers completed operations as well as ongoing work, because a roof leak can surface months after the crew has left.

Waiver of subrogation and primary and non-contributory follow the same logic. A Y in the SUBR WVD column is subject to the policy, and some policies need an endorsement for the waiver to apply. Primary and non-contributory has no box on the ACORD 25 at all. If your requirements call for it, ask for the endorsement that provides it.

Notice of cancellation deserves its own line in your requirements. The ACORD 25 says notice will be delivered in accordance with the policy provisions. Texas and Delaware both say a person has a right to notice only when the policy or an endorsement gives it. If you want notice, ask for a notice endorsement. Asking a vendor's agent to type '30 days notice' on the certificate creates no right at all.

In Texas and Delaware, the rules bind the requester too

Most certificate laws are written with agents and insurers in mind, but two of them reach the person asking for the certificate. Texas Insurance Code chapter 1811 says a person may not require the issuance of a certificate for risks in Texas unless the form has been filed with and approved by the Texas Department of Insurance, and may not require a certificate that contains false or misleading information. Section 1811.154 adds that a certificate may not reference a requirement in another contract, including a contract for construction or services. Wilful violations carry a civil penalty of up to $1,000 each.

Delaware's act says no person may request or require a certificate that contains false or misleading information or that claims to alter the coverage, and it treats a certificate issued in violation as null and void. It also says a certificate does not warrant that the policy meets a contract's insurance requirements, even when the contract number appears on it.

In practice two habits need to change. Sending vendors your own certificate form to fill in is risky in Texas, because certificate forms have to be filed and approved. Asking for wording such as 'per lease section 12' or 'meets all contract requirements' in the description of operations box asks for something section 1811.154 bars, and a promise of notice the policy does not give would be misleading. In both cases, ask for the endorsement instead.

This article is general information, not legal advice. If your properties are in Texas or Delaware, ask your counsel to review your vendor and lease insurance requirements against these statutes.

Build the requirement set first

An agent can only check a certificate against something written down. Most companies have a requirement sheet somewhere, often a spreadsheet a former coordinator built, with exceptions buried in email threads. Before automating anything, turn it into a requirement set the whole team agrees on.

Tier vendors by the risk of the work. A window cleaner and a roofing contractor should not carry the same requirements, and one sheet for everyone produces either constant exceptions or too little protection. For each tier, record the minimum limits by line, whether an umbrella is required, the entities to be named as additional insureds, whether you need waiver of subrogation or primary and non-contributory wording backed by an endorsement, and whether completed operations coverage is needed.

For commercial tenants, the requirement set comes from each lease's insurance clause. Abstract it once when the lease is signed or the property comes under management, and attach it to the tenant record. For association vendors, the board's contract terms set the bar.

Name the entities exactly. Many owners hold each property in its own LLC, and the management company is a separate entity. On a scheduled endorsement both usually need to appear by name, spelled the way they appear in the management agreement. With blanket wording, a qualified reviewer confirms that its conditions cover both. Then set a rule for renewals: a certificate is evidence for one policy term, so each renewal gets the same check as the first submission.

What to automate and what to keep with a person

A workable rule: the agent does anything a careful new coordinator could do with the requirement set in front of them, and a person decides anything that accepts less than the requirement says. The table shows where that line usually falls.

Exceptions deserve a written policy of their own. IREM, the Institute of Real Estate Management, teaches property teams to build an insurance exceptions sheet for this purpose. Whatever you call it, write down who may approve a lower limit or a missing endorsement and for which vendor tiers, with an end date for each exception. Once that exists, the agent can route each exception to the right approver with the evidence attached.

Controls worth insisting on

Before the agent sends a single request, agree these controls with whoever is accountable for vendor risk at your company:

• Additional insured status is recorded only after a review of the policy provision or endorsement that grants it, and blanket wording goes to a qualified reviewer.
• Deficiency requests ask for endorsements or corrected certificates, never for contract references or custom wording on the certificate.
• A vendor with a lapsed or deficient certificate gets no new work orders until the gap closes or an approver records an exception.
• Every exception records who approved it and why, with an end date.
• A senior manager reviews a sample of accepted certificates every week.
• The log shows each certificate read and each email sent, with the checks behind it.

Worked example: what the hours look like

This is an illustrative example with assumed numbers, not a client result. Take a 120-person company managing 70 residential and commercial properties, with about 900 active vendors and 120 commercial tenants whose leases carry insurance clauses. Renewals and new vendors bring in about 30 certificates a week. About a third come back for a second round after a deficiency request, so the team reviews roughly 40 certificate submissions a week.

Assume each submission takes 25 minutes by hand, from opening the email to recording the result or sending the deficiency request. That is 1,000 minutes, or about 16.7 staff hours a week.

Now assume 30 of the 40 are routine: a known vendor tier with a clean endorsement or a standard gap. With the agent doing the reading and drafting, a manager spends about 5 minutes reviewing each one, 150 minutes in all. The other 10, such as exceptions and lease questions, still take the full 25 minutes, another 250 minutes. Weekly time falls to 400 minutes, about 6.7 hours, which gives back about 10 staff hours a week.

The share that arrives deficient moves this result more than any other number. Count it in your own files for one month before trusting anyone's estimate, including this one. The expiry sweep is left out of these figures, and an agent can run that every night.

Starting small with certificates

Pull one month of certificates and tag each one as compliant on arrival, deficient or an exception. Start with a manageable sample, for example the 50 vendors you use most, and clean their requirement set. Write the exceptions policy down too. Then run an agent against copies of last month's certificates, with nothing sent to vendors, and compare its findings with what your team decided.

That test is roughly what our five-day AI Workflow Sprint does, for $2,500. It ends with a working prototype on your redacted documents and a fixed quote for the build, based on the staff hours each workflow costs you. Full refund if we do not find 10 staff hours a week. Whoever you work with, test against your own certificates before a single request reaches a vendor.

Common questions