Keeping posts quick while improving London closing-cost searches

coffeeAndCompass

Developer
Verified Pro
I am torn between a simple tag, which is easy to add, and a structured field, which would produce more consistent search results. On the London board, closing-cost information is difficult to find across valuation and market threads, and the same questions keep resurfacing.

A required field might improve consistency but also create more moderation work and discourage quick mobile posts. Free-form tags have the opposite weakness: members may use different wording for the same topic. Would an optional field with an “unknown” choice give search filters useful data without making the posting form burdensome, and what should it capture—a total, a percentage or itemised costs?
 
I’d choose an optional structured field that can feed a search filter. Tags will drift into variations such as “closing costs,” “fees” and abbreviations, so the search results will soon become patchy. Keep the posting form to one extra line with an “unknown/not provided” option rather than making people calculate something before posting.
 
What exactly would members enter: a total amount, a percentage, or the individual costs included? A single figure could look comparable while covering different things. It also matters whether the number is an estimate from a listing discussion or costs known after completion.
 
That ambiguity is why I wouldn’t make a bare number mandatory. For valuation and market-report threads, perhaps require only a status such as “estimated,” “actual,” “not stated” or “not applicable.” If an amount is entered, currency and a short note on what it covers could remain optional. That creates something searchable without pretending every figure has the same basis.
 
I’m not convinced a total-cost filter would travel well beyond London. Costs and terminology differ by region, transaction and buyer circumstances, so sorting from low to high may be misleading. A filter for whether closing-cost information is present would be safer; members could then read the breakdown rather than compare unlike totals.
 
On mobile, hide the details behind an “Add closing-cost information” row. Tapping it could reveal amount or range, currency, estimate/actual status and a note. People who do not have the information would barely notice it, while detailed posters could still make their threads searchable.
 
I disagree slightly with leaving the whole thing optional. Optional fields often produce too little consistent data to support a useful filter. On the relevant thread types, one required tap—provided, not provided or not applicable—would be enough. The amount and explanation can stay optional. Moderators should only correct obvious misclassification, not judge whether someone’s estimate is accurate.
 
Old threads are another trap. I would not ask moderators to retrofit them or infer figures from prose. Launch it for new threads, allow authors to add it when editing older posts, and make the search filter clear that older results may lack the field. That keeps migration effort contained.
 
A limited London-board trial sounds sensible before applying it across regional forums. Use the required status suggested by nicolas_novak only for valuations and market reports, then place the optional details behind the mobile-friendly expansion kenji_lee described. After a trial, the forum can see whether members fill it in consistently and whether anyone actually uses the filter.
 
Back
Top