LiftShift Records

Lineage & activity

See the source.
Understand the record.

When a value raises a question, follow it back. LiftShift Records keeps the source, the value in use and any later correction distinct.

Explore a report in LiftShift Records
One field, with its source contextFictional records
01 Source
The value as it appeared in the retained source.
02 Transformation
The mapping that turns a code or stored value into a readable field.
03 Correction
A later change to the record, with its own reason and history.

The history of the record

What happened
to this record?

Activity gives a reviewer a different kind of context. It shows when a report was processed, opened or exported, and who performed the recorded action.

The example shows a report view, an attachment view and an export alongside processing and publication events.

Bring a question

“Who exported this report, and when?”

During implementation, agree on the events, the review permissions and the outputs your organization needs.

A record’s activityFictional records
A record’s activityFictional records

This example is laid out for a wider screen.

Open full size ↗

Make the distinction clear

A corrected record still
has a source.

Correcting one record is different from changing how a report reads the source.

A correction can show the value in use, who changed it and why. A mapping or report change can affect a broader set of records and belongs in its own review process.

See corrections and record history

Start with a real records question

Make the history easier to explain.

Show us the questions your staff need to answer. We’ll walk through the report, source and activity views.