COI Tracking · June 29, 2026

How to Track COI Renewals Before They Become Last-Minute Fire Drills

A practical COI renewal follow-up workflow for contractor admins tracking expiring insurance certificates, broker requests, vendor follow-ups, and customer requirements.

COI TrackingRenewal TrackingContractor AdminFollow-Up WorkflowDocument Tracking

A certificate of insurance is usually easy to collect the first time. Someone asks for it during onboarding, the subcontractor forwards it from their broker, the admin saves the PDF, and everyone moves on. Lovely. Peaceful. A tiny administrative fantasy.

Then the policy expires eleven months later. The subcontractor assumes the broker sent the renewal. The broker may have sent it to the project manager instead of the office. The customer portal still shows the old certificate. Accounting wants to know whether an invoice can move forward. Someone remembers there was a spreadsheet, but the spreadsheet only says “expires 7/1” and does not explain who followed up, who has the ball, or whether the updated certificate was already buried in someone’s inbox.

That is the real COI renewal problem. It is not just tracking dates. It is tracking the work around the date.

Treat each COI as an active obligation, not a saved file

A folder full of insurance certificates can tell you what you have. It cannot reliably tell you what needs attention today. For renewals, the useful record is the obligation attached to the PDF.

For each active COI, track the vendor or subcontractor, the customer or platform where the certificate matters, the expiration date, the current renewal stage, the person responsible for the next step, the last request date, the next follow-up date, and any blocker notes.

That looks more annoying than “save the PDF and move on,” because it is. But it is also the difference between a tracker and a scavenger hunt.

Separate the expiration date from the renewal stage

One of the easiest spreadsheet mistakes is treating the expiration date as the entire workflow. A date can tell you the certificate expires in 28 days. It cannot tell you whether the renewal has already been requested, whether the subcontractor replied, whether the broker is preparing the updated certificate, or whether the customer requires a new upload before work continues.

Use a separate renewal stage. Keep it plain: Current, Renewal needed, Requested, Waiting on subcontractor, Waiting on broker, Received needs review, Updated, or Not applicable. Avoid vague statuses like “pending” unless you enjoy future-you cursing present-you. Pending what? Pending from whom?

Build a renewal cadence before the deadline gets dramatic

A single 30-day reminder is better than nothing, but COI renewals often need more than one touch. People are busy. Brokers miss emails. Subcontractors assume someone else handled it. The process needs a cadence.

A simple renewal cadence might look like this:

60 days out: review upcoming expirations and confirm the contact path
45 days out: send the first renewal request
30 days out: follow up if no updated certificate has been received
14 days out: escalate internally or contact an alternate person
7 days out: review affected customers, portals, jobs, or payment checkpoints

The exact timing depends on your business, customer expectations, and internal process. The point is that the schedule should exist somewhere other than inside one person’s head, because heads are terrible databases. Stylish, but terrible.

Do not wait until payment or job start to discover the gap

Many teams catch COI issues when a subcontractor is about to start work or when an invoice is being reviewed. Those are useful checkpoints, but a lousy first line of defense. By then, the admin has urgency, missing information, and people asking why nobody caught it sooner.

Use payment review or job-start review as a final check against the renewal tracker. The daily or weekly workflow should have already identified the expiring certificate, sent the request, recorded the follow-up, and shown whether the renewal is waiting on the subcontractor, broker, customer, platform, or internal team.

That way, when someone asks whether the updated COI has arrived, the answer is not “let me dig through email.” It is closer to: “Requested on June 3, waiting on broker, follow-up due tomorrow.”

Make “waiting on” visible

The renewal is not done just because someone sent an email. A request sent is progress, but it is not a renewed certificate.

For each open renewal, record who has the ball: subcontractor, broker, customer, platform, internal review, or someone else. Add a note that explains the blocker in normal language. “Broker preparing updated COI” is more useful than “pending.” “Need customer-specific certificate holder wording” is more useful than “check later.”

The goal is not to write a novel. The goal is a review that does not require memory archaeology.

Close the loop when the updated COI arrives

Receiving the renewal is not the end of the workflow. When the updated certificate arrives, update the expiration date, save or link the new document, record the received date, and clear the waiting state. If it belongs to a specific customer, platform, subcontractor, employee, or crew, make that relationship visible.

This is where a single source of truth earns its keep. Without one, the renewed COI might be in the folder while the spreadsheet still shows expired and the customer portal still needs an upload. Tiny little chaos goblins, all holding clipboards.

Where Sidecar fits

Sidecar is useful here because COI renewals are not just document storage. They involve expiration dates, customer-specific requirements, request history, waiting states, follow-up dates, contacts, and internal tasks. Sidecar helps organize those pieces so an admin can start from “what needs attention?” instead of rebuilding status from Outlook, Excel, shared folders, and portals every morning.

It does not decide whether a COI is legally sufficient, whether a vendor is approved, or whether a customer will accept a certificate. That review still belongs to your team and the appropriate customer, broker, or advisor. Sidecar’s job is simpler: keep the tracked work visible so fewer renewals disappear until they become someone’s emergency.

Potential Sidecar Feature

A recurring pain point in COI renewal discussions is that different teams use different reminder windows and escalation habits. One future Sidecar feature worth considering is a renewal cadence template by document category.

For example, COIs could use a 60/45/30/14-day workflow, while licenses, training cards, customer portal renewals, or certifications could use different lead times. Each template could suggest follow-up dates and waiting-party defaults without deciding whether the document is acceptable.

Another useful addition would be a pre-payment or pre-start checklist view that shows open tracked gaps before a subcontractor is paid or sent to a job, framed carefully as operational review rather than approval.

The practical takeaway

A COI renewal workflow does not need to be fancy. It needs to be current, reviewable, and clear about who owns the next step.

If your process only tracks expiration dates, you will still end up chasing people through email. If your process tracks the obligation, the status, the waiting party, and the next follow-up date, renewals become much easier to manage before the deadline starts breathing fire.

The goal is a morning workflow where a contractor admin can quickly answer: what am I missing?