What ISO 30401 asks of a knowledge base, and what a markdown wiki can show an auditor

ISO 30401 sets no metadata schema and no review interval. This page covers what the knowledge-management standard does require, which of its clauses touch individual records, and how frontmatter in a markdown knowledge base can serve as evidence. It covers ISO 30401:2018 and notes the revision now under way. Last reviewed 23 September 2026.

The short answer

ISO 30401 doesn't define a "knowledge record", doesn't prescribe metadata, and doesn't set a review interval. It is a management-system standard: it sets requirements for how an organization runs knowledge management as a whole, from scope and leadership through roles, knowledge development, culture, internal audit and management review. In its own words, it "sets requirements and provides guidelines for establishing, implementing, maintaining, reviewing and improving an effective management system for knowledge management in organizations."

Individual records meet the standard in two places:

• Clause 4.4.2, Knowledge development. The system must cover acquiring new knowledge, applying current knowledge, retaining current knowledge, and "handling outdated or invalid knowledge".
• Clause 7.5, Documented information. It has the same three sub-clauses as ISO 9001: general, creating and updating, and control of documented information.

For a markdown knowledge base, that comes down to five things every page can show: what it is, who is accountable for it, where it came from, when it last changed, and whether it is still current. Frontmatter can carry all five, and doing so is one reasonable way to evidence those two clauses.

What frontmatter can't show is how knowledge moves between people and the culture around it. ISO 30401 treats those as just as important, so a well-tagged wiki is evidence for part of the standard, not all of it.

Which edition applies

• ISO 30401:2018, the first edition, was published in November 2018 (20 pages) and has two amendments: Amd 1:2022 and Amd 2:2024 (climate action changes).
• A revision is under way. ISO/DIS 30401, edition 2 (27 pages), is at stage 40.60, close of voting. ISO's catalogue lists the 2018 edition as "expected to be replaced by ISO/DIS 30401 within the coming months."
• Clause numbers on this page are from the 2018 edition. Check them again when edition 2 is published.

What ISO 30401 is, and isn't

• It's a management-system standard, written to the same template as ISO 9001. Judy Payne, a member of the working group that wrote it, puts the most common misreading plainly: "'Systems' has nothing to do with IT."
• Knowledge is a human asset. The standard defines knowledge as a "human or organizational asset enabling effective decisions and action in context" (clause 3.25).
• Buying tools is not knowledge management. Among common misconceptions, the introduction lists "the view that simply buying a technology system will be enough for knowledge management to add value" (clause 0.1). Tidy frontmatter doesn't change that.
• Markdown counts as documented information. The standard defines documented information as "information required to be controlled and maintained by an organization and the medium on which it is contained", and notes it "can be in any format and media, and from any source" (clause 3.11). Markdown files in a repository qualify.

Where records meet the standard

Payne describes clause 4.4.2 as "a kind of knowledge lifecycle". Its last stage, handling outdated or invalid knowledge, is the one frontmatter helps with most directly.

A knowledge-base page with its governance visible

---
type: how-to
title: Restoring the order database from the nightly backup
description: Steps to restore the order database from the nightly backup, and how to verify the restore.
domain: platform-operations
owner: Platform Operations Lead
status: stable
generated: { by: human:r.chen, at: 2026-05-02T10:00:00Z }
sources:
  - resource: https://intranet.example/runbooks/backup-policy
verified:
  - { by: human:a.okoro, at: 2026-05-10T15:00:00Z }
review_policy: yearly
reviewed_at: 2026-05-10
next_review_at: 2027-05-10
stale_after: 2027-06-10T00:00:00Z
---

What each key evidences:

• type, title, description: identification and description, the first item of clause 7.5.2 in the Harmonized Structure that ISO 30401 shares with ISO 9001. These are also the Open Knowledge Format's core fields (OKF v0.2 §4.1). OKF is an open specification published by Google Cloud.
• domain: the knowledge domain from your scope (4.3). This is your own key, not a standard field.
• owner: accountability for the page, backed by your roles definition (5.3).
• generated and sources: who produced the current content, when, and from what (OKF §5.2 and §5.1). This is provenance for new knowledge.
• verified: a named person confirmed the content (OKF §5.2). OKF consumers treat a human: verifier as "human-reviewed" (§5.3). This is your review record. It answers a different question from reviewed_at: verified says who confirmed the content, while reviewed_at says when the page was last checked under your review cycle. The two can share a date without duplicating each other.
• status, the review dates and stale_after: handling outdated or invalid knowledge (4.4.2). OKF defines status as draft, stable or deprecated (§5.4), and stale_after as the instant after which the page is stale (§5.5; write it with a UTC offset). The review cadence is yours to choose; the standard names none. For how to pick one, see Does ISO 9001 require periodic document review?

When a page is replaced, don't delete it. Mark it status: deprecated and link to the replacement, so people and tools following old links land somewhere honest.

What to expect in an audit

These are practical expectations, not quotations from the standard:

• Your scope and priorities (4.3). Are the pages you govern closely the ones in the domains you prioritized?
• Evidence that outdated knowledge is handled (4.4.2). Deprecated pages should be marked and point to their replacements, and review dates should be real.
• Owners who know they own things (5.3). An owner field nobody recognizes is worse than none.
• Metadata in management review (9.3). For example, the share of pages past their review date, and what was done about it.

Certification to ISO 30401 is an audit of your whole management system by a certification body. No file schema or tool can confer it. Good frontmatter makes one part of the evidence cheap to produce and easy to check.

If you're already on ISO 9001

In ISO 9001, knowledge appears as clause 7.1.6, organizational knowledge. ISO 30401 treats knowledge management as a management system in its own right. Both use the same documented-information clause structure (7.5), so one frontmatter schema can serve both. See ISO 9001 clause 7.5.2 as markdown frontmatter.

Why this matters more once AI agents read your knowledge base

Agents amplify whatever they retrieve. When Claude Code, GitHub Copilot, Cursor or a local model answers from your knowledge base, an outdated page becomes an outdated answer, delivered with confidence. That makes "handling outdated or invalid knowledge" concrete:

1. Mark the page (status: deprecated).
2. Date it (stale_after).
3. Have the agent, or the retrieval layer in front of it, skip or flag whatever is marked or past its date.

If those tools also edit the knowledge base, see A defensible audit trail for AI-edited documentation.

Where JidoSeal fits

JidoSeal's Gold tier checks that every file carries status, review_policy, reviewed_at and next_review_at. That is its own way of evidencing the "handling outdated or invalid knowledge" part of clause 4.4.2 on a markdown corpus. ISO 30401 prescribes none of those fields and no review interval, and a JidoSeal certificate is not ISO 30401 certification. Pick a folder, scan it, and the free Self-Check shows which files are missing which fields and writes the fixes you approve. The scan and the fixes are free, and your files never leave your machine; only a certificate costs money.

Related questions

• ISO 9001 clause 7.5.2 as markdown frontmatter: the same clause 7.5, field by field.
• Does ISO 9001 require periodic document review? No interval is set; how to choose and record your own.
• A defensible audit trail for AI-edited documentation: provenance and approvals when AI tools edit your pages.

Sources

• ISO 30401:2018 catalogue entry (edition 1, amendments, revision status): iso.org/standard/68683.html; ISO/DIS 30401 (edition 2, stage 40.60): iso.org/standard/89436.html
• ISO 30401:2018, publisher's sample (introduction, clauses 1–4.3, table of contents): standards.iteh.ai sample
• The Harmonized Structure, clause 7.5: ISO/IEC Directives, Part 1, Consolidated ISO Supplement, Annex SL, Appendix 2: iso.org
• Judy Payne, BS ISO 30401: Knowledge management systems – an end to the confusion?, APM, 1 November 2018: apm.org.uk
• RealKM, Evaluating ISO 30401 standard: Part 1 – What has changed since the draft?, January 2019: realkm.com
• Open Knowledge Format v0.2 (Google Cloud, Apache-2.0): SPEC.md