The rejection notice that tells a sub’s broker exactly what to fix, by coded reason, so the corrected certificate comes back right the first time, not the fourth.
COI Rejection Notice. Reason Codes
Why every prime needs a structured COI rejection notice with reason codes
A general contractor’s risk manager or project administrator rejects non-compliant certificates of insurance all week long. The problem is rarely the rejection itself. The problem is what the rejection says. When the reply to the sub’s broker is some version of “this isn’t right, please resend,” the broker has no idea what “right” means, guesses, and sends back a second certificate that fixes one thing and misses three others. Now it’s the third certificate, then the fourth, and two weeks have burned while the sub is staging crews on a project where the prime still can’t confirm coverage. The back-and-forth isn’t a coverage problem. It’s a communication problem, and the certificate-of-insurance process creates a brand-new one for every sub on every project.
The fix is a structured rejection notice built on reason codes. Instead of a vague note, the prime sends back a document where every single deficiency gets three things: a code, the exact remedy, and the specific endorsement form the broker needs to attach. “R7: Missing additional insured (completed operations). Attach CG 20 37 naming the certificate holder, and return a copy of the endorsement form with the corrected certificate.” The broker reads that and knows precisely what to do. There is nothing to interpret, nothing to guess, no second guess that produces a fourth certificate. The reason-code concept turns a multi-week chase into a single fix because the prime did the broker’s translation work up front, the same way a good COI request letter does it at subcontract execution.
This matters because the manual version of this process does not scale. A prime with 50 active subs across four projects is running dozens of certificate reviews a month, and a meaningful share of those certs fail on first pass. Each failure becomes a rejection that has to be written, coded, sent, tracked, and re-checked when the corrected cert lands. Doing that by hand, certificate by certificate, broker by broker, is exactly the kind of repetitive document work that eats a contracts administrator’s week. If you want to stop tracking COI rejections by hand, the rejection notice is the artifact you systematize first, because it’s the one that repeats most and varies least. Teams comparing options for that often start with the roundup of the best COI tracking software for general contractors to see how the coding-and-re-chase loop gets automated.
The reason codes below are the real set a federal or large-commercial prime uses to reject a certificate. Each one names the deficiency, the remedy, and where the form number is involved, the specific ISO or workers’ comp endorsement that closes the gap. Use them as a fixed vocabulary across every project. When every rejection your team sends speaks the same coded language, the brokers on the other end learn it too, and the certs start landing compliant on the first try because everyone knows the rules of the game before the first cert is even issued. Keep the sent rejection notice in the sub’s contracts file alongside the original request letter and the eventually-compliant certificate. That bundle is the audit trail when a contracting officer asks why this sub’s coverage was accepted for mobilization, and it shows the reviewer did the work.
Who this rejection notice is for
- Risk managers at general contractors who reject and re-chase non-compliant certificates across active projects
- Contract administrators running pre-mobilization paperwork and the renewal-cycle COI reviews
- Project administrators maintaining the daily working binder of active sub coverage
- General contractors managing insurance flow-down to subcontractors on commercial and private-owner work
- Prime contractors required to verify and retain compliant sub-COIs under federal contract and Miller Act provisions
- Subcontract compliance coordinators standardizing the rejection vocabulary across a portfolio of projects
If you’re on the sub side trying to decode why a prime keeps bouncing your certificate, work through the ACORD 25 review checklist (federal projects) first. It’s the same form-by-form review the prime runs before they code the rejection, so it tells you what’s about to get flagged.
The 16 reason codes every COI rejection notice draws from
The notice carries 16 reason codes covering the deficiencies that actually get a certificate of insurance rejected. Each code names the problem and the exact remedy, including the specific endorsement form to attach where one applies:
- R1 Expired or soon-to-expire policy One or more policies on the certificate have already expired, or will expire before the project completion date or the next renewal review. A certificate is a snapshot; coverage that lapses mid-project leaves a gap the prime is exposed to. Remedy: issue a corrected certificate showing policy periods that extend through the required date, and set the renewal cert to arrive 30 days before expiration.
- R2 Insufficient CGL per-occurrence limit The Commercial General Liability per-occurrence limit is below the required floor, commonly $1,000,000 per occurrence on standard work and $2,000,000 for higher-risk trades. The per-occurrence limit is the cap on a single claim, so an underbuilt limit is a real exposure on a serious loss. Remedy: the broker endorses the policy up to the required per-occurrence limit and reissues the certificate.
- R3 Insufficient CGL aggregate limit The general aggregate or the products-completed-operations aggregate is below requirement, commonly $2,000,000 general aggregate and a matching products-completed-ops aggregate. The aggregate is the annual ceiling across all claims, so a low aggregate can be exhausted by unrelated claims on the sub’s other jobs. Remedy: raise the aggregate to the required value, and pair it with the per-project aggregate code below so the project’s limit can’t be drained elsewhere.
- R4 Missing per-project aggregate endorsement The certificate shows a single shared aggregate with no per-project endorsement, which means another project’s claims can consume this project’s coverage. Remedy: attach the ISO per-project aggregate endorsement, typically CG 25 03 (Designated Construction Project(s) General Aggregate Limit) or CG 25 04 (Designated Location(s) General Aggregate Limit), and return a copy of the endorsement with the corrected certificate. Confirm which form fits the project structure.
- R5 Missing additional insured, ongoing operations The prime (and any required upstream parties) are not named as additional insureds for ongoing operations, so the sub’s policy doesn’t defend the prime for claims arising during active work. Remedy: attach CG 20 10 (Additional Insured, Owners, Lessees or Contractors, Scheduled Person or Organization) or its equivalent naming the correct entities, and return a copy of the endorsement. Verify the edition date is acceptable, since older CG 20 10 editions extended to completed operations and newer ones do not.
- R6 Additional insured edition-date / scope gap An additional insured endorsement is present but the edition date or scope is wrong for the requirement, a frequent and easy-to-miss defect. The form number alone doesn’t tell you the scope; the edition date does. Remedy: confirm the required edition date and reissue with the correct edition, or add the second endorsement needed to cover the missing scope.
- R7 Missing additional insured, completed operations The certificate covers ongoing operations but not completed operations, so the prime loses additional-insured protection after the sub finishes and demobilizes, which is when many construction-defect claims actually surface. Remedy: attach CG 20 37 (Additional Insured, Owners, Lessees or Contractors, Completed Operations) naming the certificate holder, and return a copy of the endorsement form.
- R8 Missing primary and non-contributory wording Without primary and non-contributory language, the sub’s insurer can argue the prime’s own policy shares the loss, defeating the purpose of the additional-insured endorsement. Remedy: attach the primary and non-contributory endorsement, commonly ISO CG 20 01 (Primary and Noncontributory, Other Insurance Condition), and return a copy. Confirm the form on the sub’s policy actually carries the wording, since some carriers use a manuscript version.
- R9 Missing waiver of subrogation (CGL) The general liability policy doesn’t include a waiver of subrogation in favor of the prime, leaving the sub’s insurer free to pursue the prime to recover what it pays on a claim. Remedy: attach the CGL waiver of subrogation endorsement, commonly ISO CG 24 04 (Waiver of Transfer of Rights of Recovery Against Others to Us), and return a copy of the endorsement.
- R10 Missing waiver of subrogation (workers’ comp) The workers’ compensation policy lacks a waiver of subrogation, so the WC carrier can subrogate against the prime after paying a worker’s claim. Remedy: attach the workers’ comp waiver of subrogation endorsement. The NCCI blanket form is commonly WC 00 03 13 (Waiver of Our Right to Recover From Others Endorsement); some states use a state-specific waiver form, so confirm the applicable form for the state of work.
- R11 Insufficient auto liability limit or missing hired/non-owned The Business Auto limit is below the required combined single limit, commonly $1,000,000, or the certificate shows scheduled autos only without hired-and-non-owned coverage. Subs that use rented trucks or employees’ personal vehicles on the project have a real auto exposure the prime needs covered. Remedy: raise the limit to requirement and confirm “any auto” or the owned/hired/non-owned combination, then reissue.
- R12 Insufficient or missing umbrella / excess There is no umbrella or excess liability, the limit is below the required floor, or the umbrella is not written follow-form over the underlying CGL, Auto, and Employer’s Liability. A non-follow-form umbrella at the same dollar amount is materially weaker than a follow-form one. Remedy: provide umbrella or excess at the required limit on a follow-form basis and reissue the certificate showing it.
- R13 Missing or insufficient workers’ comp / employer’s liability Workers’ compensation is missing, below statutory requirement for the state of work, or the Employer’s Liability limits are below requirement, commonly $1,000,000 each accident, $1,000,000 disease each employee, and $1,000,000 disease policy limit. WC statutory limits are non-negotiable, and Employer’s Liability is where sub policies quietly underperform. Remedy: confirm statutory WC for the correct state and raise Employer’s Liability to the required limits.
- R14 Carrier A.M. Best rating or financial size below requirement A policy is written by a carrier rated below the required A.M. Best threshold, commonly A- or better with a financial size category of VIII or larger; higher-risk work may require A. A certificate from an underrated carrier fails before the coverage terms even matter. Remedy: confirm the carrier’s current A.M. Best rating and financial size category meet the floor, or move the coverage to a carrier that does.
- R15 Wrong or missing certificate holder, project, or description of operations The certificate holder field is blank, lists a generic entity like “General Contractor,” or names the wrong legal entity, or the description of operations references the wrong project, scope, or project number. Generic or wrong holder text can leave cancellation-notice provisions unenforceable. Remedy: reissue with the prime’s exact legal entity, the correct project number and address in the holder field, and the correct project in the description of operations.
- R16 Endorsement copies not attached, or missing trade-specific coverage The certificate box-checks the required endorsements but no actual endorsement forms are attached, or a trade that needs Professional Liability or Pollution/Environmental coverage doesn’t show it (design-build, abatement, or environmental scopes). A box-check is not evidence; the attached form is. Remedy: return copies of every required endorsement form, and for the applicable trades, provide the Professional or Pollution Liability the scope requires.
How to send the rejection notice and re-check the corrected cert
Run the rejection notice the moment a certificate fails review. For each non-compliant cert:
- Review the certificate against the project’s insurance requirements and mark every failed item with its reason code (R1 through R16). One certificate can carry several codes.
- For each code, fill the exact remedy and the specific endorsement form the broker needs to attach. Don’t leave a code without its remedy line.
- Attach the original COI request letter so the broker can see the full requirement set in one place, not just the items that failed.
- Set a return deadline with a specific date, not “as soon as possible,” and send to the sub’s named contact with the broker cc’d so the broker can reissue directly.
- Log the rejection in your COI tracker with the date, the codes fired, and the deadline, so a late or still-non-compliant resubmission surfaces instead of slipping.
- Re-check the corrected certificate against the same codes when it lands. Clear the codes that are fixed, and re-issue the notice for any that are still open before filing.
Stop coding COI rejections by hand
Writing one rejection notice is 15 minutes. Writing them across 50 subs on four projects, coding each deficiency, sending it to the right broker, logging it, and re-checking every corrected cert against the original codes is a part-time job that never ends, and the second a cert slips through uncoded the chase starts over. Contracts Connected’s COI Analyzer reviews the certificate the moment it lands, validates limits and endorsement form numbers against the project’s requirements, generates the coded rejection notice automatically for the items that fail, sends it to the sub’s broker, and re-checks the corrected certificate against the same codes on resubmission, so your team’s time goes to the genuine exceptions instead of the routine back-and-forth.
For educational purposes. These templates, checklists, and trackers are operator-built starting points designed to help you move faster on the kind of work that usually drowns construction admins in email chains. They are not legal, insurance, accounting, or tax advice. Each project, jurisdiction, and contract has its own quirks. Review the document, refine the language, and consult your attorney, broker, CPA, or compliance officer before relying on it for a live project decision.
Frequently asked questions about COI rejection notices
What is a COI rejection notice?
A COI rejection notice is the document a general contractor sends back to a subcontractor and its insurance broker when a certificate of insurance fails the prime’s compliance review. A good one doesn’t just say the certificate was rejected; it lists each specific deficiency, the exact remedy, and the endorsement form the broker needs to attach. The reason-code format turns a vague “please resend” into a precise punch list, which is what makes the corrected certificate come back compliant on the first try instead of after several rounds.
What are the most common reasons a certificate of insurance is rejected?
The recurring ones are expired or soon-to-expire policies, limits below the required floor (general liability, auto, umbrella, employer’s liability), missing endorsements (additional insured for ongoing and completed operations, primary and non-contributory, waiver of subrogation, per-project aggregate), a carrier rated below the required A.M. Best threshold, a wrong or generic certificate holder, the wrong project in the description of operations, and the certificate box-checking endorsements without attaching the actual endorsement forms. Most rejected certs fail on more than one of these at once, which is exactly why coding each deficiency separately matters.
What is the difference between CG 20 10 and CG 20 37?
They cover different phases of the work. CG 20 10 is the ISO additional insured endorsement for ongoing operations, the claims that arise while the subcontractor is actively performing. CG 20 37 is the ISO additional insured endorsement for completed operations, the claims that arise after the work is finished, which is when many construction-defect claims actually appear. Because newer editions of CG 20 10 generally do not extend to completed operations, primes typically require both forms together so the additional-insured protection doesn’t end the day the sub demobilizes. Always confirm the edition dates, since the scope shifted across editions.
What does primary and non-contributory mean on a COI?
Primary means the subcontractor’s policy responds first to a covered claim, before the prime’s own insurance is touched. Non-contributory means the sub’s insurer cannot demand that the prime’s policy chip in to share the loss. Together, the wording makes the sub’s coverage actually do the work the additional-insured endorsement promises, rather than the two policies fighting over who pays. It’s commonly added with ISO CG 20 01, though some carriers use manuscript wording, so the prime confirms the language is actually present and not just box-checked on the certificate.
What is a waiver of subrogation?
Subrogation is an insurer’s right to step into its policyholder’s shoes after paying a claim and pursue whoever else was at fault to recover the money. A waiver of subrogation is an endorsement in which the sub’s insurer gives up that right against a named party, usually the prime and the owner. Without it, the sub’s carrier could pay a worker’s injury claim and then turn around and sue the prime to get reimbursed. Primes require it on both general liability (commonly ISO CG 24 04) and workers’ compensation (commonly the WC 00 03 13 blanket form or a state-specific equivalent).
How do you ask a subcontractor to fix a rejected COI?
Send a structured rejection notice rather than a one-line email. List every deficiency with its reason code, state the exact remedy for each, name the specific endorsement form the broker needs to attach, set a firm return deadline with a real date, and cc the sub’s broker so they can reissue directly. Attach the original COI request letter so the broker sees the complete requirement, not just the failed items. The clearer the punch list, the fewer rounds it takes, which is the entire point of coding the rejection instead of describing it.