Main site

Facilities AI agent · Lease administration

Lease Administration AI Agent

Abstract every critical date onto the clause that produced it, diarise each option window under the notice terms in that instrument, and hold the drafted notice for the officer who serves it.

Typical delivery
4–6 weeks
Deployment
Your stack
Officer serves
Diary-bound
After launch
Agent Care

What this agent does

Abstracts the dates, never serves the notice

In

  1. 01

    A lease is abstracted, and every date it yields carries the clause and the document version behind it.

  2. 02

    A window opens, and the diary shows the earliest day notice may be given and the latest.

Reason

  1. 03

    A clause reads two ways, and it is marked ambiguous instead of resolving into one tidy date.

  2. 04

    A notice falls due, and the method, the address and the recipient come from the instrument.

  3. 05

    A counting convention differs, and business days, clear days and days from despatch stay apart.

Decide

  1. 06

    A side letter is filed, and each date that amendment touches is abstracted again before the view refreshes.

  2. 07

    A rent review lands, and the review dates move with it, along with whatever ran off them.

Out

  1. 08

    A break option lapses, and the file shows the day it closed and who last saw it.

  2. 09

    Execute write actions only inside the approval boundaries agreed during implementation.

Product statement

The agent abstracts the dates and drafts the notice. Whether it is served, and by whom, belongs to a named officer of the occupier.

Example workflow

One option window, lease to notice

  1. 1Lease documents receivedLeases, side letters, licences to alter, rent-review memoranda or renewal deeds
  2. 2Lease context assembledThe demise, the property it sits at, the clause the date came from and the version it was read in
  3. 3Critical dates draftedThe window, its notice terms, the ambiguities and completeness
  4. 4Controls appliedClause-provenance checks, amendment-currency checks, counting checks and completeness confidence

No human action required

Stages 1 to 4 run unaided, and nothing is served at any of them — the agent is abstracting, and the property lane opens at the completeness gate.

5DecisionSplits at the completeness gate
Evidence sufficient

Goes to the real-estate director to approve.

Anything ambiguous

Adds a lease analyst read first.

Property review

The window is held with its clause, its notice terms and the property it sits at.

Approve · Append document · Send to property review

Approved — by the real-estate director

  1. 6Lease and diary records updatedOnly where write access and records policy allow it
  2. 7Outcome evaluatedDate provenance, window coverage, analyst corrections and what review returned

Corrections

Each property correction is counted in the evaluation.

What should not run autonomously

Human approval stays in control

Outside the boundary — human approval required

8 items

  • Serving a notice on a landlord or an agent.
    • Deciding to exercise or to let a break option go.
    • Resolving an ambiguous clause into a firm date.
    • Agreeing a variation to any lease term.

  • Automation boundary

    Agent acts unaided

    • ✓Abstract each critical date with the clause and version behind it.
    • ✓Diarise every option window against the notice terms it carries.
    • ✓Draft the notice for the officer whose name.
    • ✓Mark an ambiguous clause as ambiguous, then route it.

    Nothing is served or approved except by a named person, inside the agreed boundaries.

    • Judging whether a notice was validly given.
    • Telling a landlord the occupier intends to break.
    • Setting which counting convention a clause intends.
  • Changes to the lease record, the diary or the abstract.

Example output

One option window, annotated

Our lease-processing copilot fills the approved form for a broker and our lease and fixed-asset accounting agent builds the schedules a controller posts; this record is one window inside a lease the occupier has already signed.

Diary entry · single window

Illustrative example
Window
Break option, tenant only
Recorded as
Read from the break clause and the deed of variation
Property
Regional office
Document of record
Variation deed, 3 August 2026
Confidence
Held unserved
Held for
The real-estate director, by name

As received

Taken from the lease and the deed of variation — it reaches as far as those documents do.

What the record holds

  • Executed lease
  • Deed of variation
  • Notice schedule

Why no notice here

Whether to break is the occupier's own decision, and no model may take it.

What the score decides

Below the configured threshold a window picks up a property read before the director sees it.

Action

ApproveAppend documentSend to property review

Value

Where AI adds value

The same four claims, placed at the point in the workflow where each one applies.

Where the value lands

Value 01 – 04

Every window

From the lease that sets it

03Evidence

Where the evidence is used

A missed option window has no remediation and no appeal: this page holds the dates and the documents behind them, and takes no view on whether to stay, go or renegotiate.

01Approved path

The date is in the lease

Every date is carried with the clause it came from and the document version it was read in, because a date stripped of its clause is only a rumour.

02Human review

What was checked, and not found

No survey of landlord acceptance practice was made, no portfolio-wide census of notice conventions was attempted, and the abstract reaches only as far as the documents actually filed in the repository — an unfiled side letter is invisible to it.

04

Build an evidence trail

The lease, the option it carries and the officer who served notice stay on the file.

Integrations

Typical integrations

Five system groups connect to the same agent. Which of them are in scope is decided in discovery.

  • Lease document sources

    • Document repository
    • DMS
    • Executed leases and deeds

  • Lease and diary systems

    • Lease record
    • diary
    • Critical-date register

  • Property and estates

    • Estate register
    • CAFM
    • Demise and property records

Agent

Lease administration

  • Reads the leases
  • Abstracts the dates
  • Holds for the director

  • Notice and matter systems

    • Matter tracker
    • post log
    • Served-notice records

  • Observability & evaluation

    • OpenTelemetry
    • Langfuse
    • Supported monitoring/evaluation sources

Integration availability depends on the client's existing systems and API access.

Agent controls

Six stages between the model and the officer

Six stages walked in order, the last the narrowest of them. Whatever reaches the end is in the map below.

L6 · Outermost — last line of defence

Inward → L1 · closest to the model

L6Rollback / safe modeNarrow the agent to evidence assembly when evaluation or production signals degrade.Roll back
L5Version monitoringTrack model, prompt and abstraction rules, and put a lease back through abstraction whenever a new amendment reaches the repository.Track
L4TraceabilityRecord each date, the clause behind it, the version it was read in and every read of the file.Record
L3Director releaseHold the notice for the real-estate director; the hold governs release, not whether the option is worth exercising.Gate
L2Clause guardrailsTest each date against the clause that produced it; where a clause reads two ways, the date is withheld and marked.Restrict
L1Confidence thresholdsRoute an ambiguous window to a lease analyst before the real-estate director sees it.Require review
Model coreDates abstracted — the window, the clause, the notice terms and completeness
L1 – L2
Test whether a date may stand
L3
Puts the service in a person's hands
L4 – L5
Keep the lease and the option behind it
L6
Leaves the notice undrafted when signals degrade

How Nestack evaluates it

Evaluate the whole abstract — not only the diary entry that comes out.

Coverage runs the whole depth of the workflow, and every layer is cut by slice.

Surface — the notice a landlord receives

  1. E1Final-output evaluationDid the entry record the window the clause actually gives?
  2. E2Step-level evaluationDid the agent read the right lease, the right clause and the current amendment?
  3. E3Tool evaluationDid it read and write the correct lease record and the correct diary?
  4. E4Confidence calibrationDo low-confidence windows actually attract more property corrections?
  5. E5Slice evaluationHow does performance change across specific property types?
  6. E6Business outcomeHow many windows needed a correction before the director approved?

Floor — the option the occupier answers for

Failure modes

Where each failure originates in the agent

Seven failure modes, each placed at the stage that first produces it.

Agent lifecycle

Direction of processing →

  1. 01 · Retrieval

    1 mode

    • KU-03

      Stale abstract read

      The lease read is not the one the last amendment amended.

    Stage gathers

    The leases, the clauses, the dates and the deeds

  2. 02 · Reasoning

    2 modes

    • KU-04

      Window closed too early

      A counting convention is applied that the clause never set.

    • KU-06

      Ambiguity resolved silently

      A clause that reads two ways is abstracted as one date.

    Stage proposes

    The windows, their clauses and completeness

  3. 03 · Tool / write

    2 modes

    • KU-02

      Thin window passed forward

      A window moves on without the analyst read.

    • KU-05

      Bound to the wrong demise

      A date is filed against the wrong property.

    Stage writes

    Only where write access and approval policy allow it

  4. 04 · Output

    1 mode

    • KU-01

      Approved, clause unrecorded

      The record shows an approval but not the clause behind it.

    Stage returns

    The notice an officer serves and a landlord receives

  5. 05 · Change / Version

    1 mode

    • KU-07

      Silent diary regression

      A configuration change moves the window, not the clause.

    Stage tracks

    Model, prompt, abstraction rules and diary fields

  • Sev-1 · an option window closes undiarised
  • Sev-2 · a wrong date reaches the diary
  • Sev-3 · source degrades, notice held undrafted
See the complete Facilities failure-mode catalogue

Affected slices

Acquired leases absorb the corrections

A property-level date-provenance figure can read clean while leases carried in from acquisitions hold most of the rework. Nestack reports the correction rate by property type, not only in total.

Slice performance — reported separately, not only in aggregate

Illustrative example
SliceFailure rateLiftLift vs. thresholdStatus
Leases carried in from acquisitions6.2%3.6×Review
Multi-let office portfolios4.4%2.6×Review
Retail and high-street units2.8%1.6×Watch
Single-let headquarters1.1%0.6×Normal

Bar: correction-rate lift vs. single-let headquarters baseline · scale 0–4.0× · tick marks the 2.0× review threshold

2 of 4 slices over threshold

Evidence-linked improvement

What a lapsed option costs

A loop ends when the lapsed break option has become a case the next release must pass. That suite is what the next date diarised is measured against.

Improvement cycle · five stages

Switchback — the path turns at Improve and returns at Learn

  1. 01

    Detect

    Correction rate rises on leases carried in from acquisitions.

  2. 02

    Diagnose

    The break option that opened and closed inside one quarter nobody diarised is read back until a single cause remains.

  3. 03

    Improve

    Number the change; the leases that drove it are filed underneath it.

  4. 04

    Verify

    Each touched lease case is run once more, and one red holds it back.

  5. 05

    Learn

    It stays on as a standing test, and the notice rules move alongside it.

  6. Learn → Detect

    The return edge. Every window after this one meets a suite one case longer.

Typical build scope

Twelve workstreams across six weeks

The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, date abstraction, evaluation, integration, then production validation and handover.

Workstream

Week 1Week 2Week 3Week 4Week 5Week 6

  1. 01Critical-date discovery and automation-boundary work.Week 1
  2. 02Lease, amendment and estate sources.Week 1, Week 2
  3. 03Clause-to-date and notice-provision rule mapping.Week 1, Week 2
  4. 04Lease and amendment ingestion.Week 2
  5. 05Clause, date and document binding.Week 2, Week 3
  6. 06Completeness scoring and review routing.Week 3
  7. 07Director approval workflow.Week 3, Week 4
  8. 08Repository and diary integration.Week 5
  9. 09Critical-date and notice cases.Week 4, Week 5
  10. 10Guardrails and service controls.Week 4
  11. 11Lease-trail instrumentation.Week 5, Week 6
  12. 12Deployment, documentation and Agent Care handover.Week 6

12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel

Final scope and sequence confirmed in discovery

Engagement tiers

What each tier includes

Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.

Capability✓ in scope · — not at this tierPilotOne property, one yearProductionProduction lease workflowAdvancedMultiple properties / entities
Introduced at Pilot
Abstraction to your clause rules✓✓✓
Real-estate director release✓✓✓
Critical-date baseline✓✓✓
Introduced at Production
Reporting by property—✓✓
Approval workflow in your systems—✓✓
Approved write-back—✓✓
Document-repository integration—✓✓
Introduced at Advanced
Multi-landlord lease terms——✓
Cross-portfolio evidence packs——✓
Large lease portfolios——✓
Multi-jurisdiction notice controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build price
Confirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.
Separate from build
Build pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.

What we need from you

What you bring, and what we build with it

Each input maps to a piece of build scope and a week in the delivery timeline.

  1. 01Your properties and the leases behind each one

    Property mapping and lease capture

    Week 1

  2. 02Representative leases, deeds and side letters

    Clause binding, date logic and the abstraction baseline

    Week 2

  3. 03Your notice conventions and who may sign one

    Clause mapping, date binding and the automation boundary

    Week 1

  4. 04Access to relevant APIs, feeds or exports

    Repository, lease and estate-source assessment, then integration setup

    Week 2

  5. 05Dates you would not want missed

    Notice cases and the evaluation suite

    Week 4

  6. 06What no lease abstract may guarantee

    Completeness scoring, review routing, guardrails and release controls

    Week 3

  7. 07A named officer who may serve a notice

    Director approval workflow, then pilot and production validation

    Weeks 5–6

Nothing else is required

Deployment, documentation and Agent Care handover are ours.

Delivery timeline

Four phases across six weeks

These bars are the weeks each phase actually needs and not a drawing, so the fifth holds a pair.

Phase

W1

W2

W3

W4

W5

W6

  1. DiscoveryW1
  2. BuildW2 – W3
  3. EvaluateW4 – W5
  4. Pilot & LaunchW5 – W6

Week focus

W1Lease workflow discovery, clause mapping and the automation boundary

W2Source integration and the critical-date baseline

W3Date abstraction, notice logic and release controls

W4Evaluation suite, notice cases and failure-mode testing

W5Repository integration, pilot leases and targeted corrections

W6One lease year run under the real-estate director, then Agent Care handover

Reading the band
Each bar covers only the weeks its own work is named for. Week five holds two because the work overlaps there.
At the end of W6
When the lease record validates, Agent Care picks the agent up.
Duration
Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.

Next step · Facilities AI agent

Build a lease administration agent around the option window nobody put in a diary.

An abstract is only as current as the last amendment filed, and a side letter that never reached the repository moves dates the portfolio view still shows. Show us your leases, your notice provisions and the officer who may serve.

Typical delivery
4–6 weeks
Deployment
Your lease portfolio
Officer serves
Diary-bound
After launch
Agent Care available

Nestack Agents · Lease administration

AGT-AF-12 · Agent Care available after launch

Build a lease administration agent

Four questions so the call starts from your actual setup — then pick a time that suits you.

About you
Your properties

No obligation. We’ll map the workflow, name the automation boundary and tell you if an agent is the wrong answer.