RecensaRecensa home
Recensa

Source-grounded edits

Source-grounded edits mode generates proposed edits and a corrected text path for Word (DOCX) workflows; PDF inputs follow the same assurance pipeline with export paths aligned to your verification steps. You still need to verify before filing, publishing, or signing.

Last updated 2026-05-14

At a glance

How this fits your process

  • Use this when

    You have reviewed findings and want selected issues turned into proposed edits or corrected outputs.

  • Output

    Traceable change packages and corrected outputs you verify.

  • You verify

    Yes, always—before filing, publishing, or signing.

  • Related

    Proof Report mode, Do-not-change locks, Source checks.

How it runs

Apply Fixes workflow

How to use

  1. 01

    Run Document Check

    Finished DOCX or PDF

  2. 02

    Review issue ledger

    Triage before edits

  3. 03

    Select findings to fix

    Choose what to act on

  4. 04

    Generate proposed edits or corrected output

    When plan allows

  5. 05

    Verify manually

    Inspect every package

  6. 06

    Export or save as new file

    Where supported

Details

Learn more

What Apply Fixes doesChange packages after review—not blank-page generation.

Apply Fixes turns selected issue-ledger findings into proposed edits, corrected outputs, or traceable change packages when your plan allows. It follows review—not a silent rewrite of the whole file.

Source-grounded edits (technical)Supporting language for Word/DOCX and evidence-aware corrections.

In product documentation and exports you may see source-grounded edits—the technical name for traceable edit packages grounded in your document and attached evidence. Customer-facing workflow name: Apply Fixes. Availability depends on plan and policy; confirm entitlements in-app and see pricing.

When teams use itRepeatable cleanups after a structured proof pass.
  • High-volume internal docs with clear style guides.
  • Teams that already review machine suggestions as a normal QC gate.
Limits and manual verificationPlan limits, layout constraints, and mandatory your verification.
  • Availability depends on plan and organizational policy.
  • You still need to verify—no silent approval.
  • Complex layout-heavy DOCX or PDF may not map every edit location one-to-one.
  • Numbers, party names, dates, and cross references need manual verification.
  • Meaning-changing suggestions can look locally correct—professional judgment still applies.

Run a Document Check

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

Run a Document Check