AI Summary Missing Spreadsheet Rows? Check the Filtered Range First

An AI summary says your business received eight inquiries this week. Your intake sheet appears to contain twelve. Before asking the AI to count again, check the population it was given: which records belonged in the report, and which records actually reached the tool?

A filter is one place to investigate, not a diagnosis. Do not assume that copying cells, exporting a file or connecting an AI tool includes only visible rows—or includes every row. Inspect the specific input that was supplied. The useful question is not simply whether the sheet looks complete on screen.

Define the records the summary should cover

Write the reporting scope before changing the sheet. For an inquiry summary, specify the date period, the relevant location or service, and whether closed inquiries belong in the report. State what one record represents. An inquiry count and a count of distinct people are different questions.

Keep this definition beside the report. “This week's inquiries” is too loose if one person expects all arrivals while another expects only unresolved work. A polished summary cannot resolve that disagreement for you.

Here is a fictional example, not a customer result or a tested integration:

In this example, eight is the right count for the supplied subset but the wrong answer to the requested question. Rewording the counting instruction would not supply the four missing records. Conversely, if the agreed report covers only open work, adding the closed inquiries would make the input wrong.

Inspect filters without changing a colleague's view

Google's sorting and filtering documentation describes filters as a way to hide data. It distinguishes a regular filter, visible to other people with access, from a filter view that applies to your own view. On a computer, Google documents Data → Create filter view; users with view-only access can use a temporary, unsaved filter view.

Check the active criteria and the range being filtered. Do they match your written reporting scope? Also inspect whether the source contains other tabs or records outside that range. Seeing a filter control does not prove that it caused the missing input.

Avoid removing a shared filter simply to make the screen look right. First establish who uses that view and preserve its criteria. Where appropriate, inspect a separate working copy or your own filter view. Neither step proves what an export or connector sends; that still needs its own readback.

Reconcile record IDs in the actual input

Use a stable inquiry reference, if your sheet has one, to compare the intended records with the actual input. A total alone is a weak check: two sets can have the same size while containing different records.

1. List the inquiry references that belong in the agreed report. Check the source rather than asking the AI to invent identifiers.
2. Inspect the exact pasted text, uploaded working file or available connector result used for the summary. Confirm the selected tab, range and reporting criteria where those details are exposed.
3. Compare missing and unexpected references, then spot-check their statuses against the source. Separate a missing record from an empty field within a present record.
4. If the tool does not expose enough input to establish coverage, mark coverage unverified. Use an approved, inspectable input route or hold the report instead of assuming the connection worked.

Keep only the fields the report needs, and use an AI destination already approved for that business data. This checklist does not grant permission to upload customer details to a new service.

In the fictional example, the comparison should account for the four closed inquiry references. It should not merely produce a revised total of twelve. If those references are absent from the supplied input, correct the selection first. If they are present but absent from the summary, investigate the summary instructions and output separately.

Release the summary only after coverage matches

Once the input matches the agreed scope, ask for a draft summary and compare its claims with the reconciled records. Label the period and included statuses in the report itself. Keep any unresolved omissions visible rather than turning them into a confident total.

For a recurring report, save the scope definition and the coverage check with the workflow. Repeat the check when the source layout, selection or connection changes. Do not turn a one-time successful comparison into a claim that every future run is verified.

Our AI operator prompt pack offers a starting point for reviewable drafts. Add the expected record scope to your own instructions, but retain the input comparison: a prompt is not evidence of coverage.

Need help making a spreadsheet-to-summary handoff inspectable? Talk with Business Boomer about reviewing the input selection, draft output and human approval point before the report is used.