Treat project number, location, and operations as different facts

Project or contract number

This is the client’s approved identifier for the relationship or job. It may be a contract, purchase order, work order, vendor, or project code. Record which system supplied it. A number in an old email may be obsolete even when the project name is familiar.

Location

The location may be a street address, campus, building, unit, work zone, municipality, or client site code. Use only the minimum non-sensitive label needed for the workflow. The work location is not automatically the same as the contracting office, billing address, certificate holder, or evidence recipient.

Operations or trade

This is a neutral description of the work actually performed, such as electrical installation, roofing repair, delivery, design consulting, or environmental testing. It should come from project facts, not from generic insurance wording. If several trades have different requirements or owners, separate them.

The three facts intersect but should remain individually verifiable. “Riverside / Building B / electrical” is clearer when each component has a labeled source. If the client later changes Building B to Building C, the project and operation may remain unchanged while only the location row receives a new source event.

Create a source hierarchy for identifier conflicts

1. Current executed agreement or authorized amendment. Preserve the exact record and version.
2. Current client onboarding or project instruction. Use it for destination-specific labels while checking for conflict with the agreement.
3. Current purchase order or work order. Confirm that it belongs to the same contracting entity and scope.
4. Written client clarification. Record author, date, affected identifier, and whether it replaces an earlier value.
5. Internal project record. Use it to cross-check facts, not to overwrite a client identifier silently.
6. Portal display. Treat it as a destination label unless the client confirms that it controls the underlying project requirement.

When sources disagree, keep both values and mark the row conflicting. Do not choose the newest-looking number automatically. A revised portal profile can still point to the wrong contract, and a signed agreement can be followed by a valid amendment.

Example identifier and operations matrix

A strong matrix preserves the exact facts without pretending to know what the issuer will write. The operations row gives the agent context. The endorsement row asks a policy-backed evidence question. The client supplies exact entity requirements. The contractor controls the package and delivery record.

Checks for the project number

• Is it the number the client currently uses?
• Does it belong to the same legal contracting entity?
• Is it a project, contract, purchase order, work order, or vendor number?
• Is the label understandable without copying confidential contract language?
• Does the filename or portal row use the same controlled token?
• Is it being used only for identification rather than as a compliance assertion?

The Texas Department of Insurance specifically distinguishes a job or contract number used for identification from language saying an insurer provides coverage according to that external contract. That precise distinction is valuable beyond Texas as a conservative preparation habit, but users must confirm their own jurisdiction’s rules.

Checks for the location

• Is this the actual work site rather than a mailing or billing address?
• Does the client use one campus label or separate building records?
• Is a site code needed for portal routing?
• Are multiple locations covered by one request or separate rows?
• Did the location change after award?
• Does including the address expose unnecessary personal information?
• Is the certificate-holder address being kept separate?

Checks for operations

• Does the description match work the contractor will actually perform?
• Is a subcontracted trade being confused with the prime contractor’s work?
• Are design, transportation, environmental, or other specialist operations distinct?
• Does the client request a separate requirement because of that operation?
• Is a broad phrase such as “all operations” supported by a clear source?
• Does the row contain a coverage conclusion that should be removed and routed to the issuer?

Handle changes without losing history

When an identifier changes, create a dated comparison rather than editing the prior submission record. Show the old value, new value, source, effective date, affected package, current owner, and required next action. If only the portal label changes, confirm whether the contract identifier remains the same.

When operations expand, ask whether new trades, sites, dates, entities, or insurance questions are implicated. The contractor should provide accurate project facts; the client should clarify the written requirement; the licensed agent or insurer should review policy-backed evidence. A simple update to descriptive text should never be assumed to solve a coverage or contractual issue.

Pre-submission reconciliation

1. Compare every identifier with its current source.
2. Open the actual issued document; do not rely only on the filename.
3. Check the named insured separately from the project entities.
4. Check the certificate holder separately from requested additional insureds.
5. Check policy dates separately from project dates.
6. Check descriptive text separately from attached endorsements.
7. Preserve the package version before delivery.
8. Verify the destination record and retain the permitted receipt.

Frequently asked questions

Can I shorten a project name?

Use a short token internally if it remains unambiguous, but give the issuer and client the authoritative label when the request requires it.

Which address should I use?

Identify whether the source asks for the work location, certificate-holder address, named-insured address, or another recipient. They serve different purposes.

Can “all locations” be entered?

Only preserve that phrase when the current source clearly uses it, then ask the appropriate parties what evidence can accurately be issued. A checklist cannot establish policy scope.

Should subcontractor operations be combined?

Separate them when the requirement, evidence, owner, location, or phase differs.

What if the issued certificate has an old number?

Do not edit the document. Ask the authorized issuer for a correction and control the replacement as a new package version.

Sources and scope

• Texas Department of Insurance: Identification and certificate limits
• U.S. National Archives: Consistent record naming
• University of California: Certificate workflow resources

The identifier matrix is original administrative guidance. The current project record, policy and endorsements, jurisdiction, and authorized professionals control.