Skip to content
WorkforceObservatory

Lineage: why every HR number needs a receipt

Author

Gabriel Croitoru

Date Published

A raw file traced through a hash chain into a governed metric card

When Finance reports a number, the ledger behind it is assumed. When HR reports a number, the pipeline behind it is usually a person's memory of which exports they ran. Lineage closes that gap: every figure carries a traceable path back to the source file, the rules applied and the moment it was computed.

What lineage actually records

  • The raw evidence — the exact file or API page that produced the record, hashed so tampering is detectable.
  • The transformations — the mapping and validation rules applied, in the version they were applied, not the version that exists today.
  • The chain of custody — who or what touched the data at each step, in an append-only audit log.
  • The compute stamp — when the metric was last derived, so "this looks stale" becomes a checkable property.

Why it changes the conversation

Without lineage, a disputed number produces a week of archaeology. With lineage, it produces a two-minute walk from the chart to the source row. Disagreement stops being about trust in a colleague's spreadsheet process and becomes a technical question with an answer — which is also what makes external audit, works councils and DPO reviews dramatically cheaper.

How it is built

In Workforce Observatory the path runs through three governed layers — Bronze keeps the immutable evidence, Silver standardizes entities with resolved identity, Gold holds analytics-ready facts — and every published figure references the artifacts underneath it. Nothing enters a dashboard without a receipt. See the governed pipeline.