A column contains forty-five, one and a quarter, and ninety. The heading says duration. Adding the numbers produces a result that has no stable meaning.
The first record could use minutes. The second could use hours. The third could use seconds. A clean column format does not settle the question.
Keep the quantity attached to the number before combining records. Retain the source value, identify its unit, and document the conversion into the report's chosen unit.
The worksheet below is a proposed review method. Its records are fictional. It covers duration and physical dimensions, with no currency, packaging, or equipment assumptions.
Name What the Number Measures
Start with three separate ideas: the quantity, its numerical value, and its unit.
For a fictional review lasting forty-five minutes, the quantity is the review's duration. Forty-five is its numerical value in minutes. The minute is the unit. Expressing that duration as three quarters of an hour changes the numerical value and the unit together.
NIST's guide to values of quantities defines a quantity's value as a number multiplied by a unit. That distinction belongs in the report's working records, even when the final heading stays short.
Write “review duration, minutes” above the normalized column. Keep “source duration” and “source unit” in separate columns. A later reviewer should be able to reconstruct what entered the conversion.
The business metric dictionary defines the reporting question and unit. This worksheet records how individual source values reach that definition. Use both when several exports feed the same metric.
Also name the duration's meaning. Active review time and elapsed time can both use minutes. Matching units does not establish matching business definitions. Resolve that distinction before adding records.
Preserve the Source Before Converting It
Use a working copy for conversion. Keep the original file and identify the exact source row.
For each record, preserve the original numerical text and its declared unit. Add the normalized numerical value in a new field. Keep a status field for accepted, unresolved, or rejected conversions.
This structure makes a correction inspectable. If the source owner later confirms a different unit, the reviewer can replace the conversion without reconstructing overwritten input.
A filename containing “minutes” is supporting context. Ask whether it establishes the meaning of every row. An export can contain a unit column that contradicts its filename. Record the conflict and withhold the affected records until the owner resolves it.
An empty unit stays unresolved. Do not assign the unit that makes the value look reasonable. The same numerical value can describe different durations without either being impossible.
Use a CSV data contract to specify required unit fields before the next delivery. A contract improves the handoff definition. It does not supply missing evidence for the file already received.
Write the Factor With Its Direction Visible
A conversion factor needs a direction. “Sixty” alone cannot tell a reviewer whether the calculation multiplies or divides.
NIST's alphabetical conversion table lists an hour as three thousand six hundred seconds and a minute as sixty seconds. Their ratio gives sixty minutes per hour.
Write the calculation as 1.25 h × 60 min/h = 75 min. The hour unit cancels, leaving minutes. To reverse that conversion, use 75 min × 1 h/60 min = 1.25 h.
For an independent check, reverse the result using the same documented relationship. This check can expose a reversed factor. It cannot prove the original unit was correct.
NIST's conversion guidance describes conversion as a process involving a factor, significant digits, and rounding. Treat each as a review choice. Copying a factor into a spreadsheet does not complete the conversion record.
Record where the factor comes from and when the reference was checked. If the reference distinguishes exact and rounded factors, retain that distinction. Do not replace a supported factor with a remembered approximation.
Work Through Three Synthetic Duration Records
Assume the following fictional rows all measure active review duration. Their source units are declared. The example treats the supplied decimal values as exact inputs for its arithmetic.
| Record | Source value | Source unit | Factor to minutes | Converted duration |
|---|---|---|---|---|
| R-101 | 1.25 | hours | 60 min/h | 75 min |
| R-102 | 45 | minutes | 1 min/min | 45 min |
| R-103 | 90 | seconds | 1 min/60 s | 1.5 min |
The normalized total is seventy-five plus forty-five plus one and a half minutes. That equals 121.5 minutes, or 2.025 hours.
The unconverted numerical sum is 136.25. It combines different units and has no valid total-duration interpretation. A report should reject that sum before discussing its size.
Check the normalized total in seconds. The rows become four thousand five hundred, two thousand seven hundred, and ninety seconds. Their sum is seven thousand two hundred ninety seconds. Dividing by sixty recovers 121.5 minutes.
Keep that independent calculation with the review record. State that all three rows share the same duration definition. Conversion alone does not establish whether records overlap or whether each event should be included.
If the report also needs an average, use the included observation count after normalization. The weighted-average guide handles aggregation boundaries and weights. A conversion worksheet does not replace those decisions.
Distinguish Length, Area, and Volume
A length factor does not pass unchanged into an area or volume calculation.
NIST's SI prefix table gives milli as one thousandth. One millimeter therefore equals 0.001 meter. For area, square that factor. For volume, cube it.
Use this fictional set of declared measurements:
| Quantity | Source value | Conversion | Target value |
|---|---|---|---|
| Length | 2,500 mm | 2,500 × 0.001 | 2.5 m |
| Width | 800 mm | 800 × 0.001 | 0.8 m |
| Rectangular area | 2,000,000 mm² | 2,000,000 × 0.000001 | 2 m² |
| Rectangular volume | 1,000,000,000 mm³ | 1,000,000,000 × 0.000000001 | 1 m³ |
The area example follows from a rectangle measuring 2,500 millimeters by 800 millimeters. Multiplying the source lengths gives two million square millimeters. Multiplying the converted lengths gives two square meters. Both paths agree.
The volume example uses a fictional cube with one thousand millimeters on each side. Each converted side is one meter. The resulting volume is one cubic meter.
These examples establish arithmetic under stated shapes and dimensions. They say nothing about a real object's usable capacity or suitability. Keep any real measurement conditions in the source record.
NIST explains dimensional analysis using length, area, and volume. In the worksheet, write the complete source and target units. A missing exponent can change the calculation even when every digit was copied correctly.
Reject a Conversion That Changes the Quantity
Meters and square meters describe different dimensions. No fixed length-conversion factor turns a single length into an area.
If a source supplies length and the report needs area, request the additional dimensions and the applicable geometric definition. Record that calculation separately. Do not label it as a unit conversion.
Use the same discipline with operational records. A count and a duration do not become interchangeable because they occupy adjacent columns. A rate needs its numerator, denominator, and period before a reviewer can interpret it.
Keep pieces, cases, and pallets separate unless a documented packaging definition establishes their relationship for the records concerned. This article supplies no packaging factor. A familiar label does not establish a fixed quantity.
Place unresolved records in an exception list. Include the source location, missing definition, requested evidence, and acceptance owner. Avoid substituting zero. Zero would make an unresolved measurement look like an observed absence.
A plausible magnitude can help identify a question. It cannot answer the question. Ask the source owner to confirm the unit and retain that answer beside the affected record.
Copy the Conversion Worksheet
Use one record for each quantity and conversion path. The following fictional entry documents R-101.
| Field | Fictional entry or instruction |
|---|---|
| Source quantity | Active review duration for R-101 |
| Source value | 1.25, retained from the source row |
| Source unit | Hours, explicitly declared by the source |
| Target unit | Minutes |
| Factor and direction | Multiply by 60 min/h |
| Factor source | NIST Appendix B.8, hour and minute entries |
| Source precision | Exact synthetic decimal input for this example; real precision requires source evidence |
| Calculation precision | Exact decimal arithmetic for these synthetic inputs; no intermediate rounding |
| Result | 75 min |
| Reverse check | 75 divided by 60 equals 1.25 h |
| Exceptions | None under the stated fictional assumptions |
| Acceptance owner | Report reviewer, with identity recorded before real use |
For a real report, add the source filename, version, row identifier, reference check date, and review date. Keep the worksheet close enough to the report that a replacement editor can find it.
Record a reason for the target unit. Minutes may make a duration comparison readable. Meters may match a receiving specification. The choice should follow the reporting task rather than the largest or smallest number.
For area and volume, show the powered factor explicitly. Ask the acceptance owner to review both the unit and its exponent. A result can contain the correct digits while carrying the wrong dimension.
Set Display Precision Without Inventing Measurement Detail
A precise factor does not create more knowledge about the source measurement. Preserve the source's stated precision and any uncertainty information.
NIST Appendix B distinguishes exact factors from rounded factors and provides guidance for rounded converted values. Use the relevant guidance for the measurement task. A fixed display format is not evidence of measurement accuracy.
The examples here define exact synthetic inputs so their arithmetic can be checked directly. Real exports need their own precision statement. Do not assume that a displayed 1.25 hours came from an exact measurement.
If the report displays one decimal place, retain the calculation value separately. State that formatting choice in the worksheet. Avoid feeding the shortened display back into later calculations without an explicit reason.
Before accepting the report, trace one row from source to display. Confirm its quantity, unit, factor, result, and status. Then inspect each distinct conversion path, including the paths with squared or cubed units.
Release the normalized total only after unresolved records have a stated treatment. Keep their count and effect visible to the reviewer.
Keep the unit beside the number.
Sources
- NIST: Unit Conversion. Conversion process and dimensional analysis. Checked 2026.10.28.
- NIST SP 811: Appendix B. Factor notation and converted-value rounding guidance. Checked 2026.10.28.
- NIST SP 811: Appendix B.8. Hour and minute relationships to seconds. Checked 2026.10.28.
- NIST SP 811: Chapter 4. SI prefixes. Checked 2026.10.28.
- NIST SP 811: Chapter 7. Quantity values and units. Checked 2026.10.28. Worksheets and synthetic records are original teaching examples.