Skip to content

Completeness Audit

Systematically search for missing cases, gaps, states, stakeholders, paths, records, requirements, or risks so the system does not fail in unhandled regions.

The Diagnostic Story

Symptom: Coverage artifacts exist — checklists, test suites, requirement matrices, policy documents — but nobody can explain what universe they are supposed to cover. Edge cases are decided ad hoc or routed through informal escalation. Relevant stakeholders, records, or scenarios appear only after a failure, complaint, or external audit. Different teams believe different things are included, and a default path quietly absorbs too many cases without evidence that they are genuinely equivalent.

Pivot: Make the intended coverage universe explicit, partition it into auditable units, map actual coverage against those units, identify missing or ambiguous regions, and assign each gap a defined disposition — repair, exclusion, escalation, deferral, or acceptance with rationale.

Resolution: Unhandled cases and edge failures decrease because gaps are found and assigned before deployment or enforcement. Scope and exclusion rationale become auditable rather than implicit. False assurance — treating a checklist as proof of coverage when it only documents what was thought of — becomes harder to sustain.

Reach for this when you hear…

[software testing] “Our test suite has ninety percent code coverage and it did not catch the bug because the coverage metric does not know which scenarios actually matter.”

[regulatory review] “We approved the policy for the standard cases, but the edge population we did not model is the one filing appeals.”

[product safety] “The hazard analysis covered the intended use but not foreseeable misuse, and that is exactly how the injury happened.”

Mechanisms / Implementations

  • Test Coverage Audit: This is an implementation mechanism for Completeness Audit, not the archetype itself.
  • Policy Gap Analysis: This is an implementation mechanism for Completeness Audit, not the archetype itself.
  • Stakeholder Inclusion Review: This is an implementation mechanism for Completeness Audit, not the archetype itself.
  • Data Completeness Check: This is an implementation mechanism for Completeness Audit, not the archetype itself.
  • Requirements Traceability Matrix: Threads every requirement through to the design, code, and verification that satisfy it, so any requirement with no downstream link — or no passing test — is a visible coverage hole.
  • Risk Register Review: This is an implementation mechanism for Completeness Audit, not the archetype itself.
  • Coverage Checklist Walkthrough: This is an implementation mechanism for Completeness Audit, not the archetype itself.
  • Scenario Tabletop Review: This is an implementation mechanism for Completeness Audit, not the archetype itself.

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (3)

Also references 7 related abstractions

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Case Coverage Audit · subtype · recognized

Audit whether all relevant case classes, exception classes, and edge cases are represented and assigned a disposition.

State-Space Completeness Audit · subtype · recognized

Audit whether all relevant states, transitions, modes, or lifecycle phases are represented and covered by rules, tests, or responses.

Stakeholder Inclusion Audit · governance variant · recognized

Audit whether the affected stakeholder set includes overlooked actors, indirect stakeholders, boundary populations, and those with limited voice.

Requirements Coverage Audit · implementation variant · recognized

Audit whether every relevant requirement, obligation, decision, or specification is linked to implementation, test evidence, owner, or disposition.

Data Completeness Audit · domain variant · recognized

Audit whether required records, fields, observations, periods, categories, or source types are present or explicitly classified as missing.

Scenario or Path Coverage Audit · subtype · recognized

Audit whether relevant scenarios, user journeys, escalation paths, or incident paths have defined handling and ownership.

Exhaustive Case Handling · subtype · promote to full archetype candidate

Define explicit handling for every relevant case class so cases do not fall through implicit gaps.