Once you have a count, two questions remain: which checks belong on it, and where does the finished volume statement live so someone else can find the rule behind it?

CompareDataBuyers draws the first set of checks from the World Bank's microdata preparation guide. That guide separates record-count checks, unique-identifier checks, and duplicate checks. They are different jobs. A record count asks how many rows or objects are present. A unique-identifier check asks whether you can tell those records apart. A duplicate check asks how you treat repeated identifiers. Mixing the three into one vague "quality check" hides which job you actually did.

CompareDataBuyers presents that World Bank material as archival microdata documentation guidance adapted to an original business-records preparation worksheet, not as AI buyer requirements. The checks are useful when you are preparing a business-data inquiry. They are not a claim that a buyer program has adopted the World Bank guide, and they are not a substitute for a program's own published rules.

The worksheet also borrows one distinction from W3C's DCAT 3 specification: the dataset and a supplied file representation are separate, including that file's byte size. Using those DCAT 3 concepts does not require a complete DCAT catalog, and it does not prove data rights or buyer acceptance. It only keeps the file's size from being treated as a count of business events.

When the count is done, save the sheet with the export reference and the counting instructions. Then add the resulting volume statement to the dataset manifest, and keep the unit and the exclusions in the description. A manifest line that says "700 cases after the stated exclusions," next to the export reference, is a statement another person can find later. A count that lives only in a slide or a chat thread is not.

The worksheet, the source notes, and the manifest step are in the CompareDataBuyers guide:

https://comparedatabuyers.com/blog/how-to-count-a-dataset-before-a-buyer-asks-for-its-size/

Published by CompareDataBuyers. Program requirements can change; confirm current terms with the program.