# Autopilot Help Center | LeasePilot [Help index](/resources/help#step-throughs)07 · Automate Step-through # Autopilot A chat panel inside the document for drafting suggestions, revisions, risk callouts, and quick questions. Workflow Automate Format Interactive demo Read time 2 min Interactive demo loading Fig. 01Autopilot Reading a 200-page lease to find a single risk takes hours. Drafting a one-off provision from scratch means hunting for precedent. Most leasing teams have been waiting for AI that actually understands the document in front of it. Autopilot is that surface: a chat panel inside the document where you can draft new language, revise existing language, surface risk in a clause, or ask questions about anything in the file. ## 01What you can do Four ways to start a conversation, all anchored to the document you have open: - **Draft.** Describe the provision you need and any terms or conditions to include. Autopilot returns suggested language you can copy into the draft. - **Revise.** Point at a provision and describe the change you want. Autopilot returns a revised version you can compare against the original and use as a starting point. - **Risk Analysis.** Point at a provision and describe the angle that worries you (assignment risk, indemnity exposure, rent-escalation downside). Autopilot reads the language with that lens and flags what it sees. - **Query.** Ask the document a question. \_Where does the lease address mold?\_ \_What's the cap on operating expense increases in year four?\_ \_Does the assignment clause cover subleases?\_ Useful when the lease is long, you didn't draft it, and you need an answer fast. Once you have what you need, the action stays with you: copy from the chat, paste where it belongs, edit to taste. > Note**Read-only by design.** Autopilot reads the document but doesn't write to it. AI is the right tool for drafting help, alternate language, and risk pattern-matching; it isn't the right tool for unattended edits to a binding legal document. The split is deliberate: AI suggests, you decide, and you're the one who clicks **Insert**. The deterministic side of the document — rent schedules, dates, conditional provisions — stays in [deal terms](/resources/help/demos/deal-terms), where the math is exact every time. * * * For inserting language you've already approved (your firm's curated fallback library), see [Clausebook](/resources/help/demos/clausebook). For pulling structured terms out of an executed lease, see [abstract a document](/resources/help/demos/document-abstraction). See also ## Adjacent step-throughs [Full index](/resources/help#step-throughs) 1. [01 Clausebook Your fallback language, organized inside the document, one click to insert. Draft](/resources/help/demos/clausebook) 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 Abstract a document Generate a Word abstract from a LeasePilot draft or an uploaded executed lease. Extract](/resources/help/demos/document-abstraction) 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 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. Automate](/resources/help/demos/data-sync) 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)