| K-101 | Recognises a data requirement making several claims | Skill |
| K-102 | Recognises a data requirement prescribing a design solution | Skill |
| K-103 | Recognises a statement outside the scope of data requirements | Skill |
| K-104 | Recognises an ambiguous business term in a data requirement | Skill |
| K-105 | Recognises untestable wording in a data requirement | Skill |
| K-106 | Recognises an unverifiable data requirement | Skill |
| K-107 | Recognises a reference with several possible referents | Skill |
| K-108 | Recognises a data requirement without a named subject | Skill |
| K-109 | Recognises a measure stated without unit or basis | Skill |
| K-110 | Recognises a data requirement silent on current versus past values | Skill |
| K-111 | Recognises an absolute statement with its exception unasked | Skill |
| K-112 | Recognises a mandatory attribute without its moment of obligation | Skill |
| K-113 | Recognises a business rule left inside another statement | Skill |
| K-114 | Recognises content filed under the wrong requirement | Skill |
| K-115 | Recognises an unsourced data requirement | Skill |
| K-116 | Recognises a missing or meaningless requirement priority | Skill |
| K-117 | Recognises a missing or wrong requirement type | Skill |
| K-118 | Recognises a status contradicting the requirement's content | Skill |
| K-119 | Recognises a guess recorded as fact | Skill |
| K-120 | Recognises a missing rationale for a non-obvious requirement | Skill |
| K-121 | Recognises duplicate data requirements | Skill |
| K-122 | Recognises paraphrased data requirements | Skill |
| K-123 | Recognises conflicting data requirements | Skill |
| K-124 | Recognises inconsistent terminology across the register | Skill |
| K-125 | Recognises a requirements register with unbounded scope | Skill |
| K-126 | Recognises a requirements register describing no events | Skill |
| K-127 | Recognises an uncovered identity requirement | Skill |
| K-128 | Recognises an uncovered volume or retention requirement | Skill |
| K-129 | Recognises an uncovered sensitivity or access requirement | Skill |
| K-130 | Recognises an uncovered lineage requirement | Skill |
| K-131 | Recognises undecided history requirements across the register | Skill |
| K-132 | Recognises a requirements register serving no stated question | Skill |
| K-133 | Recognises a missing or wrong requirement trace | Skill |
| K-134 | Recognises unstable requirement identifiers | Skill |
| K-151 | Explains singular and unambiguous requirement statements | Knowledge |
| K-152 | Distinguishes a business requirement from a design solution | Knowledge |
| K-153 | Explains the data requirement types of the register | Knowledge |
| K-154 | Explains requirement attributes and traceability | Knowledge |
| K-155 | Explains current value, history and point-in-time reproducibility | Knowledge |
| K-156 | Explains the identity of a business thing | Knowledge |
| K-157 | Explains the non-functional data concerns | Knowledge |
| K-158 | Explains the scope, events and questions a data register must state | Knowledge |
| K-159 | Explains referential and logical ambiguity in natural-language statements | Knowledge |
| K-160 | Explains persistent identifiers | Knowledge |
| K-161 | Explains verifiable requirement statements | Knowledge |
| K-162 | Explains consistency within a requirements register | Knowledge |
| K-135 | Retires a superseded register entry instead of deleting it | Skill |