Could market threads include sold-price history?

L

ledger.brisk

Homeowner
A structured field would make sold-price threads easier to search, while an optional tag would keep posting quicker. I can see the case for both on the Cape Town board: the first risks cluttering the mobile form and creating more moderation work, but the second may be skipped or applied inconsistently.

Could a compact optional field feed the search tool automatically when completed? It would also help to agree on the minimum information meant by sold-price history—perhaps respondents can suggest whether price alone is useful or whether a sale date and area are essential.
 
I would make it an optional structured field rather than a required one. Members starting general discussions may not have a verified sale price, and forcing an entry could discourage posts or produce guesses. If completed, the field could feed a search filter automatically.
 
What information would count as “history”? Just the latest sold price, or price plus sale date and area? Without at least a date, two Cape Town figures could look comparable while referring to very different periods. The field needs to stay small, but its meaning also needs to be clear.
 
I’m not convinced a normal tag is enough. People will create variations such as “sold price,” “sale price” and “sold history,” which weakens search usefulness. A predefined tag could work, but once the information is structured, a dedicated filter seems more useful than displaying another tag.
 
There is also the mobile layout to consider. Three short optional inputs—sold price, sale date and location—could fit behind an “add sale details” control. That keeps the basic composer uncluttered. Property type might help comparisons too, although adding too many boxes defeats the original aim of quick posting.
 
I’d push back on requiring a location more detailed than what the thread already provides. Different regional boards may organise places differently, and a design that suits Cape Town may become awkward elsewhere. Start with a standard sold-price marker and date, then let the existing board and thread text provide the local context.
 
That would reduce moderation as well. A short fixed form is easier to understand than a collection of free-form tags, but moderators still shouldn’t have to confirm every figure. Perhaps the field should describe what the member entered, rather than implying the forum verified the sale.
 
How would old threads be handled? A large migration sounds like a lot of work and may be unreliable if prices are buried in comments. I’d apply the feature to new threads first, then allow members or moderators to add the field to older high-value discussions when the information is already explicit.
 
A useful compromise might be:

• optional “sold-price information” switch when posting; • price and date fields appearing only when switched on; • one controlled label generated automatically; • filters for threads with that information; • no requirement to retrofit the archive.

That gives search some consistency without slowing every poster. The wording should also avoid suggesting that an asking price is a completed sale.
 
The optional switch plus structured price and date sounds like the best direction. I agree that a free-form tag would fragment quickly, and mandatory fields would be wrong for general market threads. Starting with new posts also avoids turning this into an old-thread cleanup project. If there were a simple mobile preview, it would be easier to judge whether adding property type is still lightweight or one field too many.
 
You must log in or register to reply here.
Back
Top