What should every full product review include?

Before the main review library launches, I want the community view on the minimum useful information every full review should contain. The standing framework is published in our Review Methodology.

My baseline is clear product/version identification, who tested it, the test period, how the sample was obtained, the criteria that mattered, direct observations, measurements where useful, limitations, comparison context, and a conclusion that explains the trade-offs instead of hiding them.

A visible test period near the top. It changes how I interpret anything about durability or maintenance.

Exact part and model identification whenever compatibility is discussed. Similar names are not enough.

Price context with a date or range. A value conclusion can age faster than the hardware itself.

Sources for claims that are not direct observations. That keeps the “what we saw” and “what a source says” layers clear.