I'd say that once you're at the point of formalizing reviews, you should have requirements documentation, and then, most of this becomes just an instance of "does the implementation meet the specification?".

When I worked in aerospace, every feature was linked to the requirement line that it implemented. Then it's easy to identify functionality which was removed (or left in) by mistake.