Lease extraction for rent-roll and renewal review

A lease opens with the parties and property, then term and rent, then the clause sections. Here is how to read the parts that matter.

What a Lease looks like

Lease — sample layoutannotated

Landlord & tenant names

The parties bound by the agreement.

Property address

The specific unit or premises being leased.

Lease start & end dates

The term of the tenancy and when it renews or expires.

Monthly rent

The recurring amount due and the day of the month it is owed.

Security deposit

The refundable amount held against damage or unpaid rent.

Key clauses

Renewal, termination, late fees, pets, maintenance, and other terms that govern the tenancy.

Illustrative layout for education. A real lease may vary by issuer.

Evaluate this workflow

For property-management operations

Capture the base lease terms while retaining amendments and unresolved clauses for review.

Check before you accept a record

Compare tenant names and unit with the property record.
Keep start date, end date, monthly rent, and deposits separate.
Check amendments and renewal language before scheduling a deadline.
The returned address may include the unit. Do not infer a separate unit field without checking the source.

An exception to hold for review

A null renewal term is unresolved, not proof that the lease cannot renew. Inspect the clause and any amendment.

Run a small evaluation

Collect the lease and relevant amendments.
Extract terms and compare them with the source.
Update the rent roll only after resolving discrepancies.

Record the number of files submitted, failed files, required-field corrections, and minutes spent reviewing each file. Those observations tell you whether this workflow fits your documents; a sample response does not measure extraction accuracy.

Download synthetic JSON and review checklist Evaluate your first 3 documents

Example reviewed September 16, 2026 against the configured field names. Fictional values, partial field set, and a suggested human workflow; not a recorded extraction or a promise of automatic approval.

A measured synthetic extraction

On September 16, 2026 Pacific time, we sent one labeled text PDF for this document type to our production extraction service. It returned HTTP 200 in 4.53 seconds, including network time. This was a backend request, not a test of signup, payment or the complete upload interface.

2 selected field comparisons differed after the production field mapping. Successful delivery does not establish extraction accuracy.

Inspect the field differences

[
  {
    "path": "property_address",
    "expected": "Fictional sample property",
    "actual": "Fictional sample property, Unit A",
    "actualMissing": false
  },
  {
    "path": "unit_number",
    "expected": "A",
    "actual": null,
    "actualMissing": true
  }
]

Expected values were fixed before the run. Comparison uses exact values and types, checks the expected object fields and requires exact array lengths. A numeric string differs from a number; missing and null values differ. These easy, clearly labeled synthetic pages do not represent scanned documents, complex official forms or customer accuracy. One observation cannot establish typical latency.

Field contract correction

We replayed the same recorded response after correcting field aliases, declared tax-number types and bank last-four handling. This is an offline replay, not another extraction request. 2 selected field comparisons still differ from the original expected sample. The original benchmark stays available; unsupported distinctions and source wording are not invented to make the comparison pass.

Inspect the corrected mapping results

Download the 15-page synthetic input packet Download expected and returned fields

Illustrative structured output

These synthetic values explain the field layout; they are not a measured extraction result or an accuracy benchmark. Actual coverage depends on your document.

{
  "landlord_name": "Example Property Company (fictional)",
  "tenant_names": [
    "Sample Tenant"
  ],
  "property_address": "Fictional sample property, Unit A",
  "lease_start_date": "2026-01-01",
  "lease_end_date": "2026-12-31",
  "monthly_rent": 1800,
  "security_deposit": 1800,
  "renewal_terms": null
}

Try the interactive sample without signup Review CSV, Excel, and JSON exports See the extraction API

Extract from your own lease — 3 free, no credit card

Want the Lease extraction guide?

Get a free step-by-step guide to extracting and reviewing data from Leases — plus tips for recurring workflows.

Free. No credit card. Unsubscribe anytime.

FAQ

What does a Lease look like?

A lease opens with the parties and property, then term and rent, then the clause sections. Here is how to read the parts that matter. The annotated example above shows each region and what it contains.

Can I use this Lease sample as a template?

Use it to understand the layout and fields. When you need the actual data off a real lease, upload it and get structured JSON/CSV back — no manual typing.

What is the difference between a lease and a rental agreement?

A lease fixes a term (often 12 months); a rental agreement typically renews month-to-month.

What key dates should I track from a lease?

Start and end dates, the renewal-notice deadline, and rent-due dates are the ones that carry consequences.

This page shows an illustrative Lease example for educational purposes and is not tax, legal, or financial advice.