THE RADARYNO NOTEBOOK

Fact-Check a Resume Written in Another Language

A resume written in another language can preserve words while changing numeric meaning. Dates may follow a different order, durations may be rounded, and units or quantities may be converted incorrectly. A careful fact check compares the translated document with the original career notes before the resume is sent. This guide focuses on measurable claims: employment periods, project timelines, counts, percentages, currency, distance, capacity, and other figures. It does not impose country-specific rules or review terminology, titles, or tone.

01

Collect the source facts

Begin with the buyer’s career notes and any approved source resume used for comparison. Isolate every claim that contains a date, duration, quantity, percentage, currency, distance, capacity, rate, or other measurable detail. Copy the source wording exactly before translating or rewriting it. Record surrounding context, such as whether a count refers to accounts, people, projects, incidents, or locations. This prevents a correct number from being attached to the wrong noun. If the Radaryno Resume Kit is used, its process relies on the buyer’s career notes, reports gaps, and asks rather than inventing. That does not remove the need to verify the source facts themselves.

02

Build a numeric evidence ledger

Create a simple comparison record with one row for each measurable claim. Useful columns include source wording, translated wording, value, unit, date interpretation, status, and required follow-up. Use statuses that describe what happened: preserved, converted, rounded, reformatted, changed, or unclear. Keep the ledger separate from the polished resume so a visual edit does not hide a factual change. If several resume designs are produced, compare each output against the same ledger rather than treating one design as the reference. The goal is traceability: another review should show where every figure came from and why its final form is acceptable.

03

Resolve date interpretation

Check every calendar date for order, precision, and scope. A source may contain a full date, a month and year, a year only, or a date range. A translated resume may reorder day and month, change a dash, or turn a precise date into a broader period. Do not infer a missing day or month from a title, location, or common local practice. Confirm whether an employment range includes both endpoint months and whether a project date describes planning, delivery, or the entire engagement. When the source does not establish greater precision, retain its level of precision rather than making the claim more exact.

04

Check durations and intervals

Compare durations independently from their start and end dates. A translated version can turn weeks into months, days into business days, or a short interval into a rounded statement. Recalculate only when the source dates support the calculation and the result uses the same scope. For example, a project lasting six weeks should not become six months because a translator or language model selected a familiar phrase. Also inspect phrases such as “within three days,” “over two quarters,” or “for nearly a year,” since they express different levels of precision. If a duration was intentionally rounded for readability, record that choice and ensure it does not inflate the claim.

05

Verify quantities and units

Review the number and the thing being counted as a single claim. Check whether “twenty accounts,” “twenty clients,” and “twenty contracts” describe the same population. Then inspect units for distance, weight, volume, storage, currency, temperature, capacity, and rate. A conversion may be valid but still misleading if the original unit matters to the work or if the converted value is rounded too heavily. Keep the source unit when there is no confirmed reason to convert. For currency, check whether the amount refers to revenue, budget, cost, or salary, and whether the period is stated. Never let a translated noun quietly broaden the scope of a quantity.

06

Inspect percentages and comparisons

Percentages often lose meaning when their reference point disappears. Check whether a percentage describes growth, reduction, completion, accuracy, allocation, conversion, or another measure. Confirm the baseline and period in the source notes. A statement such as “reduced processing time by twenty percent” is not equivalent to “processed twenty percent more requests,” even though both contain the same number. Also review ratios, rankings, ranges, and comparative words such as “double,” “half,” or “three times.” If the translated output changes a percentage into a fraction or a general adjective, compare the underlying meaning and restore the measurable claim only when the source supports it.

07

Compare every generated document

Read the final HTML and PDF against the evidence ledger, not only against the source notes. Check whether line wrapping, omitted symbols, decimal separators, superscripts, currency signs, or page breaks changed what a reader sees. The Radaryno Resume Kit can write an HTML and PDF resume, and an optional cover letter, in the offer language; review each generated document that contains measurable claims. If multiple designs are used, repeat the comparison for each one. Files and generated documents stay on the buyer computer, so keep the ledger with the local review materials and do not assume a rendered file matches the editable source.

08

Resolve gaps before release

At the final pass, classify each discrepancy as a confirmed correction, a source ambiguity, or an unsupported change. Correct confirmed errors, ask about ambiguous claims, and remove unsupported precision rather than filling it with an estimate. Check that the same fact has the same value wherever it appears in the resume and optional cover letter. Preserve a local copy of the reviewed ledger and the final documents so later edits can be compared with the approved version. The kit includes a local application tracker for recording application details and keeping documents locally, but it does not submit applications or verify claims for you. Release the document only after every numeric difference has a documented reason.

Numeric claim checks for a fictional multilingual resume review
Claim typeSource factTranslated outputReview action
Employment periodApril 2021 to September 202304/2021–09/2023Confirm the month order and inclusive meaning
Project durationSix weekssix monthsRestore the source duration; investigate the translation
Quantity18 customer accounts18 customer accountsCheck that the count and noun still refer to the same group
Unit120 kilometres120 milesConfirm whether conversion was intended and label it clearly

Worked before-and-after checks

  1. Fictional example. Before: the career notes say “April twenty twenty-one to September twenty-three.” After: the translated resume says “March twenty-one to September twenty-three.” The reviewer flags the changed start month instead of correcting it from context. The source is consulted, and the final wording keeps April.

  2. Fictional example. Before: the notes record “six weeks to complete the migration.” After: the translated resume says “six months.” The reviewer compares the units and restores six weeks. If the source was ambiguous, the claim would remain unresolved until the owner confirms it.

  3. Fictional example. Before: the notes say “eighteen customer accounts.” After: the output says “eighteen customers.” The number survived, but the object changed. The reviewer checks whether the work covered accounts, individual people, or both before accepting the sentence.

  4. Fictional example. Before: the notes state “one hundred twenty kilometres of field travel.” After: the output says “one hundred twenty miles.” The reviewer checks whether a conversion was requested. Without confirmation, the resume preserves kilometres rather than presenting an unverified conversion.

Put it into words

Before and after

Fictional examples: not real people.

Before

“Worked from 04/03/2022 to 09/03/2023.”

After

“Worked from March 4, 2022, to September 3, 2023,” only after the source confirms the date order.

Before

“Completed the rollout in six months.”

After

“Completed the rollout in six weeks,” when the verified source notes state six weeks.

Before

“Managed 18 customers.”

After

“Managed 18 customer accounts,” when the source counts accounts rather than individual customers.

Before

“Travelled 120 miles.”

After

“Travelled 120 kilometres,” when the source provides kilometres and no conversion was confirmed.

A few details

Frequently asked questions

What should be the source of truth for a multilingual resume?

Use the buyer’s verified career notes as the primary source for dates, durations, quantities, units, and other measurable claims. An existing resume can help locate facts, but it should not override clearer source notes. Keep the original wording and context beside the translated output so differences can be investigated rather than guessed.

Should I convert kilometres, currency, or other units?

Convert only when the audience or source instructions require it and the conversion can be explained accurately. Record the original value, converted value, rounding, and purpose in the evidence ledger. If conversion is not confirmed, preserving the source unit is safer than presenting a new figure that may change the claim’s meaning.

How do I handle an ambiguous date?

Do not choose an interpretation based only on local convention. Record the possible readings, check the surrounding source context, and ask the owner to confirm the intended day and month. If the ambiguity cannot be resolved, use a less precise form that the source supports, such as a month and year, rather than inventing certainty.

What if the translated resume rounds a duration?

Compare the rounded wording with the original dates and stated duration. Rounding can be acceptable when it does not inflate or distort the claim, but record it explicitly. A short interval that becomes materially longer should be corrected. When the source does not support a rounded value, retain the original precision or ask for confirmation.

Does local document storage verify numeric claims automatically?

No. Keeping files and generated documents on the buyer computer supports local handling, but it does not independently verify dates, quantities, units, or numeric meaning. AI provider access is separate from the one-time kit purchase, and the reviewer remains responsible for comparing the output with the verified career notes.

How can I check both HTML and PDF output?

Use the same evidence ledger for each generated document. Compare visible numbers, date separators, decimal marks, currency signs, units, and repeated claims. Inspect the rendered PDF as well as the HTML because formatting can omit or alter symbols. If the documents differ, correct the source or generation inputs and repeat the comparison before sending them.

RADARYNO RESUME KIT

Your experience, selected for each offer.

A downloadable kit for Claude Code or Codex. Gaps stay visible.

See the kit