RecensaRecensa home
Recensa

Do-not-change locks

Tell reviewers which wording, parties, or figures must not be altered during the proof pass. Recensa passes that intent into reviewer context to reduce accidental edits while still flagging surrounding risks.

Last updated 2026-05-14

At a glance

How this fits your process

  • Use this when

    Specific names, terms, or figures must stay verbatim during review.

  • Output

    Reviewer context that respects lock boundaries on flagged spans.

  • You verify

    Yes—locks are guardrails, not formal verification.

  • Related

    Apply Fixes, Proof Report mode, Contract redlining.

How it runs

Do-not-change locks workflow

How to use

  1. 01

    List locks

    Names, terms, figures

  2. 02

    Run Document Check

    Reviewers respect bounds

  3. 03

    Review nearby wording

    Adjacent edits still matter

  4. 04

    Apply Fixes selectively

    When plan allows

  5. 05

    Sign off

    You approve

Details

Learn more

Why locks existReduce accidental party renames and numeric edits.

The fastest way to lose trust in automated review is an accidental party rename or a small numeric edit. Locks make non-negotiable strings explicit so attention goes where you want discretion.

When it matters mostContracts and regulated boilerplate.
  • Deal documents with sensitive proper nouns and financial figures.
  • Boilerplate that must remain character-stable while surrounding prose improves.
Limits and manual verificationAdjacent wording and incomplete lock lists.
  • Adjacent wording may still change in ways that affect meaning near a locked span.
  • Missing a lock is worse than having too many—verify lists before review.
  • Punctuation around locked spans still needs your read after accepted edits.

Run a Document Check

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

Run a Document Check