Skip to main content
Ask your lease

LEASE-iQ method

The architecture behind a checked lease answer.

The useful architecture is the route a person can inspect: from the signed document to the relevant wording, current external source, competing interpretation and open decision.

A real LEASE-iQ output with the answer and source context visible
A real product screen. The answer stays connected to the source material used to produce it.

Three steps for the user. Seven checks underneath.

The source route is designed before the answer is written.

This is the current public method for technical review. It describes the answer route, not an assurance claim about undisclosed infrastructure.

  1. 01Page splitting and visual parse

    Separate the page images, OCR text and visual structure.

  2. 02Validation layer

    Check order, completeness and extraction quality before reasoning.

  3. 03Clause relationships

    Identify clauses, definitions, parties, schedules and inheritance.

  4. 04Question assessment

    Classify the live issue and route it to the relevant document areas.

  5. 05Current-law grounding

    Open current legislation where it adds to or qualifies the lease.

  6. 06Ten-pass juror

    Ask the material question ten times and surface material disagreement.

  7. 07Cited output

    Return the answer with the clause, page, source and open point attached.

Boundary: a cited answer can still be wrong. Missing documents, scan errors, disputed facts and professional judgment can change the result.

Visible answer route

Five layers the user should be able to inspect.

01

Orient the document

Identify the executed lease, parties, date, term, definitions, plans, schedules and any later deed before interpreting one clause.

02

Trace the live question

Connect the repair, charge, consent, sale or management issue to the relevant wording and page in the signed document.

03

Check the current external source

Where legislation or guidance matters, open it directly and record the jurisdiction, date and status checked.

04

Challenge the first reading

Look for connected definitions, competing covenants, reservations, factual gaps and another reasonable interpretation. Surface the conflict instead of hiding it.

05

State the boundary

Show what the documents support, what remains uncertain and which judgment or professional step belongs to a person.

What the interface must preserve

An answer is reviewable only when its evidence survives it.

Source

The cited page remains openable

The user should be able to move from the answer back to the exact lease page or official source without reconstructing the reasoning from memory.

Hierarchy

Document relationships remain visible

Definitions, schedules, plans, later deeds, headlease terms and separate company records should not be flattened into one anonymous text pool.

Conflict

Competing material is shown

Where two provisions pull in different directions, the product should surface both and explain why a human judgment or further evidence is needed.

Status

Fact, interpretation and uncertainty stay separate

A quotation, a factual record, a legal proposition and a practical suggestion have different evidential weight. The interface should not make them look interchangeable.

What this page does not claim

Visible method is not a promise about hidden infrastructure.

Accuracy

No AI system eliminates error

LEASE-iQ is designed to make checking easier. The signed source, current law and accountable review remain necessary.

Advice

The product does not replace a professional

It can organise a question and expose source material. It does not act as the solicitor, surveyor, accountant, fire professional, valuer or decision-maker.

Infrastructure

Undisclosed technical claims are excluded

This public page describes the review route visible to the user. Security, hosting and model-assurance claims should be published only when they are current, evidenced and approved.

Sources for this page

Open the law and guidance yourself.

Product evidenceHow LEASE-iQ works

The current public product route, real screen and original March 2026 walkthrough.

Verification methodBuilding Trust source standard

The governing document, current source, evidence and open-point checks used across this site.

Failure modesWhy a generic AI answer is not enough

The source, party, hierarchy and uncertainty risks a reviewer should look for.

Links and current-law position checked 18 August 2026. Apply the governing documents, building facts and current law to the case in front of you.