Why the Lease Is the Center of Gravity
In a residential portfolio, the lease is the document that everything else orbits: rent collection, renewals, resident communications, owner reporting, and unit status all trace back to it. When lease data lives in a mix of PDFs, spreadsheets, and email chains, every downstream process inherits that fragmentation. Digitizing the lease lifecycle is not a nice-to-have — it is the prerequisite for operating a portfolio at scale.
This guide walks through how lease management is structured in ArkanPM, what to expect during a migration, and how to think about regulatory reference fields across the GCC.
The Lease Lifecycle: Four States That Matter
ArkanPM models leases through four primary states:
- Draft — the lease is being prepared; it does not yet affect unit status or billing
- Pending — the lease is awaiting signature or activation; the unit may be marked as reserved
- Active — the lease is in effect; rent and deposit schedules are live
- Expired, Terminated, or Renewed — the lease has concluded or rolled forward
Every state transition is recorded with timestamps and actors. Nothing slips into "active" silently; nothing gets terminated without a trail. This is the minimum audit discipline any portfolio should expect.
Auto-Numbering That Stops Being a Concern
Leases in ArkanPM receive automatic numbers in the format LS-2025-00001. The numbering is sequential within the tenant, reset annually, and guaranteed unique. This sounds trivial until you have seen a portfolio where three different spreadsheets each claimed to be the "master" lease register, with overlapping numbering conventions and a handful of contracts that were never numbered at all.
Let the system own the sequence. Stop negotiating about it.
Financial Configuration: The Fields That Drive Everything Else
A lease carries monthly rent, security deposit, payment frequency, payment day, currency, total contract value, and — critically — rent escalation rate and frequency. Escalation is where most spreadsheet-based portfolios quietly leak revenue. A 5 percent annual escalation clause that nobody applies is worth nothing.
When escalation is configured on the lease record, the system knows when the next escalation is due, what the new rent should be, and how to display the change to both the resident and the owner. The same field drives the renewal math — because the renewal proposal starts from the post-escalation rent, not the original rent.
Payment Frequency Across the GCC
GCC residential leases commonly run on annual rent cycles paid in one to twelve cheques. Commercial leases more often run quarterly or monthly. The lease record supports all of these through the payment frequency field. Whatever your collection pattern, the billing schedule should derive from the lease, not from a separate calendar maintained by the finance team.
Renewals as a Chain, Not an Event
Renewals are not new leases that happen to reference old ones. They are linked records in a chain. When a lease is renewed, ArkanPM creates a new lease that inherits configuration from the original and records a renewal reference linking the two. The chain is traversable: you can look at any active lease and see every prior term on the same unit for the same resident.
This matters for owner reporting. An owner who asks, "How long has this tenant been with us?" deserves an answer in seconds, not an answer that requires combing through files.
The 90-Day Expiry Monitor
A background processor tracks upcoming lease expirations and surfaces them on the owner dashboard as "Upcoming Lease Expirations (next 90 days)." Ninety days is the right window for a reason: it is long enough to negotiate a renewal with the sitting tenant and short enough that the property manager has to actually act on it.
Operationally, the 90-day list should drive a standing weekly meeting. Which leases are expiring? Which residents want to renew? What escalation are we offering? Which units will return to market, and what is the remarketing plan? The monitor creates the agenda; the team has to do the work.
Regulatory Reference Fields: Configure, Do Not Certify
Across the GCC, lease registration runs through different regulatory systems — Ejari in Dubai, Ejar in Saudi Arabia, tenancy registration numbers in Qatar, and comparable schemes elsewhere. ArkanPM supports these reference numbers as configurable tenant fields on the lease and resident records. That is the accurate way to describe it: you can capture the reference number, display it on the lease documentation, and include it in owner and resident-facing outputs.
To be clear about what that means: ArkanPM does not ship certified, regulator-approved integrations with Ejari, Ejar, or equivalent systems. The platform provides fields and documentation hooks so that your team can operate within local registration requirements while centralizing the operational lease data. If your portfolio requires automatic submission to a specific regulator's API, scope that as a project with the vendor and the regulator, not as an out-of-the-box feature.
The pragmatic effect for most operators is that your lease record becomes the operational source of truth while the regulatory submission remains a workflow your team completes through the regulator's own portal, with the reference number captured back on the lease in ArkanPM.
Document Management on the Lease
Contracts, addendums, and supporting documents attach directly to the lease with file metadata tracked — size, MIME type, uploader. This is unglamorous and absolutely essential. A lease record without its contract attached is a database row, not a legal position.
When a lease is renewed, the chain keeps prior documents visible on the historical record. When a resident disputes a charge from eighteen months ago, the original lease and the renewal amendment should both be retrievable without calling the records room.
What a Good Migration Looks Like
Most portfolios begin digitization with a mix of active leases, expired leases, and half-documented arrangements. A defensible migration sequence:
- Import active leases first, with rent, deposit, and expiry dates validated against the physical contract
- Import expired leases for the trailing 24 months to support owner reporting and resident history
- Import the owner and resident records before the leases, so foreign-key relationships resolve cleanly
- Validate occupancy: every unit marked "occupied" should have exactly one active lease pointing at it
The import itself is straightforward. The data hygiene is the work.
The Outcome
A digitized lease lifecycle does not dazzle anyone. It quietly removes a class of recurring problems — missed renewals, forgotten escalations, inconsistent documentation, owner questions that take three days to answer. The goal is not a more interesting lease process. The goal is a lease process that stops being a source of operational drag.