Lease event watch
A missed break notice or a rent review that slipped past its trigger date costs real money, and the date is always sitting in a document somebody meant to diarise. This agent watches the lease register and the leases behind it, and puts the events that are approaching in front of the asset team with the clause and the notice period attached.
Step by step
Connect the lease register
The register is connected along with the leases behind it, so the agent can check a date against the wording rather than trusting the field.
Agree the dates to watch
Rent reviews, breaks, expiries, options and any other trigger your team tracks, each with the lead time you want warning at.
It reads the notice provisions
For each event the agent finds the clause setting the notice period and the form the notice has to take.
It builds the forward calendar
Events are ordered by the date action has to start, not by the date they fall, so nothing arrives too late to act on.
It posts what is approaching
The asset management channel gets the upcoming events with the clause quoted and the register entry linked.
An asset manager confirms each date
Before the team acts, an asset manager checks the date against the lease. The agent serves no notices and writes to no tenant.
Exactly what this agent can see, touch and change
The same five controls sit behind every Askollo agent. These are this one's settings — visible before you build it, not buried in an admin screen afterwards.
Context
What reaches the modelAsset managers and property managers running a portfolio where the critical dates live in several registers and at least one person's head.
Escalation
When it asks a personAn asset manager confirms each date against the lease before the team acts on it
Applications & Rights
Which tools it uses, and what it may do in eachVerification
How you know it’s rightEvery 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 managers and property managers running a portfolio where the critical dates live in several registers and at least one person's head.
What you’ll need
- A lease register connected
- The underlying leases readable
- Agreed events and lead times
- An asset manager to confirm
What you get
- A forward calendar of lease events
- A channel post per approaching event
- The clause and notice period per date
What it doesn’t do
It reports the dates it can read in your register and the leases behind it. It serves no notices, writes nothing to a tenant, and a lease it has not been given cannot be watched.
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.
Scope
One session with the people who actually do the work. We agree what the agent reads, what it may write, and who approves.
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.
Handover
You own the controls. Change the context, tighten the rights, move the approval gate — without coming back to us.
Parts of the work currently spread across the categories below. It does not replace any of those products outright.
Frequently asked
What if the register date is wrong?
That is the point of checking it against the lease. Where the register and the clause disagree, the agent posts both and marks the conflict for the asset manager instead of picking the field it trusts.
Can it serve the notice?
No, and it is not built to. Notices are legal acts with form and service requirements, so the agent stops at telling you the window is opening and what the clause requires. Your surveyor or solicitor does the rest.
Where does it post?
Wherever the team already looks, which for most is a channel rather than another dashboard. The post carries the citation so the check takes a moment rather than a document hunt.
Does it work across several registers?
Yes, if they are connected. Portfolios that grew by acquisition usually have more than one, and the agent reads across them, which also tends to surface where two registers hold different dates for the same unit.