Monthly / M3

Valuation Review

How has the indicated value changed, and which assumptions drive it?

M3 / Monthly / Product design

A clear scope.
A useful output.

Review a dated valuation scenario against accepted financials, market context and approved methodology.

Required inputs

Accepted Comp Review, closed-month financial/NOI pack, prior valuation, approved valuation method and assumptions, and market evidence for any adopted cap rate.

Review output

A versioned valuation review with assumption bridge, sensitivity and missing-evidence flags.

The human decision

Approve assumptions and decide whether an appraisal or further underwriting is needed.

Dependencies before conclusions

Make the gaps visible.

Upstream

What comes first.

M2 Comp Review; accepted closed-month financial/NOI pack; prior valuation

Required dependency

What must be accepted.

Accepted comps and NOI; approved method; versioned assumptions; valuation date; cap-rate evidence or explicit scenario-only label

If an input is missing

What stays open.

Only an assumption-labelled scenario when market support is absent; no approved valuation conclusion.

Required dependency identified; source availability and reviewer acceptance not yet confirmed. Core is separate Consulting; OS contains the data/context foundation.

Separate fictional scenario

Show the evidence.
Bound the conclusion.

This illustration is specific to this workflow. Its properties, ledger figures and assumptions are not joined to the Morning Portfolio Review or other examples.

Illustration

In a purely fictional scenario, annualizing monthly NOI of 80,000 gives 960,000. At an illustrative assumed 6% cap rate, indicated value is 16 million. Annualization is not a forecast, and the cap rate has no market validation in this example.

What a reviewer should check

960,000 ÷ 0.06 = 16,000,000; label the valuation date, methodology and assumptions; no appraisal or market-supported value claimed when evidence is missing.

See the wider review plan

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