How Cheru Estimate works

An automated property-value guide based on available property details and market evidence. It produces a directional low, midpoint and high for early-stage comparison.

It is not a formal valuation, physical inspection, title review, lending decision or guaranteed selling price. See the Estimate Disclaimer.

The engine uses the applicable submitted location, property type and size. Depending on property type, it can also use bedrooms, bathrooms, age, condition or finish, parking, floor-area information, access or services, and selected amenities. Some details are retained as context or assumptions rather than having a separate numerical adjustment.

The engine resolves the submitted location and microlocation against Cheru location records. Evidence may come from an exact location, a supported parent or same-location fallback, a nearby verified baseline, or qualified market observations. Wider or weaker matching can reduce the evidence assessment and widen the range.

Where available, the engine uses qualified asking-market observations for broadly comparable property type, listing context, location and attributes. These are advertised asking prices—not completed transaction prices—and individual comparable rows are not exposed in the public result.

Some paths use active, verified location pricing baselines. Land requires suitable land-rate evidence before a result can be produced; house calculations can combine land and building evidence. Apartment and office paths use their applicable rate or asking-market evidence and fallbacks. A fallback is not presented as evidence from the requested microlocation.

Land uses acres and applicable land-rate evidence. Houses can use land and built-up components. Apartments use unit area where supplied (or a disclosed inference in supported cases), configuration and applicable market evidence. Office/commercial requests are normalised to the office path and use relevant unit-size and office evidence.

Because the paths differ, no single input or baseline rule applies to every property type.

Some unusual sizes or inconsistent combinations trigger a request to check or confirm details; inputs that cannot support a meaningful calculation can be blocked. Missing required evidence can return an insufficient-coverage response instead of a number.

The estimated midpoint is the engine’s central guide. The low and high combine the engine’s available evidence range with a wider or narrower evidence-based spread. They are not a statistical confidence interval, and a transaction is not guaranteed to occur inside the range.

The consumer labels are Strong market evidence, Good market evidence, Some market evidence and Limited market evidence. They summarise factors such as baseline quality, quantity and recency of asking observations, input completeness, inference and fallback distance.

These labels are comparative evidence descriptions, not probabilities or published accuracy percentages.

Optional missing information can reduce evidence strength, cause an assumption such as an inferred apartment area, or prevent a property-specific adjustment. Required missing location or size information is requested before calculation.

Cheru may withhold an Estimate when it cannot establish a usable baseline or enough applicable evidence. “Insufficient data” is preferable to a zero value or fabricated precision.

The automated result cannot independently inspect unreported renovations, physical defects, interior quality not represented by inputs, title or legal defects, encumbrances, unusual views, private transaction terms, immediate negotiation circumstances, or market changes not yet reflected in available evidence.

Use an appropriately qualified professional for lending, legal, tax, accounting, insurance or transaction-critical purposes, and whenever physical inspection, title context or a signed opinion is required. You can start with Cheru Estimate for directional guidance.

Cheru may revise inputs, evidence selection, guardrails and range construction as the product changes. A deliberate engine-method revision changes the centrally maintained method version. General evidence definitions remain documented in the Data Methodology.