Confirm that the gap is real
Before sending another email, answer four questions:
- Which configured rule applied? Company default, project minimum, or optional vendor minimum.
- What did the certificate state? Quote the field or say that nothing responsive was found.
- Was the required evidence supposed to be attached? A checked box is not the same artifact as an endorsement page.
- Was the record read correctly? Recheck the original PDF, especially shared aggregates, wrapped lines, and multi-page attachments.
Keep the rule used for this review frozen with the record. If the company raises a limit next month, today’s review should not be rewritten to appear as if the new rule existed earlier.
Decide who has to act
Different gaps belong to different people.
The producer can usually correct the paper
The producer named on the form can usually fix certificate-identity errors, missing policy numbers, stale dates, omitted limits, missing attached pages, or a certificate that does not match the policy the agency intended to evidence.
The subcontractor owns a coverage change
If the policy genuinely carries a lower limit, excludes a required line, or lacks an endorsement the contract requires, the producer cannot fix that with a better PDF. The subcontractor must decide whether to change coverage, seek a contract exception, change scope, or pursue another customer-approved resolution.
The GC owns the project decision
While the correction is pending, the GC decides what happens operationally. Software can organize the facts and attempts, but it should not decide whether the subcontractor mobilizes, continues work, or receives payment. Record who made that decision and the basis supplied.
Write the request as arithmetic
The fastest correction request is specific. Put the certificate value and adopted minimum on the same line.
Examples:
- General liability each occurrence: $1,000,000 shown — $2,000,000 project minimum configured.
- Umbrella: not found in the supplied certificate — $5,000,000 vendor minimum configured.
- Additional insured: certificate box checked — requested endorsement page not attached.
- Expiration: March 14, 2027 shown — project work currently scheduled through June 2027.
Do not tell the producer which policy to sell or assert that a particular endorsement form is legally sufficient. State the customer’s requirement and the evidence the file did not contain. The agency and insured decide how to respond.
First message to the producer
Subject: Certificate correction requested — [Subcontractor] / [Project]
We reviewed the attached certificate against the requirements our company recorded for this project. Please review these differences:
- [Field]: [certificate value or not found]
- Our recorded minimum/evidence request: [requirement]
- [Requested endorsement page or corrected certificate, if applicable]
Please return the updated certificate and supporting pages through [secure upload link]. If the policy does not provide the requested item, please say so and copy [subcontractor contact] so the subcontractor can address the contract requirement with us.
This wording creates two clean outcomes: corrected paper, or confirmation that the issue is not a clerical one.
Message to the subcontractor when coverage must change
Subject: Insurance item to resolve — [Project]
The certificate supplied for [project] shows [value/evidence]. Our recorded project requirement is [minimum/evidence request]. The producer has [confirmed the policy does not currently provide it / not yet supplied corrected evidence].
Please coordinate with the producer or contact [GC reviewer] about the project requirement. Upload any replacement certificate and endorsement pages through [secure link].
Avoid threatening language and avoid stating that coverage is invalid. Name the unresolved contract item, the source, and the person who can discuss it.
Read the replacement as a new document
A replacement certificate is not a patch to the old record. Recheck:
- Named insured and project reference.
- Insurer and policy number.
- Effective and expiration dates.
- Every limit implicated by the request.
- Attached endorsement pages.
- Any other field that changed unexpectedly.
Compare the replacement with both the configured minimums and the prior certificate. A corrected GL limit can arrive with a missing umbrella, changed carrier, shorter expiry, or different endorsement evidence.
Stop the correction reminder when the replacement arrives, but leave it pending customer review until a person reads the new source. “Uploaded” and “accepted by the customer reviewer” are different states.
Endorsements require evidence-specific follow-up
For additional insured, waiver of subrogation, primary and non-contributory wording, completed operations, per-project aggregate, or cancellation notice, say what the file contained:
- Attached endorsement page and identifiable wording.
- Certificate checkbox or description only.
- Nothing found.
If the contract calls for an attached page, request the page. Do not let a producer’s “it is included” email silently become the recorded document evidence. The reviewer can consider that email, but the file should still say what was and was not attached.
When the same certificate comes back again
Reply with the unresolved line only. Attach or link the prior request and state that the returned file still shows the same value or still lacks the requested page. Repeating a generic “please fix” message trains everyone to ignore the request.
Use a capped reminder ladder. A practical cadence might send an initial note, a follow-up, and a final reminder, then stop and place the vendor on a human review list. Endless automated mail does not resolve a policy problem and can damage the relationship with the producer and subcontractor.
Expiration problems are timeline problems
A certificate can be current today and still end before mobilization, before the scheduled completion date, or before a customer-required completed-operations period. Record the date shown and the project date creating the concern.
Renewal reminders should stop when a newer certificate arrives with a later expiration date, but the new file still needs review. A renewal is not proof that every limit and endorsement stayed the same.
Preserve exceptions separately from requirements
If the GC accepts an exception, keep the adopted requirement unchanged. Record:
- The exact difference accepted.
- Project, vendor, and scope.
- Person who authorized it.
- Date and supporting reason.
- Expiration or review date for the exception.
That prevents a one-project decision from becoming an accidental company standard and preserves what the reviewer actually decided.
What the completed file should contain
- Original certificate and replacement files.
- Certificate facts and their source locations.
- Effective company, project, and vendor minimums used for the review.
- Named reviewer and time.
- Every correction message, recipient, and send date.
- Attached endorsement evidence.
- Final customer review or documented exception.
That is more useful than a green badge. It shows the document, the rule, the difference, the attempts, and the customer decision without claiming that software established coverage.
For the box-by-box read, use How to read an ACORD 25. For requirement design, use Subcontractor insurance requirements by trade.
Primary sources and verification tools
- Texas Department of Insurance — certificate FAQ, including certificate-holder and additional-insured limitations.
- New York Department of Financial Services — ACORD 25 and ACORD 27 opinion, explaining that a certificate does not change the policy.
- NAIC consumer tools, for insurer and state-department information.
- Texas Department of Insurance — filed ACORD 25 specimen, for the form’s field labels and warnings.
Where SubLien fits
SubLien reads the ACORD 25, keeps the quoted source and page beside each field, and compares the customer-reviewed record with company, project, and optional vendor minimums. It can draft a deficiency request from the recorded arithmetic, but a person confirms the producer email, edits the message, and clicks send.
Correction reminders go to the subcontractor on the customer’s cadence and stop when a replacement arrives or the ladder ends. Nothing automatically emails the producer. The replacement remains pending until a named customer reviewer reads it.
SubLien does not decide that coverage is adequate, that the certificate is authentic, or that the vendor may work or be paid. See the COI tracking software or bring one returned certificate to a 15-minute demo.