Closing a coverage gap without the email chain: a deficiency workflow for GCs and brokers

Why gaps take so long

A typical deficiency email says "Your COI is not compliant, please send a corrected certificate." It goes to the trade's office manager, who forwards it to the broker, who doesn't know which requirement failed, who asks, who waits. Three rounds later, someone sends the same certificate again.

The fix isn't faster email. It's a better first message.

The one-pass deficiency notice

Every notice should carry five things.

1. The requirement, quoted from the subcontract or exhibit, with the clause.
2. What you received, with the document and date.
3. The gap, in one sentence.
4. The fix, named as a document: "the CG 20 37 completed operations endorsement, or the carrier's equivalent, naming [exact legal name]."
5. The date it's needed by, and what happens if it isn't.

A broker can answer that message without a single follow-up question.

Paper fix or coverage fix

Classify each gap before you send it.

• Paper fix. The coverage almost certainly exists; the proof is missing. A Y in the ADDL INSD column with no endorsement attached is the classic case. These should close in days.
• Coverage fix. The policy itself has to change: a higher umbrella, a completed operations endorsement the policy doesn't carry, a waiver on workers' comp. These take a carrier, a premium and longer. Some can't be done.

Paper fixes and coverage fixes need different people and different deadlines. Mixing them in one email slows both.

Who gets it

Send the notice to the person who can fix it: the trade's broker, whose name is in the producer box on the certificate. Copy the trade. Brokers are the ones who can issue endorsements, ask carriers for changes and explain what's possible.

The loop

1. Review each certificate and endorsement against the project's requirements. See How to read a COI against requirements.
2. Send one notice per trade, listing every gap, each classified.
3. Track each gap with its due date.
4. Re-check what comes back against the same requirement. Close the gap only when the document passes.
5. Escalate on the due date: to the trade's owner, then to the contract remedies your subcontract allows.

What brokers can do from their side

The same loop works in reverse. A broker who reads the GC's exhibit before issuing the certificate, and sends the endorsements with it, prevents most notices from being sent at all. See The broker's side of the COI.

The shared record

The email chain exists because nobody shares one record of what's required, what's been received and what's still open. Whatever tool you use, a spreadsheet, a portal or software, the goal is the same: one record both sides can see, where each gap has a requirement, a status and a date.