A rich text editor for contracts and legal drafting
Legal work is review work. A draft goes back and forth, every change has to stay visible, and the other side expects a Word file. RichTextEditor puts track changes, comments, clause numbering and Word export inside your own application, on your own servers.
Where it is used
Contract drafting and negotiation
Reviewers suggest edits that stay visible until someone accepts or rejects them, with comments anchored to the clause they discuss.
Clause libraries and templates
Start a document from a template and keep 1, 1.1, 1.1.1 numbering consistent as clauses are added or removed.
Document management and matter systems
A rich text field or a full-page editor inside your existing application, saving to your own storage.
Client-ready output
Export the document to Word for the other party, or to a tagged PDF with selectable text.
Features that matter here
All of these are in every license. Each card links to the documentation, so you can check how it works before you commit.
Track changes with reviewer rules
Word-style suggesting mode. Your application decides who may accept or reject, and each decision records who made it.
Track changes and comments →Clause numbering and page view
Multi-level 1.1.1 numbering, and A4, Letter and Legal pages with headers, footers and page numbers.
Page layout →Revision history
Save named versions, compare two of them line by line, and restore an earlier one.
Collaboration and review →Word import and export
Open a .docx file in the editor and export the result back to .docx, with the tested mappings documented.
Word fidelity →Contract review example
A working example with clause numbering, cross-references, tracked changes and comments together.
Contract review demo →Self-hosted
The editor runs in your application. Documents, uploads and review data stay in the systems you operate.
Self-hosted editor →What the editor does not do for you
We would rather you find the limits here than during an audit.
- This is an editor, not a document management system. Storage, access control, retention and e-signature are your application’s job.
- Word and the browser lay text out differently. Complex Word layouts do not all survive a round trip; the Word fidelity documentation lists what is tested and what is not translated.
- Headers and footers cover the default section only. First-page and even-page variants need a template of your own.
- Confidentiality and professional-conduct obligations depend on how your platform stores and shares documents. The editor sends content nowhere by itself, and the AI tools are off unless you connect a provider.
Evaluation checklist
Round-trip three of your real contracts through Word import and export, and compare them in Word.
Decide who may accept or reject changes, and enforce it on the server as well as in the editor.
Check that clause numbering and cross-references behave as your drafters expect.
Decide whether AI tools are allowed on client documents before you enable them.
For a full evaluation plan, see the evaluation checklist.
Customer stories
We only publish customer stories that the customer has agreed to, and none from this sector is published yet. If you use RichTextEditor in legal, tell us how. We will write it up with you and publish it only after you approve it.
Related
Document editor · Security and procurement · Pricing · Other sectors: Education, Healthcare, Government, CMS and publishing
Try it with your own documents
Perpetual licenses from $129, one-time. Every feature in every license.