The 12-element letter federal and commercial-construction primes send to subs to demand a compliant ACORD 25, with required A.M. Best carrier ratings, CGL/Auto/Umbrella/WC limit thresholds, and the specific CG-form endorsements written into the letter body itself, not buried as box-checks.
[Prime General Contractor] · 1455 Federal Construction Way · Reston, VA 20190 · 703-555-0140
Why every prime needs a structured COI request letter to subs
Every general contractor has the same drawer of one-off COI request emails. Some are forwarded chains where the project administrator just typed “please send your insurance” and pasted the broker’s address. Some are signed letters from the risk manager that worked for one project two years ago and got recycled with the project number swapped. Some are blank ACORD 25 templates the prime emailed with the words “fill this out.” None of them tell the sub’s broker what coverage the prime actually requires, what limits, which carrier ratings, which endorsement forms by form number, so the broker issues whatever the sub’s policy default looks like, the cert lands in the prime’s binder ten days later, and the risk manager spends another three hours rejecting and resubmitting because the additional-insured language references the wrong form or the per-project aggregate is missing entirely.
The fix is a single, structured letter that goes to every sub at subcontract execution. The letter does the broker’s job of translating the prime’s contract requirements into specific instructions: “Issue an ACORD 25 with the following limits, name the following entity as certificate holder, attach copies of CG 20 10, CG 20 37, CG 24 04, CG 25 03, and CG 20 01 endorsements, and return both the certificate and the endorsement copies within 7 days.” Sent that way, the sub’s broker has nothing to interpret. The first cert that comes back is closer to compliant than the third or fourth iteration of the email-chain method.
What makes a federal or large-commercial COI request letter different from the generic vendor templates floating around the SERP:
- Carrier ratings written into the letter. Federal primes generally require A.M. Best A- or better with VIII or larger financial size. High-risk trades on commercial work commonly require A. The letter names the rating threshold so the sub’s broker knows up front whether the policy meets the floor before they issue anything.
- Specific limit thresholds, not “industry standard.” $1M per occurrence / $2M aggregate is the federal-prime baseline. $2M / $4M for higher-risk trades. $5M umbrella minimum on federal, $10M+ on large commercial. The letter states the actual numbers the sub’s policy must meet. Generic letters that say “industry-standard limits” produce industry-standard rejections.
- Endorsements named by form number, not by box-check shorthand. “Additional insured ongoing operations” is not specific enough. The sub’s broker may use ISO CG 20 10, AAIS CL 0220, or a manuscript form. The letter names CG 20 10 (ongoing ops), CG 20 37 (completed ops), CG 24 04 (waiver of subrogation. CGL), CG 25 03 (per-project aggregate), and CG 20 01 (primary and non-contributory) and demands copies of the actual endorsement forms attached to the certificate.
- Certificate holder named with project number. The certificate holder field on the COI must read the prime’s exact legal entity plus the project number. Generic listings like “General Contractor” or “Owner” leave cancellation-notice provisions unenforceable. The letter spells out the certificate holder text the broker should use verbatim.
- A real submission deadline with an escalation path. “Please return within 7 business days.” Not “as soon as possible.” If the cert doesn’t land by the deadline, the letter names the escalation: prime’s risk manager copies the sub’s broker directly, then the sub’s principal, then withholds the first pay application. Subs respond to deadlines that have teeth; they ignore ones that don’t.
This letter is the practitioner’s version. It’s the artifact a federal-prime contracts admin sends at subcontract execution and again at every renewal cycle. Sent once correctly, it eliminates the back-and-forth email chain that wastes 60-90 minutes per sub during pre-mobilization. Run it through every sub’s broker on every active project. Keep the sent letter in the sub’s contracts file alongside the returned COI and endorsement copies. That’s the audit trail when the contracting officer asks why this sub’s coverage was deemed acceptable for mobilization.
Who this letter is for
- Federal general contractors issuing subcontracts on Davis-Bacon and Miller Act projects with strict insurance flow-down requirements
- Commercial general contractors managing 50–500+ subcontractor COIs across active projects with insurance flow-down obligations to private owners and lenders
- Prime contractors required to verify and retain sub-COIs under FAR 28.106 and Miller Act provisions
- Contracts administrators running pre-mobilization paperwork
- Project administrators maintaining the daily working binder of active sub coverage
If you’re the sub’s risk team trying to decode what the prime’s letter is asking for, work through the ACORD 25 review checklist (federal projects) first. It’s the same form-by-form review the prime is going to run on whatever you send back.
The 12 elements every COI request letter must contain
The letter has 12 elements every COI request letter must contain. In the order an experienced risk manager structures the document:
- Letterhead, date, and reference block Prime’s letterhead at top, today’s date below, then a reference block that names the sub’s legal entity, the subcontract number, the project name, and the subcontract execution date. This block is what the sub’s broker uses to confirm they’re issuing the cert against the right project, and what the prime’s reviewer uses to file the returned cert against the right binder. Generic “to whom it may concern” letters skip this and create downstream filing problems.
- Salutation to the sub’s authorized contact, named individually Address the letter to a named individual at the sub. Typically the sub’s contracts admin or risk manager whose name is in the subcontract notice block. Not “to whom it may concern.” Not “Dear Subcontractor.” Brokers respond faster when the sub’s accountable contact is on the letter, because they know the sub’s principal will be cc’d if the cert doesn’t land on time.
- Project context paragraph: project name, address, prime, contract value One short paragraph that establishes the project: name, full street address (or federal site identifier), prime contractor’s exact legal name, and approximate subcontract value. The broker uses this to determine which of the sub’s policies apply (some carriers exclude federal work, some have site-specific exclusions) and to set the proper insurer in the certificate.
- Required A.M. Best carrier ratings stated explicitly Name the threshold: “All policies must be issued by carriers rated A- or better at A.M. Best, with financial size category VIII or larger.” Higher-risk trades may require A or A+. Say so in the letter. The threshold goes in the letter so the sub’s broker knows up front whether the existing policy meets the floor; carriers rated below the threshold fail the cert before it’s even issued.
- CGL limits stated as exact dollar values “Commercial General Liability with limits of $1,000,000 per occurrence, $2,000,000 general aggregate, and $2,000,000 products-completed-operations aggregate.” For higher-risk trades (electrical, structural steel, demolition) commonly $2M / $4M. Spell out per-occurrence, general aggregate, and products-completed-ops aggregate as three separate values. Generic “industry-standard” language is what produces sub policies that meet two of three thresholds.
- Auto liability $1M combined single limit minimum “Business Auto Liability with a $1,000,000 combined single limit covering owned, hired, and non-owned autos.” Higher limits ($2M) when the sub has fleet equipment or off-road vehicles in scope. Specify “any auto” or the owned/hired/non-owned combination explicitly: “scheduled autos” only is a frequent gap.
- Umbrella or excess limits stated with follow-form requirement “Umbrella or Excess Liability with a $5,000,000 minimum limit, follow-form basis over the underlying CGL, Auto, and Employer’s Liability.” Federal projects often $5M floor; large commercial $10M+. The follow-form requirement is critical: a $5M umbrella with non-follow-form language is materially weaker than the same dollar amount on a follow-form basis. State the follow-form requirement in the letter.
- Workers’ comp statutory plus $1M employer’s liability “Workers’ Compensation at statutory limits for the project’s state of work, plus Employer’s Liability of $1,000,000 per accident, $1,000,000 disease per employee, $1,000,000 disease policy limit.” USL&H when work is over navigable waters; Jones Act when on a vessel. Name those explicitly when applicable. Statutory WC limits are non-negotiable but employer’s liability is where most sub policies underperform without notice.
- Required endorsements named by form number, with copies demanded This is the section every generic COI request letter skips. Name each endorsement by form number and edition date: “CG 20 10 (Additional Insured, Ongoing Operations), CG 20 37 (Additional Insured, Completed Operations), CG 24 04 (Waiver of Subrogation, CGL), CG 25 03 (Per-Project Aggregate), and CG 20 01 (Primary and Non-Contributory).” Demand copies of the actual endorsement forms attached to the certificate, not just box-checks. State-specific WC waiver-of-subrogation forms get a parallel mention. Without form-number specificity, the sub’s broker may use any equivalent, and equivalents are often narrower.
- Certificate holder text and project number stated verbatim “The Certificate Holder shall read: [Prime’s Exact Legal Entity] · Project [Project Number] · [Project Address].” The broker copies this text into the certificate holder field exactly as written. Generic listings like “General Contractor” or “Owner” leave cancellation-notice provisions unenforceable; the prime’s exact legal entity at the project’s address is what makes the cancellation-notice clause stick.
- Submission deadline with day count from letter date “Please return the certificate and endorsement copies within 7 business days of this letter.” Not “as soon as possible.” Not “promptly.” The deadline goes on the letter so the sub and the broker both have a date they’re on the hook for. Federal projects often allow 5 business days; commercial projects 7-10. Whatever the cadence, name the date in the letter.
- Closing, signature block, and escalation path for non-response Letter closes with a one-line statement of what happens if the certificate doesn’t land by the deadline: “If we do not receive a compliant certificate by [Date], we will escalate directly to the sub’s broker and principal, and pay applications will be withheld until compliance is confirmed.” Then the prime’s risk manager’s signature, name, title, direct phone, and direct email. The escalation language is what makes the deadline real; without it, the deadline is a suggestion.
How to send the letter and chase the certificate
Send this letter at subcontract execution and again on every renewal cycle. For each new sub:
- Customize the letter from the template. Fill the project context, the limit values that match the subcontract’s insurance exhibit, and the certificate holder text with the prime’s exact legal entity and project number.
- Send to the sub’s named contracts admin via email, with the sub’s broker cc’d. The cc to the broker shortcuts the back-and-forth. The broker can issue the cert directly without waiting for the sub’s admin to forward.
- Calendar the deadline date. If the certificate doesn’t arrive by the deadline, send the escalation per the closing paragraph: cc the sub’s principal, then withhold the first pay application until compliance is confirmed.
- When the certificate lands, run the ACORD 25 review checklist (federal projects) on it before filing. Reject and resubmit anything that fails the 12-line review.
- File the sent letter, the returned COI, and the endorsement copies together in the sub’s contracts file. That bundle is the audit trail when the contracting officer asks why this sub was deemed acceptable for mobilization.
Renewal cadence: 60 days before policy expiration, send the same letter again with the renewal effective date filled in. Same letter, same deadlines, same escalation path. Subs and brokers respond faster on renewal when the format matches the original request.
Stop sending one-off COI request emails
The 12 elements above take a contracts admin 20 minutes per sub when the template is dialed in, and 60-90 minutes per sub when the prime is writing one-off emails, the broker comes back with the wrong form numbers, and the certificate iterates two or three times before it’s compliant. Multiply by 50 active subs across 4 projects and you’ve built a part-time job out of the COI request itself, before anyone has even reviewed the certificate that comes back. Contracts Connected’s COI Analyzer auto-generates the request letter from the subcontract’s insurance exhibit, sends it to the sub’s broker on subcontract execution, runs the 60-day renewal cadence on every active policy, parses the returned certificate the moment it lands, validates limits and endorsement form numbers against the original letter’s requirements, and only flags the certs that fail. Same 12-element letter, but it sends itself and reviews itself across every sub on every project. The contracts admin’s time goes to the exceptions, not the routine.
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 request letters
When should I send this COI request letter?
Send at subcontract execution. The same day the subcontract is countersigned. Every day between subcontract execution and certificate receipt is a day the sub may be performing prep work, ordering materials, or staging crews under uncertain coverage. Pre-mobilization is the only safe window. On renewal, send the letter 60 days before policy expiration so the sub’s broker has a 30-day window to issue the renewal cert and your project administrator has a 30-day cushion to chase if the cert is late.
What if the sub doesn’t have the required insurance limits?
Two paths. Path 1 (preferred for committed subs): the sub’s broker can typically endorse the existing policy up to the required limit at additional premium. The sub absorbs the cost. Path 2: the sub purchases a project-specific OCIP or wrap-up policy that meets the limits for this project only. Either way, the resolution happens before mobilization, not after. Subs that can’t meet the limits at all are not the right fit for the project. Surface that finding before subcontract award, not at the COI review pass.
Do I have to demand copies of the endorsement forms, or are box-checks enough?
You have to demand the copies. The certificate confirms an endorsement is in place; the actual form attached to the policy is what enforces it in a coverage dispute. Federal contracting officers regularly audit the endorsement-copy file, not just the COI. A sub with all five endorsements box-checked but no copies on file is a finding regardless of whether the policies actually contained the forms. The absence of evidence is the finding. Demand the copies on the request letter and reject any cert that lands without them.
Can I email the COI request, or does it need to be a formal letter?
Email is fine. The formality is in the structure, not the medium. The 12 elements above are what make the request enforceable. A clean PDF letter attached to a one-line email is the most common modern format. Brokers are accustomed to PDF requests; what they’re less accustomed to is the form-number specificity in element 9, which is what eliminates the back-and-forth that costs everyone time.
What’s the right deadline for the sub to return the certificate?
Industry standard is 7 business days from letter date. Federal projects with mobilization on a tight schedule may require 5 business days. Commercial projects may allow 10 business days. The right cadence is whatever lets the prime’s risk team review and reject-and-resubmit if needed before the sub mobilizes. If your project’s mobilization is 14 days from subcontract execution, a 7-day deadline gives 7 days for review-and-correct. That’s the floor. Less than that and a single rejection-and-resubmit cycle blows the schedule.
What happens if the sub’s broker pushes back on the form numbers?
Stand firm. Form numbers exist because endorsements are non-equivalent across insurers. CG 20 10 from ISO is materially different from a manuscript additional-insured form from a regional carrier. If the sub’s broker cannot provide the named form numbers, the sub’s existing policy is not built for federal or large-commercial subcontract work and the sub needs a different policy or a project-specific wrap-up. Generic “we use a manuscript form that’s substantively similar” language is what creates the coverage dispute three years later when the manuscript form’s narrower carve-out becomes the case-deciding fact.