Admin metric detail

The metric detail page is the operational hub for a single definition after it exists in the catalog. Use it to publish, tune thresholds, attach goals and alerts, drill into data, and connect the metric to scorecards.

Lifecycle

Metrics progress through lifecycle states (draft, published, archived, and transitions your process uses). Promote, publish, unpublish, archive, and clone actions are gated by policy so built-in or protected definitions cannot be damaged accidentally.

Thresholds and bands

Per-metric threshold editing is the supported place to configure score bands. The standalone Score thresholds list still exists for backward compatibility but redirects to the modern editor; see Admin score thresholds legacy.

Goals

Goals attach targets to the metric for periods you configure. Create, update, or remove goals when your compensation or operations plan requires them.

Alerts

Metric alerts define notification-style rules tied to this definition. Create and edit alerts from the detail surface when you need proactive signal on breaches or patterns.

Drilldown and recalculate

Drilldown explores underlying rows or drivers depending on grain and permissions.
For daily-grain metrics, the per-driver breakdown (and CSV export) defaults to the operational Sun–Sat week (UTC) identified by the ISO Year–Week label on the chip, trimmed so it never steps outside your from–to range. ISO week here is only the selector for which Sun–Sat block you mean; it is not a separate “Monday-first” calendar in the engine. If your to date falls mid-week, you only get the days that overlap both that Sun–Sat window and your range; the page shows an amber note when that happens. If the focused week has no rows, the page walks backward week-by-week inside your span until it finds data; only then does it fall back to the full from–to window so you still see drivers when every focused week is empty. The ← / → controls beside the chip step table_iso_year / table_iso_week through ISO weeks that overlap your from–to span so you can compare weeks without shifting the chart range. The trend chart and headline always use the full from–to window.
Drivers who have any daily fact for this metric somewhere inside your from–to span appear on every ISO-week slice; slices with no activity for a driver show empty values (em-dash) instead of hiding that row.
This admin page lists inactive or terminated drivers too when they still appear in the roster (driver-facing scorecards continue to hide them elsewhere).
Recalculate requests a refresh window when facts need rebuilding (subject to queues and sync health).

Scorecard inclusion

Toggle include on scorecard and manage scorecard layout order so weekly reporting shows the metric in the right place. Where editing is enabled, the headline grid uses drag handles and saves layout with debouncing; placement is stored as a versioned layout document (12-column slots for metrics and scorecard composites, including inner positions for composite components) plus legacy ordering for compatibility. Pair with Admin weekly scorecard.

Publish checklist

The publish checklist route supports go-live verification before you commit a lifecycle transition. When checks fail, you can still publish if you have publish permission: open Publish, read the failing rows, check Publish anyway despite failing checks, and explain why in Why now / what changed. The system records that you overrode the checklist.

Destroy

Deleting a metric is irreversible where policy allows. Built-in or published definitions may be blocked with a clear reason.