# Ancillary documents Help Center | LeasePilot

[Help index](/resources/help#step-throughs)03 · Draft

Step-through

# Ancillary documents

SNDAs, commencement letters, estoppels, and any other CRE document run on the same automation as the lease itself.

Workflow

Draft

Format

Reference

Read time

2 min

Walkthrough in production

We’re still drafting this one.

For a live walkthrough on your forms, ask the team that built your platform.

A signed lease isn't the end of the document chain — it's the start of one. Over the life of a tenancy, a single deal generates a string of related documents: an SNDA when the lender shows up, a commencement letter when the tenant takes possession, an estoppel when the building changes hands, a sublease when space gets shared, an assignment when the tenant gets acquired, more amendments than anyone wants to count. Each of those has its own structure, its own counterparties, its own negotiation patterns. Pre-LeasePilot, each one got drafted in Word from someone's most recent precedent, carrying the same risk of stale clauses, inconsistent terms, and version drift that the lease itself used to carry.

In LeasePilot, ancillary documents aren't second-class. They're modeled the same way the lease is.

## 01What counts as ancillary

Anything that isn't the lease itself but lives in the deal's lifecycle:

-   **Commencement letters** confirming the term start, delivery date, and rent commencement.
-   **SNDAs** subordinating the lease to the lender's mortgage.
-   **Estoppels** confirming the lease terms to a buyer, lender, or insurer.
-   **Subleases**, **assignments**, and **consents** to either.
-   **Amendments** of every shape, from a one-line rent reset to a full restatement.
-   **Memorandums of lease**, **terminations**, **side letters**, and anything else CRE-adjacent your firm regularly produces.

The list above is illustrative. The real list is whatever your team has on its precedent shelf.

## 02Same automation, different document

Each ancillary document is built from a form, the same way the lease is. That means each ancillary document gets:

-   **Conditional logic** that opens and closes provisions based on the deal terms.
-   **A structured deal-terms panel** specific to the document type. An SNDA's terms aren't the same as an estoppel's, and the panels reflect that.
-   **Auto-numbering and cross-references** that stay consistent as you edit.
-   **Autopilot** for drafting, revising, querying, and risk-checking the document.
-   **Compare and Import Changes** for negotiation rounds.
-   **The same export, conformed-deal, and abstraction flows** that the lease has.

The intelligence layer doesn't care whether the document in front of you is a 200-page lease or a two-page commencement letter. The form decides what's there; the platform applies the same rigor to either.

> Note**Any CRE document type can be onboarded.** If your firm produces it, the implementation team can model it. New ancillary forms get built the same way the lease form was: working from your precedent, your structure, your language.

* * *

When you spin up an ancillary document off a deal that already exists in LeasePilot, the related deal terms come along automatically. See [Copy deal terms to a new document](/resources/help/demos/data-sync) for that mechanic, [Amendments](/resources/help/demos/amendments) for the most common ancillary case, and [Forms](/resources/help/demos/forms) for how each document type is built.

See also

## Adjacent step-throughs

[Full index](/resources/help#step-throughs)

1.  [01
    
    Forms
    
    Your form templates and conformed deals — every starting point for a new draft, on one screen.
    
    Admin](/resources/help/demos/forms)
2.  02
    
    Amendments overview
    
    How amendments inherit data from the original lease.
    
    Forthcoming
    
3.  [03
    
    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)
4.  04
    
    Add a co-tenancy provision
    
    Add an opening or ongoing co-tenancy provision with triggers and remedies.
    
    Forthcoming
    
5.  05
    
    Add a ROFO or ROFR
    
    Add a right of first offer or right of first refusal for expansion space.
    
    Forthcoming
    

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)