Applying Quality Control to Data

Applying Quality Control To Data — Interactive Notes
STANDALONE NOTES

Applying Quality Control To Data

An interactive guide to quality assurance, quality dimensions, rules and metrics, validation, verification, profiling, reconciliation, peer review, audits, automated checks, calculations, and visual validation.

Quality AssuranceValidationVerificationProfilingQuality Metrics
PROFILE
VALIDATE
VERIFY
RECONCILE
REVIEW
01

Why Data Quality Matters

Quality data supports quality reporting. Inaccurate, incomplete, or inconsistent data can undermine analysis and reduce confidence in decisions.

Quality Assurance

The process of ensuring data used in analysis is high enough quality to give decision makers confidence in the findings. Quality assurance is also commonly described here as data cleaning.

Validation

Checks whether data meets required standards, structures, formats, systems, and business requirements.

Verification

Confirms whether data is accurate or true. An unusual value may be structurally valid but still require verification.

Quality Checks

Quality checks should be routine and should continue throughout the project, especially after manipulation, transformation, or transfer.

Core idea

A value can pass a format rule and still be wrong. Quality control therefore needs both validation and verification.

02

Five Dimensions of Quality

Data integrity is reflected through accuracy, completeness, and consistency, with timeliness and uniqueness also recognized as increasingly relevant quality dimensions.

Completeness

Are all expected and required fields populated?

Accuracy

Are the values in the fields correct?

Consistency

Are values entered in the same intended way according to business rules?

Timeliness

Is the data current and available within the expected timeframe?

Uniqueness

Are records or values that should be distinct free from duplication?

ProblemExampleDimension
Missing emailA required email field is blank.Completeness
Wrong product nameAn old product name remains after a rename.Accuracy
Mixed credentialsMD, M.D., PhD, PHD, Lpn, LPNConsistency
Week-old sales extractThe decision requires current sales.Timeliness
Repeated emailMultiple records use the same email where uniqueness is expected.Uniqueness
03

Why Quality Problems Appear

Quality issues can originate in people, system design, transformations, transfers, or the combination of independently maintained data.

Mergers & Acquisitions

Organizations may combine data built under different standards, structures, and systems.

Manual Manipulation

Manual entry and editing create opportunities for human error.

Transformations

Transformations should be checked to confirm they produced the intended result.

Human Error

Wrong entries, calculations, joins, or other mistakes can be difficult to detect in large datasets.

Data Transfers

Analysts need to confirm that the intended data reached the intended destination without missing or unwanted records.

04

Rules, Metrics & Quality Targets

Governance teams may define quality rules and measurable standards. These metrics can function as KPIs for evaluating quality and tracking improvement.

Business Rules

Constraints on how data is captured can reduce invalid entry. Required names, valid email structure, and standardized location codes are examples.

Quality Targets

Different fields can have different quality goals based on business importance.

Pass / Fail

Analysts may report how many rows pass all checks and how many fail the required standard.

Illustrative quality score

Expected records
1,000
Passing checks
950
Quality rate
95%
Process question

When data fails a quality check, investigate whether the entry itself was bad or whether the data did not conform to the required rules or process.

05

Data Profiling

Profiling data early establishes reasonable expectations and creates reference points that help analysts recognize suspicious results later.

Record Counts

Know how many records exist before and after movement or transformation.

Expected Totals

Knowing an expected aggregate can reveal incorrect math or joins when a result suddenly changes dramatically.

Fields & Types

Inspect fields and data types before relying on them.

Nulls & Redundancy

Profiling can include quality metrics such as missing values and redundant data.

SOURCE PROFILE10,000 records$5M expected revenueANALYSIS RESULT$10M ?INVESTIGATEmath · joinsduplicates · filters
06

Reconciliation, Cross-Checks & Peer Review

Quality control becomes stronger when results are compared against independent sources and reviewed by another person.

Example

If accounting reports total sales of 35,000 while marketing reports 50,000, do not assume one is simply wrong. Their definitions may differ—for example, actual sales versus projected sales.

07

Automated Validation

Software can enforce rules at entry or during pipelines, quickly processing large volumes and reporting which records passed or failed.

Email Rules

Validation can require an @ symbol and an acceptable ending before an email is saved.

Format Rules

Phone numbers and dates can be constrained to expected formats.

Transfer Checks

Validation tools can report successful and failed records and often provide reasons for failures.

Versioned Rules

Rules should be version-controlled because requirements can change over time, such as when an organization expands internationally.

Important limitation

Automated validation cannot guarantee truth. A birth date can have the correct format while containing the wrong year, so verification is still necessary.

08

Verification Methods

Verification asks whether the data is accurate. Analysts should examine suspicious field values, record counts, calculations, and other evidence that can confirm the data.

FIELD VALUES
look outside the norm
RECORD COUNTS
detect possible loss
CALCULATIONS
spot-check logic
COMPARE
source vs. report

Field Values

Investigate values that appear outside the norm and consult the team responsible for the data when useful.

Data Loss

Records can be lost, incomplete, poorly named, or dropped during ineffective processes or incompatible transfers.

Calculation Review

Spot-check intended outcomes and verify that formulas and equations received the correct inputs.

09

Test & Explore Visuals

Quality control continues after the data is calculated. Reports and visuals must also be validated against business requirements and user expectations.

Correct Labels

Check titles, labels, text, and spelling.

Correct Sorting

A visual titled “Top 5 Products” should actually display the top five rather than the bottom five.

Business Meaning

Confirm the visual meets the intended requirement and makes sense to users.

Consistent Encoding

Use visual encodings consistently across the project; the same category should retain the same meaning wherever it appears.

10

Quality Control Workflow

Quality is not a single final check. Validation and verification should occur throughout a data project rather than being treated as a single final check.

PROFILEcounts · types · nullsVALIDATErules · structureVERIFYaccuracy · countsRECONCILEcross-check sourcesREVIEWpeer · audit · visualsACCURATE · COMPLETE · CONSISTENT+ timely + unique → confidence in reporting
11

Knowledge Check — 20 Questions

Review the key quality-control concepts covered throughout these notes.

1. What is the overall goal of quality assurance (QA)?

Answer: A. Ensure data is high enough quality to support confident findings

2. Quality data is described as data that is:

Answer: A. Accurate, complete, and consistent

3. Data completeness asks whether:

Answer: A. Expected and required fields are populated

4. Data accuracy means:

Answer: A. A field's value is correct

5. Data consistency means:

Answer: A. Data follows intended standards and business rules consistently

6. Timeliness means data is:

Answer: A. Up to date and relevant to the triggering event or required timeframe

7. Uniqueness means:

Answer: A. Records or values expected to be distinct are not duplicated

8. Who will likely determine organizational rules and metrics for quality standards?

Answer: A. The data governance team

9. A quality metric can be used as:

Answer: A. A KPI to evaluate data quality and monitor progress

10. Why should transformed data receive quality checks?

Answer: A. To ensure transformations worked as intended

11. Data profiling should ideally occur:

Answer: A. Before working deeply with a data set

12. Which is useful during data profiling?

Answer: A. Record counts and expected totals

13. Reconciling data means analysts may need to:

Answer: A. Compare separate sources that should describe the same information

14. The ultimate goal of peer review is to:

Answer: A. Help ensure what is being reported is accurate

15. A data audit assesses data quality and:

Answer: A. Whether the data can achieve a specific purpose or objective

16. Automated validation can:

Answer: A. Prevent some invalid entries from being saved

17. Why should validation rules be version-controlled?

Answer: A. Rules can change over time

18. When verifying transferred data, record counts help detect:

Answer: A. Possible data loss

19. Calculations should be verified by:

Answer: A. Spot-checking outcomes and confirming correct inputs/formulas

20. When testing visuals, an analyst should confirm:

Answer: A. Labels, sorting, business requirements, meaning, and consistency
APPLYING QUALITY CONTROL TO DATA · INTERACTIVE NOTES · MARBLE LIGHT BLUE EDITION