Decision history
See who reviewed, changed, approved, resolved, or reopened an investigation and why.
The record develops as the investigation proceeds, so audit evidence is complete, contextual, and available when it is needed.
See who reviewed, changed, approved, resolved, or reopened an investigation and why.
Preserve inputs, methods, versions, assumptions, and limitations behind quantified impact.
Maintain the exact source references used at each decision point, even as data changes.
Most teams discover that their audit trail has a hole in it the week before a review. ReturnValue is built so the recording happens automatically, at the same level the work does. Audit logging is integrated into platform operations rather than sold as a separate product, and activity, decisions, and outputs are recorded as they happen.
Uploads, schema changes, joins, insights, exports, and reviews are captured as they occur. There is no separate logging step, and nothing relies on people remembering to write down what they did. A useful trail does not just say user X clicked Y; it says what changed, who approved it, and what they were looking at, so the surrounding context is recorded alongside each event.
Outputs maintain traceability to the inputs and actions that produced them, so when someone asks how a number was reached, you have the path rather than a memory. Review workflows can be configured for teams that require approvals; when configured, the approval is captured alongside the rest of the trail, not as a separate document you have to keep in sync.
Reviewers can move from an executive conclusion to the underlying source evidence and return with the same context intact.
Audit confidence comes from preserving the decision—not rebuilding it later.
Illustrative view. Values shown are examples, not customer data.