CONTENT OPERATIONS DASHBOARD: FICTIONAL SAMPLE
Open content-operations-sample.csv and metric-dictionary.csv in a spreadsheet.
UTF-8 CSV files contain data, not spreadsheet formulas. Import IDs and dates as
text if your spreadsheet would otherwise rewrite them. Dates use YYYY-MM-DD.

One row is one content item. This small sample records at most one release date
per item; production repeat releases need a separate release-event table.
Snapshot: 2026-10-04. Reporting week: 2026-09-28 through 2026-10-04 inclusive.
Review is overdue only when its due date is BEFORE the snapshot date.
An item due on the snapshot date is not yet overdue under this definition.

Expected checks:
8 unique items total.
4 open work items (status queued, draft or review; exclude published/canceled).
4 published items (status published).
3 published items have known review dates; 1 lacks a review date.
2 of the 3 known-date published items are overdue: 2/3=66.7%.
Review-date coverage: 3/4=75%.
2 recorded releases fall within the inclusive reporting week.
Read metric-dictionary.csv for each population, definition and action.
Keep the missing-date count visible beside the overdue percentage.

Adaptation:
Choose a decision owner and action for each measure.
Set snapshot, time zone, release-event rules and exclusions before counting.
Validate unique IDs, status vocabulary and real date values.
Display data freshness and source coverage.
Trace each total back to records. Investigate gaps and process causes before
using measures to compare people or teams.
Keep counts and denominators when rounding displayed percentages.

Source guide: https://yenra.com/business-intelligence-dashboards/
Prepared October 4, 2026.