I like the logic in VolcanoLvr's system and trying to be consistent, I get it. But once again, its equating a Code system developed by Fannie for a "holistic" view of a property and trying to fit that specific Code identifiers defined system into individual components, which FAQ 34 evidently says Not to do, hey, Fannie said it, not me. I like using Fair, Average, Good, New as condition descriptors in my reports for the individual components, its easier for the reader's of the report to understand as its how these fields were initially intended to be commented on since the beginning of time..... but why fight the "new" UAD code system?...why not include the UAD Individual component explanation comment addendum as provided by VolcanoLvr and Still use the "banned" words as it were like: Average, Good, Excellent, New....the Individual Component comment addendum as provided would equate these to the new UAD code system for the reader...C1 is like "new"; C2 is like "Good", et cetera and the problems solved, isn't it?! #1: I didn't use the UAD codes C1, C2, C3 specifically for individual component descriptions, which Fannie says not to do; I still used Average, Good, et cetera in those cells but I've tied them to those UAD Code descriptions in the Individual Component Commentary addendum which explains what I'm doing for consistency reasons due to UAD's holistic view codes which helps explain how I got from point A to Point B...which is what fannie says to do I think in FAQ 34. Now I think that's a clear logical solution to this problem and it still complies with FAQ 34.