Editorial policy

Scope and standing

This policy binds the site. Where it conflicts with a commercial preference, the policy wins. Where it conflicts with what would rank better, the policy wins. A rule that only applies when convenient is not a rule, and a reader has no way to tell the difference except by watching what we refuse to publish.

Sourcing

Every material factual claim maps to a source in the registry.
Sources are ranked by the hierarchy in the methodology. A secondary source may explain a primary one and may never override it.
A source record lists the exact claims it supports. A claim not on that list may not be attributed to that source, and the list is published on the page.
A citation is made after reading the source. Citing a search result, a snippet, or another article's description of a source is not permitted.
Every source records its publication, effective, access, and last-checked dates, its jurisdiction, and its update cadence. A source past its window is flagged stale in public.
A source that stops resolving is marked unavailable and kept, because the citation of record matters and quietly deleting it hides that a page's footing changed.

Language

The direct answer comes first, then the conditions. Burying the answer under qualifications is a failure, not caution.
Hedges such as often, may, commonly, anddepends on the policy form are used where they are the truth, and are not used as filler. A hedge is a finding, and it carries the same evidentiary burden as an assertion.
Any statement about what a policy says names the form and its edition, or says "many forms" and tells the reader their own form controls. No universal policy language.
Anything that is common market practice rather than a legal or filed requirement says so in those words.
Uncertainty is stated as a confidence status on the page: established, contextual, disputed, changing, or insufficient. Where competent sources disagree, that is disclosed rather than resolved by preference.

Companies and organizations

No best, cheapest, top, or most reliable claim.
No rating or financial-strength summary written by us. We link to the rating agency or the regulator that published it, and let it speak for itself.
No appetite claim of ours. An appetite statement may appear only as a quotation from or a link to the carrier's own published document, labeled carrier-authored and dated.
No complaint statistic without its denominator and its date, because a raw complaint count is misleading by construction.
Product and state availability appear only when sourced and current, and carry the date they were confirmed.
Inclusion in any list, and position within it, is never for sale and is never influenced by a commercial relationship.

Examples and case studies

Every example is labeled before it is read: public record, carrier authored, published industry, anonymized client, composite, or hypothetical.
A composite or hypothetical is never presented as a real outcome, and never attributed to a client.
An anonymized client case requires written approval and a documented consent record, which is named on the page. Without both, it does not publish.
No example may use information from a declarations page, an intake, an email, or an agency management system.
Never invent a premium, a savings figure, a claim outcome, a placement, a close time, or a policy term. Not as illustration, not as a range, not as an example.
No testimonials, no reviews, no star ratings, no client logos.

Disclosure

The operator is named on every page, with its legal name, its trade name, and its agency licence number.
The Bollinsure relationship is disclosed next to every licensed-help action, including that Bollinsure may be compensated by an insurer when it places coverage, and that it is not the only source of licensed help.
There is no sponsored content, paid placement, or affiliate arrangement. If that changes, the disclosure appears on the page carrying the relationship.
No page requires an email address, a phone number, or an account to be read in full.

Automation

The methodology states exactly where automation is and is not used. Two rules govern it here:

A named human author and a named licensed reviewer are responsible for every published page. Automation never publishes.
No page may imply that structured data, retrieval, or generation substitutes for licensed or editorial review.

How this is enforced

Some of this is enforced by build-time checks rather than by good intentions. A citation marker that does not resolve to a declared source fails the build. A source id that is not in the registry fails the build. An entry missing an author, a reviewer, or a review date fails schema validation and does not publish. A page cannot enter the sitemap without a canonical URL, and a tool cannot appear in navigation without a published route.

The parts that cannot be automated, the judgement about whether a source really supports a sentence, are what the reviewer is for, and why the reviewer is named.