Sources and Methodology

Transparency

Sources and methodology

Our tools are structured preparation aids. This page explains their source hierarchy, scoring approach, limitations, and update process.

Source hierarchy

  1. Insurance regulators and statutes. State departments of insurance and current state law are used when a page discusses certificate rules in a specific jurisdiction.
  2. Form publishers and standards organizations. Public guidance from organizations such as ACORD is used to explain the role and permitted use of standardized forms.
  3. Government and public procurement documents. These may illustrate how a particular public entity describes its own requirements; they are not presented as universal rules.
  4. Industry education. Insurer, broker, and risk-management materials may provide useful context, but promotional claims are not treated as neutral authority.

Core references

How the rejection-risk result is calculated

The checker assigns additional weight to administrative gaps that commonly stop a submission from moving forward, including an inactive policy period, limits below a written requirement, a legal-name mismatch, and an endorsement requested but not confirmed. “Not sure” responses are treated as unresolved questions rather than failures.

The result bands are workflow labels—not actuarial predictions. They do not estimate the probability of a claim, policy cancellation, legal liability, or the final decision of a contractor, property manager, platform, insurer, or other reviewer.

Jurisdiction and contract limits

Insurance certificate rules and permitted wording can vary by state. Contract requirements also vary by client and project. A general-purpose tool cannot determine whether a request is enforceable, available in the market, or properly supported by a particular policy. Users should take the generated questions to a licensed insurance professional familiar with the policy and jurisdiction.

Update process

Material pages show a reviewed or updated date. When a primary source changes, affected guidance is reviewed for substantive differences rather than merely changing the displayed date. Confirmed corrections are documented under the Corrections Policy.

Methodology version: 1.0, published September 2026.

Current methodology addendum

Version 1.22: source provenance, conflict routing, and final review

This addendum documents the active tool set without replacing the original editorial page. COI Workbench currently provides twenty-three browser-only administrative tools and sixty field guides. Search, workflow selection, calculations, warnings, copy output, calendar files, and CSV exports run locally in the browser; the tools do not upload user-entered source material to COI Workbench.

Problem-first navigation

The home-page finder maps six recognizable situations—rejection, first submission, unclear requirement, renewal, delivery or portal issue, and exception request—to a short sequence of existing tools. The route is a workflow starting point, not an insurance, legal, compliance, or purchasing recommendation. Every tool and guide remains directly available in the complete directories.

Endorsement evidence matrix

The matrix keeps the written requirement, policy line, requested provision, entity or operational scope, observable evidence state, document label, form or edition reference, effective dates, licensed-issuer response, client-review status, review source, current owner, and next action in separate fields.

Evidence states are deliberately limited to an issued endorsement attached, a form or policy reference only, a certificate notation or checkbox only, an issuer response or document pending, a requested document not received, or clarification needed. None of these states determines coverage, insured status, endorsement meaning, compliance, or acceptance.

Automated review prompts

Prompts identify missing document labels, reference-only rows without a reference, certificate notation used in place of requested endorsement evidence, accepted rows without a dated reviewer source, date contradictions, broad entity wording, duplicate rows, unassigned actions, possible sensitive identifiers, and unsupported coverage or compliance conclusions. A prompt exposes an administrative question; it does not resolve it.

Authority and source boundaries

The client or authorized project source defines its requirement and review outcome. The licensed agent, broker, insurer, or other authorized issuer explains policy-backed evidence and document identity. Qualified legal or risk review may be needed for contract effect. The certificate, policy, issued endorsement, current project requirement, and dated reviewer response retain their separate authority.

Source-control and final-review suite

The source register records source type, neutral label, version, date, purpose, scope, workflow state, location reference, owner, and next action without storing the underlying document. The conflict resolver preserves both source labels and values, identifies one difference, assigns the appropriate decision route, and records the dated response without choosing a winner. The review pack assembles user-entered review items and counts verified, open, pending, conflicting, exception, and superseded states; it never converts administrative completeness into a coverage or compliance conclusion.

Additional primary references

Current methodology version: 1.22, updated September 2026.