Skip to content

Keep a Vendor Insurance Certificate Register Current

A certificate register that shows which vendors may be dispatched today, which are expired, and who owns each renewal.

By PortfolioRental Editorial Team · · Updated 2026-10-22

White apartment kitchen with built-in appliances
In this article

A vendor insurance certificate is only useful if it is current on the day of dispatch. Many portfolios keep certificates in a folder and treat the presence of a document as proof of coverage. The folder fills up, renewal dates pass, and the first time anyone checks the expiry is after an incident.

Quick Overview

A certificate register is a dispatch control, not an archive. Record the dates, the required coverage for the work, the reviewer, and a dispatch status that schedulers can act on today.

A register fixes this by turning certificates into a small, maintained dataset with owners and dates.

Decide What the Register Must Answer

Before collecting more paperwork, define the questions the register should answer:

  • Which vendors are approved for dispatch today?
  • Which approvals expire in the next thirty, sixty, or ninety days?
  • Which certificate types are required for each trade or scope?
  • Who is responsible for requesting the renewal?
  • Which vendor is suspended and why?

If the register cannot answer these quickly, it is an archive rather than a control.

Record the Minimum Useful Fields

For each vendor, record the legal name, the trade or scope, the certificate holder name, the coverage types required by the agreement, the effective and expiry dates, the certificate reference, the date the document was received, and the reviewer. Add the approved dispatch status and the reason for any suspension.

Keep the certificate itself in the approved document system and link to it. Do not store personal identity documents or full policy numbers in a shared spreadsheet.

Match the Requirement to the Work

Not every vendor needs identical coverage. A vendor performing routine cleaning has a different risk profile from one entering units for electrical work or roof repair. Map the requirement to the scope in the vendor agreement, and record the basis for the requirement. That way the register reflects decisions rather than an arbitrary checklist.

Where the management agreement or owner instructions set specific limits, record those limits and the source. Do not infer coverage adequacy. Interpretation belongs to the qualified reviewer.

Build a Renewal Calendar From Expiry Dates

Sort the register by expiry and create three queues: expiring within thirty days, expiring within ninety days, and expired. Each queue needs an owner and a cadence. A request sent on the expiry date is already late.

A practical rhythm:

  • Weekly: check for anything that expired since the last review and suspend dispatch where required.
  • Monthly: request renewals for certificates expiring in the next sixty days.
  • Quarterly: sample ten certificates against the vendor agreement and confirm the coverage types still match the scope.

Make the Dispatch Rule Visible

The person scheduling work should not have to interpret the register. Use a single status field with a clear rule: approved, approved with conditions, or suspended. A condition might be a pending renewal with a confirmed issue date, but only if the reviewer has approved interim dispatch in writing.

When a vendor is suspended, record the reason and the person who can restore approval. Notify the schedulers so a suspended vendor is not dispatched from a stale contact list.

Handle the Common Exceptions

The certificate names the wrong entity. A certificate issued to an individual rather than the contracting business deserves review. Record the mismatch and route it to the reviewer instead of filing it as complete.

The expiry date passes during an active job. Decide in advance whether work may continue to a safe stopping point. Record the decision and the authority. Do not let the schedule silently override the requirement.

A renewal certificate arrives with a different coverage limit. Compare it to the requirement and record the difference. A lower limit is a decision for the reviewer, not an automatic update.

Audit the Register Itself

Once a quarter, test the register against reality. Pick five active vendors and confirm the certificate on file matches the register, the status matches the agreement, and the renewal owner is correct. Then pick five expired certificates and confirm dispatch was actually suspended.

This audit catches the most common failure: a register that is accurate in the file but not used at the point of scheduling.

Keep It Small Enough to Maintain

A register with forty fields will not be updated. A register with twelve well-chosen fields, a clear status, and a named owner will be. Start with the fields needed to answer the five questions, then add only what the quarterly review proves is missing.

The measure of success is simple. On any given morning, the scheduler can open the register, see which vendors are approved, and dispatch without calling the office to ask whether the paperwork is current.

Common Mistakes

  • Filing a certificate without a review. The document may name the wrong entity or fail to match the approved scope.
  • Checking expiry only at onboarding. Certificates expire while vendors remain active, and the register must surface the date.
  • Allowing an open-ended exception. An exception without an end date becomes the new standard.

Common Questions Answered

Who decides whether coverage is adequate?

The qualified reviewer and, where needed, the insurer or advisor. The coordinator records the requirement and the review outcome.

What if a renewal certificate has lower limits?

Record the difference and route it for a decision before dispatch continues.

Should the register include every vendor?

Include every vendor who may be dispatched for in-scope work. A register with unused rows becomes stale.

Ready to Put This Into Practice

Use the maintenance triage guide to connect dispatch decisions to the work record, and the after-hours invoice packet guide for the invoice side. For small-business risk guidance, see the U.S. Small Business Administration.