Before work starts
COI Required Before Site Access: A Contractor Pre-Mobilization Checklist
When a client says insurance evidence must be approved before anyone enters the site, treat that instruction as a separate mobilization gate. Build the evidence package early, record what was submitted, and wait for the authorization the project actually requires.
Prepared by COI Workbench Editorial Desk · Reviewed September 2026 · General U.S. guidance
A contractor should not assume that emailing a COI releases the crew to begin work. Confirm the current written requirement, prepare the exact certificate and supporting-evidence request with the licensed agent, submit it through the required channel, and distinguish delivery, receipt, review, and approval. The contract, purchase order, site rules, and authorized client contact control the project decision.
What “COI required before site access” usually signals
The phrase normally describes an administrative condition in a project workflow. The requester wants insurance evidence in its file before it issues a notice to proceed, activates a vendor, releases a badge, schedules an orientation, or allows people or equipment onto a controlled property. The exact gate varies. A certificate may be only one item in a larger packet that also includes endorsements, a safety form, license details, a purchase order, or vendor onboarding records.
Do not convert the phrase into a universal legal rule. Instead, locate the document that applies to this job. Federal contracts provide a useful example: FAR 52.228-5 requires the contractor, before work under a covered contract begins, to notify the contracting officer in writing that the required insurance has been obtained and to maintain subcontractor proofs. Private contracts, property managers, municipalities, and general contractors may use different wording and approval steps.
The four gates contractors often confuse
Prepared
Your request and supporting project facts are ready.
Issued
An authorized insurance representative returns the evidence.
Submitted
The package reaches the named email, portal, or reviewer.
Released
The authorized project party confirms the required next step.
These are not interchangeable. An agent can issue a certificate without knowing whether a portal received it. A portal can display “uploaded” while a reviewer still needs an endorsement. A reviewer can accept the insurance package while another mobilization requirement remains open.
Pre-mobilization checklist
1. Freeze the current requirement
Save the applicable contract section, insurance exhibit, purchase order, onboarding email, portal instruction, and revision date. If two sources disagree, ask the client which version controls before requesting evidence. Do not quietly combine an old limit with a new address or a remembered list of additional insureds.
2. Map every organization by role
The business that hired you, property owner, general contractor, property manager, certificate holder, portal operator, and requested additional insureds may be different entities. Record exact legal names and addresses from the client’s current source. A familiar property name is not automatically the legal organization the agent should evaluate.
3. Separate certificate fields from policy questions
Create one row for each requested coverage line, limit, party, operations period, waiver, primary-and-noncontributory request, and supporting endorsement. The contractor supplies project facts and the complete request. The licensed agent or insurer determines what the policy provides, what can accurately be shown, whether an endorsement applies, and whether policy action is needed.
4. Compare dates with the actual work window
A policy may be active when evidence is submitted yet renew during mobilization or active work. Record each displayed effective and expiration date separately. If the planned job crosses an expiration, establish a renewal-evidence checkpoint rather than assuming the existing certificate covers the entire schedule.
5. Build one controlled package
Use descriptive filenames and a short manifest. Distinguish the certificate, each endorsement, and any other requested document. Before sending, open every final file and confirm its project reference, named insured, policy period, and version. Do not edit an issued insurance document yourself.
6. Capture observable delivery evidence
Record the destination, timestamp, visible filename, submission reference, and portal or email status. A sent-message copy or portal confirmation can document an event; it does not prove substantive review or coverage. Preserve any receipt without placing unnecessary policy or personal data in an uncontrolled tracker.
7. Ask for the exact release event
Use a focused question: “Please confirm whether the insurance evidence package has completed your review and identify any remaining prerequisite before site access.” Avoid asking only “Is my COI good?” The precise wording helps the client separate insurance review from badges, purchase orders, safety orientation, permits, and scheduling.
Build a mobilization record that another person can understand
A useful record should let a project manager, office administrator, or replacement coordinator answer four questions without reconstructing an email chain: what the client requested, what package was sent, what the reviewer actually said, and whether the project released the crew. Keep the record narrow. It does not need the full policy, private employee details, or a copied collection of every internal email.
- Requirement record: source name, version or date, relevant project, and evidence deadline.
- Package record: short manifest identifying the certificate and each supporting item by filename and version.
- Delivery record: destination, timestamp, sender, and visible receipt or portal reference.
- Review record: exact status or comments from the authorized reviewer, with a date.
- Mobilization record: the notice, purchase order, badge release, orientation completion, or other project event that permits the next operational step.
If the project is delayed, this separation shows whether the open item belongs with the contractor, licensed issuer, portal team, insurance reviewer, or another project owner. It also prevents a vague “insurance issue” label from hiding a missing purchase order or site-orientation task.
Actions that create more risk instead of saving time
- Editing an issued certificate, endorsement, date, entity name, or description.
- Sending a prior project package without disclosing that it was prepared for another client or site.
- Calling an upload confirmation “approval” in the schedule.
- Forwarding only the first page when the client requested separate issued evidence.
- Typing broad coverage conclusions into an email or certificate-description request.
- Sending policy numbers, contracts, certificates, or personal data through an unapproved tracker.
- Mobilizing because a third party “usually accepts these” when the authorized client has not released this job.
A practical timeline
| Checkpoint | Owner to confirm | Record to preserve | Do not assume |
|---|---|---|---|
| Requirement received | Client or authorized reviewer | Source, version, date, deadline | That an older project used the same terms |
| Evidence requested | Contractor and licensed agent | Complete request and attachments | That “standard COI” describes the need |
| Package returned | Licensed issuer for insurance questions | Issued filenames and date | That certificate text replaces an endorsement |
| Package submitted | Contractor or designated sender | Destination, timestamp, reference | That upload means receipt |
| Review completed | Client or authorized reviewer | Dated outcome and open items | That acceptance determines coverage |
| Site release | Authorized project party | Notice, badge, PO, or other release record | That COI acceptance is the only gate |
Example: a crew scheduled for Monday
A subcontractor receives a Friday message saying, “COI required before site access.” The certificate is already available, but the attachment package does not include the requested additional-insured and waiver evidence. The contractor should not alter the certificate or upload the same file repeatedly. A better response is to preserve the message, send the complete requirement to the agent, tell the GC which evidence is pending, record the planned start date, and ask what written release will authorize mobilization.
If the agent returns the requested evidence, the contractor verifies the package and submits it through the stated route. The portal then displays “under review.” That status is not the same as a rejection, acceptance, or permission to enter. The contractor records it and seeks the GC’s actual release decision.
Run the pre-submission check
Catch common administrative gaps before mobilization.
Answer twelve browser-only questions about sources, names, dates, limits, parties, endorsements, attachments, and project details.
Frequently asked questions
Can I send an old COI while the new request is pending?
Only send evidence that is accurate for its stated purpose and clearly identify its status. Do not imply that an old project package answers the current requirement. Ask the client whether an interim item is useful and the licensed agent what can properly be issued.
Does “submitted” mean my crew can enter?
No universal answer exists. Submission is a delivery event. Follow the project’s written access procedure and obtain the release or authorization required by the client.
Should I ask the agent to copy the client?
Use the delivery route specified by the client and accepted by your business. Even when the agent sends evidence directly, keep an appropriate package reference and ask the client to confirm receipt.
What if the reviewer asks for unsupported certificate wording?
Preserve the exact request and return it to the licensed agent. If the agent says it cannot accurately be provided, ask the client for clarification or an authorized written decision. Do not add wording yourself.
Sources and limits
- Federal Acquisition Regulation 52.228-5: Insurance—Work on a Government Installation
- Texas Department of Insurance: Certificates of Insurance FAQ
- California State University, Stanislaus: Certificate and additional-insured endorsement requests
This guide provides general administrative preparation information. It does not interpret a contract or policy, verify coverage, authorize site access, or replace instructions from the client, insurer, licensed producer, or qualified legal professional.