Find empty values in a CSV for a compliance report

A compliance report can be incomplete even when a CSV looks tidy. Empty cells may be easy to miss in a large export, and values such as N/A or a dash may look blank without actually being empty.

Open the file in a CSV editor, check the columns that matter, and review each one for empty fields. Then separate true blanks from missing records, whitespace, and placeholders so you do not change data based on appearance alone.

Find empty values in the CSV

1. Open the file in the CSV Editor. It works on the file in your browser, so the file is not uploaded.
2. Check that the headings and values appear in the expected columns. If a whole row appears in one column, or values seem shifted, stop and check how the CSV is separated and quoted before reviewing blanks.
3. Make a working copy or keep the original unchanged. Decide which columns are required for the report, such as a record ID, status, date, or approval field. Do not treat every optional field as an error.
4. Sort one relevant column at a time. Look at the beginning and end of the sorted values for empty cells, since blank entries may be grouped at either end. Record the row identifier and column name for each required blank.
5. Repeat the check for each required column. Use the editor's find feature to check for known placeholder values, such as NULL or N/A, if your reporting rules treat any of them as missing.

Sorting changes the display order, not the meaning of the records. Use a stable identifier to keep track of each row, and do not rely on the current row position alone if you need to compare findings with the original file.

Decide what counts as empty

A blank CSV field usually has no value between its separators. For example, in R42,,Approved, the field between the two commas is empty. A quoted empty field, written as "", also contains no characters. The CSV Editor may display these as empty cells.

Other values can look empty but need a separate decision. A field containing spaces is not technically empty, and values like 0, Unknown, None, N/A, or - are text or numbers. Whether they count as missing depends on the rules for your report. Do not replace them automatically.

Also distinguish an empty field from a missing field. A row with fewer fields than expected may indicate a malformed or incomplete record, rather than an ordinary blank value. If columns do not line up consistently, check the source export and its row structure before classifying the data.

Keep findings useful for an audit

• Record the location. Note the record ID, column name, and original row number when available. This makes it easier to trace each finding back to the source.
• Separate blanks from placeholders. Keep empty cells, whitespace-only cells, and placeholder text in distinct groups unless the reporting rules explicitly combine them.
• Preserve the original value. Do not fill, delete, or standardize a field just to make the report look complete. Apply a correction only when you have an approved source for the replacement.
• Keep a count by field. Count empty values in each required column, rather than relying on one overall total. A single record can have more than one empty field.

If a field needs correction, keep a note of the change and its basis. For a compliance review, it is often important to show both what the file contained and what was changed, rather than silently overwriting the source data.

Check the file before sharing it

The columns do not line up

Commas, quotation marks, and line breaks inside a CSV value can affect how a row is read. If the headings or records appear in unexpected columns, correct the import interpretation before counting blanks. Otherwise, valid values may appear empty simply because the file was parsed incorrectly.

A cell looks blank but may contain spaces

Do not assume a visually empty cell has no characters. Check the cell contents closely, or inspect a small copy of the source in a plain-text editor. If spaces are present, classify them separately and follow your organization's rules on trimming or cleaning them.

You find a placeholder instead of a blank

Search for the specific placeholder used by the source system and report it separately. A literal NULL or N/A is not the same as an empty CSV field unless your compliance definition says it is.

The row has fewer fields than expected

Flag the record as a possible structure issue, not just a blank value. Compare it with the source system or a known-good export, and avoid adding empty fields by hand unless the correct structure and intended values are clear.

Save a reviewed copy

After checking the required columns, save or export a separate reviewed copy if you made changes. Reopen that copy and confirm the headers, row count, identifiers, and corrected values before using it in the compliance report. Keep the original export and your list of findings according to your organization's retention rules.