Additional-insured evidence

Blanket vs. Scheduled Additional Insured Endorsements: Evidence Workflow

“Blanket” and “scheduled” are useful document labels, but they are not final answers. A contractor workflow should preserve the actual endorsement, triggering facts, named or described parties, operations, location, project phase, dates, issuer explanation, and client-review decision.

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

Never infer insured status from the label alone. Whether a person or organization qualifies, for which operations, and during which period depends on the policy, endorsement wording, triggering facts, and applicable law. Ask the licensed issuer to explain the issued evidence.

The administrative difference to preserve

A scheduled endorsement may visibly identify specific parties or locations in the document or attached schedule. A blanket endorsement may describe a category of parties or conditions under which status applies rather than listing every project entity. That high-level distinction helps organize a request, but it cannot determine whether the current project, agreement, party, or operation meets the endorsement’s terms.

The Texas Department of Insurance’s certificate FAQ provides a useful jurisdiction-specific example: it distinguishes a blanket additional-insured endorsement from naming a certificate holder as an additional insured on the certificate. The same source states that copies of policies or endorsements may be provided and explains when additional-insured and waiver indicators are appropriate under Texas rules. This is not a universal interpretation; it shows why the actual endorsement and local requirements must remain visible.

Facts to collect before asking for evidence

Fact	Source owner	Reason to preserve it
Exact legal entity names	Client/project source	Prevents aliases, groups, and certificate-holder names from being treated as interchangeable
Relationship to the named insured	Agreement and project records	May be relevant to the issuer’s review of the endorsement
Written agreement and date	Authorized contract source	Identifies the document the parties are relying on
Operations or work	Project scope	Separates this job from unrelated operations
Location and project	Client instructions	Limits the administrative comparison to the correct site
Ongoing or completed period	Written requirement	Prevents two time scopes from being collapsed
Policy line	Requirement and issuer	General liability, auto, umbrella, and other lines require separate review
Endorsement identity	Licensed issuer and issued document	Preserves title, reference, edition, effective date, and source
Client evidence expectation	Authorized reviewer	Defines the requested document and acceptance route

Use limited references in browser tools. Do not paste full agreements, policy numbers, personal details, confidential project terms, or entire endorsement wording. Keep authoritative files in the approved document system.

Map the evidence

Keep each party, scope, policy line, and document state visible.

Create separate rows for scheduled or blanket evidence, issuer questions, reviewer status, and the next controlled action.

Build an endorsement matrix

A five-stage workflow

1. Confirm the request

Ask the client for the controlling source, exact entities, policy lines, operational and time scope, and acceptable evidence. If the request says only “blanket AI,” clarify what the reviewer expects to receive and evaluate.

2. Send verified project facts to the issuer

Provide the licensed agent or broker with accurate, limited project facts and the written request. Do not tell the issuer that a party automatically qualifies. Ask what issued evidence exists, what it is called, whether another action is pending, and what documents can be supplied.

3. Inventory the response

Record each actual document separately. Capture its title, form or reference, edition if visible, policy line, date, entity or descriptive scope, and whether the issued document is attached. If only a certificate notation or email response is present, retain that precise state.

4. Submit a controlled package

Use a manifest and version label. Identify the certificate and each endorsement as different files or components. Preserve open questions instead of hiding them in a generic “complete package” claim.

5. Record the reviewer outcome

Separate uploaded, received, under review, accepted, and correction requested. If the reviewer asks for scheduled evidence instead of blanket evidence—or the reverse—preserve the exact request and route it to the client and issuer without interpreting the policy yourself.

Administrative examples

Blanket document supplied, exact entity questioned

Record the issued document reference and the exact client entity. Ask the issuer whether and how the document relates to that entity and project facts. Ask the client whether the supplied evidence meets its request. Until both questions are resolved, keep the row under review rather than “matched.”

Scheduled document lists one of several requested parties

Create separate entity rows. Mark the visible party as observed in the scheduled document and the others as not located. This does not decide legal status; it creates focused questions and prevents one listed party from being generalized to all parties.

Certificate indicator without endorsement copy

Record “certificate notation only,” preserve the policy line, and request the issued evidence or issuer explanation. Do not rename the certificate or mark the endorsement attached.

Ongoing evidence supplied, completed-operations request still open

Use two rows. The first can proceed through review while the second remains pending. A combined “AI complete” status would conceal the unresolved period.

Quality controls

Every row cites the current requirement source.
Every requested entity is exact or explicitly unresolved.
Each policy line and time scope has its own row.
The evidence state describes what is actually present.
Document identity is confirmed or assigned to the issuer for confirmation.
Client receipt and acceptance remain different statuses.
Open actions name an owner, output, and due date.
No field claims coverage, compliance, equivalence, or guaranteed acceptance.

Frequently asked questions

Is blanket evidence better than scheduled evidence?

There is no universal ranking. The relevant questions are what the issued document provides, whether the facts trigger it, what the project requires, and what the authorized parties determine.

Must every entity appear by name?

That depends on the actual requirement, policy, endorsement, facts, and jurisdiction. Preserve the requested names and ask the issuer and client rather than assuming.

Can a certificate name the party when the endorsement is blanket?

Rules vary. Texas publishes specific guidance on this question. For another jurisdiction or policy, ask the licensed issuer and follow applicable requirements.

Should blanket and scheduled documents be in the same matrix?

Yes, if they relate to the same project, but use separate rows or evidence references so each can be reviewed independently.

Does client acceptance change the policy?

No. A client workflow decision does not amend insurance.

Sources and scope

This guide provides an original evidence-control workflow, not a policy interpretation. The actual endorsement, policy, project source, facts, jurisdiction, and authorized professional review control.