Keep the source value beside the English display
A readable English sentence can conceal a tenfold error. Start with a small comparison sheet, using a fact ID that stays attached to the value wherever it appears. The following numbers are fictional placeholders for illustrating the checks; they do not describe any company's results or product specifications.
| Fact ID | Chinese source entry | Meaning to preserve | Proposed English display |
|---|---|---|---|
| N-01 | 1.25万次 | 1.25 × 10,000 cycles | 12 500 cycles |
| N-02 | 厚度 2.50 毫米 | Thickness of 2.50 millimetres | Thickness: 2.50 mm |
| D-01 | 2026年10月12日 | A calendar date, with no time supplied | 12 October 2026 |
Under each ID, retain separate fields for the original number string, original unit, scale multiplier, decimal marker, grouping separator, source date, source time zone and English display. Use “not supplied” where the source has no date or time zone. An empty field should not silently become a guessed value.
For N-01, keep 1.25 and 万 separately as well as retaining the exact source string. Expand the scale to 12500 for comparison, then format it for readers. For N-02, keep the two decimal places unless the underlying record supports a change. Showing 2.50 as 2.500 would introduce an additional decimal place without evidence for it.
Read separators and units before comparing digits
Treat punctuation as part of the number's interpretation. A comma in an imported sheet may mark a decimal fraction or a group of thousands. If the source convention is unclear, ask for its numeric definition before converting the string. Guessing from English formatting alone can turn 1,250 into either one thousand two hundred fifty or one and a quarter.
For technical quantities, choose a consistent display convention and record it. The CIPM recommendation on decimal markers allows a point or comma as the SI decimal marker and says that dots and commas are not inserted between groups of three digits. A decimal point with space grouping, as in 12 500.25, follows that convention. Keep a separate ungrouped numeric value for calculation; reader-facing spacing should not change the stored quantity.
Then compare dimensions. Millimetres describe length; square millimetres describe area. A value such as 2.50 mm² cannot be checked against 2.50 mm by matching digits. Retain any denominator too: cycles per minute and total cycles answer different questions. If a fact comes from an image, carry over the label and attached condition along with the number; matching product images with product facts covers that context.
Make converted values visibly derived
Use a second field for every permitted conversion. Record the source value and unit, target unit, factor or formula, unrounded result, rounding rule and final display. Also state that the displayed quantity is converted from the source measurement.
For fictional N-02, a conversion from millimetres to centimetres uses a factor of 0.1: 2.50 mm × 0.1 = 0.250 cm. The rule here is to retain the exact converted value; no rounding is needed. Keeping three decimal places in centimetres retains the original display's 0.01 mm increment. This calculation does not create a new measurement or establish its uncertainty. Do not replace the original 2.50 mm field with the converted result.
Recalculate from the retained source value each time. Chaining a new conversion from an already rounded display can accumulate differences. For a range, convert both endpoints with the stated formula and identify the resulting lower and upper limits. For a purely proportional conversion, multiply the tolerance by the absolute value of the conversion factor. If the formula includes an offset, convert the lower and upper limits separately, then calculate the new tolerance relative to the converted central value. Check that the English preserves the original limit and condition.
Separate calendar dates from timed events
Use a spelled-out month for English prose, such as 12 October 2026, or a year-first field such as 2026-10-12. Avoid 10/12/26, which leaves the month and day open to different readings. Preserve the source's precision: a month-only entry does not support adding a day.
For a timed event, retain the original timestamp and offset before showing its Beijing equivalent. The Date and Time Formats note published on the W3C site lists year-first dates and timestamps with Z or a numeric offset. It is a discussion note, and its listed formats provide a concrete reference for making the offset explicit.
A fictional source instant of 2026-10-11T16:30:00Z corresponds to 2026-10-12T00:30:00+08:00 in Beijing. The date changes even though the instant does not. Retain both strings and verify the day boundary. A bare calendar date has no offset to convert; keep it as a date unless the source supplies a time.
Review the sentence after the fields match
Complete the checks in this order:
- Expand the source scale and compare the ungrouped values.
- Confirm units, dimensions, denominators and attached conditions.
- Recalculate conversions from the original values and apply the recorded rounding rule.
- Compare date precision, original offsets and the Beijing date and time.
- Read the English sentence against those verified fields.
Matching numbers cannot establish that every word preserves the claim. If wording still raises a separate question, use the guidance on Chinese–English meaning disputes. The numerical record should let a reader trace each English value back to the original entry without reconstructing the arithmetic.
Want to see how AI engines describe your brand today?
Get a free growth audit