Exporting your contract

Once you've decided every redline and every incoming edit, you can export the contract. Fusial recompiles a fresh .docx with all your accepted edits applied and adds it as a new version to the contract's history.

How to export

1. Open the contract.
2. Click Export final in the editor footer.
3. Confirm.

Fusial produces one .docx with all accepted edits applied. The exported file becomes a new version in the contract's history; you can download it from there.

What's included

The exported .docx contains:

• The original document body with accepted AI redline edits applied.
• Accepted counterparty tracked changes from the latest version.
• Accepted counter-proposals you sent in response to incoming edits, attributed to "Fusial" as the author.

Rejected edits are omitted, and the exported file is a clean .docx with tracked-change marks removed from the edits Fusial applied.

Exporting with pending edits

By default, export expects every redline and every incoming edit to be decided. The editor footer tells you how many edits are still pending — including pending incoming edits and deferred AI suggestions — so you know exactly what's left.

You can still export before reaching zero. When pending edits remain:

• The Export final button stays available.
• Fusial recompiles the .docx with all decided edits applied. Pending edits are skipped — they're not included in the exported file at all. They stay attached to the original version inside Fusial so you can decide them later.
• The new version is stamped with how many pending edits were skipped, and the skip count is recorded in the audit log.

Use this when you want to ship a partial draft right now and finish the remaining decisions in Fusial afterward. The pending edits don't travel with the file, so the counterparty won't see them.

Versioning

Every export creates a new version on the contract:

• The version number is auto-incremented (e.g., a v1 contract exports as v2, v2 exports as v3, and so on).
• The filename is auto-generated from the source (e.g., MyContract (export).docx).
• The new version is linked back to the version it was exported from, so the history stays connected.

You can re-download any past export from the version history or the editor.

Attribution

Inside the exported .docx:

• AI redline edits you accepted are attributed to the user who accepted them.
• Counter-proposals are attributed to "Fusial".
• Counterparty edits you accepted keep their original counterparty attribution.

After export

Send the new version to the counterparty as your reply. When they send back their response, upload it as a new version of the same contract so the negotiation history stays connected.

Related