Cognatum

System of record

Offboarding revokes access, not authorship

The laptop comes back and the accounts close the same week. Sixty documents still carry the leaver's name as approver, and your AI assistant reads them every day without knowing.

Cognatum Team · Nov 6, 2026 · 6 min read

Somebody left in March. The laptop came back. The accounts were closed inside a week. The checklist was signed and filed, and the process worked exactly as designed.

Served to one approved entry
AI assistants & agents
Proposal tools
Internal search & chat
Customer portals
Compliance & audit

Cognatum governs the entry

source · version · approver · permissions

Sixty of the company's documents still carry that person's name as the approver. Nobody has looked at any of them since.

The AI assistant reads those documents every day. It does not know the person is gone.

What the checklist actually covers

Offboarding is the separation process when someone leaves a company. The standard list is familiar. Document the procedures and hand over the open work. Remove the software. Close the logins and point the mail at a new owner. Collect the laptop and the badge. Finish the paperwork.

One item on that list is worth reading twice. The person is removed from the company website, the social profiles, the org chart and other active publications. The process knows to take a name down once it is no longer true.

It does that in public. It does not do it inside your documents.

Access is revoked. Authorship is not.

Access control is the part most teams get right. The account is disabled, often within hours, because an open account is a security problem with a name on it.

Approval is the part nobody touches. An approval is a statement by a person that a document is correct. The statement sits in a field. The field still reads true after the person leaves, because it records what happened in the past.

What changed is not the record. What changed is that the record no longer points at anyone you can ask.

The field that quietly changed meaning

A named approver is the right thing to capture, and it is worth keeping after the person has gone. It tells you who stood behind the document on the day it was approved. What it cannot tell you is whether anyone stands behind it now.

So the same three words, approved by Dana, mean two different things in March and in November. Nothing in the document marks the difference.

You cannot hand over a list nobody has

Handover is scoped to the open work. Live projects, client relationships, status reports, the half-finished thing due on Friday. That scope is reasonable, because it is what a manager can see.

The written record is a different problem. Almost nobody can produce a list of every document one person wrote, approved or last edited across the drives, the wiki, the shared mailbox and three departmental repositories. The handover covers what somebody remembered to put on it.

A gap you cannot list is a gap you cannot close.

Records management stops at the record

Records standards cover how records are made, captured and kept over time. ISO 15489-1 sets out the concepts and principles for that work. The scope is the record. An answer assembled on demand out of several records is not a record, so the scheme has nothing to say about it.

The problem is getting larger, not smaller

More than 30 million Americans will turn 65 in the next four years. Deloitte Insights puts the projected cost at 6.9 to 9.6 trillion dollars in lost output, and calls it the largest transfer of institutional knowledge in business history.

The same report notes that 92 percent of surveyed organizations do not consistently capture knowledge from people who are about to retire. In the survey behind that figure, 85 percent had not put AI to work on knowledge management, and 58 percent of senior leaders were very worried about the loss.

Shorter stays, more handovers

Average job tenure has fallen from 4.6 years to 3.9 years over the past decade, while the generation now leaving averages more than eight years. The exits are not only bigger. They are also more frequent.

The index has no leavers' report

Retrieval reads documents. It does not read the staff list.

When an assistant answers a question, it finds passages, ranks them and writes a reply. The passage carries its text. It does not carry the employment status of the person who approved it. Nothing in the pipeline joins the approver field to a list of current staff, because nothing was built to.

So the assistant keeps quoting a procedure whose only author left in March, in the same even voice it uses for everything else. The answer is not flagged, because there is no flag.

A name typed once

NIST defines provenance as the chronology of the origin, development, ownership, location and changes to data, and adds that it may include the people and processes that touched it. Ownership is in that definition. In most knowledge bases it is a name typed once and never checked again.

The law asks for a person

European law is blunter about this than most internal processes are. Article 26 of the EU AI Act tells deployers of high-risk systems to assign human oversight to natural persons who have the necessary competence, training and authority. The text now shown on the Commission's own service desk is based on the consolidated version as at 27 July 2026.

The law asks for a person with authority. It does not ask whether the person named on the document still works there.

What a governed knowledge base does differently

The Cognatum Knowledge Loop runs in four phases across eight steps. AI runs seven of them. Approve is the one it does not.

Approve is a hand-off. The AI finds, gathers and surfaces the item, then sends it to a person. That person decides what is true, and can rework the answer before approving it. The approver becomes a live role in a register rather than a byline in a file.

Notice, not a rewrite

Two other behaviors matter here. When a source changes, Cognatum notifies the people who depend on it rather than quietly rewriting the entry. And where two documents disagree, it shows both and points at the disagreement instead of picking a winner.

It also scores the knowledge base and splits healthy items from items at risk. At risk is broader than overdue for review. It covers duplicates, conflicts and gaps, which is the exact shape a departure leaves behind.

None of this stops anyone from leaving. It changes what is left on the shelf when they do.

The question worth asking on Monday

Take the three procedures your assistant quoted to somebody this week. For each one, name the person who approved it and the date. Then check whether that person still works here.

If you cannot answer the first question, the record was never governed. If you can answer it and the answer is no, you have found work that no checklist was ever going to surface.

Your company's knowledge isn't missing. It's unusable. Cognatum changes that.

Common questions

Questions this raises.

Does offboarding not already include knowledge transfer?

It usually does, and it is usually scoped to the open work: live projects, client contacts, status reports. That scope is set by what a manager can see on the last day. It rarely extends to the written record the person leaves behind, because almost no organization can list every document one person wrote, approved or last edited across its drives, wikis and departmental repositories.

Why does it matter who approved a document if the document is still correct?

Because you cannot tell whether it is still correct without asking somebody. An approval records a judgment made on a particular day against a particular version of the source material. When the source changes, the only person who can say whether the judgment still holds is the person who made it. If that person has left, the document reads as approved and nobody can confirm it.

Can we just reassign a leaver's documents to their successor?

You can, once you know which documents they are. Reassignment is a small job after the hard one. The hard one is producing the list, and then getting a named person to actually read each item and approve it rather than inherit it. A transferred byline with no fresh review is the same gap under a new name.

Does Cognatum keep knowledge current by itself?

No. It notifies. When a source document, a table or a query changes, Cognatum tells you what in the knowledge base now depends on something that moved. It does not rewrite the entry on its own and it is not always current. A named person still decides what is true and approves the change.

Does this make us compliant with the EU AI Act or the NIST AI RMF?

No. No software confers compliance with either, and any vendor saying otherwise is overreaching. What software can do is supply the evidence a reviewer asks for: who approved an entry, on what date, from which source, and what the knowledge looked like at the moment an answer was given.

Knowledge governed. Intelligence everywhere.

See it on your own content, in your own environment.