# Import deal terms Help Center | LeasePilot [Help index](/resources/help#step-throughs)06 · Extract Step-through # Import deal terms Upload an LOI or term sheet; LeasePilot reads it, applies the terms it finds, and asks you to confirm each one. Workflow Extract Format Interactive demo Read time 2 min Interactive demo loading Fig. 01Import deal terms An LOI's contents are mostly the same deal terms you'd type into the panel by hand: tenant name, premise area, term length, rent schedule, options, restrictions. Re-typing them is busywork. Import Deal Terms uploads the LOI (or term sheet, or a screenshot, or even a photo of a marked-up page), reads what's there, applies what matches, and asks you to confirm each change. ## 01How it works Three steps from upload to draft: 1. i.**Select files.** Word documents (`.docx`), PDFs, and images are all supported. Upload one file or several at once — useful when an LOI's terms are spread across an attached schedule, a side letter, and the body itself. 2. ii.**LeasePilot reads them.** The platform parses each file and looks for deal terms it can map onto the structured fields in your panel. Anything it finds, it applies automatically — so by the time the upload finishes, the deal-terms panel is already populated. 3. iii.**Review and decide.** Every extracted value shows up as a proposed change in the panel. Accept what's right, reject what's wrong (rejection reverts to the previous value), and adjust anything in between. Nothing is final until you say so. ## 02What gets extracted The platform looks for the deal terms your panel actually has. If your panel includes a _Tenant Trade Name_ field, the parser tries to find a tenant name. If it includes _Base Rent — Year 1_, it looks for a year-one rent. Because the schema is built around _your_ forms, the extractor isn't trying to parse a generic lease; it's trying to fill _your_ deal-terms panel. The closer the match, the higher the confidence — terms that don't appear in the upload are simply left as they were. > Note**You're the deciding party.** Every extracted value is a suggestion until you accept it. The review step exists because AI is excellent at parsing prose into structured fields, and imperfect at the judgment calls a drafter makes daily. The platform handles the parsing; the drafter handles the call. * * * For the deal-terms panel itself, see [deal terms](/resources/help/demos/deal-terms). For pulling structured terms _out_ of an executed lease (the same idea in the opposite direction), see [abstract a document](/resources/help/demos/document-abstraction). For deal data that arrives from a property-management or CRM system instead of a document, see [connected systems](/resources/help/demos/connected-systems). See also ## Adjacent step-throughs [Full index](/resources/help#step-throughs) 1. [01 Deal terms Fill structured fields on the right; the document on the left re-writes itself. Draft](/resources/help/demos/deal-terms) 2. [02 Abstract a document Generate a Word abstract from a LeasePilot draft or an uploaded executed lease. Extract](/resources/help/demos/document-abstraction) 3. [03 Autopilot A chat panel inside the document for drafting suggestions, revisions, risk callouts, and quick questions. Automate](/resources/help/demos/autopilot-intro) 4. [04 Connected systems (Yardi, MRI, and others) Your stack pushes deal data into LeasePilot. LeasePilot pushes structured lease data back out when document statuses change. Both directions, both on your terms. Automate](/resources/help/demos/connected-systems) 5. [05 Reports Build, filter, save, and export structured views of your portfolio data. Extract](/resources/help/demos/reports) Sign-off ## See it on your forms, not a generic demo. A 30-minute walkthrough, built around your forms, your clauses, and your deal logic. [Schedule a demo](/demo)[Already on LeasePilot? Contact your team](/company/contact?type=support)