Skip to main content
Property manager reviewing real estate listings across a laptop and monitor, representing a lease register review routine
Property Management

A Property Lease Register That Helps Managers Act Before Renewal Dates

Peter Bamuhigire 9 min read

A lease is approaching its recorded end date. Illustrative example, all names and figures fictional: Unit 4B, managed on behalf of an owner, tenant in place eighteen months, no maintenance disputes on file. The date sits on a spreadsheet, a printed folder, or inside whatever system the agency uses — but a date sitting somewhere is not the same as a decision being made.

This is the gap a lease register exists to close: not simply storing a date, but turning that date into a reviewed decision, with an owner informed, a next step assigned, and the supporting document at hand. A register that only stores dates is a filing cabinet with a calendar bolted on. A register that drives a decision is a management tool.

This article is a review routine, not legal advice. It does not interpret lease law or notice periods, and a software reminder is never a legal notice — those questions belong with a qualified professional in your jurisdiction. What follows is how to make sure the right date reaches the right person with the right document, every time.

Start With One Lease, Traced End to End

Pick one lease approaching its recorded end date — illustrative, with fictional details, as above — and trace it through the register exactly as your agency currently uses it.

Ask, plainly: when this date arrives, who sees it first? Does that person have the signed lease in hand, or just a line in a spreadsheet? Is there a defined next step, or does the process depend on someone remembering to act?

Most gaps in lease management are not about missing dates. They are about a date arriving with nobody clearly responsible for what happens next.

Confirm the Record Points to One Reality

Before trusting any recorded date, confirm that five things agree: the property, the unit, the owner, the tenant, and the signed lease document. In a portfolio spanning several owners, it is common for a unit to be correctly recorded under one owner's file and incorrectly cross-referenced under another's — usually the result of a manual handover between staff, not carelessness.

A lease register that links each recorded date directly to a scanned or filed copy of the signed lease closes this gap. When a manager reviews an upcoming date, the source document is one click away — not a request to a filing room.

A single house model resting on a keyboard, representing one property record linked to its owner, tenant, and lease document
One property, one unit, one owner, one tenant, one signed lease — confirm they all point to the same record.

Review the Recorded Date Against the Executed Document

A recorded date in a system is a claim, not a fact, until it has been checked against the signed lease and, where the terms are unclear or the situation unusual, against local professional advice. Build this check into the routine itself:

  1. Read the recorded date. What does the system say the lease end date and notice period are?
  2. Read the executed lease. Do the dates and terms in the signed document match what is recorded?
  3. Flag any mismatch immediately — as a data-correction task, not as a legal question to be resolved informally.
  4. Escalate genuine notice-period or renewal-right questions to the appropriate professional. A well-designed lease register surfaces the question early; it does not answer it.
Property manager reviewing printed records against data on a monitor, representing checking a recorded lease date against the executed document
A recorded date is a claim until it's checked against the signed lease — build that check into the routine.

Assign an Owner and a Review Date Before Contacting Anyone

Once a recorded date is confirmed against the document, name one staff member responsible for the next step, and set a specific review date — before the owner or tenant is contacted. This avoids the common failure mode where a lease approaches its end, several staff assume someone else is handling it, and the first real conversation with the tenant happens later than anyone intended.

Record the Decision, Not Just the Date

Every reviewed lease should end with one of four recorded outcomes:

  • Pending — under review, next check-in date set.
  • Renew — terms confirmed, responsible staff member named, owner informed.
  • Renegotiate — new terms proposed, awaiting owner or tenant response.
  • End — lease concluding, handover and unit turnaround process triggered.

Each outcome needs its approver and its supporting evidence attached — the correspondence, the owner's instruction, the updated document. A register that shows "renewed" with no record of who approved it or on what terms creates exactly the ambiguity a good system should remove.

A Lease Review Worksheet You Can Use This Week

Property Unit Lease document Recorded date Checked vs. document Open question Decision Owner Next action
e.g. Plot 14, Nakawa 4B Signed lease, filed ref. #22 2026-11-30 Yes / Pending ? Pending / Renew / Renegotiate / End ? ?

Fill this in — with tenant identity redacted if needed — before any conversation with an owner or tenant. It converts a date on a calendar into a decision someone can act on today.

Where Aqar Fits

Aqar, Chwezi's property management platform for agencies, records properties, units, owners, tenants, and leases against each other so that every recorded expiry traces back to a specific document and a specific portfolio — built for agencies managing multiple landlords from one system, with per-owner financial reporting alongside lease and tenant tracking. A product page describes the offer; ask for a demonstration of the exact alert, review, and decision history before relying on it for your portfolio.

If you manage a property portfolio and want to see how Aqar presents a recorded lease expiry and the review routine around it, bring one redacted lease record to a conversation with Chwezi.

Frequently Asked Questions

Does a lease register replace legal advice on notice periods?

No. A lease register surfaces dates and routes decisions to the right person; it does not interpret lease law, notice periods, or renewal rights in your jurisdiction. Those questions go to a qualified professional, and a system reminder is never a substitute for legal notice.

How often should a lease register be reviewed?

The review routine should run whenever a lease approaches its recorded end date, and additionally at a fixed interval — monthly is common — as a check that no upcoming date has been missed entirely.

What if the signed lease and the recorded date disagree?

Treat it as a data-correction task first: confirm which is accurate, correct the record, and only then decide whether the underlying terms raise a genuine legal question that needs professional input.

Is this approach specific to one country's property law?

No. The review routine is a management discipline that applies wherever leases are managed. The dates, notice periods, and statutory rules themselves are country-specific and must be verified locally.

Two related articles are in preparation and will be linked here once published: a guide to closing out maintenance requests with a confirmed handover, and a guide to property-owner reporting that shows the balance, the evidence, and the exceptions.

Peter Bamuhigire — Lead Consultant, Chwezi Core Systems

Lead Consultant · Chwezi Core Systems, Kampala

Peter leads consulting engagements at Chwezi Core Systems, where the team implements Aqar for property agencies managing portfolios across multiple landlords. He writes from direct experience building the review routines that turn a lease register from a calendar of dates into a working decision tool for property managers.

View full profile →

Ready to See Your Lease Register in Action?

Bring one redacted lease record. We'll show you how Aqar tracks it — from recorded expiry to reviewed decision.