---
name: lease-abstract
description: Turns a lease or property agreement and its amendments into a standardized abstract with key dates, financial terms, obligations, and exceptions. Use for lease abstraction, rent-roll preparation, tenancy data capture, property contract summaries, or portfolio review.
license: Apache-2.0
metadata:
  adlass.categories: "legal-compliance/contract-lifecycle, data-tables/cleanup-normalization"
  adlass.industries: "real-estate"
  adlass.tags: "lease, abstraction, rent, property, contract"
  adlass.adaptation: "mapping"
  adlass.source: "n8n:R-01"
  adlass.version: "1"
---

# Lease abstract

## Purpose

Convert a lease file into a consistent record that property and finance teams can use without rereading the agreement.

## Scope

Commercial, residential, and mixed-use leases or operating agreements, including amendments and side letters. **Excluded:** legal advice, enforceability opinions, and negotiation of lease terms.

## Data basis

- Lease, amendments, side letters, object record, and the company abstract schema.
- The fixed records, tables, or folders in the skill scope that hold the relevant history or schema.

## Result

A lease abstract document and a structured row containing parties, premises, dates, rent mechanics, options, security, cost obligations, and unusual rights.

## Quality criteria

- Every extracted term cites its document and page or section.
- Amendments override earlier terms only where the amendment clearly does so.
- Unknown or conflicting values remain visible as open points.
- The structured row and narrative abstract contain the same key values.

## Instructions

Read amendments in chronological order and state which version controls each changed term. Preserve contractual wording for dates, formulas, notice periods, and options before normalizing values. Distinguish fixed rent, variable charges, incentives, deposits, and pass-through costs. Never infer a missing date or amount. Use the company schema when present; otherwise use the output fields defined in the steps.

## Adapt before use

Keep the source trail close to every conclusion and preserve the difference between a source fact, a calculated value, an assumption, and a recommendation. Use stable identifiers across the document and sheet so a reviewer can move from a summary statement to the underlying row and source. Prefer a complete, transparent partial result over a confident answer built on missing evidence.

- Add the company abstract schema and required record fields.
- Define the currency, area, date, and rent-period conventions used in records.
- Specify which lease obligations property teams want tracked after abstraction.
- Add the company policy for escalation of ambiguous or conflicting amendments.