Responsibility map
Who Fixes What on a Rejected COI? Client vs. Agent vs. Contractor
A rejection moves faster when each issue goes to the party who controls the missing fact, issued evidence, package action, or review decision.
Reviewed September 2026 · Educational information, not insurance or legal advice
The five-owner model
Client or reviewer
Controls the evidence request it is making, the exact requested parties, its portal instructions, deadlines, and its own review outcome. The client can clarify what it wants but should not be treated as the issuer of policy evidence.
Licensed agent or authorized issuer
Explains the policy information it is authorized to discuss and prepares accurate certificates or endorsement evidence. A contractor should not edit issued evidence to satisfy a comment.
Contractor or vendor
Collects current written requirements, controls internal versions, compares the returned evidence administratively, stages the outgoing package, sends it through the approved route, and records observable status.
Portal or process owner
Resolves access, upload, file-category, replacement, and receipt problems. Sometimes this is a client team; sometimes it is a separate technology support function.
Qualified legal professional
Addresses contract meaning, enforceability, indemnity relationships, disputes, and legal risk when professional legal judgment is needed.
Issue-routing matrix
| Reviewer issue | First owner | Contractor’s useful request |
|---|---|---|
| Wrong certificate-holder name or address | Client | Confirm the exact written holder block |
| Named insured does not match | Agent + contractor | Preserve both names; ask the agent about accurate issued evidence and check the contracting entity |
| Coverage or limit appears insufficient | Client + agent | Confirm the exact required line/value; ask the agent what the policy and issued evidence show |
| Additional-insured endorsement requested | Agent | Provide the exact entities, policy line, operations period, and written request |
| Missing file, stale version, or wrong filename | Contractor | Restage one controlled package and open every file |
| Portal rejects file type or category | Portal/process owner | Confirm accepted format, size, category, replacement, and receipt rules |
| Deadline or review standard unclear | Client | Request a current written clarification |
| Contract interpretation disputed | Qualified legal professional | Escalate with the controlling documents and facts |
Route the queue
Assign every comment to one current action owner.
Keep the original feedback visible while separating policy, requirement, package, and portal tasks.
What a clean handoff contains
A handoff should be short enough to act on but complete enough to avoid another round of questions. Include the neutral project reference, exact issue, current written source, requested answer or deliverable, due date, and the person who will receive the result.
Client handoff example
“Please confirm the exact certificate-holder legal name and mailing address for Project Riverside417. The reviewer comment says the holder is incorrect, but it does not provide the replacement text.”
Agent handoff example
“The client requests additional-insured evidence for the listed owner under general liability for ongoing operations. Please confirm what accurate issued evidence applies; the attached requirement is the current client instruction.”
Portal handoff example
“The PDF upload shows no receipt and is absent from the submitted-files view. Please confirm whether the file was received and the approved replacement procedure.”
Statuses that preserve reality
- Open: the issue exists but no request has been sent.
- Asked: the required question or request was sent.
- Waiting: another owner has not yet responded or delivered evidence.
- Ready for package: a response or file is available but has not yet been included in a controlled delivery.
- Closed by documented response: the reviewer or controlling owner supplied an observable resolution.
“Asked” is not “resolved,” and “ready for package” is not “accepted.” Keeping those boundaries makes the log more useful when a deadline approaches.
Issues that need more than one owner
A name mismatch may require the contractor to confirm the contracting entity and the agent to confirm the policy named insured. A limit comment may require the client to identify the exact written value and the agent to explain what the policy and certificate show. Assign a current action owner even when later handoffs are expected.
If two owners disagree, preserve both source statements and escalate through the approved business process. Do not silently rewrite the reviewer’s comment into a coverage conclusion.
Frequently asked questions
Is the reviewer always the client?
No. A third-party compliance platform or project administrator may perform the review. Record both the requesting client and the actual response channel when they differ.
Can the contractor correct a typo in a certificate PDF?
No. Request accurate replacement evidence from the authorized issuing party.
Who decides whether a resubmission is accepted?
The designated reviewer or client process records its own outcome. That outcome is separate from policy coverage.
Who owns the deadline?
The client defines its deadline; the contractor should assign an internal owner to manage the response workflow.
Sources and scope
- Texas Department of Insurance: Certificates FAQ
- University of California: Certificate requests and renewals
- CSU Stanislaus: Certificates and additional-insured endorsements
The owner model is a practical workflow, not a universal allocation of contractual or legal responsibility.