# Copy deal terms to a new document Help Center | LeasePilot [Help index](/resources/help#step-throughs)07 · Automate Step-through # Copy deal terms to a new document Inherit the deal terms from an existing document when creating a related one, instead of re-typing them. Workflow Automate Format Interactive demo Read time 2 min Interactive demo loading Fig. 01Copy deal terms to a new document When a tenant signs a lease, the same deal terms show up across half a dozen related documents: amendments, SNDAs, estoppels, commencement letters, subleases. Every one of those starts with the same underlying facts: tenant name, premise area, term, rent schedule. Re-typing those facts into each new draft is busywork, and it's the kind of busywork that quietly creates inconsistency. A typo in the rent number on the SNDA that doesn't match the master, and now two documents disagree about the same deal. LeasePilot copies the deal terms over for you. Start a new document from an existing one, and the structured terms come with it. ## 01How it works From the actions menu of any existing document, start a new draft. The **Create New Document** dialog asks for what changes between the two: **Document Type**, **Form**, **Templates Version**, **Asset**, **Tenant**. At the bottom is a checkbox: > Note☑ Copy Deal Terms from \_Tenant Name — Address (Version 1.0)\_ Leave it checked and the new document is created with the deal-terms panel pre-populated from the source. Uncheck it if you want a clean slate. ## 02What gets copied, and what doesn't This is a \_deal terms\_ copy, not a document copy. Specifically: - **Copied:** the structured values in the deal-terms panel — tenant, dates, rent schedule, options, restrictions, and so on, exactly as they were filled in on the source. - **Not copied:** anything from the body of the source document. No text edits, no redlines, no comments, no version history, no conformed status. The new document uses its own form and template; only the terms travel. So when you create an SNDA off a master lease, the SNDA's body comes from the SNDA form, not from the lease. The deal-terms panel just arrives populated, ready for you to adjust the few fields that differ for that particular SNDA. > Note**Copy, not sync.** The deal terms are inherited at the moment the new document is created. Changes to the source after that point don't propagate. Each document, once it exists, keeps its own deal terms. * * * For the deal-terms panel itself, see [deal terms](/resources/help/demos/deal-terms). For the most common related-document case (amendments off a master lease), see [amendments](/resources/help/demos/amendments). For populating deal terms from an outside source like an LOI or term sheet, see [import deal terms](/resources/help/demos/import-deal-terms). See also ## Adjacent step-throughs [Full index](/resources/help#step-throughs) 1. 01 Amendments overview How amendments inherit data from the original lease. Forthcoming 2. [02 Deal terms Fill structured fields on the right; the document on the left re-writes itself. Draft](/resources/help/demos/deal-terms) 3. [03 Import deal terms Upload an LOI or term sheet; LeasePilot reads it, applies the terms it finds, and asks you to confirm each one. Extract](/resources/help/demos/import-deal-terms) 4. [04 Autopilot A chat panel inside the document for drafting suggestions, revisions, risk callouts, and quick questions. Automate](/resources/help/demos/autopilot-intro) 5. [05 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) 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)