Uploading a contract

A contract enters Fusial when you upload its .docx file. From there, every review and export hangs off that contract record.

What you can upload

• .docx files only. Convert older .doc, .pdf, or scanned files first.
• Files with tracked changes are supported and recommended — Fusial reads them as decidable edits rather than baking them into the text.

How to upload

From your dashboard:

1. Click Upload contract, or drag a .docx onto the dashboard.
2. Pick the file and confirm.

If the file fails validation — wrong format, corrupted DOCX, or unsupported XML — Fusial shows the reason inline and no contract is created.

What happens during upload

Behind the scenes, every upload runs through the same pipeline:

1. Validate the file as a real, well-formed .docx.
2. Anchor every paragraph with a stable ID. The same ID survives re-parses and is what AI outputs cite back to.
3. Store the original in durable storage. Fusial never overwrites the original; new exports are saved as new versions.
4. Parse paragraphs, runs, and tracked changes into structured data.

When the upload finishes you land on the contract page with the contract overview, ready for you to run AI analysis.

Duplicate detection

Fusial fingerprints every uploaded file and checks it against the versions already stored in your organization. If you try to upload the same .docx twice — same bytes, same content — Fusial shows a Possible duplicate document warning that tells you which contract and version already contains that file.

You can then:

• Cancel to back out of the upload — the warning tells you which contract and version number to open if you want to find the existing copy, or
• Click Upload anyway to add it as a new contract or version anyway — useful when the byte-identical document genuinely belongs in two places (e.g., the same template used on two unrelated deals).

Duplicate detection is scoped to your organization and ignores deleted contracts. It catches both the original file you uploaded and any identical file Fusial exported from another contract.

What to do next

From the contract overview, click Run AI analysis to produce the summary, key terms, section outline, and the parsed list of tracked changes you'll review. See Running AI analysis.

Tips

• Upload the version you want to mark up. The first upload is the baseline the rest of the workflow tracks against.
• Don't re-upload to "fix" a contract. Use the New contract action on the contract page so version history stays connected.

Related