Carriers and agencies write the same article fifty times with small differences, and the differences are the whole point: a form, a notice period, a cancellation rule. Any base that treats those as one page with a long table ends up with a table nobody trusts, and any base that treats them as fifty unrelated pages ends up with forty-nine that are stale.
The shape that works: one article, jurisdictional variants
Write the answer once at the level that is genuinely common, then attach a short variant per state that says only what differs. The reader lands on the article, picks their state, and sees the common answer plus the delta. What makes this work is that the delta is short enough for one person to check in a morning when the rule moves.
The date is part of the content
A rule that takes effect on a date is not an edit you make when you remember. It is a change with a known future date, and the base has to be able to say what the answer is now and what it becomes then. Products that only hold current text force you into a calendar reminder and a person, which is where insurers lose this.
Producer-facing and insured-facing answers are different articles
The same question from an agent and from a policyholder has two correct answers with different words and different caveats, and a single article written to serve both serves the agent badly and exposes you with the policyholder. Split them early. The internal one can assume vocabulary; the external one cannot assume anything.
What the base must never become
It must not become the place the policy form lives. Forms are records with filing history and effective dates, and they belong wherever your filings are kept. The base links to the form and explains how to use it; the moment somebody pastes the form text into an article, you have two versions of a filed document and one of them is wrong.
Ownership follows the line of business
A central documentation team writing personal auto answers will get the edge cases wrong, because the edge cases are exactly what the line underwriters know and nobody else does. Owners belong in the line; the base owner's job is to chase the review dates and keep the structure from fragmenting.
Questions people ask about insurance knowledge management
How do we handle a rule that changes mid-year?
Make the effective date a field on the variant rather than a sentence in the body, so the article can carry both the current and the pending answer. Then the review is a diff rather than a rewrite.
Should compliance approve every article?
Every externally facing one and every one that states a regulatory obligation. Approving the article about resetting an agent portal password is the kind of blanket rule that makes people stop writing articles.
Is a knowledge base article evidence of what we told an insured?
It can be, which is an argument for version history rather than an argument against writing them. Being able to show what the article said on the day matters more than the article being perfect.
Where do underwriting guidelines belong?
Not in a general base. They have a narrower audience, a stricter approval path and a shorter retention question, and mixing them with operational answers makes the access rules harder than they need to be.