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.
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.
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.
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.
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.
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.
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.
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.
| Claim type | Source fact | Translated output | Review action |
|---|---|---|---|
| Employment period | April 2021 to September 2023 | 04/2021–09/2023 | Confirm the month order and inclusive meaning |
| Project duration | Six weeks | six months | Restore the source duration; investigate the translation |
| Quantity | 18 customer accounts | 18 customer accounts | Check that the count and noun still refer to the same group |
| Unit | 120 kilometres | 120 miles | Confirm whether conversion was intended and label it clearly |
Worked before-and-after checks
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.
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.
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.
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.