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, or drop files & folders straight in.
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.
- A batch can hold up to 25 files per upload — if you pick more, upload the extras in another round (see Plans and usage).
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.
- 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 hit one of its included limits (pages left, or the AI processing included with the free transaction). 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.
Packets: several forms in one file
Disclosure packets 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 packet 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.
Folders are organization only: extraction, the disclosure checklist, and deadlines always work across the whole transaction no matter where a document is filed.
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.
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.