Commercial Property Vendor Certificate of Insurance Tracking: A Landlord Workflow

A technician is scheduled to arrive at 7:00 a.m. A tenant needs the repair finished. The vendor says its insurance certificate is on the way.

That is the wrong moment to discover whether the certificate matches the contract, whether the listed policies are still in force for the scheduled work, or where the prior certificate was saved. The repair may still need attention, but the operating control should happen before a vendor is cleared for site access or work.

For a small commercial landlord, vendor certificate of insurance (COI) tracking is not a once-a-year filing task. It is a repeatable workflow that connects the signed agreement, the evidence received, the job or property it supports, and the next expiration date.

This guide focuses on vendor insurance evidence—not tenant insurance compliance, policy placement, or legal interpretation. Use it to build a cleaner property-management process, then have your insurance and legal professionals review the requirements and exceptions that apply to your agreements and jurisdiction.

> This is an operational workflow, not legal or insurance coverage advice. Your contract, the underlying policy and endorsements, and qualified professional guidance control the actual requirements.

Start with the contract requirements

The certificate is evidence to compare against the agreement; it should not become the source of the requirement. Before asking a vendor for anything, create a short requirement record from the executed contract, purchase order, work authorization, or approved scope.

Capture the fields your team will need to make a consistent comparison:

• Vendor legal name and any trade name used on site.
• Property, project, and scope of work.
• Required coverage types, limits, and policy-form requirements stated in the agreement.
• Required certificate-holder name and address.
• Any contract-required additional-insured, waiver, primary/noncontributory, auto, workers' compensation, professional, pollution, or other provisions.
• Whether an endorsement or other supporting document is required in addition to the certificate.
• Delivery timing, contract start and end dates, and the internal reviewer responsible for an exception.

Do not copy a generic requirement set into every vendor record without checking the active agreement. A landscaping vendor, roofing contractor, security firm, and consultant can have different contract language and work exposure. The goal is not to make a coverage decision from a spreadsheet. It is to preserve the exact request your team must validate.

One practical lesson belongs in the record: an ACORD certificate is evidence of information and does not itself amend the listed policies. If a contract requires a particular endorsement or status, a note on the certificate alone may not establish it. The ACORD 25 form states this directly.

Collect evidence before site access or work begins

Make insurance evidence part of vendor onboarding, not an email chase after the work order is released. The sequence should be clear to the property manager, maintenance lead, accounting team, and vendor.

1. Set the requirement record. Pull the insurance section of the agreement into the vendor file and identify the reviewer. 2. Request the evidence. Give the vendor the certificate-holder details and the supporting documents the contract calls for. 3. Compare, then clear. Confirm the submitted materials against the requirement record. Record the outcome as cleared, pending clarification, or exception under review. 4. Release the work only through the agreed process. If documentation is incomplete, route it to the person authorized to decide the next step instead of treating silence as approval.

This is a useful pre-work sequence even though every portfolio sets its own requirements. For example, Cornell directs units to verify a selected caterer has a certificate on file before the event date and before orders are placed, and its vendor record tracks insurance coverage and expiration dates. See Cornell's supplier and caterer guidance.

Avoid using a verbal assurance, broker email, or an old certificate as a substitute for the record your agreement requires. If something is missing, keep the status visible and assign an owner for the follow-up.

Track the fields that create the next action

A useful tracker does more than store a PDF. It should tell the next person what expires, what it supports, and what to do next.

| Field | Why it matters | | --- | --- | | Requirement source | Contract, purchase order, work authorization, location, version, and reviewer | | Evidence received | Certificate date, file link, producer or broker contact, and supporting-document links | | Review outcome | Required coverage line, stated limit, policy identifier as shown, and the review status | | Policy dates | Effective date and expiration date for each relevant policy shown | | Compliance status | Cleared, pending, exception approved, expired, or work hold | | Next action | Reminder date, owner, vendor follow-up date, and escalation deadline |

Track the policy expiration date, not merely the date the certificate arrived. A newly issued certificate can still show a policy that expires during an ongoing service contract. California State University, San Bernardino similarly advises reviewers to check that policy dates remain current and do not expire before the contract ends. Read its COI review checklist.

Where several policies support one vendor, track the earliest relevant expiration date as the next control date—but retain the policy-level dates as well. A single vendor status of “current” is not enough if workers' compensation, auto, or umbrella evidence runs out on different dates.

Use a renewal calendar with an owner

Expiration tracking works only when a person owns the next action. Set a reminder cadence that fits the agreement and gives the vendor time to respond. A simple starting point is a first request well before expiration, a follow-up closer to the date, and an escalation before work continues after an unresolved lapse.

The exact number of days is an operating choice, not a universal rule. What matters is that every reminder ties back to a record with:

• The policy or document that is expiring.
• The vendor's active properties, projects, or recurring work orders.
• The named person responsible for contacting the vendor.
• The internal person who can approve an exception or put work on hold.
• A timestamped log of requests, responses, and decisions.

Renewal outreach does not need to be elaborate. Identify the vendor, property, required update, expiration dates shown in the file, and the date by which your team needs replacement evidence. Send the request to the vendor and, when appropriate, the producer or broker named on the certificate.

For recurring work across several properties, maintain one vendor-level record with linked property scopes. That helps teams avoid assuming someone else requested the renewal while still showing which sites and work orders could be affected. The University of Wisconsin's vendor guidance likewise describes maintaining current certificates and continued renewals for higher-risk vendor contracts while they remain in force. See its vendor certificate procedures.

Handle exceptions in the open

The weakest part of a COI process is often the undocumented exception. A vendor may be missing a document, the certificate may not match the contract, or a property emergency may create pressure to proceed anyway. Do not solve that by changing a cell to green.

Use a visible exception record with:

• The specific unmet requirement or unanswered question.
• The property, work scope, and work date affected.
• The materials received and missing.
• The person authorized to decide the exception.
• The decision, effective dates, conditions, and follow-up deadline.
• Whether access or work is on hold pending resolution.

This does not decide what your organization should accept. It makes the decision auditable and prevents the same issue from being rediscovered when a new manager, lender, insurer, or owner asks for the file.

Keep an auditable vendor file

An auditable file should let your team reconstruct the path from agreement to authorization without scrolling through old emails. Keep these items together or reliably linked:

• Executed contract, approved scope, and amendments.
• Requirement record and current review outcome.
• Certificate and any supporting endorsements or documents requested by the agreement.
• Policy and certificate dates recorded in the tracker.
• Renewal requests, vendor responses, and reviewer notes.
• Exception approvals, work holds, and resolution evidence.
• A dated history of prior certificates rather than only the newest upload.

For a broader view of keeping commercial operations organized, visit the PigJet blog. The contract, certificate, work order, invoice, and follow-up should tell the same story about who was approved to do what work, at which property, and when.

Build the workflow before the next urgent call

The best time to organize vendor insurance evidence is before the next roof leak, HVAC failure, or tenant request makes the vendor's arrival the priority. Start with your five most active vendors. Build the requirement record, capture the current documents, enter the policy dates, and test the reminder and exception path with one real renewal.

The result is not a promise that every insurance question is resolved. It is a repeatable landlord workflow that makes the next action, responsible person, supporting evidence, and unresolved exception visible before work begins.

PigJet helps commercial landlords keep contracts, vendor records, work activity, and supporting documents connected. If your team is still piecing vendor compliance together from inboxes and spreadsheets, schedule a PigJet demo and bring one real vendor onboarding workflow.