--- title: "Checking data for a review: part 2 (completeness)" description: How we check that a data extract has every record it should, what causes gaps, and why the same check matters for day-to-day reports and models. image: https://riskinsights.com.au/hubfs/checking-data-part-2.png --- [Skip to content](https://riskinsights.com.au/blog/the-checks-we-run-before-using-data-for-a-review-part-2#main-content) [![Risk Insights - Logo - (RGB, Horizontal, Small)](https://riskinsights.com.au/hs-fs/hubfs/Risk%20Insights%20-%20Logo%20-%20(RGB%2c%20Horizontal%2c%20Small).png?width=200&height=40&name=Risk%20Insights%20-%20Logo%20-%20(RGB%2c%20Horizontal%2c%20Small).png)](https://riskinsights.com.au) - [Articles](https://riskinsights.com.au/blog) - [Approach](https://riskinsights.com.au/approach) Show submenu for Approach - [Commissions (Accuracy)](https://riskinsights.com.au/broker-partner-commission-accuracy-reviews) - [Claims Fraud (Fairness)](https://riskinsights.com.au/claims-fraud-fairness-reviews) - [Fees and Charges (Accuracy)](https://riskinsights.com.au/fee-and-charge-accuracy-reviews-risk-insights) - [About](https://riskinsights.com.au/about) - [Contact](https://riskinsights.com.au/contact) Open main navigation Close main navigation - [Articles](https://riskinsights.com.au/blog) - [Approach](https://riskinsights.com.au/approach) Show submenu for Approach - [Commissions (Accuracy)](https://riskinsights.com.au/broker-partner-commission-accuracy-reviews) - [Claims Fraud (Fairness)](https://riskinsights.com.au/claims-fraud-fairness-reviews) - [Fees and Charges (Accuracy)](https://riskinsights.com.au/fee-and-charge-accuracy-reviews-risk-insights) - [About](https://riskinsights.com.au/about) - [Contact](https://riskinsights.com.au/contact) --- 15 Oct 2026 # Checking data for a review: part 2 (completeness) ![Picture of Yusuf Moolla](https://riskinsights.com.au/hs-fs/hubfs/Yusuf_Moolla_Headshot-transformed.png?width=50&name=Yusuf_Moolla_Headshot-transformed.png) [Yusuf Moolla](https://riskinsights.com.au/blog/author/yusuf) Share: [linkedin-in icon](http://www.linkedin.com/shareArticle?mini=true&url=https://riskinsights.com.au/blog/the-checks-we-run-before-using-data-for-a-review-part-2) [envelope icon](mailto:?body=https://riskinsights.com.au/blog/the-checks-we-run-before-using-data-for-a-review-part-2) **TL;DR** • The second in a series on checking data before using it for a review. • Completeness: checking we have every record we need, by reconciling to source systems. • Gaps are not uncommon, and reports or models using the same extracts can have the same gaps.   This is the second article in a [series on the checks we run](https://riskinsights.com.au/blog/the-checks-we-run-before-using-data-for-a-review-part-1) before using data for a review.   ## Why this is relevant day to day (not just in a review) The data used for models, dashboards and reports may be extracted in the same way as the data we use for a review. The extract is often set up once, with filters for a particular purpose that may not have been checked since. A recon at regular intervals, and after any system or process change, is a relatively simple way to check that all the records needed are there.   ## What we check, and what it can find For a review, we compare record counts and totals in the extract with the source system. We also check these below the aggregate level: for example, totals for each date range, product or brand. Reasons for gaps include: - filters applied to the extract, like only settled claims or only active loans - date cut-offs that don't match the review period, or that use a different date (e.g. lodgement date rather than decision date) - records held in a second system, like a front-end decisioning platform or an acquired brand's system - products, brands or channels left out, either deliberately (but not maliciously) or by accident. An extract that only includes claims with a settlement decision can leave out claims that were withdrawn. This understates the decline rate. If some groups of customers are more likely to withdraw after a difficult first conversation, a fairness analysis based on that extract won't include them. A filter that only includes active loans causes a similar problem. If we're testing whether fees were charged correctly, loans paid out or refinanced during the review period need to be included. Leaving them out removes some of the more complex calculations, which could be the ones that go wrong, so the result looks better than it really is.   --- Disclaimer: The info in this article is not legal advice. It may not be relevant to your circumstances. It was written for specific contexts within banks and insurers, may not apply to other contexts, and may not be relevant to other types of organisations. ---     ## Related posts [![Checking data for a review: part 1 (overview)](https://riskinsights.com.au/hs-fs/hubfs/checking-data-part-1.png?height=200&name=checking-data-part-1.png)](https://riskinsights.com.au/blog/the-checks-we-run-before-using-data-for-a-review-part-1) ## [The checks we run before using data for a review](https://riskinsights.com.au/blog/the-checks-we-run-before-using-data-for-a-review-part-1) [Read more](https://riskinsights.com.au/blog/the-checks-we-run-before-using-data-for-a-review-part-1) [![Catching errors before they make headlines](https://riskinsights.com.au/hs-fs/hubfs/Catching%20errors%20before%20they%20make%20headlines.png?height=200&name=Catching%20errors%20before%20they%20make%20headlines.png)](https://riskinsights.com.au/blog/catching-errors-before-they-make-headlines) ## [Catching errors before they make headlines](https://riskinsights.com.au/blog/catching-errors-before-they-make-headlines) [Read more](https://riskinsights.com.au/blog/catching-errors-before-they-make-headlines) [![Review triggers and practical checks for algorithmic systems (Part 3)](https://riskinsights.com.au/hs-fs/hubfs/Review%20triggers%20and%20practical%20checks%20for%20algorithmic%20systems%20Part%203.png?height=200&name=Review%20triggers%20and%20practical%20checks%20for%20algorithmic%20systems%20Part%203.png)](https://riskinsights.com.au/blog/review-triggers-and-practical-checks-for-algorithmic-systems-part-3) ## [Review triggers and practical checks for algorithmic systems (Part 3)](https://riskinsights.com.au/blog/review-triggers-and-practical-checks-for-algorithmic-systems-part-3) [Read more](https://riskinsights.com.au/blog/review-triggers-and-practical-checks-for-algorithmic-systems-part-3) We acknowledge Aboriginal and Torres Strait Islander peoples as the Traditional Custodians of the lands on which we live and work. We pay our respects to Elders past and present, and honour the rich diversity of the world's oldest living cultures. [View our LinkedIn page](https://www.linkedin.com/company/riskinsightsap) [email us](mailto:info@riskinsights.com.au) [Call us](tel:+61408946143) 2026 Risk Insights Pty. Ltd. | [Privacy](https://riskinsights.com.au/privacy-policy) | [Disclaimer](https://riskinsights.com.au/disclaimer) ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Yusuf Moolla", "url" : "https://riskinsights.com.au/blog/author/yusuf" }, "dateModified" : "2026-10-14T20:30:00.510Z", "datePublished" : "2026-10-14T20:30:00.000Z", "headline" : "Checking data for a review: part 2 (completeness)", "image" : [ "https://riskinsights.com.au/hubfs/checking-data-part-2.png" ], "mainEntityOfPage" : { "@id" : "https://riskinsights.com.au/blog/the-checks-we-run-before-using-data-for-a-review-part-2", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://riskinsights.com.au/hubfs/Risk%20Insights%20-%20Logo%20-%20(RGB%2c%20Horizontal%2c%20Small).png" }, "name" : "Risk Insights Pty. Ltd." } } ```