Alternative evidence

Alternative Insurance Evidence: How to Document a Client Decision

When the requested certificate or endorsement evidence is unavailable, delayed, differently titled, or technically difficult to deliver, document the exact proposed alternative and obtain a scoped client decision. Do not present the alternative as equivalent before the authorized review occurs.

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

Different evidence is not automatically equivalent evidence. A certificate, endorsement, policy excerpt, binder, insurer letter, renewal record, portal status, and client exception decision perform different functions. Preserve each document’s actual identity and authority.

What “alternative evidence” should mean

Alternative evidence is a specifically identified document or workflow record proposed in place of, alongside, or temporarily before the item named in the written requirement. It is not a generic label for whatever is currently available. The proposal should say which requirement it addresses, what the alternative shows, what it does not show, who issued it, when it applies, and what later evidence or review remains.

For example, a client may request an endorsement before work begins while the endorsement remains under insurer review. A contractor might propose a current certificate and an issuer’s written status response as temporary evidence. That proposal does not make either document an endorsement. The client decides whether to accept the temporary administrative package, subject to conditions and a replacement deadline.

Keep four authorities separate

Client requirement authority: identifies expected evidence and decides whether an alternative is accepted for its process.
Insurance authority: identifies the policy, endorsement, certificate, and evidence that can accurately be issued.
Contract or legal authority: addresses whether a response changes contractual obligations or risk allocation.
Process authority: controls portal routes, file formats, receipts, and technical exceptions.

A single person may perform more than one organizational function, but the record should still identify which authority supports each statement. “The broker approved it” may mean the broker confirmed insurance availability; it does not necessarily mean the client changed its requirement.

Compare the requested and alternative evidence

Comparison field	Requested evidence	Proposed alternative
Exact document type	Name from current source	Actual title of available document
Issuer or author	Expected authorized source	Actual source and authority
Entity and scope	Requested parties, operations, location, phase	What the alternative actually identifies
Policy line or requirement	Specific requested item	Specific item the alternative addresses
Effective period	Required dates or project phase	Dates shown or decision period
Information shown	Expected evidence point	Observable information in alternative
Information not shown	Any required element	Known limitation or open question
Replacement plan	Final evidence expectation	Owner and date for later evidence

Do not compare only filenames. Open the issued document through the approved workflow and identify its actual type. Never rename a certificate as an endorsement, call a broker email a policy form, or categorize a portal receipt as evidence of insurance merely to satisfy a technical field.

Record the alternative

Show exactly what differs and who accepted it.

Preserve the original requirement, issuer availability, alternative document, client response, effective period, conditions, package version, and next checkpoint.

Document the client decision

Minimum written client decision

A usable administrative decision identifies the project, requirement source and item, proposed alternative, accepted or declined status, authorized responder, response date, scope, conditions, effective period, required replacement evidence, and next review date. If any of these fields is not stated, record it as unresolved rather than inferring it.

Accepted with conditions

Conditions should be transformed into tasks. If acceptance lasts until renewal, create the renewal checkpoint. If it is limited to mobilization, record the phase boundary. If a replacement endorsement is due in ten days, assign the issuer request and package update. If the client requires a separate contract amendment, keep that process distinct.

Partially accepted

Split the result. One alternative may be accepted for a certificate-holder detail while another is declined for additional-insured evidence. A single “approved” label would incorrectly upgrade the declined element.

More information requested

Record each requested input, its owner, expected output, due date, and source. Do not treat the exception as accepted while the client waits for issuer confirmation, a project fact, or qualified contract review.

Declined

Preserve the decision and reason if provided. Determine whether the next step is corrected evidence, policy review, contract escalation, scope change, deadline discussion, withdrawal from the project, or another authorized action. The log should not recommend an insurance purchase or legal outcome.

Examples of alternative-evidence situations

Endorsement pending

Record the exact requested endorsement, issuer review status, temporary documents, proposed duration, client response, and replacement date. A certificate notation is not a substitute for the endorsement unless the authorized client decision addresses that administrative alternative—and it still does not change policy terms.

Renewal evidence not yet issued

Identify the current policy expiration, client deadline, expected renewal timing, interim evidence, and new-package owner. If the client accepts later delivery, record the actual date and conditions rather than a vague “upon renewal.”

Different document title

Ask the issuer what the document is and what it evidences. Ask the client whether that actual document is acceptable. Do not infer equivalence from similar wording.

Portal cannot accept a file

Separate technical and substantive questions. Portal support may authorize another format or route; the client reviewer decides whether the alternative delivery record is accepted. Preserve the error, retry path, transmission event, and receipt.

Requested entity or scope differs

Clarify exact legal names, roles, operations, locations, and project phases with the client before asking the issuer to prepare evidence. An alternative based on the wrong entity list is not ready for decision.

Package and version controls

Freeze the package version that contains the alternative.
Keep the client decision source distinguishable from issued insurance evidence.
Use filenames that identify actual document types.
Include only the files and decision records required by the approved route.
Preserve the submission timestamp, destination, category, and receipt.
Track reviewer status without calling “uploaded” or “received” accepted.
Create a new version when alternative or replacement evidence changes.
Retire superseded files from the working package without deleting history.

The University of California’s certificate resources distinguish the request and issuance roles in its process, while King County’s public contractor guidance identifies evidence requirements and contracting contacts in its own program. These program-specific sources are not universal rules, but they illustrate why the party issuing insurance evidence and the party reviewing contract requirements are separate.

Review prompts for the final record

Is the alternative named precisely?
Is the original requirement still visible?
Did the licensed insurance professional confirm policy-specific availability?
Did the authorized client source accept the alternative?
Are scope, dates, and conditions explicit?
Does the package preserve actual document types?
Is replacement evidence assigned and scheduled?
Are unresolved questions still shown?
Does any wording claim coverage, compliance, or guaranteed acceptance?
Will a later reviewer be able to reconstruct the chronology?

Frequently asked questions

Is an insurance binder always acceptable instead of a certificate?

No universal answer applies. Identify what the binder actually shows, obtain issuer guidance, and ask the authorized client reviewer about the specific requirement.

Can a client accept an agent letter?

The client may decide whether a particular letter satisfies its administrative request. The letter’s insurance meaning still depends on its author, content, policy, and authority.

Should the client decision be sent to the agent?

Send relevant conditions through the approved process when the issuer must act, while excluding unnecessary contract or personal information.

What happens when the alternative expires?

Move the row to its next checkpoint before expiration, obtain replacement evidence or a new decision, and create a new package version.

Does alternative evidence alter coverage?

No. Only the policy and authorized policy changes determine coverage. The administrative record does not amend insurance.

Sources and scope

The comparison and decision-record method is original administrative guidance. Actual acceptance, authority, policy meaning, and contractual effect must be determined from the applicable sources by authorized professionals.