Nobody wants to chase a COI: automating vendor paperwork

Why this particular chore never gets done

Every operation has chores that get done because somebody notices. The truck needs fuel. The client is on hold. The tech is standing at a gate with no code. Vendor paperwork is not one of those, and four things keep it that way.

• It is boring. Nobody enjoys asking a roofer for a certificate of insurance for the fourth time in five weeks. It is a small, awkward favor, and it has to be asked over and over.
• It is nobody’s actual job. It sits in the seam between operations and accounting, and each assumes the other has it. In practice it belongs to whoever last happened to remember, which is a role with no backup.
• The consequence is invisible until it is catastrophic. A missing certificate costs nothing on an ordinary Tuesday, and nothing on nine hundred ordinary Tuesdays. Then a ladder goes through a storefront window, or a client’s risk manager asks for your vendor file before renewing your contract, and the whole bill arrives at once.
• The documents expire on their own schedule. Policies renew on the anniversary the carrier set. Licenses renew on the cycle the county set. Neither date has any relationship to your calendar.

The result is a failure that is silent by construction. Nothing tells you a vendor’s coverage lapsed — the vendor may not know either — so the first signal arrives after the point where you could have done anything about it.

The documents that actually matter

Before automating anything, cut the list down. If you cannot say in one sentence what a document protects you from, do not collect it: every extra field is another thing to chase and another reason a vendor abandons your form halfway through.

The W-9 is the identity document. It carries the legal name, entity type and taxpayer identification number you will put on a 1099 in January. Collect it late and you are reconstructing tax identity from a check stub in the worst week of the accounting year.

The certificate of insurance exists so a vendor’s accident is billed to the vendor’s carrier and not to yours. Two details outweigh the rest of the page. The first is the policy period, the only line that says when the certificate stops being true. The second is whether you are named as an additional insured — not the same as being the certificate holder, which only means somebody mailed you a copy. The endorsement is what extends the vendor’s coverage to you. Ask which one you have; most people find out at the worst possible time.

Workers’ compensation, or a documented exemption, is what stands between you and an injured worker on a site you control. Trade licenses matter wherever the work legally requires one — electrical, plumbing, HVAC, roofing, elevator, backflow — and they renew on cycles you have never seen, through offices you have never dealt with. The signed agreement settles every later argument: rates, terms, scope, materials, responsibility. It does not expire, but a rate change with no new signature is a rate change you will re-litigate by email in eight months.

For new employees rather than subcontractors, the set changes: the onboarding packet your payroll provider needs before the first paycheck runs, plus whatever your trade demands — a motor vehicle record for anyone in a company truck, certifications for anyone touching refrigerant. Same mechanism, different documents.

Document	Why you collect it	What “expired” looks like
W-9	Correct legal name and taxpayer ID for the 1099 you will issue	No end date — it goes stale on a change of name, entity or ownership. Re-request on any business change.
Certificate of insurance (general liability)	A vendor’s accident lands on the vendor’s carrier, not on you	A hard policy-period end date, usually mid-year. The renewal certificate has to be requested; it does not arrive on its own.
Additional insured endorsement	Extends the vendor’s coverage to you — being the certificate holder does not	Tied to the same policy period, and often not re-issued with the renewal unless you ask for it by name.
Workers’ compensation (or documented exemption)	An injured worker on your site does not become your problem	Annual policy dates. Exemption filings run on their own cycle and lapse just as silently.
Trade license or registration	The trades that legally require one, in the jurisdiction where the work happens	Set by the state or county, annual or biennial, never aligned to anything on your calendar.
Signed services agreement	Rates, payment terms, scope, indemnity — the terms of the argument you have not had yet	No expiry, but void in spirit the moment rates change without a new signature.
Employee onboarding packet	Payroll and eligibility paperwork for people on your books rather than subs	Not an expiry so much as a deadline from the first day of work — your payroll provider will tell you which ones and when.

Two failure modes: never collected, quietly expired

Never collected. A vendor is needed on Thursday, does good work on Thursday, and is paid the following Friday. Somewhere in there the certificate was going to be requested. It never was, and the moment is gone. Before you dispatch, you hold something the vendor wants. After you pay, you are a phone call they can safely ignore.

Quietly expired. You collected the certificate in January, saved it, put the vendor to work. The policy lapsed in March. You dispatched that vendor eleven more times and found out in September, after an incident, when somebody finally opened the file. This is the more common story and the more expensive one, because it feels like compliance right up to the moment it is not.

To size the risk with your own numbers: take the largest deductible on your own policy, add what your attorney bills for the hours a coverage dispute eats, and multiply by your honest guess at how many vendor-days a year run uninsured on your sites. Compare that against the two minutes it takes to file a certificate on the day it arrives. You do not need a study to finish that arithmetic.

Why the spreadsheet does not work

Almost everyone’s first fix is a tracker: vendors down the left, document types across the top, expiry dates in the cells, conditional formatting turning things red. As a data structure it is correct. As a mechanism it does nothing, because it depends on a person opening it, and the whole problem is that nobody opens it.

An expiry date in a cell is not a reminder; it is a fact waiting for an audience. The tracker is only as current as the last slow afternoon somebody had, and the day it stops being current is marked nowhere. Email threads are worse: a certificate attached to a reply about a broken condenser has technically been collected and practically been lost.

The fix is not a better spreadsheet. It is moving the trigger off the human. A system that works does not wait to be consulted. It goes looking, on a schedule, and it speaks first.

What a working system does instead

Six mechanics, none of them clever. What makes them work is that they run whether or not anyone is paying attention.

1. One intake link per vendor, not an email thread. A single link listing exactly what is missing for them, taking uploads from a phone. No account, no login, no reply-all. One text message becomes a complete request.
2. Documents filed against the vendor record, not into an inbox. An upload lands on the vendor’s row with its type, its dates and the file. If it is not attached to the vendor, it does not exist — that rule is what keeps the record trustworthy enough to act on.
3. The expiry date captured at the moment of filing. This is the whole ball game. A document filed without its end date can never be chased. Read the policy period off the certificate when it arrives and write it to a real date field.
4. A daily sweep that looks forward, not back. Once a day the system asks what no human ever will: what expires in the next sixty days, thirty days, seven days? Looking backward finds the disasters. Looking forward prevents them.
5. A chase sequence that escalates on a schedule. The first request is friendly and specific. The second is shorter. The third goes to a different contact. The fourth stops talking to the vendor and starts talking to your own team.
6. A digest so a human sees the whole bench at once. What is expiring, what is expired, who has been chased how many times, who has stopped answering. Not an alert per document — that is how people learn to ignore alerts — but one honest view on a predictable day.

That is the shape of the thing worth building, and the same skeleton as the rest of the operation — the pattern that moves a request from intake to paid without anyone remembering to move it.

Warn loudly. Block nothing.

Here is where most compliance systems go wrong, and it decides whether yours survives its first month. The obvious move, once you know which vendors have lapsed documents, is to enforce it: no valid certificate, no dispatch. It is clean, it is defensible, and it is how the whole thing gets switched off.

The recorded override is what makes warn-only defensible rather than sloppy. When someone dispatches a vendor with a lapsed certificate, capture who decided, when, for which job, and why. A gate that blocks teaches people to route around it. A gate that warns and remembers teaches them to fix the underlying problem, because the overrides pile up somewhere visible.

Make the warning impossible to ignore: on the vendor record, at the dispatch step, in the digest, in the chase. Just never make it the thing standing between a flooding building and the person who can stop it.

What stays human

Two decisions do not get automated, and trying is how automation earns a bad name.

The first is the decision to use a vendor whose paperwork is not in order. That is a risk judgment about a specific job on a specific day, turning on things no rule captures — how bad the situation is, how long the vendor has worked for you, whether the lapse is a real gap or a certificate sitting in an agent’s outbox. Software’s job is to make sure the person making that call knows the file is lapsed at the moment they make it.

The second is the relationship conversation when a vendor keeps ignoring you. Once the ladder runs out, the answer is not a fifth automated message in a firmer tone. It is a person picking up the phone, because the question has stopped being about a document. Either the vendor cannot get the paperwork — lost coverage, between carriers, a license that did not renew — which you need to know, or they can and will not, which tells you how the rest of the relationship will go. Automation should get you to that call fast, with the history in hand.

An implementation sketch

The shape is small enough to describe completely. Capture per document:

• Vendor, and the document type from a fixed list — free text here ruins every report you will ever run.
• Issuing party: the insurance agency, the licensing body, the vendor themselves.
• Issue date and expiry date as real date fields. Not text. Not “annual.”
• The file itself, attached to the vendor record.
• Who filed it, and whether a human confirmed the dates or a machine read them.
• For certificates: whether the additional insured endorsement is attached, as its own yes or no.

The states a document moves through: Missing → Requested → Received → Verified → Expiring → Expired, with two side exits — Waived, which requires a reason and a name, and Not applicable, for the vendor who genuinely does not need a license. Keep the list this short: every extra state is a status nobody can define under pressure, and those stop being filled in accurately within a month.

A chase cadence that has worked for us:

1. Sixty days out: a first notice naming the specific document and its end date, with a link that accepts the upload.
2. Thirty days out: a shorter reminder, same link.
3. Fourteen days out: the reminder plus a copy to a second contact at the vendor, if you have one.
4. Seven days out: the vendor record is flagged and the item enters the digest.
5. On the expiry date: status flips to Expired, the warning appears at the dispatch step, and the item escalates to your team rather than to the vendor.
6. After expiry: the chase slows to a weekly rhythm rather than stopping, so it stays visible without becoming noise people filter.

Adjust the intervals to your trades. What matters is that the ladder is fixed and automatic, so the fourth message goes out in the same tone as the first.

Where to start

Do not start by building the sweep. Start by opening your vendor list and writing an expiry date next to every certificate you already hold. It is a bad afternoon, and it is the only honest way to learn how much of your bench is covered by a document that stopped being true some months ago. That number is the real argument for automating this, and you make it to yourself with your own data.

Once the dates exist, the rest is mechanical: a link per vendor, a record per document, a sweep that looks forward, a ladder that escalates, a digest on a fixed day, and a warning that never becomes a wall. None of it is difficult. It is just work no human being will ever volunteer for — exactly the kind worth handing to a system.

If you would rather not build it, that is the sort of thing we do. Tell us what your bench looks like on a quote request, or book a free discovery call and we will map it with you — you keep the map either way.