Two official values can both be correct and still fail as a direct comparison. Real-estate systems differ in institutions, housing segments, transaction processes, geographic units, statistical methods and publication cadence.
SAID uses a simple discipline: comparison quality should be explicit rather than implied by proximity on a screen.
Exact
An exact comparison requires materially equivalent definitions, units, asset scope, geography and time basis. This is the strongest case, and it is less common across jurisdictions than dashboards often suggest.
Normalized
A normalized comparison applies a documented transformation to reconcile a known difference. Currency conversion, common-base indexing or unit conversion can help, but normalization addresses only the specific difference it was designed to solve.
Approximate
An approximate comparison accepts remaining material differences and discloses them. It may still be useful for directional context or for identifying questions worth investigating, but it should not be presented with false precision.
Not comparable
Some measures answer different questions or rely on incompatible populations. In those cases, the correct output is not a forced value. It is an explicit statement that a meaningful comparison is unsupported.
What normalization cannot fix
Rebasing two indices to 100 does not make their methodologies equivalent. Converting local currencies does not equalize housing quality, transaction definitions or market structure. Matching calendar quarters does not remove differences in publication lag or sample coverage.
The useful outcome
The objective is not to eliminate cross-market comparison. It is to make the comparison's claim proportionate to the evidence. When equivalence is strong, the interface can be direct. When it is weak, the difference should remain visible. When it is absent, the system should decline the comparison.