Coverage Expectation

Coverage Expectations define time-bound targets for achieving metamodel coverage. They break down Organization Goals into periodic milestones, enabling incremental progress tracking and realistic planning.

Schema Version: 2.1
Schema Location: /schemas/extensions/coverage-expectation.schema.json
Specification: JSON Schema Draft-07

Overview

What is a Coverage Expectation?

A Coverage Expectation specifies:

• Target coverage for a specific time period
• Domain-level milestones within the period
• Dependencies that must be met
• Resources required to achieve the target
• Risk factors that might affect achievement

Relationship to Other Coverage Extensions

Expectation Attributes

Core Attributes

Attribute	Type	Required	Description
expectationID	string (UUID)	Yes	Unique identifier
goalReference	reference	Yes	Parent organization goal
periodType	enum	Yes	Type of time period
periodStart	date	Yes	Period start date
periodEnd	date	Yes	Period end date
periodLabel	string	No	Human-readable period name

Target Attributes

Attribute	Type	Required	Description
targetCoverage	number	Yes	Target percentage for period
baselineCoverage	number	No	Starting coverage for period
incrementalTarget	number	No	Coverage increase expected
domainMilestones	array	No	Per-domain targets

Planning Attributes

Attribute	Type	Required	Description
dependencies	array	No	Prerequisites for achievement
resources	object	No	Resources allocated
risks	array	No	Factors that might affect target
assumptions	array	No	Planning assumptions

Period Types

Period Type	Duration	Typical Use
monthly	1 month	High-velocity programs
quarterly	3 months	Standard planning cycle
half-yearly	6 months	Long-term initiatives
annual	12 months	Strategic planning
custom	Variable	Project-specific milestones

Domain Milestones

Each domain can have specific milestones within the period:

{
  "domainID": "capabilities",
  "milestoneName": "Complete L2 capability documentation",
  "targetCoverage": 75,
  "baselineCoverage": 55,
  "incrementalTarget": 20,
  "priority": "high",
  "deliverables": [
    "L2 capability map validated",
    "Owner assignments complete",
    "Performance indicators linked"
  ],
  "successCriteria": "All L2 capabilities have description, owner, and at least one KPI"
}

JSON Schema Definition

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "$id": "https://orthogramic.com/schemas/extensions/coverage-expectation.schema.json",
  "title": "Coverage Expectation",
  "description": "Time-bound coverage target for an organization goal",
  "type": "object",
  "required": ["expectationID", "goalReference", "periodType", "periodStart", "periodEnd", "targetCoverage"],
  "properties": {
    "expectationID": {
      "type": "string",
      "format": "uuid"
    },
    "goalReference": {
      "type": "object",
      "properties": {
        "goalID": {"type": "string", "format": "uuid"},
        "goalTitle": {"type": "string"}
      },
      "required": ["goalID"]
    },
    "periodType": {
      "type": "string",
      "enum": ["monthly", "quarterly", "half-yearly", "annual", "custom"]
    },
    "periodStart": {
      "type": "string",
      "format": "date"
    },
    "periodEnd": {
      "type": "string",
      "format": "date"
    },
    "periodLabel": {
      "type": "string"
    },
    "targetCoverage": {
      "type": "number",
      "minimum": 0,
      "maximum": 100
    },
    "baselineCoverage": {
      "type": "number",
      "minimum": 0,
      "maximum": 100
    },
    "incrementalTarget": {
      "type": "number"
    },
    "domainMilestones": {
      "type": "array",
      "items": {
        "type": "object",
        "required": ["domainID", "targetCoverage"],
        "properties": {
          "domainID": {"type": "string"},
          "milestoneName": {"type": "string"},
          "targetCoverage": {"type": "number", "minimum": 0, "maximum": 100},
          "baselineCoverage": {"type": "number"},
          "incrementalTarget": {"type": "number"},
          "priority": {"type": "string", "enum": ["critical", "high", "medium", "low"]},
          "deliverables": {"type": "array", "items": {"type": "string"}},
          "successCriteria": {"type": "string"}
        }
      }
    },
    "dependencies": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "dependencyType": {"type": "string", "enum": ["resource", "data", "approval", "external", "technical"]},
          "description": {"type": "string"},
          "owner": {"type": "string"},
          "dueDate": {"type": "string", "format": "date"},
          "status": {"type": "string", "enum": ["pending", "in-progress", "complete", "blocked"]}
        }
      }
    },
    "resources": {
      "type": "object",
      "properties": {
        "fteAllocation": {"type": "number"},
        "budget": {"type": "number"},
        "tools": {"type": "array", "items": {"type": "string"}},
        "externalSupport": {"type": "string"}
      }
    },
    "risks": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "riskDescription": {"type": "string"},
          "likelihood": {"type": "string", "enum": ["high", "medium", "low"]},
          "impact": {"type": "string", "enum": ["high", "medium", "low"]},
          "mitigation": {"type": "string"}
        }
      }
    },
    "assumptions": {
      "type": "array",
      "items": {"type": "string"}
    },
    "status": {
      "type": "string",
      "enum": ["planned", "active", "complete", "missed", "exceeded"]
    },
    "actualCoverage": {
      "type": "number",
      "minimum": 0,
      "maximum": 100
    },
    "variance": {
      "type": "number"
    },
    "completionNotes": {
      "type": "string"
    }
  }
}

Example

Q1 Coverage Expectation

{
  "expectationID": "exp-001",
  "goalReference": {
    "goalID": "goal-001",
    "goalTitle": "Retail Banking Architecture Coverage FY25"
  },
  "periodType": "quarterly",
  "periodStart": "2025-01-01",
  "periodEnd": "2025-03-31",
  "periodLabel": "Q1 FY25",
  "targetCoverage": 55,
  "baselineCoverage": 35,
  "incrementalTarget": 20,
  "domainMilestones": [
    {
      "domainID": "organization",
      "milestoneName": "Complete org structure documentation",
      "targetCoverage": 90,
      "baselineCoverage": 70,
      "incrementalTarget": 20,
      "priority": "high",
      "deliverables": [
        "L3 org units documented",
        "Reporting lines validated",
        "Role definitions complete"
      ],
      "successCriteria": "All L3 units have owner, description, and parent link"
    },
    {
      "domainID": "capabilities",
      "milestoneName": "L1/L2 capability map complete",
      "targetCoverage": 60,
      "baselineCoverage": 40,
      "incrementalTarget": 20,
      "priority": "critical",
      "deliverables": [
        "L1 capabilities defined and validated",
        "L2 capabilities mapped to L1",
        "Capability owners assigned"
      ],
      "successCriteria": "100% of L1 and 80% of L2 capabilities documented"
    },
    {
      "domainID": "risk-management",
      "milestoneName": "Initiate risk domain documentation",
      "targetCoverage": 30,
      "baselineCoverage": 10,
      "incrementalTarget": 20,
      "priority": "high",
      "deliverables": [
        "Risk taxonomy adopted",
        "Top 20 risks documented",
        "Risk ownership assigned"
      ],
      "successCriteria": "Risk framework established with initial population"
    }
  ],
  "dependencies": [
    {
      "dependencyType": "data",
      "description": "Access to existing capability inventory from legacy system",
      "owner": "Enterprise Architecture",
      "dueDate": "2025-01-15",
      "status": "complete"
    },
    {
      "dependencyType": "resource",
      "description": "Business analyst allocation confirmed",
      "owner": "PMO",
      "dueDate": "2025-01-10",
      "status": "complete"
    },
    {
      "dependencyType": "approval",
      "description": "Risk taxonomy approval from CRO",
      "owner": "Group Risk",
      "dueDate": "2025-02-01",
      "status": "pending"
    }
  ],
  "resources": {
    "fteAllocation": 2.5,
    "budget": 50000,
    "tools": ["Orthogramic Platform", "Confluence", "Miro"],
    "externalSupport": "Architecture consulting support (40 hours)"
  },
  "risks": [
    {
      "riskDescription": "SME availability during busy period",
      "likelihood": "medium",
      "impact": "high",
      "mitigation": "Book SME time in advance; prepare documentation templates"
    },
    {
      "riskDescription": "Legacy data quality issues",
      "likelihood": "high",
      "impact": "medium",
      "mitigation": "Build validation time into schedule; accept 80% accuracy initially"
    }
  ],
  "assumptions": [
    "Organization structure is stable during Q1",
    "No major reorganization planned",
    "Existing capability inventory is 60% accurate",
    "Risk taxonomy will be approved by end of January"
  ],
  "status": "active"
}

Planning Visualization

Usage Guidelines

Creating Realistic Expectations

1. Base on actual capacity — Don't overcommit
2. Account for dependencies — What must happen first?
3. Include buffer — Things take longer than planned
4. Prioritize ruthlessly — Focus on highest-value domains
5. Track actively — Review progress against milestones

Expectation vs. Actual Tracking

Period	Expected	Actual	Variance	Status
Q1	55%	52%	-3%	Approaching
Q2	70%	-	-	Planned
Q3	80%	-	-	Planned
Q4	85%	-	-	Planned

Adjusting Expectations

When expectations are missed:

1. Analyze root cause — Why did we miss?
2. Adjust future periods — Redistribute target
3. Address blockers — Remove dependencies
4. Communicate early — Don't wait until period end

For Data Engineers

Coverage Expectations can drive data catalog population sprints. Align your data documentation milestones with business architecture coverage expectations to ensure data assets are documented in parallel with the capabilities and processes they support.

Related Documentation

• Coverage Template — Define coverage requirements
• Organization Goal — Set overall objectives
• Coverage Status — Track current state