Invalid contact relationship updates and life event issues

Summary:

Employees are incorrectly modifying existing dependent records—reclassifying a "Spouse" as a "Child" or "Ex-Spouse". When these changes are processed as Life Events, the system detects a mismatch between the new relationship and the existing plan tier (e.g., "Employee + Family"). This triggers an automatic "invalid eligibility" status, causing employees to lose their plan enrollment entirely.

Is anyone else experiencing issues with users overwriting existing contact records? I am looking for a solution or best practice to prevent these invalid data entries and ensure these transactions are error-free.

Content (please ensure you mask any confidential information):

Version (include the version you are using, if applicable):