Use market data for pricing decisions

Market average gives direction, but it should not price the unit alone. Review city, district, unit type, size, finishing, furnishing, parking, and nearby services.

Final pricing should combine market data with the agency team knowledge of the property and nearby competitors.

Compare the current price with district price, city price, similar offers, vacancy duration, incoming inquiries, and view count if the unit is published.

If the price is above market, you should have a clear reason: better location, better finishing, services, or limited supply.

If no inquiries arrive within a reasonable period, review description and images before lowering the price. If there are many inquiries without closing, review lease terms, payment schedule, or viewing timing.

Use market data to define the price range, then use listing and collection data to decide the next action.

Data quality can vary by city, district, source, and update date. When source or scope is unclear, treat the decision as Needs Product Review or internal manager review.

Compare any market signal with city, district, property type, data date, and source. Do not rely on a broad average to price a specific unit.

Use market data as a starting point, then review images, description, interest requests, and vacancy duration before changing price.

Turn the article into a small dashboard action: open the related record, review the data, make the appropriate update, then document the outcome so the rest of the team can see it.

If the action involves a financial, regulatory, owner, or tenant-impacting decision, ask the responsible role to review it before final approval.

This is documented as an available workflow, but results can still vary by user permissions, agency settings, and data quality.

If a step described here is not visible in the agency dashboard, treat it as not enabled for your account and check with your admin or Product.