Skip to main content

Documentation debt

The accumulating gap between what a dataset or model actually is and what its documentation claims, growing every time the underlying data changes without a corresponding datasheet or AI bill of materials update; compounds the same way technical debt does, and is often unrecoverable once the people who remember the original context leave.

Defined in 2 GAGE programs, which carry 3 distinct definitions of it. The wording above is taught in Certified AI Data Governance Professional (CADGP).

How each discipline defines it

The same term does different work depending on who is using it. These are the definitions as each program teaches them, unedited.

Certified AI Data Governance Professional (CADGP)

The accumulating gap between what a dataset or model actually is and what its documentation claims, growing every time the underlying data changes without a corresponding datasheet or AI bill of materials update; compounds the same way technical debt does, and is often unrecoverable once the people who remember the original context leave.

Engineering Judgment and Professional Formation

The deferred cost of writing documentation under deadline pressure, treated as a legitimate engineering tradeoff only when explicitly named, assigned an owner, and given a plan to close it, rather than silently passed to whoever needs the missing information later.

Certified AI Data Governance Professional (CADGP)

The gap between a written policy claim (a retention period, an access review cadence, a deletion commitment) and the operational evidence that would prove the policy is actually followed. Distinct from having no documentation at all, because it appears compliant until specifically tested.

Where it is taught

The exact lessons this term appears in. The first module of every program is free with a free account.

Where it shows up at work

A definition is where Documentation debt starts. The lessons above teach it inside the competencies below, which are what job descriptions ask for and what the GAGE credential records. Every link here is drawn from the same careers map that builds a role's readiness check.

Collects, labels and preserves the evidence that a control operated, a decision was made, and a claim can be defended to an auditor or regulator.

One lesson on this page teach it as a primary outcome.

Traces where data came from, what transformed it, who owns each hop and where it flows downstream, so a number can be defended.

One lesson on this page teach it as a primary outcome.

Roles that hire for it

Each role page shows the full competency set, what the seat decides, and a readiness check against your own evidence.

How job descriptions say it

Postings rarely use the textbook word. These are the phrases the careers map reads as asking for the competencies above.

“audit evidence”“record keeping”“decision log”“data flows”“data mapping”“source to report”

Where the frameworks place it: EU AI Act Articles 11 and 12; ISO/IEC 42001 Clause 7.5; EU AI Act Article 10; NIST AI RMF MAP 4.

One interview question about it

What evidence would you have ready before an auditor asks about an AI system, and how do you produce it as a byproduct of the work?

Asked of candidates for evidence collection and audit-ready documentation. Answering it in your own words is exactly how a GAGE topic is passed, and the credential records the pass where an employer can check it.

If you come from another field

Some backgrounds already carry this competency, and the readiness check gives credit for it.

Terms it appears with

Not an alphabetical neighbourhood: these are the terms taught in the same lessons, ranked by how often they appear together.