Equipment asset IDs in CSV files: keep them as text

When reviewing an equipment list in a spreadsheet, import the asset-ID column as text before matching it to a condition record. Keep the input file, then compare the characters in any newly saved CSV with that source. If a value has changed, return to the source rather than guessing what belongs there. This is a proposed document-review check, illustrated below with fictional IDs.

Why a numeric-looking ID needs care

Microsoft says Excel removes leading zeros from number codes by default. It also documents a limit of 15 significant digits for numeric values. A code can therefore need text handling even when every character is a digit. These are Excel's vendor-described behaviors; the Microsoft explanation is not a finding about your particular file.

For a fictional asset reference, 000742 and 742 are different character strings. A reviewer should establish which string the source supplies before joining a spreadsheet row to a report. Adding zeros until two entries look alike would conceal the unresolved question.

Set the ID column to Text during import

Microsoft's text-import guidance describes using Data → From Text/CSV, opening the query editor, and choosing Text as the ID column's data type. Where Excel offers Replace Current for the type change, the guidance selects that option before loading the worksheet. Menu labels vary by version; use the linked instructions for your installation.

In LibreOffice Calc, the Text Import help describes selecting a column in the preview and setting its Column type to Text. Its leading-zero tip specifically recommends this type. Check the delimiter preview as well so the ID sits in the intended column.

For this review, apply the text choice to identifier columns. Keep a separate purpose for a meter reading or other value you intend to calculate with. The goal is to preserve the reference you are matching, not to impose one type on every field in the list.

Check the newly saved CSV, too

A worksheet that looks right is only one stage of the review. LibreOffice's CSV guide says its CSV export saves the current sheet's data and loses workbook formatting. Carrying a workbook's appearance into another file is therefore an assumption worth checking.

Here is a proposed check for an external asset list. Preserve the received file and work on a copy. Import the ID column as Text, then compare a reference against the preserved input. If you save a new CSV, inspect its ID characters in a plain-text viewer and check the recipient's import as well. Record any mismatch and the comparison still needed. This checks the file you actually pass on, rather than relying on a screenshot of a cell.

Consider this fictional review note:

Asset-list copy for review: the received CSV contains ID 000742. The first worksheet view showed 742. A fresh import with the ID column set to Text shows 000742. The newly saved CSV has been checked for those characters; the recipient's import has not yet been reviewed. Asset matching remains pending.

The last sentence leaves the unfinished work visible. If you only have the shortened copy, ask for the earlier source. Microsoft's guidance warns that applying formatting later does not restore data already lost through conversion. A guessed prefix or digit is not a recovered identifier.

Link the reviewed reference to the condition record

Once the reference has been checked, use it consistently in the record you are reviewing. AuditIt's equipment checkout and return workflow uses two stages for comparison; its one-off equipment damage template uses a single-visit record. Those are distinct workflows. The spreadsheet review described here is an external preparation step, with the asset match still for a person to assess.

AuditIt creates tamper-evident, human-review-ready records. It is not legal certification and does not determine liability.

• Equipment rental
• Asset IDs
• CSV files
• Document review