Translation of a European fire-classification report demands more than a correct word for ‘fireproof’. Searchers asking how to translate Euroclass B-s1,d0, EI 30, EI 60 or REI 60 need to know which fire property was classified, what was actually tested and which installation or assembly the result covers. Misreading the letters can turn a defensible technical record into an unsafe construction claim.
A panel marked B-s1,d0 under EN 13501-1 is not automatically an EI 30 wall under EN 13501-2. The first notation describes reaction-to-fire performance of a relevant product or system in the applicable test context; the second describes fire resistance of an element under another classification scheme. One addresses contribution to fire behaviour, smoke and droplets; the other addresses how an element maintains specified functions for a classified period.
This educational guide explains how to render the codes, minutes, suffixes and scope of European fire reports faithfully in other languages. It concentrates on the exact search intent—interpreting and translating fire-classification notation—and does not replace the governing building code, the original classification report, manufacturer installation instructions or competent fire-safety review.
Quick answer: what this document actually says
Reaction to fire and fire resistance are not interchangeable. EN 13501-1 deals with reaction-to-fire classes and applicable smoke or flaming-droplet suffixes. EN 13501-2 concerns resistance classifications such as R, E and I, normally tied to specific building elements, tested assemblies and application conditions. Preserve full notation and the source report’s field of application. Never derive an installation approval from a code alone.
The translation problem before the first sentence
Technical translation succeeds when the target-language reader can make the same practical decision as the source-language reader. In fire classification reports for construction products and assemblies, a number without a defined property may look authoritative while answering the wrong question. First identify the object being measured, then the method, then the units, then any acceptance threshold. Resist the temptation to supply missing evidence because the prose sounds smoother after simplification.
A useful working file has two columns: the original technical expression and the proposed reader-facing interpretation. Add a third column for evidence that supports that interpretation. If the original says a sample was tested, keep ‘sample’; if it says a requirement must be met, keep the obligation; if it reports a target, do not turn it into an observation. These distinctions survive far more translations than a list of one-word equivalents.
The editorial hierarchy matters too. An illustrative calculation demonstrates a method, but it is not a replacement for the laboratory certificate, carrier tariff or contractual schedule governing a real transaction. Describe uncertainty honestly; cite the named standard or provider; and avoid universal claims in fields where a different test edition, application or delivery platform would produce a different answer.
A practical source-to-target verification workflow
- Preserve the original expression, every sign, code, unit and identifier before drafting an explanatory sentence.
- Identify the measured quantity and distinguish it from an estimate, a target, a threshold, a range and an observed result.
- Record the applicable method, edition, configuration, recipient and scope of evidence; do not silently modernise a cited standard.
- Translate the human-readable words while keeping technical identifiers stable unless the source explicitly supplies an authorised local equivalent.
- Test the translated sentence against a simple practical example and ask whether it would lead to the same decision as the original.
- Check all exclusions and conditions; have a suitably qualified reviewer examine consequential safety, billing or compliance claims.
Read the following cases as a decision practice rather than as a dictionary. Each begins with a plausible excerpt. The figures and situations are teaching examples unless attributed to an identified published rule. The purpose is to explain why apparently small language choices change the meaning of a real technical record.
Part I — Read the quantity and its units
1. Reaction to fire versus resistance
Illustrative source situation. A specification pairs EN 13501-1 with EN 13501-2 references. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. The documents classify different fire properties; one result does not automatically prove the other. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Using the generic target-language word ‘fire rating’ for both without a qualifier hides a safety-critical distinction. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Translate as reaction-to-fire classification or fire-resistance classification, and retain the exact EN reference. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Check which standard, test and subject the evidence actually covers. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
2. B-s1,d0 punctuation
Illustrative source situation. A façade finish carries B-s1,d0. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. The B class and the s and d suffixes form one reaction-to-fire classification expression. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Dropping commas or suffixes can erase stated smoke and droplet aspects from the report. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Keep B-s1,d0 exactly, followed by a concise explanation of class, smoke and droplets. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Verify every character against the signed classification report. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
3. The letter B is not an hour rating
Illustrative source situation. A product brochure abbreviates its class to B. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Class B in this scheme concerns reaction behaviour, not sixty or thirty minutes of barrier performance. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. A local translator might wrongly replace B with a numerical resistance rating customary elsewhere. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Retain the B reaction-to-fire class and avoid assigning a time classification. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Compare only like-for-like classification frameworks and evidence. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
4. A1 and A2 are distinct
Illustrative source situation. Two products have A1 and A2-s1,d0 declarations. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. They are different classification outcomes with different applicable nomenclature and test criteria. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Calling both merely ‘completely non-combustible’ erases the differences and overclaims the A2 result. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Name the declared class precisely without substituting a broader marketing adjective. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Check both reports and product installation contexts before comparing. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
5. Smoke suffix s1
Illustrative source situation. A construction declaration includes s1. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. This suffix identifies a smoke-production class in the relevant reaction-to-fire classification. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Rendering s1 as ‘smoke free’ may claim zero smoke, which is not what the class means. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Preserve s1 as the declared smoke class and explain it in qualified language. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Avoid turning comparative classification into an absolute no-smoke promise. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
6. Smoke suffix s3
Illustrative source situation. The declared rating ends with s3. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Smoke performance is classified according to the applicable method and the s3 category. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Translating s3 as proof of a particular real-fire toxic dose is unwarranted. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. State smoke classification s3 without predicting health effects in a real incident. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Verify whether the relevant product category uses that suffix scheme. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
7. Droplet suffix d0
Illustrative source situation. The label ends in d0. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. The d class relates to flaming droplets or particles under specified test conditions. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Writing ‘no material can ever drip while burning’ exaggerates the classification. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Retain d0 and qualify the statement by the referenced reaction-to-fire test. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Check that the suffix belongs to the exact tested product configuration. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
8. Droplet suffix d2
Illustrative source situation. A technical certificate includes d2. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. This is a classification category rather than an instruction or duration in minutes. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. A mistranslation can turn a suffix into an invented flame-resistance period. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Describe d2 as its declared flaming-droplet classification. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Keep the entire code unchanged even if the target-language explanation varies. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
9. Flooring suffixes
Illustrative source situation. A floor covering is rated Bfl-s1. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. The fl notation identifies flooring under the applicable reaction-to-fire scheme. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Removing fl makes the product appear comparable to non-floor applications that use different criteria. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Keep Bfl-s1 intact and identify the product as flooring. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Verify that the report and use category refer to floor covering. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
Part II — Preserve boundaries, methods and conditions
10. Cables have their own notation
Illustrative source situation. A cable declaration uses B2ca-s1,d1,a1. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Cable notation and additional suffixes operate within the relevant cable classification scheme. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Reducing this to a generic B rating destroys the cable-specific components. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Preserve the full cable code and explain each suffix only against its proper reference. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Check the cable test and national requirements independently. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
11. EI 30 describes two criteria
Illustrative source situation. A partition wall has EI 30 classification. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. E denotes integrity and I denotes insulation for the specified classified period. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Calling EI 30 a load-bearing structural rating adds a criterion not present in the code. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Fire resistance EI 30: integrity and insulation for 30 minutes under the specified classification. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Check the test specimen, construction and application limitations. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
12. E 30 is not EI 30
Illustrative source situation. A glazed element is stated as E 30. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. This classification identifies integrity without independently asserting the I criterion. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Adding I because it sounds more reassuring is a substantive falsification. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Fire resistance E 30, integrity criterion only as reported. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Ensure the recipient understands what was not established. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
13. REI 60 includes load bearing
Illustrative source situation. A load-bearing wall has REI 60. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. R is load-bearing capacity, E integrity and I insulation, for the declared period. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Dropping R or interpreting it as a generic ‘resistance’ word masks structural scope. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Fire resistance REI 60: R, E and I criteria for 60 minutes in the tested system. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Confirm both the load case and assembly construction. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
14. R 60 structural criterion
Illustrative source situation. A structural element has R 60. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. R addresses load-bearing capacity under a specified fire-exposure test, not separation performance. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. A translation to ‘seals flames for an hour’ invents an E criterion. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Fire resistance R 60 for load-bearing capacity, as defined by the report. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Do not infer integrity or insulation without separate evidence. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
15. W radiation criterion
Illustrative source situation. A glazed system has EW 30. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. The added W addresses a radiation-related criterion alongside integrity under the specified classification. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Silently translating W as insulation confuses different assessed thermal behaviours. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Preserve EW 30 and explain the radiative criterion separately from I. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Confirm which performance was measured and the applicable geometry. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
16. Door smoke classifications
Illustrative source situation. A doorset report also lists Sa or S200. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Smoke leakage classes relate to designated door testing and should remain separate from EI. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Calling every EI door smoke-tight overstates the reported characteristics. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. State the smoke classification exactly where the relevant report declares it. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Review doorset evidence and hardware configuration. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
17. Self-closing notation
Illustrative source situation. A door certificate lists a self-closing class. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Such performance belongs to the certified doorset configuration and its test context. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Treating the closer as an optional cosmetic accessory may change an approved assembly. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Keep self-closing designation and component requirements in the translation. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Check the door hardware schedule against the classification documentation. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
18. Minutes are laboratory classification
Illustrative source situation. A wall is described as EI 60. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. The stated period is a classification under controlled test conditions, not a guaranteed survival or safe-evacuation countdown. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Writing that a fire can safely burn for exactly an hour in any building misrepresents evidence. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Say sixty-minute fire-resistance classification under the specified test, without emergency guarantees. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Refer safety decisions to competent designers and applicable law. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
Part III — Produce a defensible reader-facing translation
19. One component versus assembly
Illustrative source situation. A fire-resistant board is used inside a wall. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. A component claim does not by itself certify an assembled wall of arbitrary studs and fixings. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Translating panel performance as a universal wall rating skips the assembly boundary. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. State separately the board product result and the tested wall assembly result. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Compare specification and test construction before approving substitution. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
20. Orientation matters
Illustrative source situation. A test specimen was exposed on one nominated face. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Fire exposure direction may limit the declared field of application. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Omitting inward-versus-outward exposure language can broaden a rating beyond its evidence. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Record the tested direction and any permitted application directions. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Check the classification report’s scope rather than guessing from product symmetry. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
21. Substrate and mounting
Illustrative source situation. A coating test identifies a specific substrate. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Reaction-to-fire class can depend on mounting and supporting material under the relevant classification rules. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Publishing the same class for any substrate assumes untested equivalence. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Translate the complete mounting and substrate conditions attached to the rating. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Ask whether the actual project application lies within the declared field. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
22. Penetrations and joints
Illustrative source situation. An EI-rated partition contains service openings. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Fire-stopping systems, joints and penetrations need their own specified evidence or detailing. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. A translator who deletes installation notes may make an incomplete wall seem compliant. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Preserve required joint, seal, opening and penetration conditions. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Cross-check the intended construction drawings with approved details. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
23. Doorset versus leaf
Illustrative source situation. The certificate lists a doorset, frame and hardware. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. The classified product often includes components and installation details beyond the visible leaf. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Calling an isolated leaf ‘EI 60 certified’ for any frame can be misleading. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Identify exactly the door assembly and hardware scope tested or assessed. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Verify frame, seals, glazing, closer and dimensions before writing a claim. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
24. Do not equate national codes
Illustrative source situation. A contractor requests a direct ASTM E119 or local equivalent. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Different jurisdictions and tests can have different exposure, criteria and certification systems. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. An informal one-hour comparison is not a formal interchangeability decision. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. State the original EN result and flag any proposed equivalence for code review. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Require the authorised authority or qualified professional to determine acceptability. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
25. Report number and edition
Illustrative source situation. A fire certificate includes an EN edition and laboratory report number. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Those identifiers allow the translation to be linked back to the actual evidence. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Removing the date or edition makes it harder to detect a mismatched or superseded document. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Copy standard edition, report identifier, specimen description and issue date exactly. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Verify the source document against the manufacturer or issuing body. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
26. Project-specific approval
Illustrative source situation. A project specification requires EI 60 doorsets. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Evidence, installation and local building requirements jointly determine whether a particular product is acceptable. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. A translated brochure alone cannot certify on-site compliance. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Describe the product’s reported class and separately list unverified project requirements. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Keep approval decisions with the relevant building-control and fire-safety professionals. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
Ten reader questions to answer before signing off
1. What is the reader searching for?
Usually an accurate interpretation of a particular value or identifier. Give that answer first, then show the narrower condition that makes it true. For fire classification reports for construction products and assemblies, this question should be resolved against the material that the translator actually possesses, not against a generic internet shorthand. Record any uncertainty so the next reader can see what was assumed and what remains to be checked.
2. Should a code be translated?
Generally preserve formal technical identifiers. Translate explanatory words around them and use an authorised equivalent only where it is explicitly documented. For fire classification reports for construction products and assemblies, this question should be resolved against the material that the translator actually possesses, not against a generic internet shorthand. Record any uncertainty so the next reader can see what was assumed and what remains to be checked.
3. Is a numerical conversion safe?
Only after identifying the original units and whether exact or approximate conversion is appropriate. Never manufacture precision. For fire classification reports for construction products and assemblies, this question should be resolved against the material that the translator actually possesses, not against a generic internet shorthand. Record any uncertainty so the next reader can see what was assumed and what remains to be checked.
4. What happens when the source omits a method?
Flag the missing method. An apparently familiar number may not support the same conclusion under another procedure. For fire classification reports for construction products and assemblies, this question should be resolved against the material that the translator actually possesses, not against a generic internet shorthand. Record any uncertainty so the next reader can see what was assumed and what remains to be checked.
5. Can a marketing summary replace a report?
No. It can help explain a result, but it does not extend the original test population, configuration or approval. For fire classification reports for construction products and assemblies, this question should be resolved against the material that the translator actually possesses, not against a generic internet shorthand. Record any uncertainty so the next reader can see what was assumed and what remains to be checked.
6. Does a higher figure always mean better performance?
No. Some scales have indirect numbering, ceilings, tolerances or non-comparable test methods. Interpret the defined quantity. For fire classification reports for construction products and assemblies, this question should be resolved against the material that the translator actually possesses, not against a generic internet shorthand. Record any uncertainty so the next reader can see what was assumed and what remains to be checked.
7. What if the translated sentence sounds awkward?
Improve its syntax while preserving every condition. Readability is valuable only when the underlying claim remains unchanged. For fire classification reports for construction products and assemblies, this question should be resolved against the material that the translator actually possesses, not against a generic internet shorthand. Record any uncertainty so the next reader can see what was assumed and what remains to be checked.
8. Can software produce a finished translation alone?
Software can help with drafting and consistency checks. Specialist review remains important when errors affect safety, finance or contractual compliance. For fire classification reports for construction products and assemblies, this question should be resolved against the material that the translator actually possesses, not against a generic internet shorthand. Record any uncertainty so the next reader can see what was assumed and what remains to be checked.
9. Which version should the reader trust?
Prefer the signed current source document for the exact transaction or project, with its report identifier and edition. For fire classification reports for construction products and assemblies, this question should be resolved against the material that the translator actually possesses, not against a generic internet shorthand. Record any uncertainty so the next reader can see what was assumed and what remains to be checked.
10. Where should broader vocabulary and language study continue?
Use the existing specialist pathways rather than allowing a narrowly focused technical guide to become a competing general translation hub. For fire classification reports for construction products and assemblies, this question should be resolved against the material that the translator actually possesses, not against a generic internet shorthand. Record any uncertainty so the next reader can see what was assumed and what remains to be checked.
A compact handoff checklist
A complete technical handoff should preserve the exact original phrase, the revised translation, a short meaning note, units, standards or recipient instructions, source document version, decision-relevant limits and a list of unresolved questions. Put examples in a visibly educational context. Do not quietly copy a teaching example into a commercial certificate, and do not let a plausible translation substitute for evidence that has not been supplied. Readers looking for a quick answer should be able to find it near the top; readers making expensive decisions should be able to follow the reasoning to its source.
Further reading and the existing language-learning ecosystem
This guide is one practical branch of the wider translation architecture. For general language comprehension, word meaning and precise English use, continue through eduKateSG Vocabulary and How English Works. Those existing resources remain the general owners; this article handles the specialised search question: how to translate Euroclass reaction-to-fire labels such as B-s1,d0 and fire-resistance classifications such as EI 30 or REI 60 without confusing product reaction with assembly resistance.
Technical and regulatory standards can be revised. The cited resources establish definitions and published context, not permission to ignore a current contractual specification. Check source dates, editions and local requirements before acting. This article is educational nonfiction and is not a certificate, approval, engineering assessment or substitute for professional review.