# Governance Dashboard Content Model

> Defines the domain objects, relationships, statuses, and lifecycle states needed for governance and finance-led operating dashboards. Use when designing dashboards for policies, controls, evidence, issues, certifications, lineage, or audit readiness.

- Skill: `bkjohn2018/governance-dashboard-content-model` (Agent Skill)
- Install (CLI): `npx skillmds@latest add bkjohn2018/governance-dashboard-content-model`
- Raw SKILL.md: https://api.skillmd.com/api/skills/bkjohn2018/governance-dashboard-content-model/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: bkjohn2018 (https://skillmd.com/u/bkjohn2018)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/bkjohn2018/governance-dashboard-content-model

---


# Governance Dashboard Content Model

## When to Use
- Building governance, control, risk, or audit dashboards.
- Mapping business objects before designing UI or APIs.
- Turning workflow concepts into dashboard-ready entities and states.

## Core Object Types
- Policy
- Standard
- Control
- Certification / attestation
- Evidence item
- Risk owner
- Exception / issue
- Workflow request / approval
- Data asset / report / metric
- Ledger or operational artifact when finance traceability is required

## Workflow
1. Identify the core entities shown on the page.
2. Define each object’s lifecycle states, owners, and timestamps.
3. Map parent-child relationships and traceability paths.
4. Separate summary entities from drill-down entities.
5. Define which counts, statuses, and trends each object should expose.

## Output Template
```markdown
# Dashboard Content Model

## Core entities
| Entity | Purpose | Owner | Key statuses |
|---|---|---|---|

## Relationships
- Request -> Approval
- Control -> Evidence
- Issue -> Owner
- Metric -> Data asset

## Traceability paths
- Business event -> Operational data -> Control -> Approval -> Ledger -> Analytics

## Dashboard exposure
| Entity | Card metric | Drill page | Key actions |
|---|---|---|---|
```

## Quality Checklist
- Entity names match governed business terminology.
- Lifecycle states are explicit and mutually understandable.
- Traceability paths are complete enough for drill-down design.
- Summary counts are backed by drillable object models.