RecensaRecensa home

Between draft and send

Independent proof for documents people rely on

Upload the finished file. See what needs attention. Export proof your team can reconcile — then decide what is ready to sign, send, or file.
Run a Document CheckAbout Apply Fixes
Document Check
Document Check

MSA_v4_final.docx

DOCX · finished file

  • Document CheckComplete
  • Issue ledger createdGrouped
  • Findings grouped3 areas
  • Proof ReportReady
  • Apply FixesAvailable
You keep final control before send or sign

What you get back

One workflow. Three outcomes.

  • Issue Ledger
    Everything worth a second look — in one list you can disposition.
  • Apply Fixes
    After triage, turn selected findings into edits you verify.
  • Proof Report
    An export-shaped summary for sign-off — not a chat transcript.

Step-by-step

Walk through a Document Check

Seven steps from upload to final decision — each step shows what you do, what Recensa does, and a live preview.

Step 1 of 7

Step 1

Upload your finished file

DOCX or PDF — the version you are about to send, sign, file, or submit.

What you do

Upload the finished file your team will rely on.

What Recensa does

Reads layout-aware structure — not a live drafting session.

What you get: A Document Check run on the real file, not toy sentences.

Step preview

File ready

MSA_final.docx

DOCX · finished file

Upload the version you are about to rely on.

Two modes

Review first. Fix second.

Proof Report mode

Judgment before edits

The file stays stable while you inspect findings — ideal for sensitive wording and partner handoffs.

Proof Report mode →

Apply Fixes

Edits you approve

After review, selected findings can become proposed edits or corrected outputs — never a silent rewrite of the whole file.

Technical term in exports: source-grounded edits.

Apply Fixes →

Review system

AI confidence is not document confidence.

Built for review, not blind trust

The product is not a wrapper around one model response.

Recensa is a document review system: it separates issue detection from change application, keeps a record of findings, labels uncertainty, and keeps the final decision with you. Multi-model review, reviewer agreement via additional reconciliation passes when configured, source-grounded edits only after review, and exports you can verify—designed to raise confidence, not replace professional judgment.

Issue detection first

Proof Report mode stabilizes the file while you triage the ledger.

Labeled disagreement

Competing reviewer signals stay visible—not buried in chat.

Proof record

Proof Reports and exports document what was reviewed.

Changes after review

Apply Fixes packages proposed edits you verify—never silent overwrites.

Over time, document-generating AI will need independent verification workflows. Recensa is built for that proof layer—not another drafting assistant.

Why single-AI review falls shortMulti-model reviewApply FixesRun a Document Check

One AI answer

  • Opaque confidence
  • No audit record
  • Easy to overtrust fluent wording
  • Single pass on complex context

Recensa proof workflow

  • Independent review passes
  • Issue ledger + disagreement labels
  • Source checks when attached
  • Proof Report + controlled Apply Fixes
  • You approve

Issue ledger snapshot

  • VoiceTerm inconsistency flagged
  • ClaimsSource mismatch vs. exhibit
  • StructureRelated clause needs review
  • Reviewer agreement2 of 3 flagged related risk; your review recommended

Technical depth

Architecture, limits, and exports

Advanced review architectureHow findings become a single review record.

Each Document Check runs three independent reviewers in parallel on Claude, GPT, and Gemini, assigned to distinct review roles—author intent and voice, skeptical claims and citations, structure and consistency. Supporting files feed source checks when enabled. An arbiter reconciles findings into one ledger; you receive downloads only after you reconcile the ledger—and any Apply Fixes path you chose.

Multi-model reviewThree providers, three roles, one ledger.

Multi-model review runs the three reviewers in parallel and merges their output through an arbiter—not separate chat threads. See multi-model review.

Reviewer agreementAdditional reconciliation when reviewers disagree.

When reviewers disagree, the system can run additional reconciliation passes (when configured) to narrow the split into clearer reviewer agreement. It narrows disagreement without hiding competing signals in the issue ledger; it does not replace your judgment on what still matters.

Source-grounded reviewSupporting files for evidence-aware checks.

Attach policy excerpts, prior versions, or reference files so reviewers can run source checks. Source checks · Supporting files.

Save-back and export behaviorNew files on save-back—never silent overwrites.

Exports include Proof Report and layout-faithful paths where supported. Google Drive save-back writes new files so originals stay intact. Google Drive import.

Trust and limitsVerify before you rely—and honest scope.
  • Not legal advice. Drafting QA and proof support only—your team decides what ships.
  • You still need to verify. Verify every proof report and proposed edit.
  • Apply Fixes packages suggestions. Reconcile before filing, publishing, or signing.
  • Source checks depend on supplied files. Evidence quality follows what you attach.

Frequently asked questions

What is a Document Check?

A Document Check is a single review run over your uploaded document. It produces the Issue Ledger and Proof Report for that run.

What is an Issue Ledger?

The Issue Ledger is one merged, dispositionable list of findings—duplicates collapsed, reviewer disagreement labeled, with honest partial status when limits apply.

What is a Proof Report?

A Proof Report is an exportable record of what was reviewed and what was found—useful for sign-off context. It is structured proof, not a chat transcript.

What does Apply Fixes do?

Apply Fixes (source-grounded edits) generates proposed changes and corrected outputs you can inspect before you use them, mainly for Word workflows. You still verify every change — Recensa never silently rewrites your file.

Does Recensa automatically change my document?

No. Proof-report mode never edits your file. Apply Fixes only proposes changes you review, and Recensa produces new outputs rather than overwriting your original.

Can I choose which issues to fix?

Yes — you disposition each issue and decide what to accept, ignore, or handle yourself. Nothing changes without your review.

What file types does Recensa support?

Main documents: Word (DOCX) and PDF. Supporting files for source checks: PDF, Word (DOCX, with limited .doc support), text, and Markdown.

Does Recensa produce Word Track Changes or redlines?

Recensa produces redline-style and annotated review outputs you can read alongside the Issue Ledger, but it does not generate native Word Track Changes. You apply changes in your own editor after reviewing them.

Run a Document Check

Upload a finished DOCX or PDF, review the issue ledger, and export proof before the document moves.

Run a Document Check

Last updated 2026-05-14