Every document.
Organised, handled, signed.

PDF, DOCX, and image files all upload natively. PDF for finalised documents that should not be edited further. DOCX for contracts the team or counterparty may still modify. Image files for scanned originals, signed paper documents, or any visual contract. No conversion required and no preprocessing needed, the document works as expected from the moment it uploads.

Drag up to 20 files into the upload area at once and they import together. Each file lands in the current folder, gets indexed for search, and becomes available for the next workflow step. The team can apply the same template, validity window, or routing to the whole batch, or treat each document individually after upload. Twenty file ceiling per single upload action, no limit on total library size.

Save any standard contract type as a reusable template, then generate new instances from it in seconds. The template captures the document structure, default routing, validity rules, and any custom fields. New instances inherit everything from the template and only require the specifics for this particular contract. Templates can be shared across the team or kept private to specific roles depending on operational needs.

Folders nest as deep as the team's structure requires. Common patterns include client folders inside an account folder, year folders inside each client, document type folders inside each year. Any depth is supported. The team configures the structure that matches their actual operational organisation rather than fitting their workflow into a flat list or a rigid two level hierarchy.

Document Management is the foundation. Every other Sigi feature builds on top. Signing Workflows handles how the document gets signed. Risk Analysis and Clause Intelligence run on uploaded documents. Expiration Reminders fire against validity windows configured here. Stalled Signer Alerts trigger when signers behave a certain way on these documents. All of it layers over the document management foundation.

Every detail needed for audit purposes. Each signer's name, email, signing timestamp, IP address at time of signing. The signing flow type and the order signers completed. Document version hash for tamper detection. Any acknowledgements or additional inputs captured during signing. The full audit trail attached to the signed document means audits don't require separate report generation, the evidence is already there.