Measurement records
Measurement units in business datasets
A column of numbers is not a measurement description. Explain the quantity, unit and collection method before comparing values or discussing a possible dataset licence.
Last checked
Keep the original measurement meaning visible. Extra decimal places do not establish accuracy, and a conversion does not repair an unknown unit.
Name the quantity before the unit
A field labelled size may refer to length, area, volume or a category. Even a field labelled weight may describe an individual item, a package or a complete shipment. Start by identifying what was measured and the object or event to which it belongs.
The BIPM description of the International System of Units provides the international measurement framework used across science and industry. A recognised unit vocabulary is useful, but naming it does not establish how an old record was collected or whether a particular reading is reliable.
Our suggested field note records the quantity, unit, measurement method, relevant instrument or source and known limitations. Keep it with the data dictionary rather than relying on a knowledgeable colleague to explain the column every time.
Look for mixed conventions
Ask whether different sites, suppliers or periods used different units. A software migration may have changed a display without changing every historic record. Distinguish what the system shows today from what was stored when the observation was made.
For an invented example, a fictional stock system might combine dimensions entered by several suppliers. A number alone cannot tell a reviewer which unit or packaging level each supplier used. Do not infer the answer merely because one interpretation gives plausible-looking dimensions.
Prepare a private list of known conventions and unresolved cases. Where the collection includes derived values, identify the inputs and the rule if known. Describe uncertainty explicitly instead of applying a single conversion across a field whose meaning has not been established.
Document conversions as processing
Before converting measurements, ask the technical owner to confirm the source convention and the intended use. Preserve the distinction between an observed value and a transformed value within the authorised system. This is a recommendation for traceability, not an instruction to retain records beyond approved arrangements.
A useful conversion note states the source and target units, the rule used, the affected version, the rounding policy and the checks performed. Include any exceptions. A conversion performed manually in a spreadsheet deserves the same explanation as one performed by a software pipeline.
Use the version history guide to identify which release contains the transformation. Avoid silently replacing values while retaining a description that still refers to the original collection. A future reviewer should be able to tell which representation they are assessing.
Do not confuse precision with accuracy
Record the evidence behind any accuracy statement. Ask whether a value came from a direct measurement, a calculation, an estimate or a default. The number of decimal places displayed cannot answer that question. If an instrument's calibration history is unknown, record the gap rather than inventing a quality rating.
Explain whether readings are individual observations, averages, maxima or another summary. State the time interval for aggregated values where known. Measurements taken at different intervals may require a different interpretation even when they use the same units.
For operational records, the machine sensor guide covers the wider relationship between devices, timestamps and events. This article focuses on the meaning of the values, so it should complement that description rather than replace it.
Prepare a non-confidential measurement outline
An initial outline can name the broad measurement family, the known units, collection period, update pattern and any unresolved convention changes. Say whether values are raw, aggregated or converted. Do not include private site details, real equipment identifiers or extracts just to show that measurements exist.
Technical consistency and licensing readiness are separate questions. A well-documented measurement does not establish ownership, permission for reuse or interest from a buyer. Keep those questions with the relevant owner and advisers, and do not make new access arrangements merely to prepare an enquiry.
Fairlode accepts descriptions only at this stage. A concise explanation of the units and their limitations is enough to begin discussing whether further assessment is worthwhile. There is no need to upload a dataset, and no implied promise that the records will be purchased.
General information, not legal advice, a valuation or a buyer offer. Illustrative examples are not customer case studies.
Sources and further reading
Sources checked 16 November 2026. Historical research is background, not evidence of current buyer demand.