Published October 27, 2026.
A portfolio manager with nine buildings in three towns rarely has one renewal deadline. Each lease has its own end date, each municipality has its own notice rule, and each owner has a different tolerance for a late signature. The expiration calendar is the only artifact that keeps those clocks visible in one place. This guide describes how a renewal coordinator builds that calendar from the property management export and keeps it usable through the last week of the month.
Start from the lease end date, not the offer date
Export every active lease with the lease end date, the current rent, the unit number, the resident name, and the property code. Sort by lease end date. The offer draft date is irrelevant to the calendar because a late draft does not move the legal deadline. In practice, a 14-building portfolio of 1,900 units will show a cluster of end dates in the same two weeks, which is why counting offers sent per week hides the real exposure.
Add a column for the number of days the property requires between notice delivery and lease end. That number belongs to the jurisdiction and the lease form, not to the coordinator's preference. If the source of that number is unclear, mark the row as unverified and route it to the property manager before the calendar is published.
Work backward in three separate steps
Use three dated steps for every unit: notice delivery deadline, owner approval deadline, and offer expiration. Working backward from lease end, subtract the notice period first, then the owner approval cycle, then the delivery buffer. A common configuration is a 60-day notice, a 5-business-day owner review, and a 3-business-day mail buffer. That places the offer mailing date 68 calendar days before lease end.
Keep the three dates in separate columns even when they land on the same day. When an owner asks why an offer went out early, the calendar can show which buffer absorbed the change. When a resident asks for more time, the coordinator can see whether an extension of the offer expiration would push past the notice window.
Treat owner approval as a dated queue
Most missed expiration dates are not mailing failures. They are approval delays that were never assigned a date. Build an approval queue that shows the property, the proposed rent, the comparison source, and the date the packet reached the owner. Set the approval deadline from the mailing date, not from the day the owner opens the email.
If an owner has not responded by the approval deadline, the coordinator escalates with the packet and the calendar row, not with a general reminder. The escalation should state the mailing date that is at risk and the notice deadline behind it.
Publish one expiring view each week
On Monday morning, publish a filtered view of offers expiring in the next 21 days. Each row needs the resident, unit, property, offer amount, expiration date, last contact, and next action owner. Sort by expiration date, then by whether the resident has responded.
Keep the view short enough to read in one sitting. A 40-row list where every row says "awaiting response" is not a working view. Replace the status with the specific event that last occurred, such as offer emailed, resident asked about parking, or guarantor form outstanding.
Handle unknown lease end dates deliberately
Some units arrive in the export without a reliable end date, usually because a prior renewal was recorded in a note instead of a field. Do not guess. Create a short research list for those units with the last signed lease document, the amendment history, and the property manager who can confirm the date.
Until the date is confirmed, the row should sit in a separate holding view with a review date. Mixing unverified rows into the main calendar teaches the team to distrust the whole list.
Respond to extension requests without moving the legal deadline
A resident may ask to extend the offer expiration by a week while deciding. That is an operational request, not an automatic change to the notice deadline. Record the request, the new proposed expiration, and the approver. If the new date crosses the notice deadline, escalate rather than granting it.
Document the decision in the resident file with the date, the person who approved it, and the reason. The next coordinator should be able to see why the calendar changed without reconstructing an email thread.
Close the month with a reconciliation
At month end, compare the calendar to the signed leases. List every unit where the offer expired without a signature, where the lease was signed after the notice date, and where the recorded end date changed. Feed those three lists into the next month's build so the calendar reflects how the portfolio actually behaves.
The value of the calendar is not the color coding. It is the ability to answer, on any given morning, which renewal is closest to a deadline that cannot be recovered.
Sources
- U.S. Department of Housing and Urban Development, fair housing
- Consumer Financial Protection Bureau, renting tools
- U.S. Census Bureau, rental housing data
- eCFR, fair housing regulations, 24 CFR Part 100
Put the workflow into practice.
Discuss the administrative queue, systems, and approval boundaries with our team.
Request a Free consultation