Issue Ledger

The issue ledger merges structured reviewer outputs into one list you can disposition: duplicates collapsed, disagreements labeled, and limits surfaced honestly before you apply fixes or export.

Last updated 2026-05-14

How this fits your process

Use this when
You need one merged backlog of reviewer findings to disposition.
Output
Structured issue list with disagreement labels and honest partial status.
You verify
Yes—severity, merges, and regulated language.
Related
Proof Report, Multi-model review, Apply Fixes.

Issue ledger workflow

How to use

01
Run Document Check
Finished file
02
Open issue ledger
Merged findings
03
Map severity
Your org rubric
04
Resolve disagreement
When reviewers split
05
Disposition
Fix, verify, or ignore

Learn more

Why disagreement belongs in the ledger“Looks fine” is not a safe output.

When reviewers split, Recensa treats that as a review signal in the issue ledger—your team decides the resolution, not a hidden majority vote.

Merge behaviorDuplicates collapsed; limits surfaced honestly.

The ledger merges structured reviewer outputs: duplicates collapsed, disagreements labeled, and partial status surfaced when limits or quorum affect the run.

Limits and manual verificationLabels, merges, and sensitive spans still need your review.

Do not ship based on model severity labels alone—map to your rubric.
Check whether merged items over-combine materially different problems.
Regulated language, numbers, and party identity—pair with locks and your own review.

Run a Document Check

Try this on a finished DOCX or PDF—triage the issue ledger before any edits.

Run a Document Check