Cognatum

Standards

Job aids are approved. An AI answer is not.

Every quality system treats the one page extract as a document: numbered, reviewed, dated and tied to the procedure it was cut from. An AI answer does the same job at the point of work, and enters no register at all.

Cognatum Team · Nov 11, 2026 · 6 min read

Somebody on the late shift has to run a step they last touched in April. They do not open the full procedure. Nobody does.

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

They reach for the one page. The card taped to the machine, the checklist in a shared folder, the screenshots a colleague made two years ago.

That one page has a name. It is a job aid, and in a well run company it is a controlled document: a number, an owner, a date, and a link to the procedure it was cut from.

This year the same person types the question into an assistant instead. The reply arrives in four sentences. It does the same job. It carries none of the same control.

What a job aid is for

A job aid is a quick reference tool that walks someone through a task. It can be printed, kept as a file, or pushed to a phone. It is usually one page or shorter.

It is not training. One guide puts the line plainly: a job aid reminds an employee of something they were trained on before and may need a memory jog for.

When people reach for one

A national laboratory's own template library names the conditions well. A check sheet suits work where it is vital you do not miss a step, and where you do not do the task often enough to internalize it.

Read that again with an AI assistant in mind. It describes, almost exactly, the moment somebody opens a chat window and asks the company a question.

The step at the end of every method

Advice on building job aids converges on one sequence. Watch the task. Pick a format. Draft it. Then test it.

Testing is not a formality. One guide says to send the draft to a few seasoned employees in the department that will use it, because they can tell you whether a step has been left out.

Approval, in their own words

The step after that is approval. A university guide for instructional designers is blunt about it. Once you have settled on the process, get final approval or signoff from managers or other stakeholders.

The people who do this for a living already arrived at the thing that matters. Someone who knows the task reads the shortened version before anybody relies on it.

And then it is kept

The same guide closes the loop. Stay open to feedback, because processes change and the job aid will need updating. Handing it out is explicit too: give it to the team and say when and how to use it.

That last instruction is a distribution list in disguise. If you know who holds a copy, you can take the copy back.

A job aid is a derived document

Here is the part that gets missed. A job aid is not an original. It is an abridgement, and one guide says so outright: it could be used to illustrate a procedure.

Quality systems treat the shortened version as a document in its own right: its own identifier, its own revision, its own approver, and a reference to its parent. When the parent changes, the extract is on the list of things to look at.

That link is the entire point. Without it, an update to the procedure leaves an approved summary saying something untrue, with a signature at the bottom.

Standards move

ISO 9001 is now in its 2026 edition and the 2015 text it replaces has been withdrawn. Extracts have to move when the parent does, which is why somebody records where each one came from.

The older artifact in this family is the standard operating procedure. In clinical research, ICH defines one as detailed written instructions to achieve uniformity in the performance of a specific function.

One line in the general description of SOPs is worth sitting with. New employees use one to answer questions without interrupting a supervisor to ask how an operation is performed. That is the job the assistant has taken over.

What the answer does not have

Set a job aid beside a generated answer and the gaps are easy to list. The job aid has a document number. The answer has a line in a chat log.

The job aid has a named approver. The answer has a model version. The job aid has a revision and an effective date. The answer has neither, and it reads the same the week after the procedure changed.

No parent, no recall

The job aid names its parent. The answer may have drawn on four documents, one of them superseded, and it will not say which. The job aid has a distribution list, so it can be recalled. The answer went to one person and cannot be found again.

None of this says the technology is wrong. It is often right. The trouble is that nobody can tell from the outside.

Looking right is not being right

The best public evidence is a preregistered study of AI legal research tools. Despite provider claims about eliminating hallucinations, the tools examined produced false information between 17 and 33 percent of the time.

A printed job aid with a one in five chance of being wrong would be off the wall within a day. The difference is that a printed one can be found at all.

The law writes instructions for the tool

Regulation has thought about this, for the system rather than the answer. The EU AI Act requires a high risk AI system to come with instructions for use that are concise, complete, correct and clear.

Those instructions must state the accuracy level the system was tested against, the circumstances that may affect it, the limits of its performance, and where applicable what a deployer needs to interpret its output. The official text notes it reflects a consolidated version as at 27 July 2026.

A job aid for the software

Read as a document, that is what it is, and nothing attaches a comparable page to the answer the software produces. The instructions govern the instrument. The output walks away on its own.

Giving the answer the same paperwork

Cognatum is a knowledge base, and what it governs is the answer, not only the file.

Eight steps, one human gate

The Cognatum Knowledge Loop runs four phases across eight steps, from capture and structure, through cleaning, enrichment and improvement, to approval, deployment and reuse. AI runs seven of them. Approve is the one it does not.

At that step a named person reads what was assembled, reworks the wording where it is not right, and signs it off. It is the signature the job aid guides describe, applied to the thing people actually read.

Conflict, and notice

Where two documents disagree, both are surfaced and the disagreement is named, instead of one being quietly ranked above the other. A person decides which is true.

When a source changes, Cognatum notifies. It does not rewrite the answer by itself and it is never simply current. Somebody is told that something downstream is now in question.

Nothing has to move

Departmental repositories stay where they are. Cognatum runs a two way flow with the systems the work already lives in, so no migration project stands between a company and a governed answer.

What each entry then carries is the paperwork the one page extract always had. A named approver, a date, and the source it came from, including where the knowledge stood when the answer was given. NIST's glossary calls that provenance: the chronology of a thing's origin, ownership, location and changes.

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

The Cognatum Knowledge Loop is documented in full at cognatum.ai/the-loop.

Common questions

Questions this raises.

What is a job aid?

A job aid is a short reference that helps someone finish a specific task at the moment they are doing it. Common forms are checklists, step by step guides, flowcharts, decision tables and one page reference sheets. It is performance support rather than training, meant as a reminder of something already learned.

Is an AI answer a job aid?

It does the same job. Someone needs a shortened version of a longer document at the point of work and gets one. The difference is control. A job aid is numbered, approved, dated, tied to a parent document and given to a known group of people. A generated answer has none of those, which is why it cannot be reviewed, revised or recalled.

Why does a missing revision number matter?

Because supersession is invisible without one. When a procedure is updated, every approved extract from the old version can be listed and then revised or withdrawn. An answer produced from the old version cannot be listed at all, so it stays in circulation and reads exactly as it did before.

Does the EU AI Act cover AI answers?

The Act places obligations on high risk AI systems and on their providers and deployers, including instructions for use that state accuracy, limitations and how to interpret outputs. Those duties attach to the system. None of them produces an approved, versioned record of an individual answer, which is a governance job that stays with the organization.

Can software make our AI answers compliant?

No. No software confers compliance with the EU AI Act or with the NIST AI Risk Management Framework. What a governed knowledge base can do is align with those frameworks and supply the evidence an assessor asks for: who approved an entry, on what date, and from which source.

Knowledge governed. Intelligence everywhere.

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