COI tracking hub
COI Tracking for General Contractors: A Practical Workflow
COI tracking does not have to start as a giant compliance platform. It has to answer a few questions reliably: which subcontractors are current, which certificates are missing, which ones expire soon, and where is the reviewed PDF?
What COI tracking actually means
Most COI tracking problems do not start as software problems. They start as tiny loose ends: a certificate expires next week, nobody owns the reminder, the subcontractor sent the wrong version, and the project manager assumes the office already handled it.
For a general contractor, the job is not just collecting PDFs. The job is keeping a reliable operating record for subcontractor insurance certificates: who is covered, what was reviewed, what is expiring, what needs follow-up, and where the proof lives when an owner asks for it.
This guide lays out the minimum system. You can run it in a spreadsheet first. If the spreadsheet starts lying to you — or, more politely, stops being trustworthy — that is the signal to add a purpose-built tracker.
The minimum COI tracking system
A useful tracker needs four pieces:
- One active subcontractor roster — not every sub you have ever used, but the subs working now or likely to start soon.
- One reviewed certificate record per sub — including where the PDF is stored and when it was reviewed.
- One status label — current, expiring soon, expired, missing, or needs review.
- One reminder rhythm — a repeatable process for renewal requests and follow-ups.
If those four pieces are clear, the office can answer the important question quickly: “Can this sub start or continue work without someone scrambling for proof?”
Fields every COI tracker should include
Start with these fields before adding anything fancy. The point is not to create the world’s most complete spreadsheet. The point is to create a tracker someone else in the office can understand without a 20-minute explanation.
| Field | Why it matters |
|---|---|
| Subcontractor name | The company you hired, matching the insured name or flagged when it does not. |
| Trade or scope | Helps prioritize active job-site exposure and route follow-up internally. |
| Contact email | The person who should receive certificate requests and renewal reminders. |
| Certificate file location | A link or folder path to the reviewed PDF, not just “on file somewhere.” |
| Coverage expirations | General liability, workers comp, auto, umbrella, or any line your contracts require. |
| Certificate holder / additional insured check | Flags whether the certificate matches your contract requirements before it is marked current. |
| Status | The plain-English answer: current, expiring soon, expired, missing, or needs review. |
| Last requested / next reminder | Prevents the “I thought someone emailed them” problem. |
| Owner | The person responsible for follow-up if the row turns yellow or red. |
If you want a field-by-field version, use the COI tracking spreadsheet template as the starting point.
Status labels that prevent fake confidence
The worst status label is “done.” It hides too much. A COI can be received but not reviewed. Reviewed but expiring. Current but missing an endorsement your contract requires.
Use labels that force the next action into the open:
- Current — reviewed and not expiring inside the reminder window.
- Expiring soon — earliest required coverage expires inside your 60- or 90-day window.
- Expired — at least one required policy date has passed.
- Missing — no usable certificate is on file.
- Needs review — certificate received, but something is unclear or does not match requirements.
That last label matters. It keeps a newly uploaded PDF from becoming false reassurance.
The weekly COI tracking rhythm
Pick one day each week for a short review. Friday morning is usually better than Friday afternoon, for obvious human reasons.
- Filter for expired and missing certificates first.
- Check anything expiring in the next 30, 60, or 90 days.
- Send renewal reminders to the right subcontractor contact.
- Assign an owner for any follow-up that needs a phone call or project-team nudge.
- Review newly received PDFs before changing a status to current.
For the reminder cadence and email copy, use the COI renewal reminders workflow.
What to review before marking a certificate current
Receiving a PDF is not the same as having a clean certificate on file. Before marking a subcontractor current, check the basics:
- insured name matches the subcontractor you hired;
- policy numbers and effective dates are visible;
- expiration dates are not inside your immediate risk window;
- coverage limits meet the requirements your team is tracking;
- certificate holder and additional insured language are reviewed when required;
- the reviewed PDF is stored somewhere another person can find it.
This is operational guidance, not legal or insurance advice. Contract requirements and coverage interpretation should go through the appropriate insurance/legal review path for your company.
Spreadsheet or dedicated COI tracker?
A spreadsheet is a good starting point when the sub list is small, one person owns the process, and reminders are still manageable. The spreadsheet is not the enemy. The fake confidence around the spreadsheet is the problem.
Manual tracking starts to break when:
- multiple people update the same rows differently;
- the PDF location is unclear or stale;
- reminders depend on someone remembering to check dates;
- status labels mean different things to different people;
- project teams ask for proof faster than the office can find it.
At that point, the next system should not force every subcontractor into a portal or replace your full construction stack. It should make the existing COI workflow more reliable: intake, review, status, storage, reminders, and proof on demand.
Outgrowing the COI spreadsheet?
CertKeeper helps general contractors track subcontractor certificates, review dates, file locations, and renewal reminders without forcing subs into a new portal. Request early access if your current process is starting to leak.
Request early access