Several areas of RENXT would benefit from a simple Status field (Active/Inactive). RENXT instead relies on date fields, and in some cases, only a single date field (so recording a To and From concept is not really feasible), or else creating "Former" versions of roles and relationship types.
Both of these solutions are less than ideal. The date fields really isn't sufficient on Attributes, especially when you consider that Attributes is meant to contain virtually everything an organization might want to track that doesn't have a designated place in RE. The fields available there are quite limited, so dedicating the Comments field to hold the Start or Stop Date (as was suggested to us) means it can't really be used for something else we may need to track. The Former roles/relationships approach is clunky, explodes your values tables, and makes it more burdensome for people doing queries and pulling lists to be sure they are only including "Active" versions of whatever data type they're interested in.
Areas where I think a Status field would be helpful include:
Constituent Attributes
Address
Org Relationships
Many NXT forms would benefit from two dates (e.g., from/to) rather than one for the same basic reason.