---
title: "Checking data for a review: part 7 (blanks and nulls)"
description: How we check where blanks and nulls occur in a data extract, what they mean, and why they can affect both fairness and accuracy results.
image: https://riskinsights.com.au/hubfs/checking-data-part-7.png
---

[Skip to content](https://riskinsights.com.au/blog/the-checks-we-run-before-using-data-for-a-review-part-7#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)

---

 19 Nov 2026

# Checking data for a review: part 7 (blanks and nulls)

![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-7) [envelope icon](mailto:?body=https://riskinsights.com.au/blog/the-checks-we-run-before-using-data-for-a-review-part-7)

**TL;DR**

• The seventh in a series on checking data before using it for a review.

• Blanks and nulls: checking where they occur, and what they mean.

• Blanks/nulls can be concentrated in a channel, period or group of customers, so they can affect both fairness and accuracy.

 

This is the seventh 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)

Models and rules generally have a defined way to handle blanks, typically coded when they’re first built. As customers and products change, if this isn’t updated, customers can be treated differently for unintended reasons.

 

## What we check, and what it can find

For a review, we count blanks/nulls in each field. Then we check if they’re concentrated anywhere, such as in a channel, product, time period, brand or customer group. A field that is blank for a small proportion of records overall could be blank for a far higher percentage from one source.

A blank/null can mean:

- the question wasn’t asked, because the field was added later or isn’t on an intake form
- the field doesn’t apply to that customer or product
- the answer is unknown, or the customer chose not to give it
- the value is zero, but was left blank
- the value was lost in a migration.

In insurance, the number of prior claims might be blank for policies migrated from another system or an acquired brand. If a fraud model handles blanks as zeroes, the first claim (in the new system) from such a policy may appear to be lower risk than it is. On the other hand, if the fraud model treats a blank as a warning indicator, the claim may be more likely to be referred for investigation. It can get worse: if the new system isn’t coded properly, the prior claims count could remain blank even after new claims (e.g. blank + 1 = blank).

In lending, credit history fields can be blank for customers with a short history, such as younger customers or people who have recently arrived in the country. How the system treats those blanks affects how accurately it assesses their risk, and whether they’re approved at a similar rate to other customers.

 

---

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.

---

 

 

<iframe style="height: 100%; width: 100%; border: medium none currentcolor;" title="Form" xml="lang" src="https://js.hsforms.net/ui-forms-embed-components-app/frame.html?_hsPortalId=44032070&amp;_hsFormId=cb36bab6-3ff8-4e12-b808-12e547e8356b&amp;_hsIsQa=false&amp;_hsHublet=na1&amp;_hsDisableScriptloader=true&amp;_hsDisableRedirect=true&amp;_hsInstanceId=26be30e1-47ee-4652-a675-01e171763685&amp;_preview=true&amp;benderPackage=InpageEditorUI&amp;cacheBust=1795037051856&amp;cssPath=bundles%2Fapp.css&amp;inpageEditorUI=true&amp;localAssets=false&amp;portalId=44032070&amp;preview_key=RFPYQNTt&amp;scriptPath=bundles%2Fapp.js&amp;staticVersion=static-1.86804&amp;preview_theme=true&amp;env=prod&amp;injectedScripts=react-dlb%2Cbundle.production.js%2Cfalse%2Cstatic-1.97&amp;hsSmartContentDefault=true&amp;hsEditorApp=blog_post&amp;sessionId=cd910dec-05ba-44fe-9c2f-b017e7365e78" scrolling="no" data-test-id="embedded-form-cb36bab6-3ff8-4e12-b808-12e547e8356b"></iframe>

## Related posts

[![Checking data for a review: part 2 (completeness)](https://riskinsights.com.au/hs-fs/hubfs/checking-data-part-2.png?height=200&name=checking-data-part-2.png)](https://riskinsights.com.au/blog/the-checks-we-run-before-using-data-for-a-review-part-2)

## [Checking data for a review: part 2 (completeness)](https://riskinsights.com.au/blog/the-checks-we-run-before-using-data-for-a-review-part-2)

[Read more](https://riskinsights.com.au/blog/the-checks-we-run-before-using-data-for-a-review-part-2)

[![Checking data for a review: part 6 (effective date)](https://riskinsights.com.au/hs-fs/hubfs/checking-data-part-6.png?height=200&name=checking-data-part-6.png)](https://riskinsights.com.au/blog/the-checks-we-run-before-using-data-for-a-review-part-6)

## [Checking data for a review: part 6 (effective date)](https://riskinsights.com.au/blog/the-checks-we-run-before-using-data-for-a-review-part-6)

[Read more](https://riskinsights.com.au/blog/the-checks-we-run-before-using-data-for-a-review-part-6)

[![Checking data for a review: part 3 (accuracy)](https://riskinsights.com.au/hs-fs/hubfs/checking-data-part-3.png?height=200&name=checking-data-part-3.png)](https://riskinsights.com.au/blog/the-checks-we-run-before-using-data-for-a-review-part-3)

## [Checking data for a review: part 3 (accuracy)](https://riskinsights.com.au/blog/the-checks-we-run-before-using-data-for-a-review-part-3)

[Read more](https://riskinsights.com.au/blog/the-checks-we-run-before-using-data-for-a-review-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-11-18T21:38:29.891Z",
  "datePublished" : "2026-11-18T21:38:29.000Z",
  "headline" : "Checking data for a review: part 7 (blanks and nulls)",
  "image" : [ "https://riskinsights.com.au/hubfs/checking-data-part-7.png" ],
  "mainEntityOfPage" : {
    "@id" : "https://riskinsights.com.au/blog/the-checks-we-run-before-using-data-for-a-review-part-7",
    "@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."
  }
}
```