docs.fusial

Uploading a counterparty's redlined version

When the other side sends back a marked-up .docx, upload it as a new version of the same contract — not a new contract.

When the counterparty sends back a tracked-changes .docx, the goal is to keep the negotiation history connected. That means uploading the new file as a new version of the existing contract, not as a brand-new record.

Where to upload

From the existing contract page:

  1. Click New contract from the contract header (or from the version history panel, or Attach contract in the counterparty overview).
  2. Drop in the .docx you got back from the counterparty.
  3. Confirm.

Fusial assigns the next version number automatically. Using the dashboard's main Upload contract button instead would create a separate contract unlinked from the negotiation history, so upload incoming redlined files from the existing contract page.

What Fusial does on upload

  1. Validate and parse the incoming .docx.
  2. Match paragraph anchors against the previous version. Where Fusial recognizes a paragraph, it carries the same anchor forward so AI outputs stay attached. Where the counterparty inserted a new paragraph, a new anchor is generated.
  3. Extract counterparty tracked changes as decidable incoming edits, grouped by paragraph.
  4. Mark the new upload as the contract's current version, while preserving every prior version in history.

The AI briefing isn't regenerated automatically on a new version — re-run analysis from the contract page to refresh the summary, key terms, and section outline against the new text. See Running AI analysis.

What happens next is covered in How Fusial analyzes their changes.

Version history

Every contract keeps an ordered list of versions. After an incoming-redlines upload you'll see something like:

VersionSourceAuthor
v1UploadYour team
v2ExportYour team
v3UploadCounterparty

Each row links to that version's .docx.

Common issues

  • The counterparty sent a clean copy. If they accepted your redlines and removed the tracked-changes marks, Fusial still ingests the file but there are no incoming edits to decide.
  • They renamed the file or restructured headings. Anchor matching is resilient to renames and most reordering. If a section is moved, Fusial reattaches outputs where it can.
  • They sent a .pdf or different format. Convert to .docx first — Fusial ingests .docx files only.

Related

How Fusial analyzes their changes
What gets surfaced once the incoming version is parsed.
Deciding what to accept, reject, or counter
Walk through each counterparty edit and decide your response.