The talent star, per-cycle rows

Two facts and five dimensions. The rating fact keeps one row per worker per cycle, on the scale that cycle used. The event fact keeps the review process itself: launched, submitted, calibrated, completed, each step dated.

RuleVersion the scale and the org on the dimensions. A rating means nothing without the scale it was given on and the org it was given in.

Neverlet the current cycle overwrite the last. The tenant shows the latest; the model keeps them all, which is what a history is.

Two facts, five dimensions. Ratings are per-cycle rows on versioned scales, so history survives scale changes and reorgs.

◆ The tablestwo facts, five dimensions, versioning where it matters.

Table	Grain	Feeds
fct_rating	One worker, one cycle, one rating type, one value on its scale.	Distribution, nine-box, rating history.
fct_review_event	One dated step of one review: launched, self-assessed, submitted, calibrated, completed.	Completion, step elapsed times.
dim_worker	Who. Shared with the Core HR star.	Every report's population.
dim_review_cycle	The cycle: window, type, eligible rule.	Per-cycle everything.
dim_rating_scale	The configured scale, versioned as it changes.	Ratings that stay comparable, or honestly incomparable.
dim_org	The rollup, versioned, same as the other module stars.	Distributions that survive reorgs.
dim_date	The calendar, shared.	Windows and trends.

◆ Why versioning is the designscales change, orgs change, history should not.

Scales get redesigned between cycles, and a 4 on the old five-point scale is not a 4 on the new four-point one. Orgs restructure, and last cycle’s department distribution has to roll up under last cycle’s tree. Both dimensions carry versions with dates, the same discipline the trending store page shows Workday’s delivered history lacks, so every cycle reads under its own definitions forever.

The event fact adds the process: where every review stands, how long calibration took, and which steps drag. Extraction runs on the extraction pattern, business process history typed into dated rows like recruiting’s.

Use case

Problem

Ratings exist only as the latest value, scales and orgs change under them, and process status is invisible.

What we build

A per-cycle rating fact on versioned scale and org dimensions, with the review process as dated events.

What you get

Every cycle readable under its own definitions forever, and a process view that shows where reviews stall.

What did your distribution look like two scales ago?

We ship the versioned rating model that still knows.

Talk to us

Terms on this page

HR: Human resources. The Core HR star shares its dimensions with this one.
fact: A table of measured rows. Here, ratings and review steps.
grain: What one row means. One worker, one cycle, one rating.
versioned dimension: A dimension keeping each historical value with its dates.
rating type: Performance, potential, values: the axes a cycle collects.
calibration step: The session where managers align ratings before completion.
business process: Workday’s workflow engine, where review step history lives.