How to Check Names and Numbers in Translation

Prose can be roughly right and still useful; a name cannot. When a Gujarati loan document is translated and the borrower's name shifts by one letter in transliteration, or a survey number reads 47 instead of 41, the error does not look like an error. It reads as a fact. Weeks later a drafter builds a notice around that name, or a title search runs against that survey number, and the mistake has propagated into work that no one thinks to question. Names and numbers carry the highest risk in any translation because they are exactly the details a fluent output makes look trustworthy.

Pull the high-risk items onto their own list

Do not verify names and numbers by reading the paragraphs around them. Extract them into a dedicated sheet where each one stands alone and demands a decision:

• Personal and entity names, including relationships such as "son of" or "wife of".
• Identity and document numbers: Aadhaar, PAN, account, survey, khasra and case numbers.
• Dates in every form, including those written in words or a regional calendar.
• Amounts, areas and rates, with their units and currency.
• Addresses, place names and jurisdictional references.

Check every item against the image, not the extraction

The extracted text is one remove from the truth. OCR misreads a Kannada or Odia numeral, drops a matra that distinguishes two names, or joins two figures into one. So verify each list item against the original scan itself, not against the machine's transcription of it. This is the single check that catches the errors most likely to travel silently into later documents.

Treat transliteration as a decision, not a default

Indian names rarely have one correct spelling in the Latin script. The same Devanagari name may be written Sanjay or Sanjai; a place may appear as Tiruchirappalli or Trichy. Where more than one spelling is defensible, do not let the tool decide at random. Check the client's own records, passports, deeds and prior filings, choose the form the person actually uses, and keep it consistent across the matter while preserving the original script beside it. Two spellings of one name can otherwise be mistaken for two people.

Reconcile against records you already trust

A number is easiest to check when you have something to check it against. Compare each identity number, date and amount with the client's known records and any earlier documents in the file. A figure that contradicts the file is a flag whether or not the translation reads cleanly, and it is far cheaper to resolve now than after it has been relied on.

Keep the checked list with the translation

The verification is only useful if it travels with the document. Attach the checked list, showing the source spelling, the chosen rendering and any variant you rejected, so the next person drafting from the translation works with confirmed details rather than re-deriving them. Keeping the source and the translation aligned makes this straightforward: each name and number stays anchored to the place it came from.

The rest of a translation can be revisited if it reads oddly. A wrong name or number usually cannot, because nothing about it looks wrong. Verify these against the image first, settle transliterations deliberately, and pass the checked list forward — that is how a translation stays reliable in exactly the places where a fluent draft is most likely to mislead.