A Synthetic Data Quality Report is a structured diagnostic document that quantifies the statistical fidelity, privacy preservation, and downstream utility of a generated dataset. It systematically compares the synthetic data against the original real data by measuring univariate column shapes, multivariate pair trends, and boundary adherence to ensure the artificial data is a valid proxy for analytical and machine learning workloads.
Glossary
Synthetic Data Quality Report

What is a Synthetic Data Quality Report?
A comprehensive diagnostic document that quantifies the fidelity, privacy, and utility of a synthetic dataset by comparing its statistical properties against the original real data.
The report typically evaluates three critical dimensions: fidelity metrics (how well distributions and correlations are preserved), privacy metrics (measuring re-identification risk and susceptibility to membership inference attacks), and utility metrics (assessing performance parity via the Train-Synthetic-Test-Real paradigm). Tools like SDMetrics automate this evaluation to provide a standardized, auditable quality posture before synthetic data is released into production pipelines.
Key Components of a Quality Report
A Synthetic Data Quality Report is a structured diagnostic document that quantifies the fidelity, privacy, and utility of a generated dataset by measuring column shapes, pair trends, and boundary adherence against the real data.
Column Shape Analysis
Evaluates univariate distributional similarity between real and synthetic data for each column.
- Kolmogorov-Smirnov (KS) Complement: Measures the maximum distance between cumulative distribution functions. A score near 1.0 indicates high shape fidelity.
- Total Variation Distance (TVD): Quantifies the average probability mass difference across discrete categories.
- Continuous vs. Discrete: Applies appropriate metrics based on data type—KS for numerical columns, TVD for categorical.
Example: A KS complement of 0.92 for an income column means the synthetic distribution overlaps 92% with the real distribution.
Pairwise Correlation Fidelity
Measures how well the synthetic data preserves multivariate relationships between column pairs.
- Correlation Similarity: Compares the correlation matrix of synthetic data against the real data matrix using metrics like Pearson, Spearman, or mutual information.
- Contingency Table Similarity: For categorical pairs, evaluates the normalized similarity of joint frequency tables.
- Detection Risk: Low pair trend fidelity makes synthetic data vulnerable to attribute inference attacks where adversaries exploit broken correlations.
A report typically flags column pairs with similarity scores below 0.70 for investigation.
Boundary Adherence
Validates that synthetic records respect the domain constraints and logical boundaries of the real data.
- Min/Max Violations: Detects synthetic values falling outside the observed real data range (e.g., negative ages).
- Category Adherence: Ensures synthetic categorical columns contain only valid classes present in the real data.
- Referential Integrity: In multi-table synthesis, verifies that foreign keys resolve to existing primary keys.
A boundary adherence score of 1.0 indicates zero constraint violations across all columns.
Privacy Risk Metrics
Quantifies the re-identification risk and membership disclosure exposure of the synthetic dataset.
- Nearest Neighbor Distance Ratio (NNDR): Measures how closely synthetic records mimic individual real records. A high NNDR indicates strong privacy.
- Identical Match Rate: The percentage of synthetic records that are exact copies of real records—should be 0%.
- Membership Inference AUC: Evaluates how easily an attacker can determine if a real record was in the training set.
A privacy-safe report typically requires an NNDR above 0.85 and zero exact matches.
Utility Benchmarking (TSTR)
Employs the Train-Synthetic-Test-Real (TSTR) paradigm to measure downstream task utility.
- A machine learning model is trained exclusively on synthetic data and evaluated on a held-out real test set.
- Utility Score: The ratio of synthetic-trained model performance to real-trained model performance (e.g., F1-score or RMSE).
- Task-Specific: Utility is measured for the intended use case—classification, regression, or clustering.
Example: If a real-trained classifier achieves 0.95 AUC and a synthetic-trained classifier achieves 0.90 AUC, the utility score is 0.947.
SDMetrics Standardized Reporting
Leverages the SDMetrics library to generate a comprehensive, reproducible quality report in a standardized format.
- Quality Report Object: Programmatically generates a multi-metric diagnostic with column-level and table-level scores.
- Visualization Suite: Includes distribution plots, correlation heatmaps, and privacy risk histograms.
- Threshold Flagging: Automatically highlights metrics falling below configurable quality thresholds (e.g., KS complement < 0.80).
SDMetrics integrates directly with the Synthetic Data Vault (SDV) ecosystem for end-to-end evaluation pipelines.
Frequently Asked Questions
A Synthetic Data Quality Report is a diagnostic document that quantifies the fidelity, privacy, and utility of a synthetic dataset. Below are common questions about interpreting and generating these reports.
A Synthetic Data Quality Report is a structured diagnostic document that quantifies how well an artificially generated dataset replicates the statistical properties of the original real data while ensuring no private records have been memorized. It is essential because raw synthetic data is mathematically generated noise unless proven otherwise; the report provides the empirical evidence needed for compliance officers and data scientists to trust the data for downstream machine learning tasks. Without it, you risk deploying models trained on statistically flawed or privacy-leaking data. The report typically measures three orthogonal pillars: statistical fidelity (do column shapes match?), privacy protection (can we re-identify real individuals?), and utility (does a model trained on synthetic data perform as well as one trained on real data?).
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Master the core components that underpin a rigorous synthetic data quality report, from the metrics that measure fidelity to the attacks that test privacy.
Statistical Fidelity
The cornerstone of any quality report, measuring how well the synthetic data replicates the original. It analyzes:
- Univariate distributions: Column shapes, means, and standard deviations.
- Bivariate correlations: Pairwise trends and relationships between columns.
- Boundary adherence: Ensuring synthetic values respect the min/max ranges of real data. High fidelity means the synthetic data is a statistically indistinguishable mirror of the source.
Re-identification Risk
A critical privacy metric that quantifies the probability an adversary can link a synthetic record back to a real individual. The report evaluates this by:
- Measuring the distance between synthetic records and their nearest real neighbors.
- Calculating the proportion of synthetic records that are exact copies of real data (a failure condition).
- Assessing k-anonymity thresholds within the synthetic dataset to ensure each record is sufficiently hidden in a crowd.
Membership Inference Attack
A diagnostic test used in a quality report to gauge privacy leakage. An attacker model is trained to distinguish real records from synthetic ones. The report then measures:
- Attack AUC: The area under the curve of the attacker's classifier. A score near 0.5 indicates the synthetic data doesn't leak membership.
- Precision/Recall: How accurately the attacker can pinpoint which specific records were in the original training set. This provides a direct, empirical measure of privacy risk.
Mode Collapse Detection
A critical fidelity failure that a quality report must explicitly check for. Mode collapse occurs when the generator fails to capture the full diversity of the real data, producing only a few 'safe' examples. The report detects this by:
- Coverage analysis: Measuring the proportion of real data modes represented in the synthetic data.
- Diversity scores: Quantifying the variety of synthetic samples compared to the real distribution. A high-fidelity report confirms that the synthetic data captures the long tail, not just the common patterns.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us