Pick an option on each card and press Done; your answer goes straight
back to the session. The raiser's pick is marked. "I'm not sure" and "Take it to the engineering bridge" are real answers.
1
In plain terms. A Western Slope resident's lease ran out in July 2025, long before we started with that company, and in October the manager made them a renewal offer in AppFolio by hand. Our system now sees an expired lease with an open offer and, where month-to-month is switched on, would text that resident a warning and change their rent in AppFolio. Leaving it alone means old leases the manager is handling by hand stay untouched; keeping it as today means we act on them like any other expired lease.
The full question, as raised
A lease that ended 2025-07-31 was onboarded into PropFlow on 2026-09-13; on 2026-10-05 a PM prepared a renewal offer for it in AppFolio and PropFlow's poller opened a renewal cycle from it. The daily scan now treats it as a lapsed lease with a live cycle: at a building with month-to-month ON it would run the rollover (which can text the resident a month-to-month warning and then write a rent change to AppFolio); at a building with it OFF it raised an engineering alert that falsely said the offer went unanswered before the lease ended. What should PropFlow do with a lease that lapsed before onboarding and then got a PM-prepared offer?
Why, and what was tried
The session raising this recommends: Leave it alone when the offer came after the lease ended An offer made 14 months after the lease ended is the PM working the lease by hand in AppFolio; PropFlow texting that resident or changing their rent is a surprise to both, and the alert's 'unanswered before lease end' claim is false by construction. The offer's own prepared date is the one signal that separates this from the Camellia 420/522 shape (our offer, before lease end, never answered), which must keep converting and alerting. Build: add a PMS-agnostic offer-prepared date to the lease provenance read so the scan can tell the two apart. Tried first, unsuccessfully: fable-decide was run with these three options and the prod receipts and did not answer inside the turn's 280s cap; not re-run. Receipts: [propflow-prod] LOG#renewal#saga_c21da52c… → RenewalObservedPrepared preparedAt=2026-10-05 openedBy=system; the lease row's createdAt is 2026-09-13 and endDate 2025-07-31. #23777 merged (a building with month-to-month off no longer alerts). #23779 closed: it gated on the cycle's discovery time, not the offer time, and the renewal replay bench caught the false silence.