Agent

Lease abstraction

Abstracting a lease is careful, slow, unglamorous work, and it is where portfolio data quietly goes wrong. This agent reads the lease with its variations and side letters and returns the abstract in your own field structure, with the clause reference sitting beside each entry. A surveyor checks fields instead of re-reading the document.

How it runs

Step by step

01

Connect leases and side letters

The document store is connected read-only, including the licences, deeds of variation and side letters that sit apart from the head lease.

02

Give it your field structure

We use the abstract fields your team already works to, so the output drops into the register you keep rather than a new format.

03

It reads the whole document

The agent works through the lease and everything varying it, not just the front schedule, and reconciles the two where they differ.

04

It fills the fields with citations

Each entry carries the clause it came from, so a checker can jump straight to the wording.

05

It flags what reads ambiguously

Unclear drafting, handwritten amendments and poor scans are marked for a person instead of being resolved by guesswork.

06

A surveyor checks before filing

The register is only updated once a surveyor has approved the abstract, flagged items included.

The harness

Exactly what this agent can see, touch and change

The same five controls sit behind every ollo agent. These are this one's settings — visible before you build it, not buried in an admin screen afterwards.

Context

What reaches the model

Asset management teams keeping a lease register honest, and transaction teams abstracting a tenancy schedule against a deadline.

Escalation

When it asks a person

A surveyor checks every abstracted field before the lease register is updated

Applications & Rights

Which tools it uses, and what it may do in each
DropboxRead only
SharePointRead only
Google DriveRead only
NotionWrites newCreates new records or documents. Never edits, moves or deletes anything that was already there.

Verification

How you know it’s right

Every claim links to the document it came from. A statement the agent cannot cite does not make it into the output — which is what makes the result reviewable in minutes rather than re-read end to end.

Who it’s for

Asset management teams keeping a lease register honest, and transaction teams abstracting a tenancy schedule against a deadline.

What you’ll need

  • Leases, licences and side letters connected
  • Your abstract field structure agreed
  • A lease register the agent may write to
  • A surveyor to check each abstract

What you get

  • A structured lease abstract
  • A clause reference per field
  • A list of ambiguous clauses

What it doesn’t do

It reads what the documents say; it does not interpret them for you. Handwritten variations and poor scans come back flagged rather than guessed at, and what it produces is a record of the wording, not a lawyer's view of it.

How you get it

We build the first one with you

Not a template you configure alone. We sit with your team, build it on real data, and hand over the controls.

01

Scope

One session with the people who actually do the work. We agree what the agent reads, what it may write, and who approves.

02

Co-build

Built on your own data, not a sandbox. You watch it being made, so you know why it behaves the way it does.

03

Handover

You own the controls. Change the context, tighten the rights, move the approval gate — without coming back to us.

What it replaces

Parts of the work currently spread across the categories below. It does not replace any of those products outright.

Manual lease abstractionLease registers maintained by hand
Estimated savingNot setNo figure ships until someone at ollo owns it and the method behind it.

Frequently asked

Our older leases are scanned, some badly. Does that break it?

Poor scans are the common failure and the agent is built to be honest about them. Pages it cannot read reliably are reported as unreadable with the page reference, so someone can pull the original. It does not fill an unreadable field with a plausible value.

Can it update the register on its own?

Only after a surveyor approves. The write to the register is behind the gate, so an unchecked abstract never becomes portfolio data. That ordering is deliberate: a wrong break date is worse than a slow one.

What about side letters that contradict the lease?

It reports both and marks the conflict on the field. Reconciling a side letter against a head lease is a judgement your surveyor makes, so the agent presents the evidence and stops.

How do we start?

In the co-build session we run the agent over leases your team has already abstracted by hand and compare the two. That tells you where it is reliable and where the checking effort should sit before it touches anything new.

Let's Build

AI is a capability you build. Let's build it together.

30 minutes with our team and you'll leave with a real plan — not a sales pitch.