Renewals and notices7 min readUpdated 2026-04-28en-CA

Control renewals, notices, and proof without side spreadsheets.

How to keep renewal cycles, notice deadlines, delivery proof, and resident responses inside one governed operating path instead of scattered documents and inbox checks.

Deadline visibilityNotice proof trackingResident response continuity

Treat renewals as a queue, not a calendar reminder

A queue gives teams visibility into due windows, ownership, and next action while preserving a consistent review order across the portfolio.

Rank cycles by due window and response risk.

Keep province-aware deadlines on the same cycle record.

Surface the next operator action before the notice is generated.

The notice is a governed artifact, not a loose document

Generated notices need template identity, ruleset version, delivery method, and proof state attached to the record so the audit trail stays usable.

Retain template key and ruleset version alongside the notice.

Track drafted, sent, and archived states explicitly.

Store proof-of-delivery completeness on the notice itself.

Keep responses tied back to the lease and resident history

The operating team should not have to reconstruct what the resident said or when a follow-up happened from separate messages and PDFs.

Link the notice to the lease, ledger, and communication thread.

Capture response status and next action on the cycle.

Keep proof, response, and timeline events visible from one view.