NovAsia

A comparison should reveal where it cannot compare

Nova Asia AI assistant

Let’s explore this page together

A clean comparison table can be misleading when areas, fees or other property figures use different definitions; the product should expose that mismatch before ranking the numbers.

This article reflects the named expert’s practical perspective. See NovAsia’s editorial policy for how material is prepared and reviewed.

Property comparison tools are often judged by how much they can line up in neat columns. I think the more important test is whether they know when not to line things up yet.

Two numbers can look directly comparable while answering different questions. Area is an obvious example. One source may use a measurement that includes spaces another source excludes. Fees can have the same problem: one monthly figure may cover a defined bundle of building services while another excludes costs that appear elsewhere. If the interface gives both rows the same label and then highlights the lower number, it has converted a definition problem into a buying recommendation.

A missing common basis is information, not a formatting defect

Suppose two hypothetical apartments have the same asking price. One card shows 52 square metres, the other 48. It is easy to calculate two price-per-square-metre figures and present the smaller result as better value. The arithmetic can be perfectly correct and the comparison still be wrong.

The deciding question is what the two areas mean. If 52 square metres includes a component that the 48-square-metre figure does not, the denominators are not equivalent. The product has not discovered a bargain; it has divided by two different definitions.

I want a comparison system to have more than two states for data: present and missing. It also needs “present but not yet comparable”. That state is useful. It tells the buyer that the underlying figures exist, but a direct ranking would overstate what is known.

Recurring charges need the same comparison discipline. Imagine two monthly amounts that happen to be identical. One may include the services the buyer expects to use, while the other may be a base charge with additional items billed separately. A table that marks them as equal has answered too soon. Before comparing the totals, the service needs the scope of each number.

This is where automatic normalisation has a clear boundary. Converting the same unit from metres to feet is straightforward once the source quantity is known. Converting different definitions into one apparently common concept is not a unit conversion. It requires evidence that the concepts genuinely match.

A well-designed comparison should therefore make the mismatch visible where the buyer is looking, not bury it in a footnote several screens away. “Different area basis” or “fee scope not aligned” is more useful than a false winner. The label can then open the source definition or the specific item still requiring confirmation.

This may produce a less polished table. Some cells remain unranked. A calculator may refuse to generate one metric. That is not failure. The comparison is doing something important: protecting the boundary between calculation and interpretation.

The purpose of comparison is to reduce uncertainty honestly

There is a temptation to think that every comparison needs one final common denominator. Property decisions rarely work that way. Sometimes the buyer does not need all data reduced to a single figure. They need to understand which differences belong to the homes and which differences belong to the way those homes were described.

If internal usable area matters for furniture and room planning, show that measure when it is available on a consistent basis. If the question is contractual carrying cost, separate confirmed mandatory charges from variable or unverified items. If neither definition can be aligned across the two offers, keep both source figures and explain the limitation instead of manufacturing an average.

The crucial part is traceability. Each number should show where it came from, what it includes and what would have to be confirmed before it can sit in the same row as another number. That makes the comparison slightly slower to read, but much safer to rely on.

It also prevents a second problem: once a calculated ranking appears on screen, people naturally treat it as an attribute of the property. A lower price per square metre starts to feel as real as the number of bedrooms, even if it was produced from inconsistent measurements. The interface has turned its own assumption into a property fact.

I would rather let a comparison say, plainly, “we cannot compare this yet”. The buyer still gains something: they now know exactly which definition is blocking a fair comparison. Once that point is confirmed, the table can become more complete. If it never becomes comparable, the limitation remains part of the decision.

A useful comparison does not eliminate uncertainty by hiding it. It reduces uncertainty by separating what is aligned, what is genuinely different and what has not yet earned a place in the same row.

Choose the right specialist