The Overview tab is the transaction's single source of truth. Its centerpiece, the Transaction Record card, holds the facts LetterScript extracted from your documents — the full transaction sheet a coordinator would otherwise build by hand: address, APN, sale price, list price, the deposit structure (earnest money, increased deposit, seller credits), financing type, buyer's broker compensation, who pays which closing costs (escrow fee, title policy, transfer taxes, the Natural Hazard Disclosure report, home warranty), escrow holder and file number, HOA and occupancy status, key dates, and highlights.
It fills itself in
You don't type these fields. A brand-new transaction shows a single prompt in their place — click Upload documents right there to add the first files. As each uploaded document finishes Analyzing, its facts merge into the record:
- The purchase agreement anchors most of it — price, parties, contingency periods, cost allocations.
- Counter offers supersede the original terms they amend; the record always reflects the finally-agreed numbers and dates.
- Later documents enrich and cross-check what's already there. The more of the file you upload, the firmer the record gets.
Every value traces back to a document
No fact in the record is just asserted — each one remembers where it was read. Values that carry a source are underlined; click one to see it in context.
- Most values open the document at the exact spot, with the value highlighted on the page.
- Some values open the document alongside the assistant instead — the document on the left, the assistant on the right — with the question already written for you. Press Enter to run it, or reword it first.
The second case is deliberate, and worth understanding. Some facts are a conclusion rather than a phrase the document prints. A purchase agreement saying "the Property is within the Stonelake Master Association" establishes that there's an HOA — but the word "yes" appears nowhere on the page, so there's nothing honest to highlight. Rather than drop you at the top of a 20-page contract to hunt for it, LetterScript puts the document and the assistant side by side and hands it the question. The assistant has to ground its answer in the text, so the reply comes back with citations — and clicking one scrolls the document beside it straight to the passage it quoted. You end up looking at the wording that backs the value, which is what the highlight would have shown you if we'd been able to find it.
The same happens for who pays which cost (the answer is a checked box, not the words "Buyer" or "Seller"), occupancy, sale type, and for anything we couldn't pin down — a scanned page with no searchable text, for instance.
A value a person set carries a badge instead of a source link, and the same two words are used everywhere in the app — the record card, the Parties roster, the milestones editor, the disclosure checklist:
- Edited — someone changed a value the engine had produced. Hovering it names who and when ("Edited by Dana Reyes · Aug 27"), and the small revert arrow beside it puts the document's value back.
- Added — someone created a value the engine never had. There's nothing to revert to, so no arrow; remove the value instead.
Attribution matters the moment a transaction is shared: the badge says which person, not just "you". On the Parties roster, where hand-set and extracted rows sit side by side, extracted ones carry the counterpart From documents badge, so an unmarked row never has to carry meaning on its own.
It follows the data across the tabs
The same click-through sits on the Overview's Parties and Milestones sections, and on the People tab. Because those rows are editable fields rather than plain text, the citation is a small document icon at the end of the row — click it for the same two outcomes: the page with the value highlighted, or the document opened side by side with the assistant.
A person shows the same citation whether you look at them in the Overview's Parties list or on the People tab — it's the same answer to the same question, so it doesn't change with the view.
The Workflow tab traces back a little differently, because its rows aren't values read off a page — they're things documents did. See Deadlines and the timeline.
A row shows the icon only when we can point at something honestly:
- Parties — the roles the record resolves as a fact of the transaction (buyer, seller, owner of record, lender, escrow holder, title company, tenant), and only when the cited wording actually names that person. Agents and transaction coordinators aren't record fields, so they carry no icon. Neither does an escrow officer whose name doesn't appear in the escrow company's citation — pointing you at the wrong line would be worse than pointing nowhere.
- Milestones — the ✨ auto-derived dates. Dates you typed yourself have no document behind them, and neither does a date whose underlying record field you corrected: the icon goes away entirely rather than falling back to "somewhere in this document". The deadline now follows your value, so pointing at the page you corrected it away from would be worse than pointing nowhere — and for the same reason, that correction is no longer what ⌘K or the assistant's scope deep-links to.
Parties become contacts
The people on the documents become the transaction's Parties automatically — buyers, sellers, both agents (with brokerage and license number), transaction coordinators, the escrow officer, the loan officer — each with whatever phone and email the paperwork (and, for trusted senders, transaction email) states. Extraction only ever fills blanks: a party you typed or edited yourself is never renamed or overwritten, and details found later just complete the card. These contacts are what the email composer suggestions, recipient groups, and automated drafts all draw from. Milestone reminders don't — those come to you, the transaction owner.
Auto-derived dates get flagged
Some deadlines aren't stated outright in a document — they're calculated from the contract (a contingency that runs a set number of days from acceptance, for example). LetterScript marks these so you can give them a second look:
- On the Workflow tab, an auto-derived deadline carries an amber date needs review note — worth a glance, especially right after a new counter offer lands.
- In the milestones editor, an auto-added date shows a small green sparkle icon; hover it to see what it was derived from (Auto-added · …).
Dates you set or confirm yourself carry no flag. See Deadlines and the timeline for how the dates are derived.
When a document contradicts itself
A conflict marker means two documents disagree, and you pick which one is right. A blue check source badge means something different: nothing is contradicting the document — the document is contradicting itself, or LetterScript's two readings of it disagree. There's no rival document to choose, so the badge explains what happened and offers the readings side by side. Hover it for the short version; the matching entry below the record spells it out in full.
Three things raise it:
- Pages that don't read alike. A scanned or flattened form can OCR one page differently from the rest — sixteen pages reading "5001 Cribari Vale" and one reading "5001 Cribart Vale". LetterScript takes the reading on the majority of pages and tells you which pages backed it, with the other reading listed beneath. It only does this when the majority is unambiguous; a genuine two-way split is left alone.
- A percentage that can't be right. A signed PDF sometimes renders "3.000 %" into text that reads as "3,000 %". A buyer's broker compensation of 3,000% of the purchase price isn't a term any contract means, so it's read as 3% and flagged. When the figure can't be explained that way, it's left exactly as extracted and flagged anyway.
- The record and the summary disagreeing. Two passes read your documents — one builds the Transaction Record, the other the plain-language deal summary. When they land on different answers for the same fact, you see it here instead of finding the two surfaces quietly saying different things.
Every one of these is a prompt to look, not a verdict. Open the source document from the field's citation, then Use this to adopt a reading, the pencil to type your own, or Accept as-is to dismiss the flag. Whatever you set by hand wins and carries the Edited marker from then on.
If something looks wrong
A wrong or missing field usually traces back to the documents: the anchoring contract isn't uploaded yet, is still processing, or a newer counter offer hasn't been added. Start with Extraction didn't fill in.