What Are Data Quality Rules?

Data quality rules are the specific, repeatable checks that tell you whether a piece of data is fit for use — or garbage that will waste your team's time.

Think of them as automated gatekeepers. Before a record enters your CRM, your outreach tool, or your analytics dashboard, a data quality rule asks: Does this data meet the standard we've set? If yes, it passes. If no, it gets flagged, quarantined, or rejected.

Without data quality rules, bad data sneaks into your systems quietly. A misspelled company name here. A disconnected phone number there. A duplicate record that splits your engagement history across two contacts. Individually, these look minor. At scale, they destroy pipeline efficiency.

The good news: building effective data quality rules isn't complicated. It just requires knowing which checks matter most for your specific workflows — and applying them consistently.

Why Data Quality Rules Matter in B2B

In B2C, a bad data record might mean one customer gets the wrong coupon. Annoying, but survivable.

In B2B, a bad data record can mean a rep wastes a week chasing a prospect who left the company two years ago. Or your SDR team burns through hundreds of emails that bounce, tanking your sender reputation. Or your pipeline report shows $2M in opportunities that don't actually exist because the underlying contact data is stale.

Bad data compounds. Every system downstream trusts the data it receives from upstream. If your enrichment data is wrong, your segmentation is wrong. If your segmentation is wrong, your campaigns target the wrong people. If your campaigns miss, your pipeline forecasts become fiction.

Data quality rules break this chain. They catch problems at the point of entry — before bad data has a chance to multiply across your stack.

For a deeper look at the specific metrics you should track, see our guide to data quality metrics.

The 6 Types of Data Quality Rules

Data quality rules map to six core dimensions. Each dimension targets a different failure mode. Here's what they look like in practice for B2B teams.

1. Accuracy Rules

Accuracy rules check whether data reflects reality. Not whether it looks right — whether it is right.

Examples:

• Does this email address actually belong to this person at this company?

• Is this phone number a working mobile line — not a landline or a disconnected number?

• Does the job title in your CRM match the person's current role?

Accuracy is the hardest dimension to enforce because it requires external validation. You can't check accuracy by looking at the data alone — you need to verify it against a real-world source.

2. Completeness Rules

Completeness rules check whether all required fields are populated. This is usually the easiest dimension to implement, and the most commonly neglected.

Examples:

• Every contact record must have at least an email or a phone number.

• Every company record must have a domain, industry, and headcount range.

• Every opportunity must have a close date and a dollar amount.

The key word is "required." Not every field needs to be mandatory. Completeness rules should reflect what's actually needed for your workflow — not aspirational data models that nobody fills out. For a broader look at maintaining clean records, check out our data hygiene best practices guide.

3. Consistency Rules

Consistency rules check whether the same data matches across different systems or fields.

Examples:

• The company name in your CRM should match the company name in your marketing automation platform.

• A contact's country code should match their phone number format (a UK contact shouldn't have a US phone prefix).

• The "account owner" in your CRM should match the assigned rep in your outreach tool.

Inconsistency usually isn't a data entry problem — it's a data integration problem. When two systems store the same information independently, drift is inevitable. The fix is either a single source of truth or a sync rule that catches mismatches.

4. Validity Rules

Validity rules check whether data conforms to the correct format or falls within acceptable ranges.

Examples:

• Email addresses must match the name@domain.tld pattern.

• Phone numbers must include a country code and contain only digits (plus formatting characters).

• US zip codes must be exactly 5 or 9 digits.

• Revenue values must be positive numbers.

Validity is the most automatable dimension. A regex pattern or a format check can catch most validity errors at the point of entry with zero manual effort.

5. Uniqueness Rules

Uniqueness rules prevent duplicate records. In B2B databases, duplicates are one of the most expensive data quality failures because they fragment your engagement history, distort reporting, and cause reps to step on each other's toes.

Examples:

• No two contact records should share the same email address.

• No two company records should share the same domain.

• LinkedIn profile URLs should be unique across all contacts.

Deduplication sounds simple until you deal with fuzzy matches — "John Smith at Acme" vs "J. Smith at Acme Inc." — which is why most mature teams combine exact-match rules with probabilistic matching. If your CRM has this problem, our CRM data quality guide walks through how to fix it.

6. Timeliness Rules

Timeliness rules check whether data is current enough to be useful.

Examples:

• Contact data older than 6 months should be flagged for re-verification.

• Job title data should be refreshed quarterly — B2B contacts change roles frequently, and the decay is constant.

• Company headcount data should be updated at least annually.

Timeliness is especially critical for sales teams. An SDR emailing someone who left their company three months ago isn't just wasting time — they're damaging your brand with every irrelevant touchpoint.

How to Build Data Quality Rules (Step by Step)

Most teams overcomplicate this. They try to define every possible rule upfront, build a massive governance framework, and end up with documentation that nobody reads and nobody enforces.

Here's a more practical approach.

Step 1: Identify Your Highest-Impact Data

Start with the data that directly affects revenue. For most B2B teams, that's:

• Contact data — email, phone, name, job title

• Company data — domain, industry, headcount, location

• Pipeline data — deal stage, close date, amount

Don't try to govern everything at once. Pick the 3–5 data objects that matter most for your sales and marketing motions.

Step 2: Define "Good Enough" for Each Field

For each critical field, define the minimum acceptable standard. Be specific and binary — every rule should produce a clear pass or fail.

Bad rule: "Email should be valid."

Good rule: "Email must pass format validation, resolve to an active MX record, and not return a hard bounce from a verification service."

The difference matters. Vague rules can't be automated. Specific rules can. For a full methodology, see our data quality framework guide.

Step 3: Decide Where to Enforce Each Rule

Rules can be enforced at three points:

• At entry: Validation before data enters your system (form validation, API checks, import rules).

• In transit: Checks that run during data syncs between systems (ETL rules, integration filters).

• At rest: Periodic audits that scan existing data for violations (scheduled jobs, data quality dashboards).

Entry-point enforcement is always the cheapest. Catching a bad email before it enters your CRM costs almost nothing. Cleaning it up after it's triggered a bounced campaign, updated a lead score, and been synced to three other tools? That costs real time and money.

Step 4: Automate What You Can

Manual data quality reviews don't scale. If you have more than a few hundred records, you need automation.

The good news: most data quality rules are inherently automatable. Format checks, completeness checks, uniqueness checks — these are all things a script or a tool can handle without human intervention.

Save human review for the exceptions: fuzzy duplicate matches, ambiguous job titles, edge-case company hierarchies. Everything else should run automatically on a schedule or in real time.

Step 5: Monitor, Don't Just Enforce

Rules without monitoring are rules you'll eventually forget about. Set up a simple dashboard (or even a weekly report) that tracks:

• Rule pass rate: What percentage of records pass each rule?

• Failure trends: Are failure rates going up or down?

• Top offenders: Which data sources or entry points produce the most failures?

This gives you the feedback loop you need to refine rules over time. A rule that fails 80% of records isn't enforcing quality — it's misconfigured. A rule that passes 100% of records isn't useful — it's too lenient. For tracking these numbers effectively, our guide to data quality assessment covers the full process.

Data Quality Rules Examples for B2B Sales Teams

Theory is nice. Here are concrete rules you can implement this week.

Contact Data Rules

Company Data Rules

Pipeline Data Rules

Common Mistakes When Implementing Data Quality Rules

Building too many rules too fast. Start with 5–10 rules that address your biggest pain points. You can always add more. A team that enforces 10 rules consistently beats a team that has 200 rules on paper and follows none of them.

Making every rule a hard block. Not every data quality issue deserves to stop a record from entering your system. Use a tiered approach: hard blocks for critical fields (email format, duplicate detection), soft warnings for nice-to-haves (missing industry, incomplete address). If you block too aggressively, reps will start gaming the system with junk data just to get records through.

Ignoring data at the source. Rules that only run inside your CRM miss the problem. If your data enters through CSV imports, API integrations, form submissions, and manual entry, you need rules at every entry point. The difference between data integrity and data quality often comes down to where in the pipeline you're catching issues.

Treating rules as set-and-forget. Business requirements change. Your ICP evolves. New data sources get added. Review your rules quarterly. Kill the ones that aren't catching real issues. Tighten the ones that are letting bad data through.

Not assigning ownership. If nobody owns data quality, nobody maintains the rules. Assign a data quality governance owner — whether that's RevOps, a data team, or a designated person on each team who reviews violations weekly.

Enforcing Data Quality Rules at Scale

There are three tiers of enforcement maturity.

Tier 1: Manual Audits

Someone exports data from your CRM, runs it through a spreadsheet, and flags issues. This works for small teams (under 1,000 records), but it doesn't scale and it's always reactive — you're finding problems after they've already caused damage.

Tier 2: CRM-Native Rules

Most CRMs have built-in validation rules, required fields, and deduplication. This is table-stakes for any team. Set up format validation on email and phone fields, require key fields before records can be saved, and enable duplicate detection. It covers validity, completeness, and basic uniqueness.

Tier 3: Automated Verification Pipelines

This is where serious B2B teams operate. Instead of just checking format, you verify data against external sources in real time. Email verification services confirm deliverability. Phone validation services confirm the number is active and mobile. Enrichment providers fill in missing fields and update stale records automatically.

The most effective approach combines all three — but if you're just getting started, begin with Tier 2 and add Tier 3 for your highest-impact data (contact emails and phones).

Start With Rules That Actually Matter

Data quality rules aren't a theoretical exercise. They're the difference between a sales team that burns cycles on bad data and one that spends their time actually selling.

Start small. Pick the 5 rules that address your most painful data problems. Automate enforcement where you can. Monitor pass rates. Iterate.

For contact data specifically, the highest-leverage rules are the hardest to enforce manually: Is this email actually deliverable? Is this phone number a real mobile line? Does this data belong to the person you think it does? These are accuracy and validity checks that require external verification — which is exactly what waterfall enrichment with triple email verification and multi-step phone validation handles automatically. FullEnrich's built-in verification pipeline applies these checks across 20+ providers for every contact, so unverified data gets filtered before it ever reaches your CRM.

Want to see what clean, verified contact data looks like? Start with 50 free credits — no credit card required.