No, there is no mechanism for that. You could blame me for using a forum platform for structured reviews.
There is an option for making review threads look like reviews plus comments that go on forever. I don't like that but the option exists.
Best to not change anything unless you have to. I think what you do is very practical.
Here is my proposal to solve the problem of facts hidden in long threads:
Add a Wiki, enthusiastic members will then be able to collect all the facts hiding in the pages into a very condensed form. I'm not proposing that the review happens in the Wiki, just that the review contains a link to the Wiki (
https://subdomain.domain.topleveldomain/dacs:topping:e30). A Wiki is a communal knowledge database, something all the Forums try to be sooner or later, but fail.
For example, the Topping L30 has hundreds of pages now. 256 to be precise. Good luck searching for the serial numbers of the flawed versions in there. Would there be a Wiki linked, one would read that directly after the review and get the important knowledge of all the 256 pages.
Here is how that could be implemented, in practice: A Dokuwiki gets installed into a subdomain, like wiki.audiosciencereview.com. A few wiki Admins get installed, they can make changes to the Dokuwiki settings (Theme, Title, license of contributions). A few Content Admins get installed, they do what they do around here, remove unwanted users, move things around into the right categories and so on.
The the Users, the most important people: The Users are allowed to edit everything. Some will only login to fix a typo. Some will be enthusiastic enough to condense all the information from an old review thread. Some will collect FAQs. Some can link to research papers for certain topics. Some can write about the basics and options of record cleaning. Only rule would be that everything has to be rooted in facts. Discussion will be in the Forum, not the Wiki.
Technically i would recommend Dokuwiki over a Forum-plugin (which you will regret comes update time) or MediaWiki. It's actual content is stored in text files, which means they can be manipulated/parsed by shell scripts, or read in by PHP software. I run a Dokuwiki in my LAN for about 18 years or so. I also have installed Dokuwiki as a knowledge base in a few companies, with good success. Everyone is able to add value after a five minute introduction, even non-techies. Try that with MediaWiki ;-).
Picture time!

This is the index page of my personal Wiki that i run at home since 2004 (has it really been 18 years?). Just a list of topics i wanted to makes notes for, really:
This is what the LVM site looks like, exquise the german language:
And this is the edit view of that same page, pretty basic, formatting i use mostly are headings (which the wiki then makes in a TOC) and commands (two spaces in front), there is more, but i don't use much of it:
Here is a last picture, a script i wrote for a customers monitoring system 10 years ago:
So this is my proposal. I would consult to get it running and onboard the first Admins and create a sensible first structure, something i have done for a few companies before. You would link to the Wiki from the review and the Users would do the rest.
If it works, it works and will be a monument to our great wisdom. If it fails, we delete it in a few month and deny it ever existed.
