“Some CSV files import incorrectly” gives the reader little to work with. A useful limitation names the exact input, the setting that triggers the problem and what the reader will see.

Make the symptom recognizable

For example, “With a semicolon-separated inventory export and Comma selected as the delimiter, the preview shows each record in one column.” Record the editor or import tool version you checked. Include one sample row, such as Clamp;D-4;6, so the reader can see the intended field boundaries.

A sample limitation pairs semicolon-separated input with a comma import setting and a one-column preview.

Illustrated trigger. Name the exact input and setting that produce the symptom.

Give a workaround the reader can verify

In a tool that lets you choose the delimiter, select Semicolon before committing the import. In the preview, verify that Asset, Bay and Count are separate headings and that the sample row reads Clamp, D-4 and 6 in the corresponding columns. If the tool lacks that option, use the source exporter’s comma-delimited setting if available and test a copy.

The workaround proof shows separate Asset, Bay and Count columns after choosing semicolon.

Illustrated verification. Check the headings and one record in the resulting preview.

Ask a reviewer to try the exact case. They should be able to recognize the one-column symptom and confirm the corrected headings and sample row.