No COI on file, no authorization to proceed — the compliance mindset veteran GCs already have

I come from a military family. My brother served as a Marine, and for a stretch of time after he got out, I worked on his paving crew in south Florida — laying pavers in the kind of heat that makes you question your life choices before 9 a.m. It was hard work. Real work. And it taught me more about how a small construction crew actually operates than anything I learned later.

One afternoon a patrol officer rolled up on us in the subdivision we were working. Someone had spotted a bobcat on the road between lots. The problem: I was driving it, and I was underage. No operator license, no authorization, nothing on paper to say I was cleared to be behind the controls of that machine on a public road. We got a serious talking-to. No fines that day — we were lucky — but the point landed hard. The exposure was real, the documentation was missing, and "we didn't think it would be a problem" was not a defense.

That moment is a big part of why I built Send The Proof. Because the same failure pattern that got us sideways that afternoon plays out on job sites every day — not with unlicensed operators, but with uninsured subcontractors. And the fix is the same: get the paperwork in order before the work starts, not after something goes wrong.

You already understand authorization to proceed

If you served, you lived inside a system where documentation was the prerequisite for action — not a formality, not a nice-to-have. You didn't deploy personnel without briefing them in. You didn't move equipment without the logbook current. You didn't authorize entry without verified clearance. The sequence was non-negotiable because the consequences of skipping it were not theoretical.

Subcontractor COI compliance works exactly the same way. A certificate of insurance is not a piece of paperwork you collect to satisfy a project owner's checklist. It is the document that tells you, as the person commanding the job site, that the vendor you are authorizing to work is covered — that if something goes wrong on your site, their liability does not automatically become yours. Without it, you are letting uncleared personnel through the gate. And in construction, the consequences of that are just as real as they were in the service.

Veterans represent roughly 11 percent of owner-operated construction businesses in the United States. That is a disproportionately high share for a population that is a small fraction of the general workforce. It is not an accident. The operational discipline, the tolerance for complex logistics, the accountability culture — it all translates. But the one area where that discipline can quietly break down is document oversight at scale. When you have 15 active subs and every one of them has a COI with a different expiration date, keeping manual track of who is cleared and who is not is harder than it sounds.

Compliant vs. non-compliant: you need a status board, not a spreadsheet

Think about how a well-run operations center tracks personnel readiness. Not a list of names in a notebook. A board — or a system — that shows status at a glance. Green means ready. Red means blocked. You do not have to dig through files to know if someone is cleared for the mission. The status is visible, current, and maintained without someone manually updating it from memory.

That is the exact thing most GC teams do not have for subcontractor compliance. What they have instead is a spreadsheet that someone updates when they remember to, an inbox full of COIs in PDF format with no expiration tracking, and a vague sense that "everyone's probably current." That vague sense is what creates exposure. A sub's policy renews in March. Nobody notices when it lapses in February. A worker goes down in April. Now you are the GC with an expired certificate on file, and the question of who carries the liability has a very uncomfortable answer.

What I built with Send The Proof is closer to the status board model. Every vendor has a compliance signal — compliant, expiring soon, or blocked. You see it at a glance without opening a single file. When a COI is about to expire, the system flags it and sends the sub a renewal request automatically, 30 days out. When a new sub uploads their certificate, it lands in their record with a timestamp. When someone asks you what was on file and when, you pull the audit trail — not a thread of forwarded emails.

The protocol is simple. The execution is where it breaks down.

The right COI protocol for any GC operation is straightforward: no certificate on file, no authorization to begin work. Period. Not "we'll get it before the end of the week." Not "they've worked with us before, they're covered." The document has to be in hand, current, and showing the right coverage limits and additional insured language before the first crew member sets foot on site.

Every veteran GC I have talked to gets this immediately. The protocol makes sense. The problem is execution — specifically, the manual work of enforcing it across a rotating roster of subs at different stages of the project, with different renewal dates, different agents, and different levels of responsiveness. The protocol holds until workload pressure hits, and then shortcuts start. Someone mobilizes a day early. Someone's COI expires mid-project and nobody catches it for three weeks. The protocol is right. The system to enforce it without relying on memory is missing.

That gap is exactly what Send The Proof closes. You set the protocol once — what documents each vendor needs, what the coverage requirements are, what the deadline is. The system runs the follow-up. Automated reminders go out when documents are missing. Expiration alerts fire 30 days before a policy lapses. You see who is cleared and who is not without touching a spreadsheet. Payment can be gated on compliance status so there is never a question of whether a check goes out to a non-compliant sub.

The paperwork is the gate. Automate the gate.

Running a GC business with the discipline you brought home from the service means holding the line on process — even when it is inconvenient, even when a sub pushes back, even when the deadline is tomorrow and the crew is already staged. You know better than most that "we'll sort the paperwork later" is how operations go sideways.

The first five vendors are free, no credit card required. If the workflow holds up on a handful of live subs — and it will — the paid plan runs $29.95 a month. For a veteran-owned GC operation built on accountability and precision, that is about the lowest-cost insurance against the one failure mode that tends to get overlooked: the vendor you trusted slipped through the gate without clearance, and you did not have a system to catch it.

Start free at Send The Proof — no account setup for your subs required. They get a link, they upload, you see it.

Related: what a lapsed COI actually costs when an incident hits, the compliance status dashboard, and the subcontractor compliance checklist.