Case study·Healthcare REIT

Portfolio valuation support

From a re-typed valuation pack — to an assumption log the committee can challenge

44%
Valuation-pack prep downMeasured against the prior cycle's analyst time log
“It made the valuation pack easier to challenge before committee.”
Finance Director · UK healthcare real-estate investor
UK healthcare real-estate investor·~120 healthcare assets across the portfolio, quarterly valuation cycle·6-week pilot·United Kingdom
Talk to us about this workflowTry Unify
01Pilot envelope
Pilot length6 weeks
First signal7 days
First ROI35 days
Team alongside5 seats · 2 colleagues

6-week valuation committee pilot; connected rent roll, lease events, operator health and valuation assumptions; the colleague flagged assumption inconsistencies.

02What it owns
Reports toFinance Director, with the investment team and asset managers consulted on every flagged assumption.
Owns
  • Source-linked valuation pack — rent roll, lease events and operator health joined per asset, with every figure traceable to Yardi, MRI, the SharePoint tracker or Power BI
  • Assumption check log — daily log of inconsistencies between the assumption set, the live rent roll, the lease event tracker and the operator overlay, posted in the valuation Teams channel
  • Rent roll reconciliation — Yardi and MRI rent rolls reconciled against the Excel working copy with a named owner on every disagreement
  • Committee dry-run pack — pre-committee draft circulated to the finance director and investment team with the open assumption questions surfaced
  • Reusable check rules — repeated assumption inconsistencies promoted into a shared rule library that runs against the next quarter's workbook automatically
Does not do
  • Valuation figure — never sets a value, yield, growth rate or discount rate; the external valuer signs the number
  • Committee decisions — surfaces inconsistencies and open questions; the finance director and investment team decide
  • Direct writes to Yardi or MRI — every correction stays as a flag for the analyst or asset manager to apply
Done looks like

The finance director walks into committee with a source-linked pack and a short list of assumption questions, not a stack of late corrections. The committee debates judgement, not arithmetic.

03The team
AI teammates2
NoraReads the Yardi and MRI rent rolls, joins them to the lease event tracker and the operator health metrics, and assembles a source-linked draft of the valuation pack for the analyst to review.
LeoCross-checks every assumption in the valuation workbook against the live rent roll, the lease event tracker and the operator health overlay; flags inconsistencies to the finance director before the committee meets.
Human team5
  • Finance DirectorFinance
  • 3 Investment teamInvestment
  • 2 Asset managersAsset management
  • AnalystFinance
  • Valuation coordinatorFinance
04Connected stack
YardiMRI SoftwareExcelSharePointPower BIMicrosoft Teams
05What it returned
44%Valuation-pack prep downMeasured against the prior cycle's analyst time log
26Assumption checks surfacedFlagged before committee across the portfolio in the first cycle
30%Committee questions reducedPre-committee resolution of assumption inconsistencies
  • Day 0
    Co-ordinator sessionFinance director, investment team and asset managers agreed the rent roll join, the assumption set in scope and the first three answerable consistency questions.
  • Day 7
    First signalNora produced a source-linked draft for one sub-portfolio; Leo flagged eleven assumption inconsistencies for the analyst to triage.
  • Day 14
    Read-only assumption log liveDaily assumption log lands in the valuation Teams channel; asset managers correct two operator-health joins and one lease event field.
  • Day 21
    Committee dry-runFull source-linked pack circulated to the finance director and investment team three working days before committee; open questions surfaced ahead of the meeting.
  • Day 28
    Reusable check libraryRepeat assumption inconsistencies promoted into a shared rule library; the next sub-portfolio's workbook is checked against the library on save.
  • Day 35
    ROI reviewSponsor signed off the three baseline metrics; pilot held to the assumption-flagging remit, no production writes to Yardi or MRI.
↗Get started

Want this for your team?

Each design-partner pilot starts the same way: one workflow, the minimum useful context, and a first ROI signal measured in days.

Talk to us about this workflowTry Unify