Package delivery
COI Package Cover Sheet Template for Contractors
A useful cover sheet identifies one outgoing package without pretending to verify insurance. It tells the reviewer which version is being delivered, what is included, what is not included, and which questions remain open.
Reviewed September 2026 · Educational information, not insurance or legal advice
What the cover sheet should accomplish
The cover sheet is an index and communication aid. It should let a recipient connect the message, package version, visible filenames, project reference, delivery channel, and expected next step. If a document is still being requested from the issuing professional, the cover sheet should say so plainly rather than implying it was attached.
A cover sheet is especially helpful when a submission contains a certificate plus several endorsements, when a reviewer asked for a correction, when a portal offers similar upload categories, or when more than one project is active for the same client. It reduces ambiguity at the handoff. It does not replace the certificate, endorsement, contract requirement, portal receipt, or reviewer decision.
The Texas Department of Insurance explains that, under the Texas rules it cites, a certificate cannot contain information that goes beyond the policy and may not use a construction or service contract as if it were the insurance contract. That is jurisdiction-specific guidance, not a nationwide rule. The practical boundary remains useful: keep the cover note administrative and leave statements about policy terms to accurate issued evidence and qualified professionals.
Recommended fields for a controlled cover sheet
| Field | What to record | What to avoid |
|---|---|---|
| Project or vendor reference | A neutral identifier that connects the delivery to the correct job | Unnecessary policy, tax, personal, or payment identifiers |
| Sender and recipient | The contracting business and intended reviewer or client | Assuming the recipient is also the certificate holder or additional insured |
| Package version | A short controlled label such as V02 | Overwriting the prior submitted version |
| Planned delivery date and route | The intended date and approved portal, platform, email, or secure link | Calling a planned date proof of transmission |
| Document inventory | Every visible filename or expected evidence reference, type, scope, and status | Using one vague line such as “all insurance documents” |
| Open questions | Concise disclosed issues and current owner | Hiding a known missing item behind “complete package” |
| Requested next event | Acknowledgment of receipt or a specific reviewer question | Demanding a coverage opinion from an administrative recipient |
Use filenames that are consistent, descriptive, and meaningful. The U.S. National Archives recommends consistent file-naming conventions and, when dates or versions are used, keeping those elements in the same position. Its guidance is for federal records rather than contractor COI packages, but the naming principle reduces avoidable confusion when files move between systems.
Build the handoff
Create a cover message tied to the exact outgoing package.
List included, disclosed, pending, excluded, and superseded items without uploading any file.
Plain-language cover sheet template
Subject: [Project reference] — COI package [version] — [delivery status]
Hello [recipient],
[Sender] is providing COI package [version] for [project reference] through [delivery channel] on [planned delivery date]. The package inventory below identifies what is included and any item that remains pending or has a disclosed question.
Included:
[Exact filename] — [document type] — [scope] — included and opened in local review
[Exact filename] — [document type] — [scope] — included; question disclosed: [short note]
Not included:
[Expected document reference] — awaiting issuer — [short next action]
Please acknowledge receipt through the approved workflow. Receipt confirms the handoff only; review or acceptance should be recorded separately.
Thank you,
[Sender or package owner]
Adjust the greeting and channel instructions to the client’s process. A portal may not accept a narrative message, so save the same package inventory in the approved internal record and use the portal’s available comments field only when permitted. Do not put confidential policy data into a tool, filename, email subject, or unsecured note merely because the field exists.
Pre-delivery review
- Open each file from the staged outgoing folder rather than relying on the filename alone.
- Match the project reference and recipient to the current written instruction.
- Confirm the package version differs from prior submissions and that older files are not mixed in.
- Classify every row honestly as included, included with a disclosed question, awaiting issuer, excluded or not requested, or superseded.
- Check that an “included” row has an actual visible filename and the correct document type.
- Remove unsupported conclusion words such as “approved,” “compliant,” “covered,” or “valid.”
- Keep the planned delivery date separate from the actual transmission timestamp.
- After transmission, preserve the sent snapshot and available receipt in the approved system.
- Record review, correction, and acceptance as later events rather than editing the delivery record.
The University of California describes certificates as evidence used in contract workflows and assigns certificate-issuing responsibility to designated risk-management offices for its own program. Its page also emphasizes accurate legal names and current contract terms. The exact roles vary by organization, but the lesson is that package preparation, certificate issuance, and requirement review should not be blurred into one action.
Common mistakes
“Everything attached” when one item is pending
This creates an avoidable factual conflict. List the expected document under “not included” and state the observable next action.
Using “accepted” before a response exists
Submitted, received, under review, needs correction, and accepted are different events. The cover sheet can request acknowledgment; it cannot manufacture it.
Describing a holder as an additional insured
Those roles are not interchangeable. Texas regulator guidance, for example, links additional-insured statements to policy or endorsement support. Ask the agent or issuer about the applicable evidence.
Attaching a superseded certificate
A filename with “final” does not prove currency. Open the staged file, compare dates and entities, and preserve a manifest of the exact outgoing snapshot.
Frequently asked questions
Should the cover sheet be a separate PDF?
It can be an email, portal comment, PDF, or internal record depending on the approved process. Consistency and connection to the exact package matter more than format.
Can the cover sheet say the contractor is compliant?
It should not make that conclusion. It can say what was included and what status the reviewer actually communicated.
Should pending items be omitted?
No. A concise disclosed pending list is more useful than implying a package contains evidence that is absent.
Does receipt mean acceptance?
No. Receipt records delivery or availability to the recipient. Review and acceptance are later, separate statuses.
Sources and scope
- Texas Department of Insurance: Certificates of Insurance FAQ
- U.S. National Archives: File and folder naming conventions
- University of California: Certificates of Insurance/Self Insurance
The cover-sheet model is original administrative guidance. It does not issue evidence, verify coverage, amend a contract, or prescribe a universal records-retention period.