Everything downstream — the transaction record, the disclosure checklist, the deadlines — starts with the documents you upload.
Upload
Open the transaction and click Add documents in the header — or go to the Files tab and click Upload documents (next to New folder in the folder bar). In the dialog you can click to browse, drop files, folders and ZIPs straight in, or paste a screenshot with Cmd-V / Ctrl-V — handy for wire instructions or a lender condition you captured rather than downloaded. A pasted image is named for the moment you pasted it, so two screenshots stay two documents.
On a transaction with nothing in it yet you don't even need to switch tabs — the Overview tab shows an Upload documents button that opens the same dialog.
If you're inside a subfolder when you upload, the files land in that subfolder; otherwise they land at the top of the transaction folder.
What's accepted:
- PDFs and images up to 50 MB each — including scanned documents; LetterScript OCRs them.
- CSV / Excel files up to 10 MB each.
- As many files as you like in one go. A long selection — a whole folder, or a ZIP of a full package — uploads automatically in batches, with one progress view. There is nothing to split up and no extras to add afterwards.
- A .zip of documents exported from your forms or e-signature platform — see below.
Click Start Upload (or Upload N files for a batch). You don't have to babysit it — Close — continue in background lets processing finish while you work elsewhere.
What the statuses mean
Each file moves through a short pipeline:
- A progress percentage while the file transfers securely.
- Starting — the file is uploaded and processing is being started. If the server is busy it waits and retries by itself; a file that still can't start right away begins on its own within the hour, so there's no need to upload it again.
- Analyzing — the document is being OCR'd and its facts extracted. Bigger or scanned documents take longer.
- A checkmark when it's done — extracted fields flow into the Transaction record, matching forms tick off the POS disclosure checklist, and dates feed the timeline.
- Held — limit reached — the document wasn't read because your free first transaction used all the AI processing included with it. It's held, not lost; buying a transaction lifts the limit and it processes — and you get another transaction to use.
- Partly read — limit reached — the included AI processing ran out part-way through this file. What was read is kept; buying a transaction has the rest read.
- Failed or Canceled — see Upload problems.
Zipped documents (.zip)
Export the whole set from your forms or e-signature platform as a .zip and drop it in — LetterScript opens it in your browser and adds every supported document inside as its own file. The archive itself is never uploaded; only the documents in it are.
Some entries won't come across, and the dialog now lists each one by name with the reason rather than just counting them:
- Unsupported type — not a document format LetterScript reads (a Word file, a
.msg, a stray.xml). - Over 50 MB / Over 10 MB — that one file is past the per-file cap. Pull it out of the .zip and split or compress it.
- Empty file — a zero-byte entry.
- Suspicious compression — an entry that expands far beyond its stored size; left out as a safety measure.
If the .zip holds more than 200 documents, the first 200 come in and the dialog says so — add the rest in a second round.
Import from Dropbox or Google Drive
Under the drop area, Dropbox and Google Drive import files straight from your cloud without downloading them first. Both now include .zip files, which are expanded the same way a dropped one is. Google Drive shows shared drives as well as My Drive, so a brokerage's transaction folder is reachable.
A cloud import replaces whatever you've already picked in the dialog, so upload your local selection first — the buttons grey out while one is waiting.
Several forms in one file
Disclosures often arrive as one PDF holding many forms. LetterScript reads what's inside, so when a file carries more than one C.A.R. form the document row adds a second line — Contains: AD · RPA · SCO (six codes, then +N for the rest); hover it for the full form titles. Those forms tick the disclosure checklist individually, so one upload can satisfy several required items. You don't need to split a file like that up before uploading it.
Organize with subfolders
The transaction's transaction folder can hold subfolders (nested as deep as you like):
- New folder on the Files tab creates one wherever you're standing; the breadcrumb at the top walks you back out. The folder you're in is in the address bar, so the link you paste to someone opens where you were.
- Move any document by dragging its row onto a folder — or onto a breadcrumb to move it back up — or with ⋮ → Move to… on its row; rename or delete a folder from its ⋯ menu. Deleting a folder never deletes documents — they return to the top of the transaction folder.
- Each folder row also has a chat icon for a folder-scoped assistant — see Ask the transaction assistant.
Two files with the same name in the same place are told apart with a counter: upload, move or attach a second RPA.pdf and it becomes RPA.pdf (1). Names are only compared within one folder of one transaction, so each transaction's own RPA.pdf keeps its plain name however many other transactions have one.
Folders are organization only: extraction, the disclosure checklist, and deadlines always work across the whole transaction no matter where a document is filed.
The document's type
Each finished document's row shows the type LetterScript identified it as, such as Purchase Agreement or Transfer Disclosure Statement; one it couldn't identify reads Set type. Click the type to confirm it or pick another. A type someone picked by hand shows a small person icon on its badge, and hovering it says who set it and when, so it can't be mistaken for LetterScript's own reading. Re-classifying the document from scratch hands the type back to LetterScript.
Download and other row actions
Hover a document row (they're always visible on touch) and you get, at the end of the row:
- a chat icon to ask about just that document,
- a download icon that saves the original file exactly as it was uploaded, and
- a ⋮ menu holding every action for that document — Ask about this document, Open document, Download original, Move to…, and Remove from this transaction.
Downloads are original files, not a rewritten copy — what you get back is the same PDF or image you (or your inbox) put in. Remove from this transaction takes the document out of the transaction and re-runs extraction on what's left. On a transaction someone shared with you, it's offered only on documents you uploaded (see Share a transaction).
Correct the text read from a scanned page
Open a scanned document and click Verify Text to see each page's image beside the text read from it, and correct the text where it's wrong. Clicking into a page holds it for you, so someone else can't edit the same page at the same time. Save Changes saves only the pages you changed.
If someone else saved a change to one of those pages after you opened it, nothing is saved, and the page says so. Use theirs drops your edit and shows their version; Keep mine keeps your text, and your next Save Changes replaces theirs with it.
A page whose text someone corrected says so, with who and when, both in Verify Text and on the page in the document viewer. Revert to the OCR text beside it puts back the text LetterScript originally read from the page, after asking you to confirm, and the page is no longer marked as corrected. Pages corrected before LetterScript started keeping the original text show who corrected them, but have no Revert to the OCR text.
Download every document at once
Download all, in the Files tab's folder bar, saves every document on the transaction as one ZIP named for the property's address — the whole file, ready to hand to escrow or a broker. The same download is All documents (ZIP) in the Send menu in the transaction's header (see Send and share from a transaction). Anyone who can open the transaction can download it, including a collaborator with view-only access, except that a collaborator's ZIP leaves out documents holding a taxpayer ID (see Share a transaction). The ZIP's list of contents names what was left out and why.
The ZIP holds the original files, flat: subfolders aren't recreated inside it, and when two documents share a file name the second is renamed, such as TDS (2).pdf, so neither is lost. A document that's still uploading isn't included. (Emailing a document from the transaction works differently: it goes out under a name made from its type and the property's street, never the name it was uploaded with. See Send and share from a transaction.)
Every ZIP also contains a MANIFEST.txt listing what's in it and anything that isn't, with the reason. After the download, a message says how many documents it holds, or how many couldn't be included and to check MANIFEST.txt for which:
- Archived to cold storage — an older document can be moved to long-term storage, and reading it back takes about 12 hours. Open it once from the Files tab to start the retrieval, then download again once it's back.
- Not found — the file itself couldn't be found in storage.
Two limits keep the download from overwhelming your browser:
- 300 documents. A transaction with more gets a message instead of a ZIP; download its documents from the Files tab.
- 750 MB of documents in all. Past that, the message gives the total; download the largest documents one at a time from the Files tab.
Tips for best results
- Upload the purchase agreement and any counter offers early — they anchor the transaction record and the deadline derivation.
- Whole document sets are fine. You don't need to curate; LetterScript classifies each document itself.