A Property Manager Asked for a COI: What Contractors Should Gather First

A property manager emails, “Please send your COI before the crew arrives.” You have a certificate from another job, a work order naming a tenant, and an email signature with the management company’s trading name. Sending the old certificate immediately may create another round of corrections because those documents answer different questions.

The useful first step is to build a request packet that someone else can follow without guessing. This guide gives you a party map, a worked example, a copyable intake checklist, and a way to track the response. Use it for your own administrative notes; it is not a certificate, an insurance affidavit, or a substitute for documents issued by an authorized insurance professional.

1. Get the requirement that applies to this property and this job

Ask for the current vendor insurance instructions and any project-specific supplement. Save the version or date alongside the request. A sample certificate can help identify the requested layout, but ask which accompanying written instructions apply rather than treating every name and statement on an old sample as current.

Record the building reference, the work order or job number, a short description of the work, and the expected work dates. Note whether the work is a one-off repair, an ongoing service, or a separate phase of a larger project. If the manager provides a general vendor packet and a different building packet, keep both and flag the conflicting item for clarification.

Your record should answer: who sent the requirement, when it was received, which property it covers, and who can clarify it. Preserve the original request instead of repeatedly rewriting it into shorter emails. A short summary is useful, but it should point back to the source.

As an example of why timing matters, Oregon’s published contract insurance clauses require evidence before the contractor begins work and can require it earlier. That is an example from a particular contracting framework, not a universal deadline for private buildings. Confirm the deadline and release process for your job. Source: Oregon Department of Administrative Services.

2. Map the parties before filling in names

Use one row for each organization. The tenant who ordered the work, the property owner, the management company, the certificate recipient, and the person reviewing submissions may be different. Ask the requester to confirm the exact legal names and the role requested for each entity.

Keep unknown fields visibly marked “awaiting confirmation.” Do not fill them with an assumption just to make the packet look complete. The Project Party Role Mapper provides a practical place to organize these roles before you request issued evidence.

For example, Texas law states that a certificate cannot confer rights beyond the policy or an executed endorsement, or amend the coverage it describes. This is why a requested certificate label and the agent’s confirmation of applicable policy wording belong in separate fields. Rules can vary by jurisdiction. Source: Texas Insurance Code, Chapter 1811, especially sections 1811.152–153.

3. Turn each requested item into a question with an owner

Make a short list of the evidence the manager actually requested. This might include a certificate, an endorsement, confirmation about a named party, or a particular submission format. Copy policy-line labels and requested limits accurately into your intake notes without stating that the existing insurance satisfies them.

Use two question lists. The manager’s list concerns the requirement: which entity, which property, which work, which evidence, and which deadline. The agent’s list concerns the policy and issued documents: what can be supported, what is already available, and what needs further review. A question that concerns interpreting an agreement belongs with the appropriate legal adviser.

If you see “additional insured,” “primary and noncontributory,” or “waiver of subrogation,” use the Requirement Phrase Explainer to organize administrative questions. Do not select concepts that are absent from the written request.

Texas Department of Insurance guidance illustrates the need for care: a blanket endorsement does not automatically justify naming a holder as an additional insured on a Texas certificate, and cancellation wording cannot exceed the applicable policy requirements. Let the issuer handle the certificate wording and the jurisdiction-specific restrictions. Source: TDI certificates FAQ, questions 1 and 5.

4. Worked example: tenant, owner, and manager are different

Fictional example: Example Electrical receives a work order from a tenant for lighting work in Suite 204. The building manager sends an insurance packet listing the owner and management company. The installer’s old certificate relates to an unrelated property.

The coordinator creates three party rows instead of copying the tenant into every field. They ask the manager to confirm the certificate-holder instructions and which entities are included in the additional-insured request. They also ask whether the work order reference and suite number should accompany the submission.

Next, the coordinator sends the current requirement, the clarified party map, the scope, and the review deadline to the agent. The message identifies two unresolved questions rather than claiming that the old certificate is acceptable. The agent identifies the evidence available under the issued policies and any item requiring further action.

When documents arrive, the coordinator checks basic administrative matches: the intended contractor, the specified recipient, relevant dates, readable files, and the requested attachments. They send the packet through the manager’s stated channel and save the submission receipt. The record remains “submitted, awaiting review” until the reviewer gives a response. The crew’s access arrangements are tracked separately.

The value of this example is the sequence: clarify names, route policy questions, assemble the issued packet, then record the reviewer’s decision. It does not tell a contractor which insurance to purchase or predict whether a particular claim would be covered.

5. Copy this intake checklist into your job notes

Keep this checklist in your internal job file. Use neutral references in public or shared tools and send confidential insurance documents only through the agreed private channel. The checkboxes below are a temporary reading aid; keep your durable record in your own job notes.

6. Build one clear request brief for the agent

A useful brief has a subject that identifies the job and the required review date. Its opening explains that you are requesting assistance with the attached current requirements. Then separate confirmed facts from questions: property reference, work scope, parties, requested evidence, and submission instructions.

Finish with a short list of items you need the agent to resolve. Ask which issued documents are available and what further information is needed. Avoid asking the agent to certify that a broad contract has been satisfied. Include the full source requirement so the agent can review the actual wording rather than an abbreviated reconstruction.

The Agent Request Builder can help structure the request. Review the output before using it, add information through the appropriate private channel, and keep a copy with your job record. Generating the text does not send it or obtain an insurer’s approval.

7. Track what happened after you sent the packet

Use distinct statuses: gathering information, with agent, issued documents received, submitted, corrections requested, and reviewer response received. Add the date and the person responsible for the next step. This prevents an attachment arriving in your inbox from being mistaken for a completed vendor review.

If the manager requests a correction, quote the specific item in your internal record and assign it to the right owner. A spelling or property-reference clarification goes back to the requester or issuer as appropriate; a policy wording question goes to the agent. Keep the previous packet identifiable and record which replacement files were sent.

When a future job begins at the same property, revisit the saved requirements and party details. Confirm what has changed before reusing the workflow. A repeat visit is an opportunity to reuse a clear process, not to assume that last year’s documents or review decision remain current.

Common questions

Should I send the certificate from my last job?

First compare the new request with the information on that document and ask your agent what should be issued or supplied. A familiar building name or similar task is not enough to resolve different parties, dates, or evidence requirements.

Can I edit the certificate to add the property manager?

Route the requested correction to the authorized issuer. Keep your own notes separate from issued insurance evidence. If a name or address is unclear, ask the manager to clarify it before the issuer prepares the correction.

Does a portal upload mean the crew may start?

Record the upload as a submission event. Check the manager’s stated review and site-access process, and obtain the required response from the responsible person. Keep the insurance evidence workflow and any other work-start requirements visible in your job record.

What if the manager’s instructions conflict?

Save both versions, identify the exact difference, and ask the manager which requirement applies. Give the agent the clarified requirement when available and identify anything still unresolved. Do not silently choose the easier version.

Related guides and next step

Create your party map, then use the current written request to prepare your agent brief. For supporting background, see certificate holder versus additional insured, the name and address checklist, and the pre-mobilization checklist.