GitLaw How-To guides
Import a Word or PDF contract
To import contracts into GitLaw, click Files in the main menu, select Upload files, and choose one or more DOCX or PDF files from your device, or use Add from Google Drive. GitLaw stores the originals exactly as they are, automatically extracts parties, status, category, key dates and governing law, and only converts a file to its editable format when you open it to make changes.
Before you start: a GitLaw account, and your contracts as DOCX or PDF files (or in Google Drive).
How do I import contracts into GitLaw?
If your contracts live in a folder of Word documents or PDFs, you can bring them into GitLaw all at once:
- Open the upload panel: in the main menu, click Files, then select Upload files. You can also upload during onboarding; GitLaw offers this step after you complete your profile, and you can skip it and come back at any time.
- Select your files: choose one or more DOCX or PDF files from your device, or use Add from Google Drive (up to 20 files per batch). Processing is limited by your monthly allowance. If a batch would exceed your remaining allowance, GitLaw processes files in order and holds the rest with a clear message.
- Watch extraction run: after upload completes, GitLaw routes you to Files → Overview, which fills in progressively as each file finishes.
- Review extracted details: click any file to open its detail view. You will see the extracted fields as chips at the top and a summary below. Fields that could not be extracted with confidence are flagged for your attention, and you can edit any field inline.
GitLaw accepts DOCX and PDF files from your device. Add from Google Drive additionally accepts native Google Docs, TXT, MD and HTML, up to 20 files per batch. DOCX files with tracked changes and comments are supported: revision marks and comments, including author and timestamp, are preserved on import.
What GitLaw extracts automatically
Extraction runs on the original file; no conversion is needed for GitLaw to read the content.
| Field | Notes |
|---|---|
| Parties | Primary parties become Contacts; other named parties (signatories, witnesses, advisors) stay on the file detail and can be promoted manually |
| Status | Inferred as Draft, Needs review, Pending signature, Signed or Expired |
| Category | Matched against the GitLaw category list (NDA, SaaS Agreement, Employment Contract, etc.) |
| Execution date / Effective date | Captured as distinct fields when both are present |
| Expiry / renewal date | Captured on the file; once the contract is signed it shows as Expiring soon for the 30 days before that date |
| Governing law and courts | Captured when stated |
What gets preserved on import
| Preserved on import | |
|---|---|
| Track changes (inserts, deletes, replacements) | Yes, imported as revision marks; counterparty edits are attributed to a placeholder identity |
| Comments (author, timestamp, anchored range) | Yes, but not reply threads: a thread arrives as one comment and the rest are dropped |
| Headings, tables, lists, numbering | Yes where feasible; lossy cases surface a warning on the file detail |
| Original file format | Yes, your DOCX or PDF is stored as version 1 and remains accessible via version history |
The original file is not converted until you open it to edit. At that point the conversion happens once, and the original is preserved as v1 in version history. If any content cannot round-trip cleanly, a warning appears on the file detail.
What happens after import
- Contacts: each primary party becomes a Contact in Memory → Contacts, deduplicated by name. Click a Contact to see every file, reminder and chat related to them.
- Reminders: GitLaw looks for the dates the contract sets deadlines on, such as renewal and expiry, notice and payment deadlines, reporting obligations, reviews and termination windows, and raises them as reminders on those dates; there is no fixed lead time. It is a best-effort read, so check the result against the contract. Look for the "inferred" tag on auto-created reminders; confirm or edit them to remove it.
- Chat: attach any imported file to a chat session and ask the agent to review, redraft or compare it. See Attach a file to chat.
- Export: once a file is in GitLaw's editor, you can export it as DOCX or PDF. Comments are included in DOCX exports only. See Export your document.
Merging files manually
If GitLaw does not automatically detect that two files are versions of the same contract, for example because the filenames are very different, you can merge them via chat. Open a chat, attach both files, and tell the agent, for example "This is the same contract as the Acme MSA from last month". The agent will propose the merge for your confirmation.
Frequently asked questions
Does importing change my original file?
No. The original DOCX or PDF is stored as version 1 and is not converted until you open it to edit. The conversion then happens once, with the original preserved in version history.
Are tracked changes and comments preserved on import?
Yes, with one exception. Revision marks and comments, including author and timestamp, are preserved from DOCX files, but comment reply threads are not: a thread arrives as one comment and the replies are dropped.
How many files can I upload at once?
Processing is limited by your monthly allowance, and Google Drive imports take up to 20 files per batch. If a batch exceeds your remaining allowance, GitLaw processes files in order and holds the rest with a clear message.
Related articles
- How to add a new file to GitLaw
- Review a document using Agent
- Attach a file to chat
- Export your document
Reviewed by the GitLaw team. Last updated 29 July 2026.