Required inputs
Two weekly rent rolls, stable unit and lease IDs, leasing events, signed-lease dates and plan targets.
Weekly / W1
Leasing and Rent-Roll Review
What changed this week, and is leasing on plan?
W1 / Weekly / Product design
A clear scope.
A useful output.
Compare dated rent rolls and leasing activity with the property's weekly plan.
Review output
Matched unit and lease changes, funnel movements, plan gaps and unmatched-record exceptions.
The human decision
Choose where to investigate and agree the leasing team's next priorities.
Dependencies before conclusions
Make the gaps visible.
Upstream
What comes first.
OS rent-roll and leasing source pack
Required dependency
What must be accepted.
Two stated weekly snapshots; stable IDs; dated application/signature/move-in events; leasing plan
If an input is missing
What stays open.
No matched-change conclusion without two snapshots or reliable IDs.
Required dependency identified; source availability and reviewer acceptance not yet confirmed. Core is separate Consulting; OS contains the data/context foundation.
Worked example
Show the evidence.
Bound the conclusion.
Example
Between October 2 and October 9, occupied units increase from 92 to 93. One signed lease for C-014 has a future move-in date; it is not counted as current occupancy.
What a reviewer should check
Report occupied-unit change as +1 unit and +1 percentage point for 100 units; keep approvals, signatures and move-ins distinct.
Start with one useful review
Bring the question.
And the context.
Show us the property, the inputs your team has and the decision the review needs to support. We can discuss fit and a scoped pilot.
Book a demo