TL;DR: A data quality score is a single 0-100 number that rolls completeness, validity, uniqueness, timeliness, and consistency into one figure you can track over time. It is calculated as a weighted average of those dimensions. As a rule of thumb, aim for 95%+ on customer-facing or regulated data, 85%+ on general operational data, and treat anything below 70% as needing remediation.
What a Data Quality Score Is
A data quality score is a single number that summarizes how fit your data is for its intended use. Instead of asking “is our data good?” and getting a vague answer, a score turns the question into one figure — usually a percentage from 0 to 100 — that you can track, compare, and act on.
The score is sometimes called a data reliability score. Both names describe the same thing: a composite measure that rolls several underlying quality checks into one headline number.
A score on its own is not the goal. Its value is what it lets you do: set a baseline, watch for degradation, and prove that improvement work is paying off.
Why Does a Single Number Matter?
The stakes are not abstract: Gartner estimates that poor data quality costs organizations an average of $12.9 million per year (Gartner, 2020). A single score turns that hidden cost into a number you can watch — and reduce.
Raw quality checks produce dozens of separate signals — fill rates, duplicate counts, format errors, stale records. On their own they are hard to communicate and easy to ignore. A single score solves three problems at once:
| Problem | How a Score Solves It |
|---|---|
| No shared language | One number everyone understands, from analysts to executives |
| No way to track progress | A trend line that shows whether quality is improving or slipping |
| No way to prioritize | A breakdown that points to the weakest dimension or field |
The score is the headline. The breakdown behind it is what you act on.
How Is a Data Quality Score Calculated?
A data quality score is a weighted average of individual quality dimensions. The calculation happens in three steps.
Step 1: Measure Each Dimension
Each dimension is measured as a pass rate — the share of records or values that satisfy a defined rule.
| Dimension | What It Measures | Example Rule |
|---|---|---|
| Completeness | Required data is present | Mandatory fields are populated |
| Validity | Data conforms to a format | Email addresses match a valid pattern |
| Uniqueness | No duplicate records | One record per customer |
| Timeliness | Data is current | Records updated within 90 days |
| Consistency | Values are uniform | Country stored as “USA”, never “US” |
For a deeper look at each, see The Five Dimensions.
Step 2: Apply Weights
Not every dimension matters equally. A weight reflects how important a dimension is to the business, and the weights add up to 100%.
| Dimension | Pass Rate | Weight | Contribution |
|---|---|---|---|
| Completeness | 92% | 30% | 27.6 |
| Validity | 88% | 25% | 22.0 |
| Uniqueness | 99% | 20% | 19.8 |
| Timeliness | 75% | 15% | 11.3 |
| Consistency | 90% | 10% | 9.0 |
| Total | 100% | 89.7 |
Step 3: Combine Into One Score
The contributions are summed into the final figure. In the example above, the data quality score is 89.7 out of 100.
The general formula is:
Data Quality Score = Σ (Dimension Pass Rate × Dimension Weight)
Because the score is weighted, two organizations with the same raw data can report different scores if they weight the dimensions differently — and that is intentional. The weights encode what “good” means for your business.
Levels of Measurement
A single org-wide score is useful for reporting, but the real work happens when you can break it down.
| Level | Question It Answers | Use |
|---|---|---|
| Org / dataset | How healthy is our data overall? | Executive reporting, trend tracking |
| Object / table | Which entity is dragging the score down? | Prioritizing remediation |
| Field | Exactly which column is the problem? | Targeted fixes and validation rules |
A score of 89.7 might hide a single field at 40% completeness. Field-level breakdowns turn a vague number into a specific to-do list.
What Counts as a Good Score?
A good score is ultimately about trust — and trust is now the bottleneck for AI. In Salesforce’s 2025 State of Data and Analytics report, nearly nine in ten data leaders said inaccurate AI outputs came from faulty data, and only 57% were fully confident in their own data (Salesforce, 2025).
There is no universal pass mark. The right target depends on what the data is used for — the same “fit for purpose” principle that underpins data quality generally.
| Score Range | Interpretation | Typical Use |
|---|---|---|
| 95–100% | Trusted | Customer-facing and regulated data |
| 85–94% | Reliable | General operational data |
| 70–84% | Needs attention | Internal or secondary data |
| Below 70% | Not trustworthy | Remediate before relying on it |
Set the threshold from the cost of being wrong. A field that feeds billing or compliance needs a higher bar than one used for occasional internal lookups.
How Do You Track the Score Over Time?
A score measured once is a snapshot. Measured repeatedly, it becomes a trend — and the trend is where the value is.
- Point-in-time scores answer “where do we stand today?”
- Continuous scores answer “are we getting better or worse?”
CRM and operational data decay continuously through manual entry, integrations, and the passage of time, so a score that looked healthy last quarter can quietly slip. Scheduled re-measurement catches degradation early, before it reaches a report or an AI model.
How Does a Data Quality Score Work in Salesforce?
This has become urgent in the AI era: 84% of data leaders say their data strategy needs a complete overhaul before their AI initiatives can succeed (Salesforce, 2025). A continuously measured score is how you close that gap.
Inside Salesforce, the same model applies: dimensions are measured across objects like Accounts, Contacts, and Leads, weighted, and rolled into a single score you can monitor on a dashboard.
DQS (Data Quality Score) measures this natively — no data export — across the five dimensions, and adds PII detection for AI readiness. To see how the score is built and read inside a CRM, continue with:
- How to Measure Data Quality in Salesforce — the score applied to a Salesforce org, also called a data reliability score
- Salesforce Data Quality Dashboard — the metrics worth tracking alongside the headline number
- Data Quality in Salesforce — the wider picture
Frequently Asked Questions
What is a data quality score?
A data quality score is a single number, usually expressed as a percentage from 0 to 100, that summarizes how fit your data is for its intended use. It is calculated as a weighted average of individual quality dimensions such as completeness, validity, uniqueness, timeliness, and consistency.
How is a data quality score calculated?
Each quality dimension is measured as a pass rate — the share of records or values that meet a defined rule. Those dimension scores are then combined into a weighted average, where each dimension’s weight reflects how important it is to the business. The result is a single percentage between 0 and 100.
What is a good data quality score?
There is no universal pass mark, because the right target depends on what the data is used for. As a rule of thumb, 95% or higher is expected for customer-facing and regulated data, 85% or higher is acceptable for general operational data, and anything below 70% signals data that needs remediation before it can be trusted.
Is a data quality score the same as a data reliability score?
Yes. The terms are used interchangeably. Both describe a single composite number that expresses how trustworthy a dataset is by combining several underlying quality dimensions into one figure you can track over time.
Next Steps
- Measure it in your CRM: How to Measure Data Quality in Salesforce
- Understand the inputs: The Five Dimensions
- Start with the foundation: What is Data Quality?
- Benchmark your own data: take the AI Readiness Assessment to get your scores in 3 minutes