Profiling and join checks
Column types, fill rates, ranges, and top values for every source in scope, run on real extracts. Join checks show how many keys in one system turn up in the systems it has to join to.
Test the data behind one decision before you pay to build on it.
A short PDF to share with your team. It covers what is in the package, how it works, and a worked example.
Your download has started.
We also emailed the link to . It works for 7 days.
Download didn't start? Get the PDF
Want to try it on your own data? Talk to us.
A use case is approved from a slide. A few weeks into the build, the team finds duplicate customer IDs, a source nobody has access to, and fields that are mostly blank. Half the budget is gone and the decision is no better.
Column types, fill rates, ranges, and top values for every source in scope, run on real extracts. Join checks show how many keys in one system turn up in the systems it has to join to.
Access, ownership, completeness, validity, uniqueness, timeliness, join coverage, and personal data, each scored against what the decision needs. Columns that look like personal data report counts and never show sample values.
Each gap is ranked by the effort to fix it and how much it affects the decision. Source owners review the list and correct it where they know better.
A draft brief for the Decision Owner to sign, a plan for the first build increment, and a verdict of proceed, fix first, or stop. The verdict can gate a pipeline, and a JSON record tracks readiness as fixes land.
With the Decision Owner, agree what the decision is, who acts on it, how you will know it improved, and what that is worth.
For each system, record the owner, the access route, the business key, the fields needed, how fresh the data must be, and what it joins to.
A recent full extract or a large sample is enough. Direct database queries work too.
Set thresholds with the Decision Owner before the run, so nobody argues about the results afterward.
Go through the ranked gaps with the source owners.
The Decision Owner signs the brief, or the work waits for fixes or stops. Either way there is evidence behind the call.
The decision pulls from a CRM, an ERP, and a helpdesk. We seeded the sample data with the problems real projects hit.
The run catches each problem, ranks the gaps, and recommends fixing the data first. It writes the readiness report, the draft Decision Brief, and a record of every check.
Ask about the Data Readiness Assessment
Dex answers from our own pages and links to where it found the answer.
Name it and the systems behind it. We will tell you what a readiness check would look at first.