Lease abstract from signed agreements

Use this process to turn a signed commercial lease into an operational abstract that a property team can use for diary dates, charges and day-to-day decisions. It is for property managers and asset managers who need a consistent first draft, with every important term traceable back to the signed documents.

This produces an abstract, not a legal interpretation. Where wording is unclear, conflicting or commercially significant, record the issue and send it to the appointed legal adviser for a decision.

1. Assemble the signed document set

Start with the executed lease, not a circulated draft. Create one review folder and save the documents in a fixed order:

1. Signed lease and all signature pages.
2. Any agreement for lease.
3. Deeds of variation, supplemental deeds and side letters.
4. Licences to alter, assign, underlet or change use, where they alter an ongoing obligation.
5. Plans, schedules, rent review memoranda and any document expressly incorporated into the lease.

Rename each file so its status is clear, for example: 2019 Lease executed, 2023 deed of variation executed, and side letter signed.

Check the parties, property address and dates across the set before extracting any terms. A later variation may replace a clause in the original lease. A side letter may change a payment, break condition or notice procedure without changing the lease text.

If you use the model to work with document text, handle document access according to your organisation's information policy. Document handling and available workflow features can vary, so check the current guidance in the xAI documentation overview.

2. Set up the abstract template first

Use one standard template across the portfolio. Do not ask the model to decide which fields matter from scratch. Give it the fields, the format and the rule that it must say not found rather than infer a value.

Create these sections in the abstract:

Section	Fields to capture	Operational use
Property and parties	premises, plan reference, landlord, tenant, guarantor, permitted use	identifies the asset and responsible parties
Term	lease date, commencement, contractual expiry, term length, rent commencement	establishes the core diary dates
Rent and payments	current annual rent, payment dates, VAT wording, interest, service charge, rent deposit	supports billing and arrears review
Rent review	review dates, basis, assumptions, disregards, notice steps, time limits	creates the review timetable
Break rights	who may break, break date, notice period, conditions, service method	prevents a missed or invalid break
Repair and alterations	repair standard, demise, reinstatement, alteration consent	informs inspections and dilapidations work
Insurance	insured risks, premium recovery, tenant duties, uninsured damage provisions	supports insurance and recovery processes
Notices and compliance	notice addresses, permitted methods, statutory or contractual notices, reporting duties	controls formal communications

Add four columns beside each extracted term: source document, clause reference, verbatim wording or short quote, and review status. The source evidence makes a second review possible without repeating the whole reading exercise.

3. Extract terms in operational passes

Work one section at a time. First read the relevant clause and linked schedule yourself. Then use the model to create a structured candidate entry from the text you provide. This is safer than asking for a general summary of a long agreement.

Use this prompt for each section, replacing the bracketed text:

Extract only the operational terms for [RENT REVIEW] from the text below.

Return a table with: field, extracted value, exact clause reference, short supporting quote, operational action, ambiguity or missing information.

Rules:
- Do not infer a value that is not stated.
- If a later document changes this term, identify the conflict.
- Keep defined terms exactly as written where they affect meaning.
- Mark any date, notice requirement, condition or time limit as CHECK REQUIRED.
- State "not found" where the text does not answer the field.

Document: [document name and date]
Text: [relevant clause, schedule and any amendment wording]

Complete each pass in this order:

1. Term and rent. Capture dates, payment frequency, payment in advance or arrears, VAT treatment and all sums described as rent or additional rent.
2. Rent review. Capture the review trigger, review dates, review basis, assumptions, disregards, notice mechanics, backdating and dispute provisions.
3. Break. Capture the break holder, date, notice period, exact conditions and the service clause. Do not reduce a condition to a label such as “vacant possession” without retaining the actual wording.
4. Repair and alterations. Identify the extent of the demise, repair standard, decoration duties, yielding-up obligation, alterations controls and reinstatement rights.
5. Insurance. Record who insures, what is recovered from the tenant, the tenant's insurance duties, excesses, suspension provisions and treatment of uninsured damage.
6. Notices and other obligations. Extract addresses, allowed delivery methods, deemed service rules, reporting duties, consent requirements and deadlines.

4. Resolve changes before you publish

Make a change log after the first extraction. Compare every later document with the affected field in the abstract. Use a simple status: unchanged, amended, superseded, or unclear.

For example, if a deed changes the review dates, retain the original lease reference in the history but put the revised date in the live field. State the deed name, date and clause that made the change. Never overwrite the source trail.

Where the documents conflict, do not ask the model to choose the prevailing term. Flag the conflict in the abstract and send a focused question with the relevant clauses to the legal adviser.

5. Check the output against the documents

The most common failure is a polished abstract that misses a condition hidden in a schedule, definition or variation. Check the entries that create money, deadlines or loss of rights first.

Use this review table before circulating the abstract:

If you see this	Check this	Then do this
A break date	notice period, service clause and every condition	create a provisional diary entry and obtain legal confirmation where needed
A rent review date	whether notice is required and whether the date can be backdated	assign an owner and diary the preparation date
A repair obligation	the plan, exclusions and definition of premises	link it to the inspection record
An insurance recovery clause	exclusions, excess and uninsured damage wording	compare it with the insurance schedule and service charge process
“Not found” or “unclear”	related definitions, schedules and later documents	leave the field open and escalate it

Ask a second reviewer to test at least the term dates, current rent, rent review mechanics, break mechanics, repair scope, insurance recovery and notice provisions. They should check the source documents, not merely approve the wording in the abstract.

6. Publish one live version and keep the evidence

Save the final abstract in the property record with its review date, reviewer and document-set list. Make the live fields available to the team that manages billing, inspections, insurance and notices. Keep the evidence columns in the controlled source version, even if a shorter operational summary is shared more widely.

Set a review trigger whenever a new deed, side letter, licence or rent review memorandum is signed. Update only the affected fields, then repeat the focused checks above.

If the extraction does not work, stop using the output as a source. Return to the signed document set, split the work into smaller clause-level extracts, and compare the wording manually. For an unclear definition, conflicting amendment or a right that could be lost through timing or service, record the issue and obtain a qualified legal review before acting.