Free browser-only request review

COI Description of Operations Checklist Builder

Separate identification facts from client clarifications, issuer questions, supporting evidence, and delivery references before a certificate request is prepared.

No document uploadUse short neutral labels rather than confidential contract text. Entries stay in this browser tab and exports are created only on your device.

This tool does not write or issue a certificate. It cannot interpret a policy or contract, determine insured status, verify coverage, or decide what wording an authorized issuer may use.

Identify the request

Connect the checklist to one current written source and one intended certificate workflow.

Project or vendor reference *Client or reviewer *Written source label *Source date *Intended certificate holderAgent or broker labelInternal checklist ownerResponse deadline

Confirm the preparation boundary

The result should expose broad wording and unresolved ownership, not turn a request into certificate language.

I used limited, non-sensitive labels and understand that the output is a preparation brief—not certificate wording, issued evidence, a contract interpretation, or a coverage determination.

Private pre-issuance review

Your description-item checklist

0Identification facts

0Client or issuer review

0Unclear or conflicting

0Review prompts

Item type	Short fact, request, or question	Intended use	Source state	Current owner	Supporting label	Next action	Flags

Copy-ready issuer and client review brief

Do not paste the output onto a certificate. Send accurate facts and the client’s request through the authorized workflow, then compare the actual issued documents and supporting endorsements.

From client wording to issued evidence

Separate

Keep project facts, requested entities, insurance questions, and delivery instructions in distinct rows.

Route

Send requirement meaning to the client and policy-backed evidence questions to the licensed issuer.

Compare

Review the actual issued package without editing it or upgrading its status.

Read: What belongs in the description? · Project, location, and operations · Can description text change coverage?