How do you translate an EN 10204 3.1 inspection certificate, compare a 3.1 certificate with 3.2, or explain a mill test certificate to a buyer who reads another language? Start with the evidence rather than the wording. The document identifies metallic products, their inspection basis and their declared conformity. A mistranslated certificate type, heat number or test condition can change what a reader believes has been verified.
People searching for EN 10204 2.1, 2.2, 3.1 and 3.2 translation usually need more than a dictionary equivalent for ‘certificate’. They need to preserve inspection specificity, the manufacturer’s declaration, the independence of the person validating results, material grade, heat traceability and the limits of the reported tests. This guide explains those distinctions for international suppliers, purchasing teams, engineering readers and technical translators.
An accurate multilingual mill test certificate translation keeps the original codes, results, units and evidence boundaries intact. It can improve the clarity of the explanatory language without converting a declaration into an independent inspection or turning a batch test into a test of every individual component. The practical aim is a translated document a technically competent reader can reconcile against the original and the physical material.
The central question is not whether a certificate looks official. It is what exactly this document proves about which product, through which testing route, and under whose validation. Read each table and identifier as part of that chain. The following sections walk from the four document types to heat numbers, mechanical tests, declarations, handovers and detailed quality assurance.
All miniature scenarios below are illustrative teaching examples rather than certificates issued by a real mill. Always apply the actual product standard, purchase order, laboratory method and current licensed standard to a real job. This is a translation and evidence-reading guide, not a substitute for the product’s conformity assessment or a qualified inspector.
The fields that must keep their meaning
1. A statement of compliance is not a table of test results
Type 2.1 is the manufacturer’s declaration that products meet the order requirements; it does not present test results. A translator who renders it as a laboratory inspection report gives the reader evidence the document never supplied. Think of this line as a coordinate on an evidence map: which object is involved, who is making the statement, what procedure produced the information, and what degree of certainty is supported? A multilingual reader should recover the same four answers after translation.
The document title and the sentence of conformity should remain consistent. In some languages a single everyday word covers both declaration and certificate, so a clarifying phrase about the absence of results may be necessary in explanatory notes. Before publishing, compare this paragraph against the source document at its original page and row, then against the terminology register. Check whether the translated heading still asks the same question of the evidence as the original.
Illustrative source: ‘Inspection document 2.1 – conforms to purchase order 418’. Preserve the code 2.1, order reference and declarant. Verify that no added wording implies independent sampling, witnessed tests or reported chemical values. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
2. What type 2.2 adds and what it does not
Type 2.2 is a manufacturer’s test report that includes results from non-specific inspection. It reports data, yet that does not by itself say the measured specimen belongs to the precise heat delivered to the buyer. The safest approach begins with a source-to-target field register. Assign each datum a location, type, expected format and check method. That turns a complicated table into verifiable translation units rather than one prose paragraph that hides crucial distinctions.
The distinction between non-specific and specific inspection should be explicit in teaching prose. A translated heading that says ‘tested delivery batch’ may be materially wrong if the tests represent production of the same type rather than the dispatched material. The safest explanatory sentence includes the qualifier, not just the headline noun. That qualifier helps buyers avoid converting a limited test statement into an unrestricted guarantee when a document is forwarded.
Illustrative source: ‘2.2 test report; typical tensile properties’. The word typical is not cosmetic. It protects the difference between a representative production test and product-specific certification, so retain it and review every nearby compliance claim. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
3. Why type 3.1 means specific inspection
A 3.1 inspection certificate includes results based on specific inspection and is validated by a manufacturer’s authorised inspection representative independent of the manufacturing department. This internal organisational independence is important but is not equivalent to certification by an external body. An ordinary word can acquire a formal meaning inside a technical standard. Use the formal term when the document invokes a standard, and reserve the everyday expression for plain-language explanation. Otherwise a familiar translation may be more misleading than an unfamiliar code.
For a reader comparing suppliers, the translation must retain both halves: the evidence belongs to a defined product or inspection unit, and the authorised validator is part of the manufacturer’s organisation. Avoid promoting that validator into a government regulator. Read the example twice: first as a language learner, then as someone responsible for accepting goods. The latter perspective reveals whether a seemingly harmless substitution could change traceability, acceptance or inspection scope.
Illustrative source: ‘EN 10204 3.1; heat LQ742; authorised inspection representative’. Translate the role accurately, keep the heat string unchanged, and ensure the buyer can trace the reported results to the material marking. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
4. The extra validation represented by type 3.2
Type 3.2 involves specific inspection with validation by the manufacturer’s authorised representative and an additional authorised representative of the purchaser or an inspector designated by official regulations. The precise appointment and arrangements depend on the applicable requirements. Numbers tend to survive language transfer visually, but their meaning can still change through labels, reference limits, decimal conventions or missing conditions. Verify the field as a complete claim, not as isolated characters.
Calling 3.2 simply ‘better steel’ confuses a document-validation route with product performance. It is the independent validation relationship, not an automatic upgrade in alloy chemistry, that distinguishes this document category. Different languages may use different sentence order, but the relationship among subject, result and condition must remain fixed. The reader should not need the original source merely to discover which number belongs to which claim.
Illustrative source: ‘Inspection certificate 3.2, inspector representative noted’. Match each signatory to the organisation and role shown. A logo alone should not be translated into a statement that an accredited body approved every supplied item. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
5. Specific inspection has a defined unit of evidence
Specific inspection may concern the products being supplied or test units of which they form part. That is different from saying an instrument measured every piece individually. Sampling plans, test units and material standards specify what the measurements represent. A procurement reader needs to distinguish what was requested, what was reported and what was actually validated. Keeping those as separate statements improves both translation and contract administration without inventing legal conclusions.
The translation should carry phrases such as ‘test unit’, ‘sample’, ‘batch’ and ‘item’ distinctly. If the source is ambiguous, preserve the ambiguity for a technical query rather than choosing the most expansive assertion. This is a good place to use a translator’s query rather than an editorial guess. Ask the manufacturer or technical owner to confirm the basis, then log the clarification with a page reference for future reuse.
Illustrative source: ‘Test unit A, specimens taken from parent plate’. This is not permission to translate ‘all plates tested’. Preserve the relationship between the sampled parent material and the scope of supplied products. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
6. Keep the standard number and edition visible
EN 10204 is a document-type standard; the material itself may be governed by a separate product specification. Translators must not silently replace one with the other or assume a country-specific document uses an equivalent standard. When a source uses a compact abbreviation, retain it if it functions as an identifier, then explain it at first mention. The result is accessible to a new reader and still searchable against the original technical literature.
Record the edition when the source states it, and preserve references to related technical standards as identifiers. Descriptive text can be localized, but standard numbers should remain searchable for the recipient and the procurement team. An audit-friendly translation can be elegant and restrained. Repeating the source’s code exactly is not a failure of localization; it protects the reader’s ability to search, compare and verify independently.
Illustrative source: ‘EN 10204:2004 / EN 10025-2’. Do not collapse the two references into ‘European steel certificate’. They answer different questions: the first concerns inspection documents, while the second can govern particular steel-product requirements. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
7. Purchase order references are part of the evidence chain
A certificate can be correct on its own terms but unrelated to the shipment a reader is checking. Order number, item number, product description and promised certificate type create the link between contract and document. The practical question for a reviewer is: could I use this target-language passage to identify the same sample, test, criterion and issuer as the source? If not, the passage is fluent but has not yet passed technical quality assurance.
A translation that drops a line-item suffix or normalizes leading zeroes can destroy matching. Preserve these identifiers as strings, not arithmetic quantities, and compare against the procurement record before release. A table cell can travel into purchasing software, spreadsheets or quality records. Design the translation so that copying it into those systems does not change decimal meaning or break the underlying identifier.
Illustrative source: ‘PO 000417 / item 04B’. The leading zeros and letter B are meaningful identifiers. Never rewrite the pair as ‘417/4’ merely because that appears cleaner in another language. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
8. Heat numbers must survive every language conversion
The heat or cast number links a melt of metal to a production record and, through controlled traceability, to the supplied products. It is a code, not ordinary prose; transliteration of its letters can be risky if identifiers are matched electronically. A useful bilingual glossary records approved terms with context and disallowed near-synonyms. It is not a list of words in isolation; it records which document function each expression serves and when a possible translation would overstate the source.
Label the identifier in the target language if needed, but preserve the original alphanumeric value. The same rule applies when the source uses ‘heat’, ‘cast’, ‘melt’ or a locally defined production term with a documented relationship. If this field appears in a footnote, preserve that footnote. Removing qualifications for visual neatness often does more harm than preserving a slightly more detailed target-language table.
Illustrative source: ‘Heat No. X7B-0192’. An Arabic, Thai or Chinese explanatory label may be translated, but X7B-0192 must remain exact. The inspector should be able to compare it character for character against a stamped mark. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
9. Batch, lot and heat are not interchangeable
A batch can denote a production or inspection grouping; a heat normally relates to a melt; a lot can be defined by the manufacturer’s system or the product standard. These groupings sometimes overlap, but translators must not assume they are synonymous. Do not make the translated output seem more complete than the source. Missing context should be noted as missing, not restored from memory or an unrelated example. Technical honesty is a readability feature when decisions depend on the document.
Ask which unit the original laboratory result represents. If the report shows one heat and two delivery batches, collapsing them into one ‘lot’ may erase a traceability distinction that matters during a recall or rejection. Ask what an adversarial reviewer would question: authorship, inspection scope, specimen identity, reference standard or numeric precision. Answer only with evidence actually provided, not a comforting assumption.
Illustrative source: ‘Heat H77 / batch B12 / inspection lot I3’. Keep three separate fields. A target-language glossary can explain how the producer uses each one without pretending that the values refer to identical groupings. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
10. The material grade is a formal designation
Grades such as S355JR, 316L or another product-specific designation carry technical meanings that ordinary descriptions such as ‘high-strength steel’ cannot replace. Grade names often involve composition, mechanical requirements, processing routes and edition-specific rules. At the release stage, have one reviewer inspect the words and another inspect identifiers, units, numbers and evidence links. The second pass catches defects that fluent prose makes easy to overlook.
Translate explanatory words around a grade, but do not translate the grade code into a made-up foreign-language equivalent. When comparing national specifications, explicitly mark any mapping as a technical comparison requiring confirmation. When explanation requires more words in the target language, place the explanation beside the value rather than replacing the value. This preserves compact source identifiers and improves comprehension without editing the original evidence.
Illustrative source: ‘Plate, grade S355JR’. Retain S355JR as a code. A translator should not infer that the result is interchangeable with an unverified grade bearing a similar yield-strength number in another system. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
11. Product form and condition define the claim
A plate, bar, seamless tube, welded pipe, forging and casting may have different testing requirements even under related materials families. Likewise, normalized, quenched-and-tempered and solution-annealed conditions are not interchangeable production states. Think of this line as a coordinate on an evidence map: which object is involved, who is making the statement, what procedure produced the information, and what degree of certainty is supported? A multilingual reader should recover the same four answers after translation.
A correct translated certificate lets the reader identify the supplied form and the state in which it was tested. Avoid replacing a precise heat-treatment expression with a generic assurance such as ‘factory processed’. Before publishing, compare this paragraph against the source document at its original page and row, then against the terminology register. Check whether the translated heading still asks the same question of the evidence as the original.
Illustrative source: ‘Seamless tube, solution annealed’. Keep both the tube-manufacture route and the heat-treatment condition. Translating only ‘tube’ erases context a buyer may need to check against an ordered specification. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
12. Chemical composition is a measured table, not marketing copy
Chemical results commonly use mass percentages and symbols such as C, Mn, P, S, Cr, Ni and Mo. The symbol identifies the element, the value records the result, and the column may indicate a limit, a measured value or both. The safest approach begins with a source-to-target field register. Assign each datum a location, type, expected format and check method. That turns a complicated table into verifiable translation units rather than one prose paragraph that hides crucial distinctions.
Be wary of decimal separators and of dropping the less-than sign from a limit. Chemistry rows should be matched digit by digit, with explicit clarification where locale conventions would otherwise create confusion. The safest explanatory sentence includes the qualifier, not just the headline noun. That qualifier helps buyers avoid converting a limited test statement into an unrestricted guarantee when a document is forwarded.
Illustrative source: ‘P ≤ 0.035 %; measured P 0.021 %’. The first is a limit and the second a test value. Rendering both as ‘phosphorus 0.035 percent’ would remove the actual result. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
13. Carbon equivalent calculations require their formula
A document may report a carbon equivalent or a related weldability index. Different specifications and calculation methods can use different formulae; the label alone does not justify substituting one calculation for another. An ordinary word can acquire a formal meaning inside a technical standard. Use the formal term when the document invokes a standard, and reserve the everyday expression for plain-language explanation. Otherwise a familiar translation may be more misleading than an unfamiliar code.
Translate the index name with its exact abbreviation and specify the referenced equation or standard where present. Do not calculate or round a replacement value from an incomplete chemistry table. Read the example twice: first as a language learner, then as someone responsible for accepting goods. The latter perspective reveals whether a seemingly harmless substitution could change traceability, acceptance or inspection scope.
Illustrative source: ‘CEV 0.42 (formula referenced in purchase specification)’. Preserve CEV and 0.42. An explanatory paragraph can define its role without asserting that every carbon-equivalent measure uses the same coefficients. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
14. Yield strength labels identify a measurement method
ReH, Rp0.2 and other yield-related notations indicate distinct definitions or reporting conventions. A generic translation of each as ‘strength’ can hide which point on a stress–strain relationship was measured. Numbers tend to survive language transfer visually, but their meaning can still change through labels, reference limits, decimal conventions or missing conditions. Verify the field as a complete claim, not as isolated characters.
Preserve the symbol in the table, add an accurate localized descriptor, and keep the corresponding unit. If the receiving audience asks for a comparison, distinguish measured yield behaviour from minimum specified values. Different languages may use different sentence order, but the relationship among subject, result and condition must remain fixed. The reader should not need the original source merely to discover which number belongs to which claim.
Illustrative source: ‘Rp0.2 355 MPa’. Do not change it to tensile strength 355 MPa. The figure belongs to a specified proof-strength convention, and a downstream engineering decision may depend on that distinction. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
15. Tensile strength and yield strength must not trade places
Rm commonly denotes tensile strength, whereas a yield metric concerns the onset or offset definition of plastic deformation. A certificate that reports both lets a designer check more than one property, but translation can easily blur the pair. A procurement reader needs to distinguish what was requested, what was reported and what was actually validated. Keeping those as separate statements improves both translation and contract administration without inventing legal conclusions.
Present values in the same table order as the original and retain symbols beside translated descriptors. Do not infer a missing engineering property from another measured value simply because a bilingual layout has a spare column. This is a good place to use a translator’s query rather than an editorial guess. Ask the manufacturer or technical owner to confirm the basis, then log the clarification with a page reference for future reuse.
Illustrative source: ‘Rp0.2 320 MPa / Rm 510 MPa’. A bad translation might say ‘maximum stress 320 / minimum stress 510’. Correctly identify which figure represents the reported proof strength and which the tensile result. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
16. Elongation needs its test basis
Elongation labels, specimen lengths and gauge-length conventions can differ. A lone percentage may be meaningless in comparative prose if the original uses a specific test specimen or standard. When a source uses a compact abbreviation, retain it if it functions as an identifier, then explain it at first mention. The result is accessible to a new reader and still searchable against the original technical literature.
Translate the measurement designation and preserve the percentage and sample basis where shown. Avoid promising that a value from one gauge-length convention is equivalent to another without a legitimate conversion route. An audit-friendly translation can be elegant and restrained. Repeating the source’s code exactly is not a failure of localization; it protects the reader’s ability to search, compare and verify independently.
Illustrative source: ‘A5 = 24 %’. Retain A5, not merely ‘ductility 24%’. A translator can explain that the measured elongation depends on a defined tensile-test setup rather than converting it into a broad product-quality rating. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
17. Impact energy includes temperature and specimen details
Charpy impact testing often involves absorbed energy in joules and a specified test temperature. The orientation, specimen dimensions or reduction rules may also matter when the source provides them. The practical question for a reviewer is: could I use this target-language passage to identify the same sample, test, criterion and issuer as the source? If not, the passage is fluent but has not yet passed technical quality assurance.
Removing a minus sign from the test temperature or forgetting that an average applies to several specimens is more serious than a grammar problem. Numbers and test conditions must be proofread together. A table cell can travel into purchasing software, spreadsheets or quality records. Design the translation so that copying it into those systems does not change decimal meaning or break the underlying identifier.
Illustrative source: ‘KV2: 35 J at −20 °C’. Preserve the negative temperature and KV2 designation. A translated ’35 J at 20 °C’ points to a radically different test condition. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
18. Hardness and other supplementary tests have their own scales
Hardness values reported as HBW, HRC or another scale are not bare numbers. Supplementary tests may depend on material form and purchase requirements, and not every inspection certificate reports them. A useful bilingual glossary records approved terms with context and disallowed near-synonyms. It is not a list of words in isolation; it records which document function each expression serves and when a possible translation would overstate the source.
Keep the scale designation beside the number and do not invent a conversion into another scale. If a customer needs converted engineering values, that is a separate technical assessment with limitations. If this field appears in a footnote, preserve that footnote. Removing qualifications for visual neatness often does more harm than preserving a slightly more detailed target-language table.
Illustrative source: ‘Hardness 210 HBW’. Translating the number alone as 210 without HBW makes the result harder to interpret and may invite an incorrect comparison with Rockwell scales. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
19. Non-destructive testing statements need boundaries
Ultrasonic, radiographic, magnetic-particle and penetrant examination can be mentioned on inspection documentation, but their methods, coverage, acceptance classes and report references must not be silently generalized. Do not make the translated output seem more complete than the source. Missing context should be noted as missing, not restored from memory or an unrelated example. Technical honesty is a readability feature when decisions depend on the document.
A phrase such as ‘no indications above acceptance threshold’ is narrower than ‘no defects exist’. Translations should preserve the tested area, the applicable acceptance criteria and the status of any separate NDT report. Ask what an adversarial reviewer would question: authorship, inspection scope, specimen identity, reference standard or numeric precision. Answer only with evidence actually provided, not a comforting assumption.
Illustrative source: ‘UT accepted to method reference, area stated’. Do not turn that into ‘entire product defect free’. A buyer should still be able to identify which examination was performed and what it evaluated. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
20. Dimension columns are not interchangeable
Thickness, width, outside diameter, wall thickness, length and nominal sizes describe different geometry. Even within a single product family, units and nominal dimensions can diverge from actual measured dimensions. At the release stage, have one reviewer inspect the words and another inspect identifiers, units, numbers and evidence links. The second pass catches defects that fluent prose makes easy to overlook.
Use unambiguous target-language column headers and preserve unit notation. Convert units only when asked, and when converting add the exact basis rather than replacing the documentary measurement silently. When explanation requires more words in the target language, place the explanation beside the value rather than replacing the value. This preserves compact source identifiers and improves comprehension without editing the original evidence.
Illustrative source: ‘OD 114.3 mm / WT 6.0 mm’. OD is outside diameter and WT is wall thickness. Translating both as ‘pipe width’ would make a procurement table impossible to check. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
21. Dates, revisions and superseded pages are evidence fields
Issue date, test date, manufacturing date and document revision can serve different purposes. A corrected certificate may supersede an earlier version; a simple ‘last modified’ translation cannot establish which evidence was current at dispatch. Think of this line as a coordinate on an evidence map: which object is involved, who is making the statement, what procedure produced the information, and what degree of certainty is supported? A multilingual reader should recover the same four answers after translation.
Keep dates unambiguous, especially where day/month order differs internationally. Preserve the certificate number and revision marker, and review stamps or headers that identify cancelled or replaced pages. Before publishing, compare this paragraph against the source document at its original page and row, then against the terminology register. Check whether the translated heading still asks the same question of the evidence as the original.
Illustrative source: ‘Issued 04/05/2026; revision B’. If the origin’s date convention is unknown, do not silently choose April 5 or May 4. Mark it for clarification before issuing a translated certificate. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
22. Signatures and stamps do not independently prove authenticity
A signature field can identify who validated a document, but its presence alone does not establish that the issuer is real, authorised or connected to the actual product. Authenticity checks belong to a verification process. The safest approach begins with a source-to-target field register. Assign each datum a location, type, expected format and check method. That turns a complicated table into verifiable translation units rather than one prose paragraph that hides crucial distinctions.
Translate personal titles and organisational roles conservatively. Never add a claim such as ‘officially approved’ merely because the scan contains a stamp, embossed mark or business logo. The safest explanatory sentence includes the qualifier, not just the headline noun. That qualifier helps buyers avoid converting a limited test statement into an unrestricted guarantee when a document is forwarded.
Illustrative source: ‘Verified by quality representative’. Keep the signatory’s role as actually printed. Buyers can verify directly with the issuer if necessary; a translator should not certify the underlying inspection. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
23. Different languages handle decimals differently
Some languages and document formats use commas for decimal separators and spaces or periods for grouping. Translating engineering results requires protecting the underlying numerical value across these conventions. An ordinary word can acquire a formal meaning inside a technical standard. Use the formal term when the document invokes a standard, and reserve the everyday expression for plain-language explanation. Otherwise a familiar translation may be more misleading than an unfamiliar code.
A bilingual layout can show original numeric data unchanged to avoid ambiguity. If the target locale mandates a different separator, the change needs structured verification against source and units, not a global find-and-replace. Read the example twice: first as a language learner, then as someone responsible for accepting goods. The latter perspective reveals whether a seemingly harmless substitution could change traceability, acceptance or inspection scope.
Illustrative source: ‘0.035 % C’. An unreviewed conversion to ‘0,035’ may be understood in some locales, while a comma placed in a thousands position can be misread; preserve precision and the percent sign. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
24. Pass and fail are judgments against a named requirement
A measured value by itself is not a compliance decision. Conformance depends on the specified limits, applicable test method, condition and test unit. The translator should preserve the reported judgment without creating an independent one. Numbers tend to survive language transfer visually, but their meaning can still change through labels, reference limits, decimal conventions or missing conditions. Verify the field as a complete claim, not as isolated characters.
When a source column says ‘accept’ or ‘conforms’, keep that claim scoped to the named criteria. When it does not say pass, do not add a reassuring tick mark just because a value looks reasonable. Different languages may use different sentence order, but the relationship among subject, result and condition must remain fixed. The reader should not need the original source merely to discover which number belongs to which claim.
Illustrative source: ‘Rm measured 515 MPa; requirement per PO’. Do not insert ‘pass’ unless the source or verified criteria support it. A translation can accurately present both the measured figure and the referenced requirement. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
25. When a heat is divided, traceability must continue
Cutting, machining, repacking or relabeling material can separate pieces from the original visible heat marking. Transfer of identification is a quality-system question, not something the translator can establish through elegant terminology. A procurement reader needs to distinguish what was requested, what was reported and what was actually validated. Keeping those as separate statements improves both translation and contract administration without inventing legal conclusions.
Translate any transfer statement precisely, including who transferred marks and under what procedure. Where the source contains no transfer evidence, do not claim that the finished part is linked to the original heat. This is a good place to use a translator’s query rather than an editorial guess. Ask the manufacturer or technical owner to confirm the basis, then log the clarification with a page reference for future reuse.
Illustrative source: ‘Transferred heat identification per procedure M-04’. Retain M-04 and its scope. If the next document lists another identification number, the connection must be supported by records, not guessed. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
26. A distributor’s reissued copy has a different role
Material distributors sometimes forward or reissue documentation related to a manufacturer’s original certificate. Their cover letter does not automatically make them the manufacturer or an independent inspection authority. When a source uses a compact abbreviation, retain it if it functions as an identifier, then explain it at first mention. The result is accessible to a new reader and still searchable against the original technical literature.
The translated heading should distinguish original producer, stockholder, trader and test laboratory. If a distributor’s document attests to a copy, say so rather than rewriting it as the underlying laboratory record. An audit-friendly translation can be elegant and restrained. Repeating the source’s code exactly is not a failure of localization; it protects the reader’s ability to search, compare and verify independently.
Illustrative source: ‘True copy of mill certificate supplied by stockholder’. Keep ‘copy’ visible. A purchaser should be able to ask for the original certificate and reconcile names, material IDs and supplied quantities. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
27. A certificate does not automatically cover finished fabrication
Heat-related evidence can establish properties of parent material, while welding, machining, fabrication and service suitability involve additional requirements. Translators must not stretch material certification into whole-assembly certification. The practical question for a reviewer is: could I use this target-language passage to identify the same sample, test, criterion and issuer as the source? If not, the passage is fluent but has not yet passed technical quality assurance.
Where the source references welded parts, preserve whether it discusses the raw material, weld filler, weld procedure or completed assembly. Each has different evidence and responsible parties. A table cell can travel into purchasing software, spreadsheets or quality records. Design the translation so that copying it into those systems does not change decimal meaning or break the underlying identifier.
Illustrative source: ‘Pipe material certified to 3.1’. This is not the same as stating that a completed pressure system has been inspected, pressure-tested and approved for operation. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
28. Comparing international grades is a separate technical task
A customer may ask whether an EN grade corresponds to an ASTM, JIS or other national grade. Similar names and typical numerical properties do not establish contractual interchangeability across standards. A useful bilingual glossary records approved terms with context and disallowed near-synonyms. It is not a list of words in isolation; it records which document function each expression serves and when a possible translation would overstate the source.
In translation, preserve the source designation and provide a separate, clearly qualified comparison only when supported by the appropriate material specification and engineering review. Do not replace the grade in the original record. If this field appears in a footnote, preserve that footnote. Removing qualifications for visual neatness often does more harm than preserving a slightly more detailed target-language table.
Illustrative source: ‘S355JR to ASTM equivalence requested’. A safe translation records S355JR first and asks the technical reviewer to assess chemistry, mechanical minima, impact requirements, product thickness and delivery condition. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
29. Missing fields should become queries, not inventions
Scanned certificates may contain illegible stamps, cropped signatures, blurred decimal points or absent headers. The worst practice is filling the gap with the most likely meaning because a neighboring certificate looks similar. Do not make the translated output seem more complete than the source. Missing context should be noted as missing, not restored from memory or an unrelated example. Technical honesty is a readability feature when decisions depend on the document.
Use a transparent query log recording page, row, ambiguous character, possible interpretations and the person asked to resolve it. A target-language reader should not mistake a translator’s guess for the manufacturer’s test data. Ask what an adversarial reviewer would question: authorship, inspection scope, specimen identity, reference standard or numeric precision. Answer only with evidence actually provided, not a comforting assumption.
Illustrative source: ‘Heat H8?2, final digit obscured’. Preserve the uncertainty in the working record and request the original. Do not quietly decide that the character is 7 because it matches another shipment document. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
30. A bilingual certificate needs one-to-one field mapping
A two-column translated certificate should let a reviewer trace every title, table cell, footnote, disclaimer and signature to its source location. This is particularly important where right-to-left scripts reorder punctuation or mixed Latin codes. At the release stage, have one reviewer inspect the words and another inspect identifiers, units, numbers and evidence links. The second pass catches defects that fluent prose makes easy to overlook.
Protect identifiers from bidirectional rendering problems and check values visually in exported PDF, not only in the editor. Hidden reordering of digits can pass a casual language review while breaking traceability. When explanation requires more words in the target language, place the explanation beside the value rather than replacing the value. This preserves compact source identifiers and improves comprehension without editing the original evidence.
Illustrative source: ‘Heat AB-107 / document 00392’. Preserve the exact Latin code and numerical ordering in the delivered bilingual file. Confirm that the PDF text layer and visual display agree. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
31. What to do when a source certificate contradicts itself
A certificate may show a grade in its title and another in a table, or one heat number in the header and a different number on page two. Translation is not authorised to silently reconcile these discrepancies. Think of this line as a coordinate on an evidence map: which object is involved, who is making the statement, what procedure produced the information, and what degree of certainty is supported? A multilingual reader should recover the same four answers after translation.
Keep an exception record, quote the conflicting fields by location, request issuer clarification and pause release of any statement that would hide the conflict. A revised source may be needed before a trustworthy translation exists. Before publishing, compare this paragraph against the source document at its original page and row, then against the terminology register. Check whether the translated heading still asks the same question of the evidence as the original.
Illustrative source: ‘Header heat A117; chemistry page heat A171’. Do not choose the version appearing more often. The appropriate outcome is a query linked to the original pages. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
32. Decide whether the output is a translation, summary or review
A full certified-document translation, a bilingual explanatory summary and an engineering verification report are different deliverables. A reader should know which one has been provided, and whether numbers are transcribed or independently checked. The safest approach begins with a source-to-target field register. Assign each datum a location, type, expected format and check method. That turns a complicated table into verifiable translation units rather than one prose paragraph that hides crucial distinctions.
State the deliverable type, translation language and source version. If an independent reviewer has not tested material or verified the issuer, avoid language that implies those acts occurred. The safest explanatory sentence includes the qualifier, not just the headline noun. That qualifier helps buyers avoid converting a limited test statement into an unrestricted guarantee when a document is forwarded.
Illustrative source: ‘Translation of certificate supplied by customer, original dated …’. That disclaimer does not weaken useful work; it prevents the translation from being mistaken for fresh inspection evidence. The useful translation decision is to preserve this piece of evidence exactly where it belongs, while making its function clearer to the reader. A reviewer should be able to trace both the term and its factual referent back to the source without reconstructing the missing context.
Eighteen realistic handover situations
Handover 1: A plant imports stainless pipe
Procurement receives an English 3.1 certificate with chemical and mechanical tables. The localized summary should keep the manufacturer’s name, heat identifiers and test symbols while explaining the scope of specific inspection. If the goods arriving at the warehouse have no matching heat marks, translation cannot close that evidence gap. For this situation, the translated deliverable should distinguish the source statement from any reviewer inference. Keep original identifiers and results visible, document unresolved questions, and refuse to turn a convenience summary into a new claim of technical approval.
Handover 2: Two vendors use different document types
One supplier provides 2.2 while another provides 3.1. A bilingual comparison must not call them equivalent ‘quality certificates’. The first may report non-specific results; the second reports results of specific inspection. The purchasing decision depends on the order and application, not a translator’s preference for stronger-sounding wording. For this situation, the translated deliverable should distinguish the source statement from any reviewer inference. Keep original identifiers and results visible, document unresolved questions, and refuse to turn a convenience summary into a new claim of technical approval.
Handover 3: A pressure-equipment project requests 3.2
The engineer’s order specifies independent validation. Receiving a well-formatted 3.1 is not a reason to relabel it 3.2. The translator should preserve both the contractual requirement and the certificate actually supplied, leaving conformity assessment to the responsible team. For this situation, the translated deliverable should distinguish the source statement from any reviewer inference. Keep original identifiers and results visible, document unresolved questions, and refuse to turn a convenience summary into a new claim of technical approval.
Handover 4: A heat code is scanned incorrectly
The material mark reads ZX-708B while OCR extracted ZX-7088. Text recognition has confused a letter with a digit. The bilingual QA compares the translation to the original scan and, ideally, the physical inventory record. The source photograph, not the auto-transcribed line, decides the correction. For this situation, the translated deliverable should distinguish the source statement from any reviewer inference. Keep original identifiers and results visible, document unresolved questions, and refuse to turn a convenience summary into a new claim of technical approval.
Handover 5: A negative impact-test temperature vanishes
An impact result of 27 J at minus 40 degrees Celsius is rendered at positive 40 degrees. The unit and number look plausible, but the specification meaning has changed. The translator restores the negative sign and checks every temperature-linked result on the document. For this situation, the translated deliverable should distinguish the source statement from any reviewer inference. Keep original identifiers and results visible, document unresolved questions, and refuse to turn a convenience summary into a new claim of technical approval.
Handover 6: A value is labelled ‘minimum’
A specification minimum and a measured result are not synonymous. If the certificate has separate requirement and actual columns, the translation should show both. A row that says ‘minimum yield 355 MPa’ should not imply a measured yield of exactly 355 MPa. For this situation, the translated deliverable should distinguish the source statement from any reviewer inference. Keep original identifiers and results visible, document unresolved questions, and refuse to turn a convenience summary into a new claim of technical approval.
Handover 7: The purchase order contains an optional test
The general material standard does not itself guarantee the optional test appears. The original order, addendum and certificate must be read together. A translated document should reflect whether the optional requirement was fulfilled, waived or never documented; it must not invent a result. For this situation, the translated deliverable should distinguish the source statement from any reviewer inference. Keep original identifiers and results visible, document unresolved questions, and refuse to turn a convenience summary into a new claim of technical approval.
Handover 8: A distributor issues a cover sheet
The stockholder’s multilingual cover sheet lists shipment quantities and attaches a mill certificate. Its role is documentary transmission, not proof that the stockholder conducted every reported test. Preserve issuer attribution separately for both sheets. For this situation, the translated deliverable should distinguish the source statement from any reviewer inference. Keep original identifiers and results visible, document unresolved questions, and refuse to turn a convenience summary into a new claim of technical approval.
Handover 9: A batch was cut into small parts
The heat marking originally sat on the parent plate. When it was cut, each daughter piece needed traceability arrangements under the producer’s control system. A translated label cannot repair a lost chain of identification; it can help an auditor locate the transfer record. For this situation, the translated deliverable should distinguish the source statement from any reviewer inference. Keep original identifiers and results visible, document unresolved questions, and refuse to turn a convenience summary into a new claim of technical approval.
Handover 10: A buyer asks for ‘certification’
The request may mean third-party product certification, an EN 10204 inspection document or an ordinary supplier declaration. Rather than force all meanings into one word, the translation should identify the expected evidence category and ask the buyer which standard or contract clause governs acceptance. For this situation, the translated deliverable should distinguish the source statement from any reviewer inference. Keep original identifiers and results visible, document unresolved questions, and refuse to turn a convenience summary into a new claim of technical approval.
Handover 11: The engineering team wants unit conversion
Source values are reported in MPa and the project summary uses psi. Keep the original value and unit visible, then provide an explicitly labelled calculated conversion checked for rounding. Do not change the original certificate’s issued figures or imply conversion is a laboratory retest. For this situation, the translated deliverable should distinguish the source statement from any reviewer inference. Keep original identifiers and results visible, document unresolved questions, and refuse to turn a convenience summary into a new claim of technical approval.
Handover 12: The file arrives as a low-quality scan
A blurred decimal can be the difference between a compliant result and an alarming reading. QA flags every uncertain digit and requests a higher-quality source. Linguistic fluency is not a substitute for source legibility. For this situation, the translated deliverable should distinguish the source statement from any reviewer inference. Keep original identifiers and results visible, document unresolved questions, and refuse to turn a convenience summary into a new claim of technical approval.
Handover 13: A document crosses a right-to-left language boundary
Latin alloy codes, heat numbers and punctuation can display out of order in an otherwise correct Arabic or Hebrew paragraph. A reviewer should check the exported file character by character and ensure copying the code produces the exact same sequence. For this situation, the translated deliverable should distinguish the source statement from any reviewer inference. Keep original identifiers and results visible, document unresolved questions, and refuse to turn a convenience summary into a new claim of technical approval.
Handover 14: A certificate refers to a separate NDT report
The translated summary can cite the NDT report identifier without asserting universal freedom from defects. Its inspection coverage and acceptance criteria must be reviewed in that separate report, not inferred from an abbreviated certificate reference. For this situation, the translated deliverable should distinguish the source statement from any reviewer inference. Keep original identifiers and results visible, document unresolved questions, and refuse to turn a convenience summary into a new claim of technical approval.
Handover 15: An old revision circulates alongside a new one
The supplier emails revision C but the warehouse stores revision B. A multilingual title page should identify the revision translated and its issue date so receiving staff can reconcile the current file instead of treating both as independent product approvals. For this situation, the translated deliverable should distinguish the source statement from any reviewer inference. Keep original identifiers and results visible, document unresolved questions, and refuse to turn a convenience summary into a new claim of technical approval.
Handover 16: A laboratory symbol resembles an English word
Symbols Rm, ReH and Rp0.2 are not everyday words to translate phonetically. They should remain stable identifiers with carefully selected explanatory labels, while their values and units remain attached to the proper rows. For this situation, the translated deliverable should distinguish the source statement from any reviewer inference. Keep original identifiers and results visible, document unresolved questions, and refuse to turn a convenience summary into a new claim of technical approval.
Handover 17: A buyer wants a one-page decision memo
The memo can say what document type was received, which heat it names, whether the figures are legible and which fields need expert verification. It should avoid pretending that a translation specialist independently determined material suitability. For this situation, the translated deliverable should distinguish the source statement from any reviewer inference. Keep original identifiers and results visible, document unresolved questions, and refuse to turn a convenience summary into a new claim of technical approval.
Handover 18: A certificate’s signature is partly cropped
The translated copy should not invent a signatory or institution from a partial stamp. Mark the area requiring clarification and request the complete scan. The purpose is to preserve the evidentiary chain rather than create a cleaner fiction. For this situation, the translated deliverable should distinguish the source statement from any reviewer inference. Keep original identifiers and results visible, document unresolved questions, and refuse to turn a convenience summary into a new claim of technical approval.
A practical translation release procedure
First, identify the exact source version and confirm all pages are present. Second, record the document type, issuer, product specification, purchase order, heat numbers and test units in a traceability sheet. Third, translate the surrounding language while preserving identifiers, technical symbols, column structures and source figures. Fourth, check the target-language text against the original one field at a time. Fifth, route material-grade or test-method interpretation to a qualified technical reviewer rather than attempting to decide conformity through language alone.
Next, inspect the final output in its delivered format. A PDF may introduce line wrapping, superscript errors, reversed character order or missing inequality signs that were not visible in an editor. Perform a numeric review covering decimals, negatives, units, percentages, degrees and inequality signs. Perform a document review covering page totals, revision IDs, seals, signatures, references and attached reports. The final check is whether the material, document and order can still be reconciled.
Questions readers frequently ask
Is a 3.1 certificate the same as third-party certification? No. The manufacturer’s authorised representative is independent of the manufacturing department, which is not the same thing as an external independent inspection body. That distinction belongs in the translated explanation.
Can a translator turn a 2.2 into a 3.1 by adding more test data? No. The document type refers to the inspection and validation arrangement, not the length of its table. It must be issued through the relevant process by the responsible parties.
Does a 3.2 document guarantee fitness for any purpose? No. It indicates a particular inspection-document category and validation route. The material still needs to be assessed against the actual purchase specification and intended use.
Should test figures be converted to the reader’s preferred units? Only if the deliverable calls for it, and preferably as an additional, clearly labelled derived value. Preserve the original issued result and its unit.
What happens if the supplier’s document is unclear? Flag the uncertainty, request a clearer source or issuer clarification, and keep an exception record. Do not confuse fluent guesses with verified inspection data.
A final way to read the certificate
A useful translation enables the buyer to answer four questions without losing technical meaning: what material was ordered, which material was supplied, what evidence was reported, and who validated that evidence? Every translated heading, number and footnote should contribute to those answers. The goal is not to sound authoritative. It is to carry the precise original basis for a decision across languages.
Related reading: How English Works: Translation and Meaning Across Languages and the protected Vocabulary Learning Hub explain the wider language foundations without being replaced by this document-specific guide.
Useful technical reading: Inspection document types and validating representatives. Always use the purchased edition of EN 10204 and the applicable material standards for formal requirements.