Location control

COI Location-Specific Requirements Checklist

“The project” may include several buildings, work zones, addresses, jurisdictions, or client records. A location matrix keeps each written qualifier connected to the evidence request and prevents one site’s instruction from silently spreading to every site.

Reviewed September 2026 · Educational information, not insurance or legal advice

A location label is not a coverage statement. It connects an administrative row to a site described by the user. Only the policy, endorsements, applicable law, and facts can answer coverage questions.

Identify the location without exposing unnecessary data

Use the location identifier that appears in the current written requirement: project name, building, campus zone, job number, unit, city, or another approved token. Avoid putting a private residence, employee information, policy number, access credential, or other unnecessary sensitive value into a browser worksheet or export.

Compare all project records that may name the place differently. The contract may use a legal property name, the work order a street address, the client portal a site code, and field staff a short nickname. Preserve the client’s authoritative label and add a neutral cross-reference rather than assuming similar names are the same site.

A location can matter because the written request limits an operation to one premises, identifies a certificate holder or evidence recipient for a site, requires a project reference, assigns a portal record, or establishes a date and review workflow. Those are separate administrative functions. Do not use a location description to assert policy coverage.

Location-specific review checklist

Record the current written source, version, and date.
Capture the exact site or project-location label.
Confirm whether the row applies only to that location or also to other sites.
Identify the trade or operation when location alone is insufficient.
Identify the phase if the requirement begins or ends at a milestone.
Separate the contracting party, named insured, certificate holder, requested additional insured, and evidence recipient.
List the exact evidence or clarification requested.
Assign the current action to the client, agent, contractor, portal owner, or qualified reviewer.
Preserve not found, inferred, and conflicting states.
Set a follow-up date before mobilization, submission, renewal, or closeout when appropriate.

Build the location matrix

Connect each requirement to its exact site and companion qualifiers.

Flag missing location labels, mixed scopes, conflicting sources, and unassigned clarification work.

Map location requirements

Example location matrix

Item	Scope	Location	Other qualifier	State	Action
Certificate holder block	Specific location	North Campus	None	Clearly stated	Use exact client instructions
Auto evidence	Trade + location	Distribution yard	Delivery contractor	Inferred	Confirm applicability with client
Additional-insured evidence	Location + phase	Building B	Active construction	Conflicting	Reconcile addendum and portal row
Renewal package	Project-wide	Blank	All active sites	Clearly stated	Confirm project-level destination

A project-wide row should not carry a leftover location value unless the value is merely the project identifier and is clearly labeled that way. A specific-location row must name the site. A trade-plus-location row must identify both. When a single requirement covers three sites with different owners or deadlines, use three rows so the status of one does not hide the others.

Questions for the client or reviewer

Does this item apply only to the named site or to the full agreement?
Which written location label should appear in the submission?
Are multiple buildings reviewed as one project or separate portal records?
Does the certificate-holder or recipient information change by location?
Which party should be identified for each site?
Does the requirement begin before access, at mobilization, or at another phase?
How should a site addition, closure, or relocation be documented?
Which current source resolves a conflict between the portal and contract exhibit?

Questions for the licensed agent or issuer

What exact project and location facts are needed to prepare accurate evidence?
Can the requested location text be supported without implying a policy amendment?
Does the request call for a certificate, endorsement, schedule, or another issued document?
Which named entities and operations must be confirmed before issuance?
What lead time is required if the client clarifies or adds a site?

The Texas Department of Insurance notes, in the jurisdiction-specific framework described by its FAQ, that a job or contract number may identify a certificate but external contract language cannot be used to imply unsupported coverage. Use location and job identifiers to connect records, while keeping coverage statements with the policy and authorized issuer.

Control site additions, removals, and renaming

Do not overwrite the old location label when a project changes. Add a dated source event showing the prior label, revised label, effective date, and affected rows. If work moves from one address to another, confirm whether the existing evidence request continues, whether new entities or certificate-holder data apply, and whether a new portal record is required.

During renewal, compare the active site inventory with the prior submission. A renewal certificate with current dates may still be routed to the wrong project record or omit a new location-specific request. During closeout, separate sites that are complete from sites with ongoing work or later evidence checkpoints.

Common location errors

Using the billing address instead of the work location.
Treating a campus as one site when the reviewer uses building-level records.
Copying a certificate-holder address into an additional-insured request without source support.
Leaving an old project nickname in a renewed filename.
Applying one location’s special trade requirement to all vendors.
Recording a site as complete because one building was accepted.
Using a portal site code without preserving the underlying project reference.
Including unnecessary personal or confidential location information.

Frequently asked questions

Should the full street address always be entered?

No. Use only the minimum approved identifier needed to distinguish the location. Retain sensitive details in the authorized system.

What if the contract and portal use different site names?

Preserve both labels, identify their sources, and ask the client to confirm the mapping.

Can one certificate refer to several locations?

Ask the licensed issuer what accurate evidence can be prepared and the client how it should be submitted. The checklist cannot decide policy treatment.

Does a specific-location request apply after the job ends?

Not automatically. Map the phase separately and ask about later evidence checkpoints.

What if the client adds a site by email?

Preserve the email as a dated source, confirm the affected requirements, and create new rows rather than silently broadening old ones.

Sources and scope

The checklist is original administrative guidance. The current written requirement, issued documents, jurisdiction, and authorized professional advice control.