COI Tracking for Commercial Real Estate: How to Prevent Expired Vendor Insurance From Delaying Invoices and Draws

Certificate of Insurance tracking is rarely anyone’s favorite part of operations, but it is one of the fastest ways to introduce risk and slow projects down. A missing or expired COI can surface at the worst possible moment, like right before a vendor starts work, during an audit, or when a draw package is being finalized.

Many teams manage COIs in spreadsheets and shared folders. Others buy standalone COI tracking software. A third option is to manage COIs inside the same system you already use for vendor assignments, invoices, and draw compliance. That is the approach Rivur takes.

This post covers:

• Why COI tracking breaks down in real life

• What a practical COI process looks like

• How integrated COI management helps prevent invoice and draw delays

Why COI tracking breaks down

COI tracking usually starts as a simple list: Vendor name, project, COI received, expiration date.

Then the portfolio grows, vendors change, projects overlap, and the list turns into an operational liability:

• COIs are emailed to different people, stored in different places, and are hard to find later

• Expiration dates are updated inconsistently, or not at all

• Teams only discover gaps when a lender, auditor, or internal stakeholder asks for proof

• Compliance becomes reactive, and the organization relies on heroics to catch problems

Even when a team buys standalone COI software, COI can still become “disconnected.” It gets tracked in one system, but invoices, approvals, and draw packages live elsewhere. The result is the same late-stage scramble, just with another tool in the stack.

What a practical COI process looks like

A strong COI process has a few consistent characteristics:

1. COI is tracked where the work happens
   COI is not just a vendor attribute; it is a vendor plus project attribute. A vendor may be compliant for one project and not for another, depending on requirements.

2. Expiration monitoring is automatic
   The system should track expiration dates and proactively notify the right people before a COI expires.

3. Compliance is visible and actionable
   It is not enough to store the document. Teams need a clear view of who is missing COIs, who is expiring soon, and who has expired, and they need direct links to resolve issues.

4. Compliance is enforced before money moves
   If COI is required for a project, it should be enforced before invoices are approved and before draw packages are generated.

How Rivur handles COI management

Rivur includes COI management as part of the vendor workflow, so COIs do not live in a separate system.

Here is how it works in practice:

COIs are tied to vendor assignments
COI is tracked per vendor per project, which matches how teams actually operate. Users upload the COI PDF and set the COI expiration date right on the vendor assignment.

Project-level requirements are supported
Projects can include an insurance requirements document that vendors can download, and projects can be flagged as requiring COIs. This makes expectations explicit, and reduces back-and-forth.

Dashboards surface three COI states
Rivur maintains project-level alerts for:

• Missing COI

• COI expiring soon

• COI expired

These alerts appear in the dashboard and link directly back to the project vendor list so teams can resolve the issue without digging.

Proactive alerts start 45 days before expiration
Forty-five days before a COI expires, Rivur triggers an “expiring soon” workflow with in-app activity, and optional email notifications based on role preferences. This gives teams time to collect updates before work is impacted.

COI is enforced in the draw and invoice workflows
COI status is checked during draw compliance. In addition, missing COIs can prevent invoice submission when contract rules require lien waivers and related compliance, which helps teams catch issues early, before the draw package is assembled.

Why integrated COI management is different from standalone COI software

Standalone COI tools can work well for teams whose primary problem is COI tracking alone.

But for many commercial real estate teams, the operational pain is that COI is one piece of a broader workflow that also includes vendor onboarding, invoice approvals, and draw submissions.

When COI lives inside the same system as those workflows:

• Compliance becomes part of daily execution, not an afterthought

• Missing COIs are discovered earlier and resolved faster

• Invoices and draws are less likely to stall at the last minute

• Teams can avoid paying for separate COI software when COI is already included

If you want to see how COI management works inside Rivur, request a demo, and we can walk through a real project example, including the dashboard alerts, expiration notifications, and how COI impacts invoices and draw compliance.