Editorial standards

Editorial policy

COI Workbench publishes practical, source-led information intended to help users prepare for a conversation with a licensed insurance professional.

Research and drafting

Each substantive guide begins with a defined user task and a review of relevant primary sources. Drafts must distinguish a certificate, policy, endorsement, and contract requirement. Examples are labeled as examples and should not be presented as universal requirements.

Source and link standards

Regulators, statutes, standards bodies, and official public documents are preferred. Commercial sources may be cited for clearly attributed industry context. We avoid relying on unsourced statistics, anonymous claims, or a competitor’s summary when an authoritative source is available.

AI-assisted production

Automation may assist with research organization, drafting, formatting, internal linking, and quality checks. Material claims are checked against cited sources before publication. Automation is not treated as professional insurance or legal review, and the site will not invent an author, credential, reviewer, or first-hand experience.

Expert review

A page will identify a licensed or credentialed reviewer only when that person has actually reviewed the page and authorized the attribution. Until then, pages are presented as editorially researched educational material, not professionally approved guidance.

Updates and corrections

We review content when a cited regulator changes its guidance, a tool’s logic changes, or a reader identifies a possible error. Substantive corrections are handled under our Corrections Policy.

Commercial independence

Advertising, if introduced, does not determine tool results or editorial conclusions. Sponsored or affiliate relationships will be disclosed near the relevant content. We do not rank an insurer, broker, or software provider merely because it advertises on the site.

Current quality controls

The publication checklist

A guide is ready only when it answers a defined user task, uses the appropriate source type, states what cannot be concluded, and connects the reader to a practical next action. Length alone is not a quality measure. A page should add a distinct workflow, comparison, example, decision boundary, or tool connection that is not already served better by another URL.

  1. Define the audience and moment. The draft identifies who is acting and whether the reader is preparing a first request, checking returned evidence, resolving a rejection, tracking renewal, or recording delivery.
  2. Separate source roles. Client instructions describe the requested evidence; policies and issued endorsements contain insurance terms; licensed issuers address policy-backed evidence; portal records describe technical events; reviewers state their own outcomes.
  3. Check material claims. Statements about certificate limits, regulator guidance, or public procedures are compared with current primary sources. Jurisdiction-specific examples are labeled and are not expanded into universal rules.
  4. Test the next action. Links, forms, buttons, copy output, calculations, local downloads, empty states, and warning paths are checked before publication. Tool results use observable labels instead of “approved,” “covered,” or “compliant.”
  5. Review presentation. The page is checked for one descriptive H1, logical headings, usable mobile layout, keyboard focus, readable color contrast, internal links, source access, and a visible limitation.

Authorship and review labels

Managed guides are published under “COI Workbench Editorial Desk,” a site-level publishing identity. This prevents a private WordPress login from being presented as an expert byline. The label does not imply a professional license or first-hand handling of the reader’s documents. A licensed or credentialed reviewer is named only after completing and authorizing a defined review; the page will state exactly what was reviewed and when.

Use of automation

Automation can help structure drafts, locate repeated language, check internal links, generate interface code, and surface potential inconsistencies. It does not provide professional judgment or make a source authoritative. Before publication, material statements must remain traceable to identified sources, and generated examples are checked so they do not invent statutes, form wording, credentials, experiences, or client outcomes. Pages created only to vary keywords, locations, or trades without meaningful new value are not part of the editorial plan.

Updates, versions, and corrections

A displayed review date should correspond to a substantive check, not a cosmetic refresh. When a source or tool changes, the affected workflow and related pages are examined for consequences. Small clarity or formatting improvements may be made without a correction note; factual, calculation, or outcome-changing errors are handled under the Corrections Policy. Older URLs remain stable where practical so readers and search engines can follow the correction trail.

Advertising and user trust

Advertising may fund the site, but it is separated from tool controls and editorial decisions. Ads are not designed to look like form buttons, generated results, downloads, or navigation. A user does not need to submit contact details or request an insurance quote to access the core educational material. Commercial relationships, if any, are disclosed near the affected content and do not override the published source hierarchy.