Validation Rules

What is Validation Rules?

Validation Rules are the first line of defense in data quality. They run at the point of capture or update — rejecting invalid email addresses, requiring critical fields, enforcing consistency between related fields. Modern Validation Rules layer on increasingly sophisticated logic: an email address must match RFC format AND not be on the disposable-domain list AND match the company's known domain pattern. The trade-off is friction vs quality — strict validation rejects bad data but also rejects edge cases that are legitimate. Mature systems log rejections so the rules can be tuned over time.

Why it matters

• First line of defense — prevents bad data from entering rather than cleaning it later.
• Layered validation (format + business logic + cross-field) catches more than single-check validation.
• Logged rejections enable rule tuning — too strict creates friction, too loose lets bad data through.

Use cases

• Form-field validation. Form submission requires valid email format and required fields.
• CRM-record validation. CRM rules prevent records with missing critical fields from saving.
• Import validation. CSV import validates every row against rules before commit.