Small forum idea: an energy label filter

[anika_vale]

I checked the Phoenix property threads and found energy information appears in several different forms. What I could not find was a reliable way to search it.

A standard entry could improve comparisons and reduce repeat questions, but forcing everyone to supply a rating may discourage quick posts from mobile users. Could this begin as an optional structured field with a clear “not provided” choice, then become a search filter once there are enough entries? Tags seem easier to launch, although inconsistent wording could make them less useful over time.

 

[long_frame]

I would use an optional structured field rather than tags. Tags will drift into different spellings and meanings, while a field can feed a search filter. Include “not provided” so nobody has to research a rating just to start a thread.

 

[clear_lane]

What exactly counts as an energy label here? If members mean different things—an official rating, estimated efficiency, or simply utility costs—the filter may produce misleading comparisons. That definition needs settling before the interface.

 

[nia_sage]

That is the difficult part. Phoenix discussions may mention energy information without using one shared label. I’d keep the field narrowly tied to whatever label appears in the property information, with “unknown” for everything else. Utility costs belong in the post because household use varies.

 

[lina_repairs]

I disagree with making it required, even with an unknown option. People will select anything to get past the form, which makes the search less useful. Optional but visible beside the other property details seems a better compromise.

 

[esme.snow]

Could the filter distinguish between “unknown” and “field left blank”? For new posts they might mean the same thing, but blanks on older threads would also show which content was never categorised.

 

[noor_taxes]

That distinction is useful administratively, but probably too fussy for ordinary search results. Show members one “not specified” choice and keep any legacy difference behind the scenes. The mobile layout should not gain another row of nearly identical options.

 

[otis.drew]

Market reports are another wrinkle. One report can discuss many properties with different labels, so a single required value would be wrong. Perhaps enable the field only for threads about an individual property, while reports can still use the phrase in their text.

 

[nia_sage]

Agreed on reports. A limited trial on individual Phoenix property threads would reveal whether enough people complete the field for filtering to be worthwhile. No need to redesign every posting form before seeing whether the information is commonly available.

 

[liv_compares]

Please don’t rely on member-created tags for the trial. Even a small variation breaks consistency, and moderators would end up merging tags. A short optional selector is less flexible but much easier to search.

 

[xavi_flint]

Regional differences matter if this later expands beyond Phoenix. The interface should not imply that every place uses the same energy-label system. A region-specific selector could work, but only after each board has agreed what its choices actually represent.

 

[nia_sage]

My preference after these comments: start with Phoenix, individual-property threads only, optional structured entry, and one public “not specified” state. Put it in the extra-details section on mobile rather than the first screen. That tests search usefulness without slowing the basic post flow.

 

[eli.holt]

What happens to existing Phoenix threads? Manually updating them would be a lot of work and automated guesses could be inaccurate. I’d leave old posts unlabelled and allow authors or moderators to add a value only when they already know it.

 

[ada_lowe]

Leaving the archive alone is sensible, but search results should say that the filter mainly covers newer or updated threads. Otherwise someone may filter by a label and assume older matching properties do not exist.

 

[SteadyRoom]

One caveat: if very few listings provide a usable label, the selector could become mostly “not specified” and add clutter without improving comparison. The trial should look at completion and whether members actually use the filter, not just whether the field can be built.

 

[SteadyRoom]

I’d also avoid backfilling from comments unless a person deliberately edits the field. A passing remark may refer to a renovation target or another property, not the subject listing. Clean gaps are better than confident-looking but unreliable labels.