Business context
Define ownership, purpose, period, sensitivity, and acceptable use in language teams understand.
Policies and controls remain attached as evidence moves from source to calculation, finding, investigation, and outcome.
Define ownership, purpose, period, sensitivity, and acceptable use in language teams understand.
Trace transformations, joins, mappings, calculations, and versions from field to final impact.
Apply role-based access, approvals, separation of duties, and explicit human validation.
Lineage is the record of how data moves from raw input to final claim. ReturnValue tracks that movement automatically, as part of the platform, and builds it into core workflows instead of a separate tool you switch into. Open any insight or export, and the path that produced it is one click away, from source to claim.
The lifecycle runs in six steps, captured automatically: discover, connect, transform, surface, trace, and govern. You do not configure these; they are emitted as the work happens. Sources are catalogued as they are added, and each one gets a stable identity that the rest of the system refers back to. Joins between sources are recorded with their keys, conditions, and the analyst who created them.
Type changes, derivations, and aggregates are tracked at the column level, not just at the dataset level, and insights, datasets, and exports inherit the lineage of the inputs that produced them. There is nothing to wire up: open any output and follow its lineage back through transforms and joins to the original sources.
Lineage is not a separate technical diagram. It is available wherever a user needs to evaluate the reliability of a financial conclusion.
Trust grows when business context and technical lineage tell the same story.
Illustrative view. Values shown are examples, not customer data.