CRM Data Validation Rules: 6 Examples for Sales Teams

You made "Next Step" a required field three months ago. Your pipeline still has "TBD," "Will circle back," and blank dates sitting on every third deal. You required "Close Date" and reps are entering the last day of the quarter every time, regardless of what the buyer actually said.

Required fields lower the barrier to data entry. They do not enforce data quality. That is the job of validation rules, and most sales teams have not set them up.

According to a 2025 report from Validity, 76% of organizations say less than half of their CRM data is accurate. Required fields have been standard for years. Validation rules are the missing layer that most teams skip.

Required Fields vs. Validation Rules: Why the Distinction Matters

A required field says: this field cannot be empty.

A validation rule says: what you enter must meet a specific standard before the record saves.

The gap between those two concepts is where most CRM data quality breaks down. A rep can satisfy a required phone field by typing "123," satisfy a required close date by picking any future date, and satisfy a required "Next Steps" field by writing "follow up." All three fields appear populated. None of them are useful.

Validation rules close that gap. They enforce format (a phone number must have 10 digits), logic (a close date cannot be in the past), and conditional requirements (if a deal moves to Closed Lost, a lost reason must be selected). A rep cannot clear the save alert with junk input because the rule checks the value itself, not just whether the field has something in it.

People.ai research found that 74% of targeted contacts or activities are never recorded in CRM systems at all. Of the data that does get entered, a significant portion is low-quality placeholder text. Validation rules address the second problem. Combined with automation that captures activity from email and calls, they address both.

The six rules below represent the highest-leverage starting points for a B2B sales team running HubSpot, Salesforce, or Pipedrive.

The 6 CRM Validation Rules Worth Setting Up

Rule 1: Close Date Must Be a Future Date at Creation

The problem it solves: Reps select the last day of the quarter as a default close date without any connection to what the buyer has communicated. A historical date in the past, or a date set months out with no supporting conversation, corrupts your forecast from the first save.

What the rule does: Blocks any new deal from being saved with a close date in the past, and optionally flags dates more than 180 days out for manager review.

Setup:

• Salesforce: Create a validation rule with formula CloseDate < TODAY() and error message "Close date must be today or in the future."
• HubSpot: HubSpot's date property validation can enforce a minimum date. For dynamic logic (relative to today), use a Workflow that triggers on deal creation or update and flags records where the close date field predates the current date.
• Pipedrive: Set a required field rule on deal creation. For date logic, use an automation that runs when a deal is created and sends a task to the rep if the close date is in the past.

Severity: High. A wrong close date corrupts every forecast view the moment the deal is created.

Rule 2: Lost Reason Required on Closed Lost Stage

The problem it solves: Deals that move to Closed Lost with no reason attached are invisible to analysis. You cannot improve your process if you do not know why you are losing. At Futureman Labs we see this often: teams do solid win-loss tracking for won deals and almost none for lost ones.

What the rule does: Prevents a deal stage change to Closed Lost unless the "Lost Reason" field is populated from a defined picklist.

Setup:

• Salesforce: Validation rule with formula AND(ISPICKVAL(StageName, "Closed Lost"), ISBLANK(Lost_Reason__c)) with error message "Please select a lost reason before marking this deal as Closed Lost."
• HubSpot: Create a Workflow that triggers when Deal Stage equals Closed Lost and checks whether Lost Reason is empty. If it is, re-open the deal to the previous stage and send the rep a task to complete the field. (HubSpot does not support gate-on-save for custom picklists natively; the Workflow approach is the practical alternative.)
• Pipedrive: Use a stage-required field for "Lost Reason" so it appears as mandatory before the deal can be marked lost.

Severity: High for any team doing quarterly win-loss reviews. Without this rule, your lost reason data is self-selected and incomplete.

Rule 3: Phone Number Format Enforcement

The problem it solves: Phone numbers entered as "555-1234," "5551234," "(555) 123-4567," and "+1-555-123-4567" all mean the same thing but break every automated call-logging and dialer integration that depends on consistent format. Sales teams with BDR/SDR functions are especially affected.

What the rule does: Checks that phone number fields contain exactly 10 digits (US) or match a defined pattern for your market, blocking non-conforming values.

Setup:

• Salesforce: Use a validation rule with a REGEX formula: NOT(REGEX(Phone, "^\\(\\d{3}\\)\\s\\d{3}-\\d{4}$")) for (555) 123-4567 format, or a simpler digit-count check.
• HubSpot: HubSpot's phone number property type includes built-in format validation when the property is set to the Phone Number type (not plain text). If your phone properties are legacy Text type, migrate them or create a Workflow that checks digit count and flags records.
• Pipedrive: Pipedrive's Phone field type handles format natively for standard formats. Add a field validation note in your internal CRM documentation for non-standard markets.

Severity: Medium. Critical if your team uses click-to-call, automated dialer sequences, or SMS outreach tools that expect consistent phone formatting.

Rule 4: Deal Amount Must Be Greater Than Zero

The problem it solves: A deal with a zero-dollar or blank amount looks like legitimate pipeline in a coverage ratio report but contributes nothing to forecast. This often happens when a deal is created quickly from a form fill or lead import before anyone assigns a value.

What the rule does: Blocks a deal from advancing past an early stage (typically "Qualified") without a non-zero deal amount.

Setup:

• Salesforce: Validation rule AND(NOT(ISPICKVAL(StageName, "Prospecting")), Amount <= 0) prevents any stage past Prospecting from saving with zero or blank amount.
• HubSpot: Use a stage-gated required field combined with a number property minimum of 1. For conditional enforcement (only after stage 1), use a Workflow that checks amount on stage change.
• Pipedrive: Add Deal Value as a required field for stages after "Qualified." Use the required fields by stage feature to gate this per stage.

Severity: Medium to high depending on your pipeline volume. On a small team the blanks are easy to spot manually; at 50 or more open deals, zero-amount deals silently inflate your coverage ratio.

Rule 5: Next Step Text Required if Next Step Date Is Set

The problem it solves: A next step date with no description is meaningless. "Meeting on Thursday" tells the manager nothing. This rule enforces that the two fields travel together: if a rep sets a next step date, they must also enter what the next step is.

What the rule does: Blocks the save if "Next Step Date" is populated but "Next Step" (description) is blank.

Setup:

• Salesforce: Validation rule AND(NOT(ISBLANK(Next_Step_Date__c)), ISBLANK(Next_Steps)) with error message "Please describe the next step before setting a next step date."
• HubSpot: Workflow-based enforcement. When "Next Step Date" is set and "Next Steps" is empty, create a task for the rep and optionally revert the date field.
• Pipedrive: Create a Pipedrive automation that triggers when Next Activity Date changes and sends a reminder if the activity note is blank.

Severity: Medium. This rule has an outsized impact on the quality of pipeline review conversations because managers can actually coach off next step descriptions.

Rule 6: Stage Advancement Gate on Qualification Fields

The problem it solves: Deals move to "Proposal Sent" or "Negotiation" before anyone has documented budget, authority, or timeline. The deal looks more advanced than it is. Forecasts built on it are wrong.

What the rule does: Requires specific fields to be non-empty before a deal can advance past a defined stage. Common gate points are "Proposal" (budget confirmed, decision maker identified) and "Negotiation" (mutual close plan documented).

Setup:

• Salesforce: Create a validation rule per stage transition. Example for Negotiation: AND(ISPICKVAL(StageName, "Negotiation"), ISBLANK(Budget_Confirmed__c)).
• HubSpot: Use HubSpot's "Required fields by pipeline stage" feature (available in Sales Hub Professional and above). Define which fields must be populated before the deal can advance to each stage.
• Pipedrive: Pipedrive's required fields feature in the Kanban view enforces this natively. Set which fields are required per stage in pipeline settings.

Severity: High for any team using a qualification framework like MEDDIC or BANT. Without stage gates, pipeline coverage reports over-state deal readiness. For more on the underlying qualification tracking, see how to track MEDDIC in CRM without it going stale.

How to Roll Out Validation Rules Without Killing Rep Morale

The most common failure mode is not technical. It is implementing eight rules at once across all stages, triggering rep frustration, and watching the team find creative workarounds.

A practical rollout looks like this:

Week one: Implement one rule that solves the most obvious problem on your team. If your forecast is corrupted by wrong close dates, start with Rule 1. If your lost-reason data is empty, start with Rule 2.

Week two: Monitor. Look at how many saves the rule is blocking. If reps are hitting the validation error on more than 20% of saves, the rule is either too aggressive or the problem is more systemic than a data quality rule can fix alone.

Week three and beyond: Add one rule at a time, with a short team communication explaining what changed and why.

Always write error messages in plain English. "Please select the deal's primary contact before advancing to Proposal" is more helpful than "Validation error: primary_contact_id null."

What Validation Rules Cannot Fix

Validation rules stop the obvious errors: a blank field, a malformed phone number, a close date set to January 1 without any supporting evidence. They cannot catch judgment errors.

A rep can enter a close date three months out with a clean confidence score, and no validation rule will flag it as optimistic. A rep can write a detailed next step ("send contract") without any record of the buyer actually agreeing to receive one. The fields look right. The data is still wrong.

This is the layer that requires reading the underlying conversation: what did the rep and buyer actually discuss? What was agreed? What changed since the last call? Most CRMs cannot answer that from field values alone.

Tools that auto-capture email and call activity and surface what was actually said help bridge this gap. When a pipeline reviewer can look at the raw conversation thread alongside the CRM fields, they can spot a field that does not match the conversation. This is the same principle behind Company Brain's pipeline visibility approach, where rep activity is captured automatically and deal records reflect what the data actually says, with reps approving any field updates before they write.

Validation rules and activity capture work together: one prevents garbage data at the gate; the other ensures the data that passes the gate reflects real buyer conversations.

A Starting Point That Actually Works

The fastest way to improve CRM data quality is to combine three things: a short list of stage-gated required fields (see which CRM fields to enforce and when), validation rules that check format and logic on the fields that matter most, and automated activity capture that reduces how much manual typing reps do in the first place.

None of this requires a six-month CRM implementation project. Most teams can roll out two or three validation rules in an afternoon and see measurable improvement in field completion quality within a week.

Start with the close date rule. Every team has this problem. Fix it this week and your next pipeline review will be visibly different. Then work through the list above one rule at a time until the data your team relies on for forecasting actually reflects what is happening in the field.

For a broader look at how to measure whether all of this is working, CRM data quality scoring covers the metrics to track and what good looks like for a B2B sales team.

Frequently Asked Questions

What is the difference between required fields and CRM validation rules?

Required fields force a rep to enter something before saving a record. Validation rules check whether what they entered is actually correct: a required phone field accepts 1234 without a validation rule in place. Validation rules enforce format, logic, and conditional requirements so the data that gets in is actually useful.

What are examples of CRM data validation rules for sales teams?

Common examples include: phone numbers must contain exactly 10 digits; close dates must be in the future at creation; lost reason must be populated when a deal moves to Closed Lost; deal amount must be greater than zero; next step text must be filled if a next step date exists; and stage advancement must require specific fields to be complete.

Do validation rules slow down sales reps?

Well-designed validation rules add only a second or two to the save flow and only trigger when something is wrong. The slowdown comes from poorly scoped rules that fire on every save rather than on specific conditions. Gate rules by stage so they only apply when the data actually matters for forecasting.

How do I set up validation rules in HubSpot?

For format validation, go to Settings, then Properties, select the object type such as Deal or Contact, find the property, and edit it to add format requirements. For conditional logic across multiple fields, use HubSpot Workflows to check field values on stage change and flag or correct records that fail the check.

Can Pipedrive enforce CRM data validation rules?

Pipedrive's native validation is lighter than HubSpot or Salesforce. Stage-required fields are the primary built-in option. For more complex logic, use Pipedrive automations or connect a tool like n8n or Zapier to check field values after a deal stage change and alert reps to missing or malformed data.