When you need to cover your ass, providing feedback for rejection is always a bad idea. If you're dealing with a pushy sales person and you give them a reason w

When you need to cover your ass, providing feedback for rejection is always a bad idea. If you're dealing with a pushy sales person and you give them a reason why you're saying no, you've given them something to work with. They can debate whether your reason is legitimate. They can promise to meet that criteria, then you have no reason to say no. The same can apply in ending or rejecting a romantic relationship. If you give a reason, it can create an expectation that when the reason changes, the rejection will change as well. Put this in a legal context and giving a reason for rejection is just asking for trouble. First of all, the rejected candidate could argue that your reason was illegal. Second, they could argue you were misinformed, so the reason is not legitimate. Finally, they could argue they've changed, so you have to reconsider them, since your stated reason no longer applies. In all these cases, it's easiest to provide no reason whatsoever. (See also Miss Manners, who frequently has advised repeating a meaningless, "No, because I can't; I can't because I won't be able to" type response until the other person gives up.) Giving a reason creates a focus for an argument. No reason, no argument, just the other person incessantly begging for a reason, which is never going to make them look good.