Independent educational guide for building designers, commissioning teams, technical translators, facilities analysts and multilingual energy-model reviewers. All mini-cases below are fictional teaching examples rather than excerpts from the standard or claims of certification.
Translating ISO 17772-1:2017 indoor environmental input parameters requires more than finding words for temperature, ventilation and lighting. Building energy-model translation and multilingual design documentation must preserve whether a value is a design assumption, an input criterion, a calculation result or a field measurement. One misplaced word can turn a modeled condition into a claimed fact about how a building performs.
A consultant might write that an energy simulation assumes a certain occupancy schedule, while a translated brochure states that the premises are occupied during those hours. Or a design criterion for ventilation becomes a claim that measured indoor air quality already meets it. The numbers may be identical, yet the meaning changes. The solution is to translate the evidence type, criterion category, units, zone and time basis as carefully as the headline.
In brief: identify the document’s design stage; separate assumed, calculated and measured values; preserve category definitions; document occupancy patterns; distinguish thermal, air-quality, lighting and acoustic criteria; check time and unit conventions; flag missing environmental context; and have the model owner validate translated data tables.
The exact question this guide answers
This article answers how to translate indoor environmental design criteria, occupancy schedules and building-energy model tables across languages without converting assumptions into performance guarantees. It is a focused reference for a single professional translation problem, not a general language-learning hub. The guiding question is simple: what must remain true when the words move from one language to another, and what evidence will establish that the receiving reader understands the same action, object and degree of certainty? A natural-sounding sentence is not sufficient if it changes a code, data value, required step, professional role, condition or record status.
Use the article as a learning guide, not as a replacement for a purchased normative document, a regulated professional decision, or project-specific instructions. Official source: ISO 17772-1:2017 catalogue record. The publicly available catalogue describes the subject and edition; detailed normative requirements must be checked in an authorized copy where they matter. This guide provides original educational examples and explains how to make and test bilingual decisions responsibly.
Where the standard begins, and where translation responsibility begins
ISO 17772-1:2017 concerns indoor environmental input parameters for building energy-performance design and assessment, including criteria categories and occupancy schedules. It does not prescribe a complete building design method or prove that a particular occupied room will achieve a desired condition. Designs, simulations and measured building conditions are different evidence types. Translators should read each parameter with its applicable assumptions, unit, location, time period and category.
For indoor environmental input parameters for building energy and comfort models, the source package often includes more than the standard’s title. It may contain a specification, a glossary, an amended requirement, a dated procedure, a user interface, a spreadsheet, evidence files, a contract and a training document. These items have different authority. The translator should list them in a source register before drafting and mark which one controls identifiers, definitions, calculations, action verbs and approval status. A conflict between two source documents is a problem for the document owner, not a licence for the translator to guess.
A useful project record has six columns: source object or phrase; what it refers to; target wording; unchanged code or value; reason for the decision; and named reviewer. Add a seventh column for revision and an eighth for remaining uncertainty if the job is large. The result is a termbase that does not merely collect synonyms. It records the circumstances in which each expression can safely be used. That is what prevents a later writer from substituting an attractive but incorrect word.
First, identify the reader and the consequence of misunderstanding
Different readers need different kinds of clarity. A system integrator needs exact strings and stable mappings; a professional reviewer needs provenance and conditions; a manager needs a defensible summary; a learner needs definitions and worked examples; a customer needs an instruction they can act upon without believing an unverified promise. Agree which reader is primary and which secondary. If a text serves several audiences, write layered explanations rather than weakening exact technical meaning.
Apply a consequence test to every significant phrase. Ask what a reader might do differently if it were translated another way. Could they identify the wrong object, enter the wrong value, mistake a draft for an approval, treat a condition as a guarantee, repeat a step unnecessarily, or omit a required exception? This test puts review time where it matters most. A typo in an illustrative heading deserves correction; a changed identifier or false acceptance claim deserves release blocking.
The practical method: source map, meaning map, target text, evidence
- Source map: locate the authoritative edition, project-specific document, revision and owner.
- Meaning map: identify actors, objects, events, quantities, conditions, controlled terms and uncertainty.
- Target text: write natural, grammatical language without changing the source relationship.
- Data integrity: keep machine identifiers, document references, units and controlled status values exact where appropriate.
- Evidence review: compare each high-risk decision with the originating record and competent reviewer.
- Release test: read the translated output in its real interface, report, instruction or export.
1. Input is not outcome
An indoor environmental input criterion can guide analysis before the building exists or before a new operating mode is tested. It should not be translated as evidence of a completed room’s performance. Give each reported number a provenance label: intended design input, simulation result, commissioning measurement or operational observation.
A practical exercise is to cover the original adjective or noun and describe the underlying event or object in ordinary language. Then compare that description with the proposed translation. If the translated phrase would cause a qualified reader to locate a different object or infer a different outcome, it needs repair. Write the corrected meaning first; choose polished wording second.
2. Criteria and categories
Criteria may be organized into categories reflecting different expectations or applications. Do not call a category ‘premium’, ‘legal compliance’, or ‘safe’ without support. Preserve the label and explain its context. Where a project adopts national annexes or local requirements, identify those separately from the general standard.
Before final sign-off, mark the evidence next to the sentence: document name, version, worksheet cell, identifier, diagram, or approved decision. A target-language reviewer who can only say that a sentence “sounds natural” has not yet checked its technical truth. Include one deliberately ambiguous example in the review pack to test whether reviewers notice what the source has left unresolved.
3. Thermal parameters
Air temperature, operative temperature, radiant temperature, air speed and other thermal quantities may be related but are not synonyms. Their relevance changes with measurement location, occupancy and model method. Translators should always preserve the named physical quantity and the measurement or calculation method stated in the source.
The common temptation is to simplify until the distinction disappears. A better educational explanation has two layers: a short visible line for rapid use and a fuller note for readers who need boundaries and exceptions. Both must remain faithful. If the short version overpromises, it is not made safe by a hidden footnote.
4. Indoor air quality
Ventilation air supply, indoor pollutant indicators, occupancy and outdoor air quality influence interpretation. A translated ventilation rate needs both units and denominator. It does not by itself certify clean air for every contaminant or exposure condition. Keep the source’s assumptions and limitations visible.
Quality control here benefits from a reverse trace rather than blind back-translation. Have a second person point from the translated sentence to its original source concept and explain why any numbers, roles, conditions or record states stayed unchanged. That checks the job performed, rather than rewarding two sentences that merely resemble each other.
5. Lighting and visual environment
Illuminance, daylight availability, glare and visual comfort are distinct. A number in lux is not automatically a statement about how a particular person experiences lighting. Preserve whether an assessment concerns a design target, calculation plane, simulated daylight or an actual measurement.
Suppose the source changes after translation has begun. Do not patch only the most visible word. Search the termbase and the full delivered file for every dependent occurrence, then record what was updated and what remained valid. This matters in multilingual teams, where a single modified requirement can affect a caption, warning, training example and summary page.
6. Acoustic context
Acoustic environment descriptions can refer to limits, target criteria or measured conditions. Avoid converting a numerical model requirement into a promise of complete silence. The location, operating mode, background conditions and evaluation metric must be clear.
A practical exercise is to cover the original adjective or noun and describe the underlying event or object in ordinary language. Then compare that description with the proposed translation. If the translated phrase would cause a qualified reader to locate a different object or infer a different outcome, it needs repair. Write the corrected meaning first; choose polished wording second.
7. Occupancy and schedules
Occupancy calendars, density, work hours and activity profiles can drive energy calculations. They are analytical assumptions unless a record says they are observed utilization. Days of week, holiday handling, start/end times and time zones need exact localization. Never turn a schedule template into a statement of contractual building hours.
Before final sign-off, mark the evidence next to the sentence: document name, version, worksheet cell, identifier, diagram, or approved decision. A target-language reviewer who can only say that a sentence “sounds natural” has not yet checked its technical truth. Include one deliberately ambiguous example in the review pack to test whether reviewers notice what the source has left unresolved.
8. Zones and building boundaries
An energy model may divide a building into zones whose names look like public room names but are internal analysis groupings. Keep zone keys stable and translate friendly descriptions separately. If two rooms share a zone or one room spans zones, let the model reflect that rather than inventing a one-to-one mapping.
The common temptation is to simplify until the distinction disappears. A better educational explanation has two layers: a short visible line for rapid use and a fuller note for readers who need boundaries and exceptions. Both must remain faithful. If the short version overpromises, it is not made safe by a hidden footnote.
9. Climate and seasons
A design table can refer to winter, summer, outdoor conditions, heating season or cooling season. The applicable calendar and local climate should be confirmed for each location; a hemisphere switch cannot be solved by word substitution alone. Review weather files and the project location before translating season-dependent results.
Quality control here benefits from a reverse trace rather than blind back-translation. Have a second person point from the translated sentence to its original source concept and explain why any numbers, roles, conditions or record states stayed unchanged. That checks the job performed, rather than rewarding two sentences that merely resemble each other.
10. Validation across modeling and measurement
A bilingual design report should let a reader trace each claim to its data source. Compare model settings, assumption tables, calculation outputs and any measurement report. Keep a change log when translators find missing units or inconsistent occupancy assumptions, and have the project professional resolve them.
Suppose the source changes after translation has begun. Do not patch only the most visible word. Search the termbase and the full delivered file for every dependent occurrence, then record what was updated and what remained valid. This matters in multilingual teams, where a single modified requirement can affect a caption, warning, training example and summary page.
Worked translation cases: source situation, likely mistake, repair and independent check
The following cases are invented, scenario-based exercises for indoor environmental input parameters for building energy and comfort models. They do not quote ISO requirements, certify a product, or provide a substitute for professional decisions. Their aim is to make the reasoning visible so a reader can repeat the process on a real authorized document. Each case distinguishes four questions: what the source actually says, how a translation could mislead, what a defensible revision would preserve, and what evidence closes the issue.
Case 1: Operative temperature
Picture the document in use. A model schedule specifies operative temperature for a zone. A translator who sees only the isolated phrase could miss the relationship that gives it its meaning. Before drafting, identify the object, its role, the surrounding sentence and the record that will govern a later decision.
Where the meaning can drift. Replacing it with ambient room temperature without confirming equivalence. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Keep the physical quantity named in the source and explain it separately if needed. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
The quality test is concrete: Engineer verifies the model variable and its units. Check any linked data values and revision references as well as the words. Save the decision with the original example, reviewer and date so that another translator can use the same reasoning without treating an isolated phrase as universally interchangeable.
Case 2: Air temperature
Consider a real handover conversation reconstructed as a fictional exercise: An office briefing gives a calculated air temperature. The reader is not primarily trying to admire the prose. They need to understand a particular instruction, definition or piece of evidence. The translation must allow them to reach the same practical conclusion as the source reader.
Where the meaning can drift. Writing it as the temperature measured by a wall thermostat. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Mark whether the value is simulated or observed. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
To close the case, Compare the source result table and instrument records. A successful test should let the reviewer reconstruct the source event from the target language and distinguish stated facts from assumptions. If the translation is understandable but the reviewer cannot trace it to source evidence, the case remains open.
Case 3: Radiant temperature
Here is a typical point of failure in a bilingual workflow: A technical note references radiative thermal conditions. The source wording needs to be read together with its technical context. A short glossary entry is helpful, but a glossary cannot decide a disputed meaning without the underlying document and its owner.
Where the meaning can drift. Collapsing radiant temperature into air temperature. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Use the correct thermal parameter without inventing a measurement. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
The required evidence is not a vote on elegant style: Check the modeling method and variable glossary. Put both language versions into the format people will actually read. Captions, truncated headings or a reformatted table can undo an otherwise correct linguistic choice; the release check must include that final view.
Case 4: Air speed
Start with a question the receiving reader would ask: what is this statement telling me to recognize or do? In this example, A room model contains air velocity at a relevant location. The answer determines whether the translated expression should read like a role, an object, an event, a status, a condition or an explanation rather than a loose synonym.
Where the meaning can drift. Translating speed as a fan setting rather than local air movement. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Preserve location, unit and physical quantity. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
Independent confirmation means that Mechanical engineer checks the diagram and variable. Record what was accepted, which version was inspected and which conditional facts remain unresolved. Professional translation quality includes an honest boundary around what the material does not establish.
Case 5: Humidity
Picture the document in use. An input table presents relative humidity as a percentage. A translator who sees only the isolated phrase could miss the relationship that gives it its meaning. Before drafting, identify the object, its role, the surrounding sentence and the record that will govern a later decision.
Where the meaning can drift. Converting it to an absolute moisture content by wording alone. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Retain relative humidity and its percentage basis. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
The quality test is concrete: Compare original and bilingual table headers. Check any linked data values and revision references as well as the words. Save the decision with the original example, reviewer and date so that another translator can use the same reasoning without treating an isolated phrase as universally interchangeable.
Case 6: Thermal category
Consider a real handover conversation reconstructed as a fictional exercise: A project applies an indoor environmental criterion category. The reader is not primarily trying to admire the prose. They need to understand a particular instruction, definition or piece of evidence. The translation must allow them to reach the same practical conclusion as the source reader.
Where the meaning can drift. Marketing it as evidence of legal approval or universal comfort. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Keep the chosen category and intended design context explicit. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
To close the case, Check the project’s official criteria selection record. A successful test should let the reviewer reconstruct the source event from the target language and distinguish stated facts from assumptions. If the translation is understandable but the reviewer cannot trace it to source evidence, the case remains open.
Case 7: Ventilation rate
Here is a typical point of failure in a bilingual workflow: A report describes outdoor air provision with a rate. The source wording needs to be read together with its technical context. A short glossary entry is helpful, but a glossary cannot decide a disputed meaning without the underlying document and its owner.
Where the meaning can drift. Dropping the per-person or floor-area denominator. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Preserve the full quantity, denominator and flow unit. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
The required evidence is not a vote on elegant style: Modeler checks the calculation input and scenario. Put both language versions into the format people will actually read. Captions, truncated headings or a reformatted table can undo an otherwise correct linguistic choice; the release check must include that final view.
Case 8: Indoor pollutant
Start with a question the receiving reader would ask: what is this statement telling me to recognize or do? In this example, A design note includes a pollutant concentration assumption. The answer determines whether the translated expression should read like a role, an object, an event, a status, a condition or an explanation rather than a loose synonym.
Where the meaning can drift. Calling an assumed level a measured air quality finding. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. State exactly that the quantity is an assumption when applicable. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
Independent confirmation means that Check if there was a valid field monitoring report. Record what was accepted, which version was inspected and which conditional facts remain unresolved. Professional translation quality includes an honest boundary around what the material does not establish.
Case 9: Outdoor air
Picture the document in use. A ventilation schedule distinguishes outside air from recirculated air. A translator who sees only the isolated phrase could miss the relationship that gives it its meaning. Before drafting, identify the object, its role, the surrounding sentence and the record that will govern a later decision.
Where the meaning can drift. Translating both as generic fresh air. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Retain source and flow distinctions without adding performance claims. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
The quality test is concrete: HVAC designer inspects system diagrams. Check any linked data values and revision references as well as the words. Save the decision with the original example, reviewer and date so that another translator can use the same reasoning without treating an isolated phrase as universally interchangeable.
Case 10: Air filtration
Consider a real handover conversation reconstructed as a fictional exercise: A report records an assumed filtration parameter. The reader is not primarily trying to admire the prose. They need to understand a particular instruction, definition or piece of evidence. The translation must allow them to reach the same practical conclusion as the source reader.
Where the meaning can drift. Saying the installed filters passed an inspection. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Preserve design specification versus installation evidence. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
To close the case, Compare design spec and commissioning documents. A successful test should let the reviewer reconstruct the source event from the target language and distinguish stated facts from assumptions. If the translation is understandable but the reviewer cannot trace it to source evidence, the case remains open.
Case 11: Illuminance
Here is a typical point of failure in a bilingual workflow: A lighting design uses an illuminance value in lux. The source wording needs to be read together with its technical context. A short glossary entry is helpful, but a glossary cannot decide a disputed meaning without the underlying document and its owner.
Where the meaning can drift. Converting it to brightness or luminance without basis. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Keep illuminance and the reference plane or area. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
The required evidence is not a vote on elegant style: Lighting engineer checks the calculation report. Put both language versions into the format people will actually read. Captions, truncated headings or a reformatted table can undo an otherwise correct linguistic choice; the release check must include that final view.
Case 12: Daylight
Start with a question the receiving reader would ask: what is this statement telling me to recognize or do? In this example, A simulation predicts daylight at a stated time. The answer determines whether the translated expression should read like a role, an object, an event, a status, a condition or an explanation rather than a loose synonym.
Where the meaning can drift. Turning a daylight model into an all-day measured result. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Retain simulation, time interval and assumed sky conditions. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
Independent confirmation means that Cross-check model scenario and input assumptions. Record what was accepted, which version was inspected and which conditional facts remain unresolved. Professional translation quality includes an honest boundary around what the material does not establish.
Case 13: Glare
Picture the document in use. A design discussion evaluates a visual discomfort criterion. A translator who sees only the isolated phrase could miss the relationship that gives it its meaning. Before drafting, identify the object, its role, the surrounding sentence and the record that will govern a later decision.
Where the meaning can drift. Reporting that there is no glare anywhere. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Translate the selected evaluation and its limits. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
The quality test is concrete: Lighting owner checks the defined glare metric. Check any linked data values and revision references as well as the words. Save the decision with the original example, reviewer and date so that another translator can use the same reasoning without treating an isolated phrase as universally interchangeable.
Case 14: Acoustic target
Consider a real handover conversation reconstructed as a fictional exercise: A concept design sets an acoustic goal for occupied space. The reader is not primarily trying to admire the prose. They need to understand a particular instruction, definition or piece of evidence. The translation must allow them to reach the same practical conclusion as the source reader.
Where the meaning can drift. Claiming actual sound tests have met the goal. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Call it a target until measurement evidence exists. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
To close the case, Acoustician approves the translated section. A successful test should let the reviewer reconstruct the source event from the target language and distinguish stated facts from assumptions. If the translation is understandable but the reviewer cannot trace it to source evidence, the case remains open.
Case 15: Noise measurement
Here is a typical point of failure in a bilingual workflow: A commissioning annex contains a measured acoustic value. The source wording needs to be read together with its technical context. A short glossary entry is helpful, but a glossary cannot decide a disputed meaning without the underlying document and its owner.
Where the meaning can drift. Presenting it as a generic environmental target. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Keep measurement date, location and metric intact. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
The required evidence is not a vote on elegant style: Reviewer matches instrument report to the summarized result. Put both language versions into the format people will actually read. Captions, truncated headings or a reformatted table can undo an otherwise correct linguistic choice; the release check must include that final view.
Case 16: Occupancy density
Start with a question the receiving reader would ask: what is this statement telling me to recognize or do? In this example, An energy model assumes people per area. The answer determines whether the translated expression should read like a role, an object, an event, a status, a condition or an explanation rather than a loose synonym.
Where the meaning can drift. Replacing modeled occupancy with the fire-code maximum. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Distinguish simulation population from an independently defined maximum. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
Independent confirmation means that Building professional compares assumptions and occupancy approvals. Record what was accepted, which version was inspected and which conditional facts remain unresolved. Professional translation quality includes an honest boundary around what the material does not establish.
Case 17: Weekday schedule
Picture the document in use. A building simulation uses a Monday-to-Friday profile. A translator who sees only the isolated phrase could miss the relationship that gives it its meaning. Before drafting, identify the object, its role, the surrounding sentence and the record that will govern a later decision.
Where the meaning can drift. Rewriting it as posted opening hours. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Label it as modeled usage and keep days and hours. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
The quality test is concrete: Energy analyst compares the calendar profile. Check any linked data values and revision references as well as the words. Save the decision with the original example, reviewer and date so that another translator can use the same reasoning without treating an isolated phrase as universally interchangeable.
Case 18: Weekend schedule
Consider a real handover conversation reconstructed as a fictional exercise: A simulation sets lower weekend presence. The reader is not primarily trying to admire the prose. They need to understand a particular instruction, definition or piece of evidence. The translation must allow them to reach the same practical conclusion as the source reader.
Where the meaning can drift. Calling weekends fully unoccupied in public notices. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Translate the numerical schedule without broadening its implication. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
To close the case, Check a weekend input table and exceptions. A successful test should let the reviewer reconstruct the source event from the target language and distinguish stated facts from assumptions. If the translation is understandable but the reviewer cannot trace it to source evidence, the case remains open.
Case 19: Holiday override
Here is a typical point of failure in a bilingual workflow: A workbook contains a separate public-holiday pattern. The source wording needs to be read together with its technical context. A short glossary entry is helpful, but a glossary cannot decide a disputed meaning without the underlying document and its owner.
Where the meaning can drift. Dropping it because the translated country uses different holidays. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. State the model’s actual location-specific holiday treatment. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
The required evidence is not a vote on elegant style: Review the weather year and local calendar setup. Put both language versions into the format people will actually read. Captions, truncated headings or a reformatted table can undo an otherwise correct linguistic choice; the release check must include that final view.
Case 20: Time zone
Start with a question the receiving reader would ask: what is this statement telling me to recognize or do? In this example, A multinational portfolio imports schedules from different regions. The answer determines whether the translated expression should read like a role, an object, an event, a status, a condition or an explanation rather than a loose synonym.
Where the meaning can drift. Switching local times without updating their time-zone meaning. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Keep time-zone context or document verified conversion. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
Independent confirmation means that Modeler tests an hour-by-hour export. Record what was accepted, which version was inspected and which conditional facts remain unresolved. Professional translation quality includes an honest boundary around what the material does not establish.
Case 21: Room zone key
Picture the document in use. A schedule assigns thermal-zone identifiers such as Z-07. A translator who sees only the isolated phrase could miss the relationship that gives it its meaning. Before drafting, identify the object, its role, the surrounding sentence and the record that will govern a later decision.
Where the meaning can drift. Translating the identifier itself into a descriptive room name. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Preserve the zone key and translate the description separately. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
The quality test is concrete: Join the output to the native model using unchanged keys. Check any linked data values and revision references as well as the words. Save the decision with the original example, reviewer and date so that another translator can use the same reasoning without treating an isolated phrase as universally interchangeable.
Case 22: Space use
Consider a real handover conversation reconstructed as a fictional exercise: A planning spreadsheet categorizes meeting, corridor and plant areas. The reader is not primarily trying to admire the prose. They need to understand a particular instruction, definition or piece of evidence. The translation must allow them to reach the same practical conclusion as the source reader.
Where the meaning can drift. Treating these categories as legally binding occupancy certificates. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Present them as model categories in context. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
To close the case, Compare actual design brief and model classification. A successful test should let the reviewer reconstruct the source event from the target language and distinguish stated facts from assumptions. If the translation is understandable but the reviewer cannot trace it to source evidence, the case remains open.
Case 23: Clothing assumption
Here is a typical point of failure in a bilingual workflow: A thermal assessment lists clothing-related parameters. The source wording needs to be read together with its technical context. A short glossary entry is helpful, but a glossary cannot decide a disputed meaning without the underlying document and its owner.
Where the meaning can drift. Explaining them as mandatory clothing rules for occupants. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Retain the model assumption and its unit when applicable. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
The required evidence is not a vote on elegant style: Review thermal comfort calculation notes. Put both language versions into the format people will actually read. Captions, truncated headings or a reformatted table can undo an otherwise correct linguistic choice; the release check must include that final view.
Case 24: Activity level
Start with a question the receiving reader would ask: what is this statement telling me to recognize or do? In this example, A comfort estimate assumes an occupant activity profile. The answer determines whether the translated expression should read like a role, an object, an event, a status, a condition or an explanation rather than a loose synonym.
Where the meaning can drift. Changing it into a statement about employee behavior. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Translate the assumed activity category rather than inventing observed behavior. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
Independent confirmation means that Check the source methodology and scenario. Record what was accepted, which version was inspected and which conditional facts remain unresolved. Professional translation quality includes an honest boundary around what the material does not establish.
Case 25: Outdoor design condition
Picture the document in use. A calculation references a representative outdoor weather condition. A translator who sees only the isolated phrase could miss the relationship that gives it its meaning. Before drafting, identify the object, its role, the surrounding sentence and the record that will govern a later decision.
Where the meaning can drift. Calling it the measured temperature on commissioning day. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Keep the weather-file or design-condition identity. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
The quality test is concrete: Review geographic station and climate data basis. Check any linked data values and revision references as well as the words. Save the decision with the original example, reviewer and date so that another translator can use the same reasoning without treating an isolated phrase as universally interchangeable.
Case 26: Heating season
Consider a real handover conversation reconstructed as a fictional exercise: A European design model includes heating-period assumptions. The reader is not primarily trying to admire the prose. They need to understand a particular instruction, definition or piece of evidence. The translation must allow them to reach the same practical conclusion as the source reader.
Where the meaning can drift. Using the same winter dates for a tropical location by literal translation. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Preserve the original model dates and note location context. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
To close the case, Model owner signs off on climate adaptation. A successful test should let the reviewer reconstruct the source event from the target language and distinguish stated facts from assumptions. If the translation is understandable but the reviewer cannot trace it to source evidence, the case remains open.
Case 27: Cooling load
Here is a typical point of failure in a bilingual workflow: A spreadsheet reports cooling-system sizing results. The source wording needs to be read together with its technical context. A short glossary entry is helpful, but a glossary cannot decide a disputed meaning without the underlying document and its owner.
Where the meaning can drift. Presenting load as actual electricity consumption. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Distinguish thermal demand from energy consumption. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
The required evidence is not a vote on elegant style: Cross-check the unit and report section. Put both language versions into the format people will actually read. Captions, truncated headings or a reformatted table can undo an otherwise correct linguistic choice; the release check must include that final view.
Case 28: Calculated versus observed
Start with a question the receiving reader would ask: what is this statement telling me to recognize or do? In this example, A report includes model estimates and sensor readings side by side. The answer determines whether the translated expression should read like a role, an object, an event, a status, a condition or an explanation rather than a loose synonym.
Where the meaning can drift. Removing the labels because the columns have similar values. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Keep the distinction in headings and captions. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
Independent confirmation means that Compare both data provenance records. Record what was accepted, which version was inspected and which conditional facts remain unresolved. Professional translation quality includes an honest boundary around what the material does not establish.
Case 29: Decimal format
Picture the document in use. A bilingual table has values using different decimal separators. A translator who sees only the isolated phrase could miss the relationship that gives it its meaning. Before drafting, identify the object, its role, the surrounding sentence and the record that will govern a later decision.
Where the meaning can drift. Changing 1.5 into 15 through regional formatting. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Localize numeric display only with machine-tested semantics. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
The quality test is concrete: Verify parsed values remain identical. Check any linked data values and revision references as well as the words. Save the decision with the original example, reviewer and date so that another translator can use the same reasoning without treating an isolated phrase as universally interchangeable.
Case 30: Design promise
Consider a real handover conversation reconstructed as a fictional exercise: A brochure summarizes environmental targets from design documentation. The reader is not primarily trying to admire the prose. They need to understand a particular instruction, definition or piece of evidence. The translation must allow them to reach the same practical conclusion as the source reader.
Where the meaning can drift. Saying the completed building is proven comfortable. That would be more than a stylistic difference if it changed the object being discussed or the degree of certainty of the record. The translator should annotate the suspected ambiguity before refining the prose. If two readings are plausible, the approved source owner must choose; the translator should not make a hidden technical decision.
Better wording and handling. Describe the design intention and avoid unsupported performance guarantees. Keep one stable formulation in the approved terminology table, and make the explanatory language as accessible as the audience requires. It is useful to show a complete sample sentence or annotated table cell, not merely a pair of words, because most misunderstandings arise from what the term does in context.
To close the case, Legal and building professionals approve public-facing statements. A successful test should let the reviewer reconstruct the source event from the target language and distinguish stated facts from assumptions. If the translation is understandable but the reviewer cannot trace it to source evidence, the case remains open.
A field-ready bilingual review and correction worksheet
Open a worksheet with the columns “original text”, “source record”, “proposed translation”, “term type”, “required unchanged data”, “possible reader mistake”, “review evidence”, “owner”, “approved wording”, and “revision.” Populate it with each important heading, table caption, instruction, exception and status. In the term-type column distinguish ordinary prose, protected identifier, numeric quantity, controlled vocabulary and conditional requirement. A single field should not be marked approved merely because its spelling is correct. A second reviewer should be able to explain its function.
Prioritize checks in this order: any change that could reverse a decision or action; any loss of a qualification, warning, condition or exception; any change to numeric values, units, codes or identifiers; any source-version mismatch; and then naturalness and formatting. If a text is legally or technically consequential, do not use back-translation alone as final approval. It can be a diagnostic aid, but the source and target reviewers must inspect the underlying technical scenario.
When a discrepancy is found, write a repair note with four parts: the observed mismatch, its consequence, the authoritative source and the proposed remedy. Mark the item unresolved until its designated owner accepts the repair. Publish only a release whose version can be reproduced. This discipline makes translation a controlled knowledge-transfer activity instead of a series of private guesses.
Five roles and what each must actually approve
Linguist
Linguist is responsible for accurate grammar, genre, tone, reference tracking and consistency between all occurrences of a term. Give this reviewer two genuine test cases: one easy case where the correct answer is obvious, and one ambiguous case where the source lacks an important detail. Ask the reviewer to state what they can verify, what they cannot verify, and whether the translation signals that boundary. A signature without the example and source version is an inadequate audit trail. The team should also record whether this reviewer checked the PDF, screen, spreadsheet or printed instruction in its final delivery format.
Domain specialist
Domain specialist is responsible for technical relationship among objects, measurements, procedures, roles and permitted interpretations. Give this reviewer two genuine test cases: one easy case where the correct answer is obvious, and one ambiguous case where the source lacks an important detail. Ask the reviewer to state what they can verify, what they cannot verify, and whether the translation signals that boundary. A signature without the example and source version is an inadequate audit trail. The team should also record whether this reviewer checked the PDF, screen, spreadsheet or printed instruction in its final delivery format.
Document controller
Document controller is responsible for revision lineage, correct originals, identifiers, archive copies and release authorization. Give this reviewer two genuine test cases: one easy case where the correct answer is obvious, and one ambiguous case where the source lacks an important detail. Ask the reviewer to state what they can verify, what they cannot verify, and whether the translation signals that boundary. A signature without the example and source version is an inadequate audit trail. The team should also record whether this reviewer checked the PDF, screen, spreadsheet or printed instruction in its final delivery format.
Quality reviewer
Quality reviewer is responsible for risk-bearing wording, test coverage, disputed cases and evidence of corrective action. Give this reviewer two genuine test cases: one easy case where the correct answer is obvious, and one ambiguous case where the source lacks an important detail. Ask the reviewer to state what they can verify, what they cannot verify, and whether the translation signals that boundary. A signature without the example and source version is an inadequate audit trail. The team should also record whether this reviewer checked the PDF, screen, spreadsheet or printed instruction in its final delivery format.
Final reader representative
Final reader representative is responsible for whether a person using the real report or interface can act on the text correctly without unintended assumptions. Give this reviewer two genuine test cases: one easy case where the correct answer is obvious, and one ambiguous case where the source lacks an important detail. Ask the reviewer to state what they can verify, what they cannot verify, and whether the translation signals that boundary. A signature without the example and source version is an inadequate audit trail. The team should also record whether this reviewer checked the PDF, screen, spreadsheet or printed instruction in its final delivery format.
Four-week learning and practice plan
Week 1 — Build the source and role map
Collect a small, authorized, de-identified document set. Identify authoritative versions, controlled codes, intended users, object relationships and all numerical or conditional language. Create a twenty-term glossary and justify each definition with a specific source occurrence. Test your glossary on sentences that deliberately use one word in two different senses. The goal is classification, not speed.
Week 2 — Translate context rather than isolated terms
Select ten practical source fragments and translate each with an explanatory note. Mark all facts, conditions, uncertainties and unchanged identifiers. Have a second person identify the action or finding described by the translation without seeing the original. If they select the wrong action, repair the text and record whether the problem came from missing context, vague grammar or incorrect terminology.
Week 3 — Run adversarial quality checks
Create five fault-injected versions: one changed number, one swapped role, one omitted condition, one outdated revision and one unsupported claim of approval. Ask a teammate to find the problems with the bilingual worksheet. The exercise teaches that readability and correctness are separate variables. Document which checks detected the problem and improve the checklist where something escaped.
Week 4 — Simulate a controlled release
Produce a final translated mini-package with source register, terminology sheet, tracked exceptions, technical reviewer signoff and release version. Use the actual output medium; a table that works in a text editor may be unreadable in a mobile screen or on a workshop card. Compare with the old version and write a short lessons-learned note describing what you would prevent earlier next time.
Frequently asked questions
Does this standard guarantee a comfortable building?
No. It provides indoor environmental inputs for design and assessment; actual comfort depends on use and achieved conditions.
Can I translate a simulated temperature as a measured result?
No. The provenance must remain explicit even if the numerical value is the same.
Should I change season names for a new country?
Check the model’s actual climate context and dates first. A translated season label must not silently change source assumptions.
Why does occupancy matter to the translation?
Schedules and density assumptions can change energy calculations. Their labels, units and date patterns must be precisely preserved.
Does a category mean a building is legally compliant?
Not automatically. Determine what criterion, local requirement and project evidence are relevant.
Who should approve the bilingual report?
A language reviewer and the competent model or building-design owner should each check their own part.
How this specialist guide connects to broader learning without replacing it
For the general conceptual map of carrying meaning between languages, read Master Art of Translation | The Complete System for Moving Meaning Between Languages (EDKSG-TRANS-MASTER-WORLD-000). This article applies one subset of that approach to indoor environmental input parameters for building energy and comfort models; it is not a second master index, nor should it replace the master page as the owner of the larger translation architecture.
For language development, continue through the Vocabulary Learning Hub. Vocabulary matters here because specialists need to distinguish word form, meaning, register, collocation and technical reference, not merely memorize a dictionary equivalent. For sentence meaning, audience, inference and pragmatic context, use How English Works | Translation and Meaning Across Languages. These routes deepen understanding without diluting the specific problem this article solves.
Source and edition note
The external standards reference for this article is the ISO 17772-1:2017 official ISO catalogue entry, consulted in November 2026. This independent article paraphrases public scope information and provides original instructional scenarios. ISO retains rights to its standards. Readers applying a binding requirement should obtain the authorized edition, check amendments or changes, and follow the relevant professional, local and contractual rules. Nothing in these invented translation exercises constitutes product certification, formal compliance, financial authorization, or technical approval.
The final test is a reader test. Someone should be able to locate the source, identify the object and responsible actor, understand what has happened and what is merely planned, distinguish measured values from labels, and reproduce the intended decision. If that cannot be done, the translation is not yet finished, however fluent it sounds.