ACORD 25 Explained: A Property Manager's Field-by-Field Guide to Certificates of Insurance

If you manage a residential or commercial property portfolio, the ACORD 25 is likely the document you request more than any other. It is the standard certificate of insurance form used across the United States to summarize a vendor's liability coverage, and it is what you collect from contractors, landscapers, maintenance vendors, and any other third party who works on your properties.

Most property managers know they need to collect it. Far fewer have a systematic process for reading it correctly.

This guide walks through the ACORD 25 section by section, explains what each field is telling you, and identifies the compliance gaps that are most commonly missed during manual review.

What the ACORD 25 Is — and What It Is Not

The ACORD 25 (Certificate of Liability Insurance) is a standardized summary form produced by the Association for Cooperative Operations Research and Development. It is not the insurance policy itself. It is a snapshot of coverage as of the date it was issued.

This distinction matters. A certificate can accurately reflect a policy that was active on the issue date but has since been modified or cancelled. It can also omit endorsements that are attached to the underlying policy. Collecting a COI is a necessary step in vendor compliance; it is not a sufficient one unless you are also verifying the fields that matter.

Section-by-Section Breakdown

Producer and Insured Information (Top Section)

The top-left box identifies the insurance producer (broker or agent) who issued the certificate. The "Insured" box names the entity whose coverage is being documented — this should match the legal name of the vendor you have contracted with exactly. A mismatch between the certificate insured name and your vendor contract name is a compliance flag that is easy to overlook and difficult to defend if a claim arises.

Certificate Holder (Bottom-Left Box)

This is where your company's name and address should appear. If you require additional insured status, the certificate holder box alone is not sufficient — additional insured status must be reflected in the endorsements section and ideally confirmed by a copy of the actual endorsement. Many certificates show a certificate holder without granting additional insured rights.

Coverages Section (Middle of Form)

This is the most information-dense part of the ACORD 25 and the area where most compliance gaps occur.

Commercial General Liability (CGL): Look for occurrence-based coverage (preferred over claims-made for most property management purposes), and verify that the limits meet your property-specific minimums. Common required limits for residential property vendors are $1,000,000 per occurrence and $2,000,000 aggregate, but your requirements may differ by property type, contract value, or jurisdiction.

Automobile Liability: If a vendor operates vehicles on your property, auto liability coverage is required. Check that the "Any Auto" box is selected rather than "Owned Autos Only" — a vendor's employee using a personal vehicle for a work errand creates exposure that "Owned Autos Only" does not cover.

Umbrella / Excess Liability: For higher-risk vendors (roofing, structural work, elevator maintenance), you may require umbrella coverage above the CGL limits. Verify that the umbrella follows form with the underlying CGL policy.

Workers' Compensation: The ACORD 25 should reflect workers' compensation coverage if the vendor has employees. A vendor who claims to have no employees and carries no workers' comp is a liability exposure if a worker is injured on your property. Some jurisdictions hold property owners responsible for workers' comp costs when an uninsured subcontractor is injured on-site.

Policy Effective and Expiration Dates

Every coverage line shows a policy period. This is where expiration tracking is critical. A certificate that was valid when you collected it provides no protection once the policy lapses. For any vendor with recurring access to your properties, you need a process that flags upcoming expirations and requests renewal certificates before coverage ends — not after.

Description of Operations Box

This free-text field is where additional insured status, waiver of subrogation, and project-specific endorsements are typically noted. Do not assume these protections exist unless they are explicitly stated here. Common entries to look for:

• "[Your company name] is named as additional insured on a primary and non-contributory basis"
• "Waiver of subrogation applies in favor of certificate holder"
• "30-day notice of cancellation applies"

If your contract requires any of these provisions and they are absent from this box, the COI is non-compliant regardless of the coverage limits shown.

The Three Fields Most Often Wrong

In manual COI review workflows, the fields that generate the most compliance failures are:

1. Additional insured status — stated in the contract but missing from the certificate
2. Coverage limits — present but below the property-specific minimums
3. Expiration dates — past or within 30 days, with no renewal on file

These are not rare edge cases. They are routine findings in any portfolio tracking more than a few dozen vendor COIs.

From Manual Review to Systematic Compliance

Understanding what the ACORD 25 contains is the first step. Building a process that catches every field, across every vendor, on every renewal cycle is the operational challenge.

AI-powered extraction tools trained on ACORD form structures can parse each field automatically, score the certificate against your defined requirements, and flag non-compliant certificates without requiring a staff member to read every document manually. For portfolios with 30 or more active vendor relationships, this is the difference between a compliance process that works and one that only appears to work until something goes wrong.

---

Verifolio extracts and scores ACORD 25, 27, and 28 certificates automatically, flagging coverage gaps against your property-specific requirements. Join the beta at getverifolio.com to see how it works on your vendor COI corpus.