Governed Solutions / Knowledge management
One home for what your company knows.
Every answer your company has already approved lives in one place, with the name of the person who approved it and the date.
| Select | Title | Type | Taxonomy | Status | Expires | Reach |
|---|---|---|---|---|---|---|
| Which retention period applies to client trade communications? | Q&A | Records | Approved | in 214 days | 38 | |
| Standardize retention schedules on the records policy | Decision | Compliance | Approved | in 149 days | 31 | |
| Applying a legal hold to a retention schedule | Procedure | Legal | Approved | in 24 days | 27 | |
| How long are supervisory review records kept? | Q&A | Supervision | In review Approved | in 96 days D. Whitfield · 2026-09-02 | 18 | |
| Which regions are approved for data residency? | Q&A | Security | Stale | Expired 6 days ago | 12 | |
| Retention questions raised in the Q3 examination | Note | Compliance | Draft Approved | No expiry M. Alvarez · 2026-09-04 | 4 |
Without Cognatum
You already answered this.
“The product only works if the knowledge stays current after the launch party ends.”
The answer exists. What nobody can tell you is which copy is current, who owns it, or what changed.
Somebody wrote the answer last quarter. It sits on a shared drive, or a chat thread, or the memory of the person who left in March.
So the question comes back. Someone answers it again, a little differently, and now you have two answers. Then the source changes, and both answers stay where they are.
Nobody notices until a client, an auditor, or a new hire asks which one is right.
Seven years from the end of the contract, across all record types.
No source · no approver · no date
With Cognatum
Work goes in. Answers come out.
Documents, tickets, and threads arrive from the tools your teams already use. AI drafts an entry from each one, a person approves it, and the set of entries is scored and kept current.
Every entry carries a health score, and the score moves. It falls as an entry ages towards its review date and rises when somebody confirms it, so the ones that need attention sort themselves to the top.
What a governed knowledge base is, and the questions teams ask first, is on the governed knowledge base overview.
Corpus health
71
| Item | Type | Health | Reach | Band | Why |
|---|---|---|---|---|---|
| Applying a legal hold to a retention schedule | Procedure | 74 ↗ was 67 | 38 answers | Healthy | cited by 38 answers · reviewed this quarter |
| Which regions are approved for data residency? | Answer | 52 ↘ was 61 | 24 answers | At risk | source changed · no owner confirmed |
| Standardize retention schedules on the records policy | Decision | 68 → was 68 | 17 answers | Healthy | stable since approval · owner active |
| How long are supervisory review records kept? | Answer | 59 ↗ was 51 | 12 answers | At risk | awaiting approval · one open conflict |
| Retention questions raised in the Q3 examination | Note | 31 ↘ was 44 | 6 answers | Critical | no approved source · superseded twice |
A corpus health score over four bands, healthy, at risk, critical and stale, above a table of entries with a health score, a trend against its previous score, and the reason each is where it is
How it works
Four things it does daily.
Capture
It reads the work
AI watches the systems where answers already get written, and drafts an entry from each one.
Approve
A person signs it
Nothing goes live without a name on it. The name, the date, and the source are stored with the entry.
Refresh
It flags what went stale
Change a source document and every entry that leans on it is queued for a fresh look.
Report
It shows you the gaps
Questions nobody has answered become a ranked list, each with an owner and a date to answer by.
-
01
Capture
Ingest from every source.
-
02
Structure
Normalize the format.
-
03
Clean
Update, deduplicate, reconcile, archive.
-
04
Enrich
Add context and tags.
-
05
Improve
Refine clarity, usability.
-
06
Approve
Human sign-off, audited.
A person handles this step
-
07
Integrate/Deploy
Push live everywhere.
-
08
Reuse
Serve people and AI.
In practice
Twelve answers, one quarter.
One of your experts owns twelve approved answers. All twelve come up for review in their busiest quarter.
They get one list, not twelve emails. Each item shows how often that answer was used and what else depends on it.
They approve nine, edit two, and hand one to the colleague who owns it now. They do it in the chat tool they already have open.
Every answer that leaned on the two they edited is queued the same day, to the people who own those, not back to them.
Which onboarding steps require a second approver?
Entry SOP-2210
- v4 In force
Second approver required for any account opened outside the branch network.
J. Mercer, Knowledge Administrator · 2026-06-11
- v3 Superseded · retained
Dual approval extended to accounts opened by partner agents.
D. Whitfield, Records management · 2025-10-22
- v2 Superseded · retained
Exception path added for accounts reopened within ninety days.
M. Alvarez, Compliance · 2025-04-03
- v1 Superseded · retained
First approved version.
M. Alvarez, Compliance · 2024-08-14
→ what the entry said on a date is a lookup
Common questions
What teams ask first.
Is this a cleanup project?
No. You do not stop work to reorganize anything. Entries are drafted from work your teams are already doing, and your people approve a few each week.
Who approves an entry?
A named person you choose, usually the one who owns that subject. The name, the date, and the source travel with every answer built on that entry.
What happens when two answers disagree?
They are held apart and sent to a person to settle. They are never merged into one confident answer that nobody approved.
What happens when the person who approved an answer leaves?
The entry still shows who approved it and when, and it appears on the report of entries whose owner has gone. Ownership moves without the answer disappearing.
Knowledge governed. Intelligence everywhere.
See it on your own content, in your own environment.