XDocs for Legal
Contract redlining, playbooks and e-signatures for legal teams, in one document
Suggesting mode, word-by-word version comparison and a playbook of standing positions — with an audit trail and integrity digests on everything that gets signed.
- Returned Word files reconciled against what you sent
- Deletions flagged even when the covering note does not mention them
- Every date and duty read out of executed agreements
- An append-only audit trail with timestamp, actor and IP address
How it goes
1
The redline
Attach the .docx the other side returned. Their changes are merged in as tracked suggestions in their name, and each difference becomes a row: clause, before, after.
2
The playbook
Write down the positions you hold — no uncapped liability, and the fallback you can live with — and every returned draft is ranked by how far it strays from them.
3
The record
Sending freezes the document. The certificate of completion carries consent records and two SHA-256 digests that can be recomputed and verified later.
The returned redline, reconciled against what you sent
The other side rarely edits in your tool; they return a Word file with tracked changes and a covering note that mentions some of them. Attach that .docx to the document in XDocs and their changes are merged in as tracked suggestions in their name, exactly where they fall in your text. Each difference becomes a row — clause, before, after — and is classified as cosmetic, material or dangerous, with deletions flagged even when nobody mentioned them. Accept or reject from a review queue, or write back. The document never leaves the editor, so there is no version on somebody's desktop that is the real one.
A playbook that reads every draft for you
Write down the positions you hold — no uncapped liability, a mutual indemnity, governing law at home — and the fallback you can live with on each. Every returned draft is scored against that playbook and the departures are listed first, with the clause that triggered them. A ledger of concessions by round records what was given and when, so the fourth turn of a negotiation starts from a page rather than from memory. The assistant reads the same playbook: ask it what is unusual in an incoming agreement and it cites the clause, and it drafts a counter in the house wording with your approval before anything is written.
Version comparison that is the actual text, word by word
Version history snapshots as you work, and any two versions are compared word by word rather than paragraph by paragraph, which is the difference between seeing that a definition changed and seeing which word in it did. Suggesting mode turns every edit by every party into a proposal with an author and a timestamp. Comments thread with @-mentions and mail. A document with a contents block, numbered footnotes, defined-terms checking and running headers prints like a contract should, to PDF or back to Word for the counterparty who insists.
A signed record you can defend
Sending freezes the document: what the signer saw is a snapshot, not the live draft, and no later edit can touch it. Consent to transact electronically is recorded before any field accepts input, as ESIGN and UETA require. The certificate of completion carries the signers, timestamps, IP addresses, the consent records and two SHA-256 digests — one for the document, one for the certificate — which anybody can recompute and verify years later. The audit trail is append-only. Four roles, SAML single sign-on and SCIM provisioning on the Business plan keep the workspace itself in order. What XDocs does not yet offer is eIDAS advanced or qualified signatures; if a matter needs them, say so and we will tell you honestly.
The parts you will use most
One place for every important document.
Create, sign, share and understand your documents with XDocs.