Admin weekly scorecard
The weekly scorecard admin view is a paginated grid of users with driver and dispatcher metric columns for operational weeks. Pick the week from the Operational week dropdown: it lists every UTC Sunday (YYYY-MM-DD) that already has rows in metric_weekly_scorecard, plus the current week (even before rows exist), labeled Week N: Month D - Month D, YYYY. With no query parameter, the grid defaults to the week that contains today (UTC). Legacy bookmark links may use ISO year/week; the app redirects to the same week via week start. Weekly Samsara snapshot metrics (safety, efficiency, etc.) can update during the open week as sync runs, through the Saturday close, not only after the week ends. It is the operational place to review weekly performance, compare roles side by side where configured, and perform weekly lock or override actions your permissions allow.
Scorecard composites (weighted blends of other driver metrics) appear as one compact mini-card per composite in the metrics column; embedded-only components do not get a duplicate mini-card beside the composite block.
Use Driver scorecard list only (driver columns) to hide driver-scoped metrics that are not on the driver-facing scorecard list — the same setting as Include on driver scorecard list on each metric’s admin detail page. Dispatcher columns stay visible. Your choice is remembered with the other list filters. On finalized weeks, narrowing uses the frozen snapshot copy of that flag.
Dispatchers with weekly scorecard access but without view any drivers (admin.drivers.view_any) see only drivers assigned to them for the selected week (from Dispatcher assignments). Admins and users with view-any still see the full roster.
Live week versus finalized (frozen) week
For some weeks the grid reads a finalize snapshot stored when the week was locked: metric columns and roster can differ from the usual live catalog union. Weekly Samsara snapshot metrics (Safety, Efficiency, and similar) are included in that snapshot when they are in shadow or published. If you see an empty metric list on such a week, the snapshot may need to be rebuilt (see operator docs for scorecard:snapshot-finalized-weeks), which targets weeks that already have locked scorecard rows unless an operator uses the explicit unlocked escape hatch documented there, or the week may still need to be locked. Values on finalized weeks usually require locked scorecard rows; dashes often mean rows are not locked yet or the value was never written.
Weekly lock and overrides
Locking a week freezes canonical inputs for downstream processes (including bonus runs where applicable). Overrides adjust specific cells when policy allows. Treat these actions as audited, material changes.
Cell drilldown
Cell routes support focused inspection of a single user/week intersection when you need to trace a value.
Bonus context
Bonus schemes and payout jobs respect locked weeks. Coordinate with Admin bonus schemes operators when you change historical weeks.