Add contract redlining to your application.

Create tracked DOCX changes, let reviewers accept or reject them, and export a Word document. Use browser or Node.js APIs.

You supply the review policy and approval workflow. DOCX Editor supplies document editing and revision APIs.

Try the contract redlining demo

Review a nondisclosure agreement (NDA) with a scripted assistant. Apply suggestions, accept or reject tracked changes, and export to Word.

Contract redlining demo showing an NDA beside a review assistantOpen the contract redlining demo →

Choose an integration

Use the same revision model for an interactive review interface or a background document job.

Contract redlining integration options
Your taskIntegrationImplementation
Review in your applicationBrowser editor, Pro review module, and browser editing APISave through the browser editor.
Generate redlines in a jobNode.js editing API and core engineCall runtime.save() and store the returned bytes.
Apply an agent proposalYour model, proposal validation, and either runtimeApply a validated edit with tracking enabled.

For installation instructions, see Runtime and setup.

Implementation guides

Check DOCX compatibility

Check feature support and try the DOCX samples in the editor.

Reopen exported files in Word to check tracked changes and formatting.

DOCX compatibility and samples

Understand the limits

  • Set an explicit author and TrackMineOnly. The runtime starts with tracking off. TrackAll is unsupported.
  • Browser tracked writes require the Pro review module on an editable editor. Runtime tracking and UI tracking are separate settings.
  • Tracked ranges cannot cross table or structured document boundaries, such as content controls. Collaborative tracked replacements must stay within one paragraph.
  • Collaboration restricts edits around another author’s pending changes. Check the supported operation before applying it.
  • Revalidate stale proposals and reject ambiguous targets. Your application owns authorization, approval, and retention rules.

For supported operations and refusal conditions, see Tracked changes.

Evaluate with your documents

Start with a representative contract and define the review decisions your application needs.

  1. Create one tracked replacement with an explicit author.
  2. Test accepted, rejected, and pending changes in the same document.
  3. Export the file and reopen it in your target Word version.
  4. Check revision authors, tables, numbering, headers, and formatting.

The base editor uses Apache-2.0. Pro review features and the editing API use the EigenPal Pro License.

You can evaluate the commercial packages for free. Production use requires a commercial agreement.