DPO Radio

Cross-Review Comparison

Overview Image

Why Cross-Review Comparison Matters

A vendor portfolio reviewed quarter over quarter, a contract corpus reviewed before and after a clause-library revision, a framework comparison across pack updates — each is a comparison across review cycles. The question that matters is "what has shifted?", and answering it manually means walking two grids cell by cell.

Cross-review comparison surfaces the shifts automatically. The diff view shows which cells have changed, which documents have entered or exited the portfolio, and which attributes have new patterns. Annotation threads carry over so the prior cycle's discussion stays attached to the relevant cells.

How It Works

Run Two Grids

The user runs the same tabular review on two document sets — quarter-over-quarter, before-and-after revision, framework-pack update. Each grid is a separate run with its own audit trail.

Side-By-Side Diff View

The diff view shows the two grids side by side. Cells that have changed are highlighted; cells that are stable are visible but de-emphasised.

Entered and Exited Documents

Documents present in one grid but not the other are surfaced explicitly so the reviewer sees the portfolio movement.

Attribute Trends Across Cycles

For grids run on a recurring cadence, the trend view shows attribute distribution shifts (e.g. governing law moving from English to Vietnamese across the vendor portfolio over four quarters).

Annotation Carry-Over

Cell-level discussion threads from the prior cycle carry over to the new grid where the cell remains stable. Threads are not duplicated; they remain attached to the cell.

Export Through the Unified Pipeline

The diff view exports through the platform's unified export pipeline. The export carries the side-by-side grids and the annotations.

The Difference

Graphic Image

Without Cross-Review Comparison

Graphic Image

With Forseti Cross-Review Comparison

IconCross-cycle comparisons are bespoke per analyst.
IconSide-by-side diff view surfaces shifts automatically.
IconShifts surface only at audit time.
IconEntered and exited documents surface explicitly.
IconPrior-cycle annotations are lost.
IconAnnotation threads carry over from prior cycles.

Built for Auditable AI

Build For Image

Each grid is an independent run with its own audit trail. The diff view consumes both runs read-only; it does not mutate either underlying grid.

Build For Image

The export through the unified pipeline preserves the audit-trail context. Auditors walk the comparison with full provenance.

Build For Image

Annotation carry-over preserves the prior cycle's reasoning. Nothing is silently dropped.

Overview Image

Compare Documents or Compare Runs

Use tabular review workflows to put documents side by side in one grid. Cross-review comparison reads two completed grids and shows what changed. The reviewer starts each document review with its selected set.

Background Image

See Cross-Review Comparison in Action

Ready to see two vendor-contract grids compared side by side with annotation carry-over? Request a personalised demo.

Demo Image
Ronni K. Gothard Christiansen

Ronni K. Gothard Christiansen - Technical Privacy Engineer & CEO

Technical Compliance Expert, 32+ Years Open Source Advocate, X-BoD Open Source Matters Inc.

Or contact via

ronni@aesirx.io+84 909 500 760

Next Steps

Icon Image

Start a Compliance Pilot

Run quarterly tabular reviews for one year and use the cross-review comparison to surface portfolio trends.

Icon Image

Discuss Your Compliance Needs

Talk to our team about cadence and which portfolios benefit from quarterly comparison.

Frequently Asked Questions About Cross-Review Comparison

Documents present in one grid but not the other are listed explicitly so the reviewer sees portfolio movement.

Yes. Cell-level discussion threads from the prior cycle carry over to the new grid where the cell remains stable.

Yes. The diff view exports through the platform's unified export pipeline.

The comparison itself is a read-only join of two existing runs and does not draw additional tokens. The underlying grids are independent runs that draw tokens at their own run time.

Yes. All tiers with Tabular Reviews support cross-review comparison.