Lease expiration schedule: deadlines and portfolio exposure

An end date can be known while the next action remains unresolved; keep that gap visible in the leasing queue.

Kartik Deshpande··7 min read

The January expiration list is ready, but several rows have no confirmed next-action date. Your lease expiration schedule should keep those leases in the review queue, with an owner responsible for resolving the missing deadline. Build two linked views: a calendar of reviewed actions and an expiration cohort showing which active leases end in each period.

A known lease end date does not establish when an option must be exercised, whether a renewal is committed, or when space will become available. Keep each of those states separate. The process starts with the active lease population, connects reviewed deadlines to their evidence, and releases a dated queue that can be checked again when the source records change.

Fix the active lease population and reporting cutoff

The property administrator owns the population. Declare the properties, reporting cutoff, and horizon before selecting expiring leases. Use one record per active lease, with stable property and lease IDs and linked premises, so several spaces or tenant contacts do not multiply its rent or expiration count. Keep future commencements and ended agreements outside the active cohort, with separate lists when the review needs them.

Reconcile the starting population with a dated rent roll. Investigate missing lease IDs and status disagreements before grouping by expiration month. An export filtered to the next quarter cannot show whether a missing lease was excluded because its end date is blank, its status is wrong, or its property was omitted.

AppFolio’s Owner Portal documentation lists lease end dates and occupancy status as separate property fields, and its property view reflects properties active today. That distinction matters when reconstructing an earlier cutoff: a current screen does not establish the population that existed when the earlier schedule was released.

Keep active leases with missing end dates in an exception bucket that reconciles to the total population. Track month-to-month and other open-ended arrangements separately from dated expirations. A blank end date must not become a fabricated month-end date just to make the chart balance.

Attach reviewed action dates without guessing notice periods

The lease administrator prepares the date record; the authorized lease or legal reviewer confirms the contractual basis. Link each action to the lease ID, action type, relevant clause or approved abstract, and review status. Preserve the deadline or window, any triggering event, and the person responsible for deciding or acting. An internal review target belongs in a different field from a contractual deadline.

Yardi’s lease renewal documentation describes lease expirations, tenant options, and encumbered spaces together. Its product example shows why an expiration date alone is insufficient: a tenant option can affect the leasing decision before the lease reaches its end. This is a reason to preserve the option relationship, not evidence that a particular option applies to your agreement.

Use a reviewed lease abstract as the supporting term record rather than extracting the same provision again inside the schedule. If an amendment changes the expiration, reopen dependent action dates for review. Do not reuse an old option deadline or subtract a standard 30 or 60 days from the new expiration without approved evidence for that calculation.

Where the deadline remains unresolved, record “awaiting review,” assign the reviewer, and set an internal review date. Keep the lease visible even if the contractual date field is empty (a date filter can otherwise remove the rows needing attention). The applicable agreement, amendments, and jurisdiction require qualified review; this schedule is an operational record, not legal advice.

Separate source dates, approval, and the action queue
Lease record

Term end and source

Reviewer

Confirm or hold deadline

Owned queue

Approved actions and open reviews

Unresolved deadlines remain assigned for review instead of disappearing when the calendar is filtered.

Prioritize action deadlines and rent exposure separately

The leasing lead owns the action queue, while the asset manager owns the concentration view. Sort approved contractual actions by their reviewed due dates, and show unresolved reviews beside them. Group lease expirations by month or quarter in a separate view. A distant expiration can have an earlier option deadline than a lease ending next month, so one expiration sort cannot order both jobs.

Assume a hypothetical portfolio has four active fixed-term leases at November 20, 2026, with $50,000 in total monthly base rent. The table uses invented dates and reviewed-deadline assumptions solely to demonstrate the schedule. There are no concessions, partial months, currency differences, or overlapping premises. Lease C’s signed extension has been reviewed and its revised expiration accepted.

LeaseAccepted expirationMonthly base rentNext action or review
AJanuary 31, 2027$12,000December 15, 2026: assumed reviewed option deadline
BFebruary 28, 2027$18,000Deadline unresolved; lease administrator review due November 24, 2026
CMarch 31, 2029$10,000Signed extension accepted; no open action assumed
DJanuary 31, 2027$10,000December 4, 2026: internal leasing discussion target

January contains two of the four active leases, or 50% by count. Their $22,000 monthly base rent is 44% of the $50,000 portfolio base. The first quarter contains three leases and $40,000, or 80% of that rent base. These are concentrations of current contract rent associated with expirations, not forecasts of vacancy, lost revenue, or collections.

Lease B remains in both the February cohort and the unresolved-review queue; its missing deadline does not reduce either rent exposure or the active lease count. Lease C belongs in the 2029 cohort under the example’s accepted extension. Keep its earlier expiration in version history so a change in the quarterly total can be explained.

Alexandria Real Estate Equities’ September 2026 quarterly filing reports contractual expirations with rentable area, rental revenue, and leasing-status categories, and discloses scope exclusions. Use that reporting discipline without importing its metrics into your portfolio. State whether your denominator is lease count, area, or a defined rent basis, and keep negotiations distinct from executed commitments.

Where Permute supports a reusable expiration view

Permute sells connected business data and custom applications. We can connect permitted Excel lease registers and document records in Google Drive, reconcile lease and property references, and apply your approved cohort and status definitions. The resulting structured view can retain source references alongside deadline-review exceptions.

We help make that view reusable by keeping the cutoff, selected properties, rent basis, and review rules together. An operations application can expose an assigned queue and a portfolio summary from the same governed records. Agree the document coverage, refresh timing, and release checks during setup so a refreshed result can be compared with its prior version.

A leasing operations lead could ask which upcoming expirations lack reviewed action dates and inspect the affected leases and supporting references. We sit underneath Claude, ChatGPT, and Copilot, supplying the governed data those tools use. Permission to see a portfolio total does not automatically grant access to every tenant document behind it.

Start with a dated lease review queue

Use a permitted lease register and approved date records to explore an expiration view with visible exceptions.

Release a version that preserves unresolved reviews

The lease administrator owns release, with the leasing lead approving action assignments. Publish the business cutoff, generation time, source versions, and approved population beside the schedule. Reconcile dated expirations and open-ended or missing-date exceptions to the active population. A rent total that balances can still contain a lease assigned to the wrong month.

Set separate statuses for a proposed renewal, an executed extension awaiting review, an accepted revised term, and a completed action. Attach completion evidence to the action record; a checked box does not prove notice was delivered or an option was exercised. Your authorized owner determines what evidence supports that conclusion.

When the schedule enters the property management reporting pack, carry its cutoff and exceptions with it. A portfolio summary needs the same population and rent basis as the underlying lease rows. Keep tenant contact details out of an asset-level copy when the recipients need only lease references and exposure totals.

Compare each refresh with the last approved schedule

The property administrator owns the change comparison. Match rows by lease and premises IDs, then identify changed expirations, new agreements, missing records, and altered action statuses. Give each change a reason and source reference. A missing row could reflect a property sale, a filter change, or a correction, so do not label every disappearance a renewal.

Return changed contractual fields to the authorized reviewer and changed operational assignments to the leasing lead. Retain the earlier release rather than overwriting it, including late-arriving amendments that affect a prior cohort. Set the review cadence around the approved action workload, while recognizing that a refresh cannot recover a deadline whose supporting evidence never arrived.

Keep legal decisions and tenant communication with owners

We do not choose legal interpretations, determine enforceability, or confirm that a contractual notice is valid. The schedule workflow described here reads source records and prepares an analytical view; it does not update lease terms, notify tenants, or exercise options. Qualified owners review the contract and applicable requirements, approve dates, and carry out the action. We are not a forecasting engine, and expiration concentration alone does not predict vacancy or rental income.

A usable lease expiration schedule preserves the active population, accepted term ends, and reviewed next actions at a stated cutoff. Keep leases with unresolved deadlines visible and assigned, then separate their expiration exposure from the work needed to resolve them. Reconcile concentrations to the same count, area, or rent basis before sharing them. Preserve each release and explain changes so the next review can trace both the calendar and the portfolio totals.

Review the handoff from lease dates to assigned actions

Bring a redacted expiration report, the active lease population, and one unresolved deadline for a focused workflow review.

Questions about lease expiration schedules

What if a lease has several options or action windows?

Keep one lease record for the expiration cohort and separate linked action records for each reviewed obligation or decision. That prevents several options from multiplying the lease count or rent total. Each action needs its own basis, owner, status, and completion evidence.

Should a lease with an unknown deadline be left off the calendar?

Keep it in an assigned review queue even when it cannot appear under a contractual due date. Show the known expiration and an internal review target without treating that target as a notice deadline. The lease remains part of the applicable exposure cohort.