Conflicting dates
The signed lease, system record, owner instruction, and notice calendar do not agree.
For property management companies
A renewal is not one reminder. It is a chain of dates, lease facts, owner decisions, pricing, resident questions, notices, signatures, and updates. AI can carry the routine handoffs while a property manager keeps control of every material decision.
The safest first renewal employee watches the timeline and builds an exception list. It shows what needs an owner decision, a resident response, a notice, a corrected record, or human approval before a deadline becomes a vacancy problem.
Why renewals become messy
Most property management systems can store a lease end date and create a task. That does not mean the renewal is under control. A manager may still need to review the lease, check notice requirements, confirm property condition, gather owner direction, choose pricing, prepare the offer, answer resident questions, track delivery, collect signatures, and update the system.
One missing owner reply can hold the whole chain. One wrong date can shorten the legal notice window. One resident answer can change the next action. When the portfolio grows, managers spend more time checking what is waiting than making the decisions only they can make.
An AI employee should not replace the lease, property-management system, manager, owner, or legal guidance. Its job is to keep the approved facts and routine handoffs moving, record the result, and surface anything late, conflicting, or outside the rules.
Example workflow
Read the approved lease record and written policy. Calculate internal review dates and compare them with the property-management system. Conflicting dates stop for review.
Gather current rent, lease term, payment or policy flags allowed by the company, open maintenance, inspection status, owner instructions, and any approved market context.
Draft a short owner decision note showing the current facts, proposed options, response deadline, and unresolved questions. The owner or authorized manager chooses the business terms.
Use the approved decision and current template. Check names, property, dates, rent, term, required language, and delivery method before human approval.
Track delivery and reply status. Classify simple acceptance, questions, counterrequests, move-out intent, no response, and delivery failure. Judgment calls go to the manager.
Confirm signatures or approved notice delivery, update the source of truth, set the next date, and flag anything that did not finish cleanly.
The exception queue
The signed lease, system record, owner instruction, and notice calendar do not agree.
The owner has not approved the new rent, term, concession, or other material offer.
The resident challenges the facts, requests an accommodation, raises a legal issue, or makes an unusual counteroffer.
Serious maintenance, habitability, inspection, insurance, or compliance work may affect the renewal path.
The approved notice was not delivered through the required method or proof is missing.
The next required action is close enough that the normal follow-up schedule is no longer safe.
What stays human
AI should not choose rent, decide whether to renew a resident, interpret a lease or law, make a fair housing decision, handle an accommodation request alone, waive a requirement, sign an agreement, or send a material notice outside verified rules. The system can organize facts and prepare work. The owner, manager, attorney, or other authorized person makes the decision.
Human approval should be explicit. The reviewer needs the source lease, relevant policy, proposed action, deadline, and reason the system stopped. Every approved notice should be tied to the exact version sent and the proof of delivery kept in the source of truth.
How to build safely
The first version should read past renewal files and produce a review list. Compare that list with what experienced managers did. Test early renewals, month-to-month leases, nonrenewals, missing signatures, resident counteroffers, owner delays, military or legal issues, accommodations, bad contact details, and conflicting dates.
Next, let the employee prepare owner briefs and resident drafts. Require human approval. Measure missed deadlines, manager review time, owner response time, resident response time, record accuracy, and unresolved exceptions. Only consider limited automatic steps after the workflow is accurate, the inputs are reliable, and stop rules are proven.
Keep the property-management system as the source of truth. Connections may use an approved API, export, email rule, shared folder, webhook, or controlled browser workflow. Verify access and recovery before live use.
Frequently asked questions
It can watch dates, build review lists, gather facts, request owner decisions, prepare notices, follow up, and surface exceptions. Pricing, legal judgment, and final approval stay human.
Start with a daily exception list for leases entering the window, missing owner approval, unanswered resident offers, notices nearing a deadline, and conflicting dates.
It can organize approved market and property context. The owner or authorized manager should choose the price and approve the offer.
Only after the lease, law, policy, delivery method, timing, and approval rules are verified. New workflows should begin with drafts and human approval.