SDS / DATA. DECISIONS. SYSTEMS.
SYNTHETIC SAMPLE / NO CLIENT DATA
Can you trust the records behind your report?
This synthetic example shows the structural checks that start a data and reporting review. Findings come from the SDS assessment engine. These are invented records, not a customer case study.
8Rows assessed
1Duplicate rows
3Missing cells
Field checks
| Field | Missing | Observed types |
|---|---|---|
| amount_kes | 1 | number, string |
| customer_id | 0 | string |
| plan | 1 | string |
| renewal_date | 1 | string |
| subscription_id | 0 | string |
What needs review
- Review duplicate records against the intended record key before removing them.
- Review missing fields against business requirements.
- This assessment reports structure and completeness; it does not verify factual accuracy.
What this establishes
- Duplicate rows require a business-key review before removal.
- CSV values remain strings; mixed-type checks are most useful with typed JSON.
- This assessment does not test financial reconciliation, customer churn, accuracy or causation.
- A paid assessment also requires agreed business rules, source checks and a reviewed action plan.
Inspect the evidence
JSON reportEditable reportField statisticsSynthetic source records
Generated 2026-10-14T14:48:51.637ZInput SHA-256: ba297d2a3968d4292b81f225aa234a0d7061e86b04fcf56fe5058d1e185c3111
Start with your reporting problem.
SDS offers a KES 45,000 assessment of up to two agreed data extracts. Scope, timing, access and commercial terms are agreed in a written quote.