How to Specify a Data File
A practical field guide for business data and consumer lead requests.
Describe the unit of a record.
Start by defining what one row represents: a company, a branch, a person, a household, or an inquiry event. Without this definition, a total record count can be misleading. The same company may have multiple contacts; the same person may have submitted more than one request.
Separate essential fields from optional fields.
Name the fields your workflow cannot operate without, then list useful extras separately. Ask for completeness by field rather than assuming every row contains every value. A file with names and postal addresses is a different deliverable from one with usable business email addresses.
Agree on a simple data dictionary.
| Example field | Definition to agree |
|---|---|
| record_id | Stable identifier used to reconcile updates |
| state / city / postal_code | Which location the fields describe and their formatting |
| source_category | Meaning of the source label and supporting context |
| inquiry_date | Original submission date, if documented; include time zone when relevant |
| review_status | Which check was performed and what each status means |
These field names are illustrative. They are a specification aid, not a sample from an available customer dataset.
Preserve dates, phone numbers, and blank values.
State the expected date format and keep phone numbers and postal codes as text when formatting matters. Define whether a blank means unknown, unavailable, or not applicable. Avoid replacing missing values with guesses or placeholder values that look like real data.
Define duplicates and delivery format.
Choose duplicate rules appropriate to the record type. Agree on file format, text encoding, header names, and whether the original IDs remain intact. For an update project, preserve source values alongside proposed changes so the result can be reviewed before import.
Use the data quality checklist to assess a file, explore B2B data enrichment when information is missing, or submit your field requirements.
