Coverage Status

Coverage Status is a derived record that compares the actual coverage of a business architecture domain in an organizational unit with the level expected for it, and records the gap. It provides a point-in-time snapshot, enabling progress tracking and gap identification.

Schema: coverage-status.schema.json
Specification: JSON Schema Draft-07

Overview

What is Coverage Status?

Each Coverage Status record covers one domain in one organizational unit and records:

• Coverage score — A numeric score (e.g. 0.0–1.0) from document and data analysis
• Level achieved — The coverage level the score corresponds to
• Level expected — The target level from the matching coverage expectation
• Gap — The difference between the achieved and expected levels
• When it was last evaluated, with optional notes explaining the gap

Coverage Calculation

coverageScore = documented items / expected items     (0.0 – 1.0)
coverageLevelAchieved = the level the score corresponds to
coverageGap = number of levels between coverageLevelAchieved and expectedCoverageLevel

Where:

• Documented items = attributes and elements with valid values
• Expected items = attributes and elements the expected level calls for

For example, documented achieved against analysed expected is a gap of 1. A gap of zero means the expectation is met. Compare the gap with the organization goal's coverageGapTolerance to decide whether it needs action.

Status Attributes

Attribute	Type	Required	Description
coverageStatusID	String	✓	Unique identifier for the coverage status record
orgUnit	String	✓	Organizational unit assessed
domain	String	✓	The business architecture domain assessed
coverageScore	Number	✓	Numeric score (e.g. 0.0–1.0) based on actual coverage determined by document and data analysis
coverageLevelAchieved	Enum	✓	Categorical level derived from the score
expectedCoverageLevel	Enum	✓	Target level defined in the coverage expectation
coverageGap	Number	✓	Calculated gap between achieved and expected levels (may be zero)
lastEvaluatedAt	Date-time	✓	Timestamp when this coverage status was last assessed
notes	String or null		Optional comments or explanation for the gap

Coverage Level (coverageLevelAchieved, expectedCoverageLevel)

Value	Description
none	The domain is not documented
minimal	A few entities are recorded with little detail
documented	Core entities and their attributes are recorded
analysed	Relationships, dependencies and gaps have been analysed
governed	Ownership, review and change control are in place
optimised	The domain model is maintained continuously and used to drive decisions and improvement

Reading the Gap

Gap	Criteria	Color Code
Negative	Achieved level is above the expected level	Green
Zero	Expectation met	Green
Within tolerance	Gap within the goal's coverageGapTolerance	Amber
Above tolerance	Gap exceeds the goal's coverageGapTolerance	Red
none achieved	Domain not started	Grey

Example

Finance Unit Capability Coverage

{
  "coverageStatusID": "cstat-100",
  "orgUnit": "OU-Finance",
  "domain": "capability",
  "coverageScore": 0.67,
  "coverageLevelAchieved": "documented",
  "expectedCoverageLevel": "analysed",
  "coverageGap": 1,
  "lastEvaluatedAt": "2025-07-02T09:00:00Z",
  "notes": "Good initial coverage, but process-level granularity missing"
}

Usage Guidelines

Performing Assessments

1. Use consistent methodology — Apply the same scoring criteria across assessments
2. Document evidence — Record how coverage was calculated in notes
3. Assess quality, not just quantity — Completeness alone isn't enough to reach analysed or governed
4. Identify root causes — Why are gaps occurring?
5. Prioritize remediation — Focus on gaps in the most heavily weighted domains

Assessment Frequency

Scenario	Recommended Frequency
Active BA program	Monthly
Mature organization	Quarterly
Project milestone	At each gate
Annual review	Yearly comprehensive

For Data Engineers

Coverage Status metrics map directly to OpenMetadata completeness scores. Consider creating automated assessments that calculate coverageScore from data catalog population, enabling real-time tracking of business architecture documentation alongside data asset documentation.

Related Documentation

• Coverage Template — Typical coverage levels by sector and size
• Organization Goal — Weight domains and set gap tolerances
• Coverage Expectation — Set the target level for a domain