Why translate an environmental impact assessment (EIA)? Because a proposed road, port, energy project, mine, water system or residential development can affect people who do not speak the language in which the study was written. Environmental impact assessment translation, EIA report translation and multilingual public consultation should let readers understand what is proposed, which places and communities may be affected, what environmental changes are predicted and how they can respond while decisions are still open.
An EIA can include screening, scoping, baseline research, impact prediction, alternatives, mitigation and monitoring, depending on the governing legal framework. Errors matter because the translated version may be a resident’s only practical path to the technical evidence. A predicted effect can be misdescribed as something already measured. An advisory mitigation measure can be turned into a binding permit condition. An illustrative route can become a supposedly final design, and a community question can be misrepresented as support. Clarity therefore requires more than familiar terms: it requires retaining the entire chain from evidence to decision.
This guide explains how to translate and read EIA documents responsibly, including maps, water and air data, biodiversity, alternatives, community input and commitments. It is intended for students, translators, residents, project teams and public-interest readers. The International Association for Impact Assessment emphasises rigorous and participative assessment. Its best-practice guidance does not override local laws, but it provides a useful principle: readers of different languages should be able to see the same evidence, limitations, alternatives and opportunities to take part.
How to read an EIA before the technical details
Begin with the project description, map and decision stage. Then compare alternatives, likely effects, proposed measures and how you can comment. Read each summary claim alongside its data or map reference. These steps make the document usable for readers who want answers quickly while preserving the technical evidence needed for deeper assessment.
Start with the decision being supported
An EIA is produced in connection with a decision, not simply to describe the surrounding environment. Before translating a sentence, identify the proposed activity, the relevant authority, the report’s author and date, the development stage and the decision that remains to be made. Screening material, a scoping consultation, a draft assessment and an official permit do not have the same authority. Translating a draft as an approval can convince residents that public consultation is pointless. A document register should record the version, boundaries, report sections and current status. A reader ought to be able to distinguish what the developer asserts, what independent reviewers concluded and which obligations an authority has imposed. That is the foundation for meaningful public understanding.
Screening is not scoping
Screening determines whether an assessment is needed or how it is classified under the governing framework, while scoping identifies topics, study areas and methods for subsequent assessment. A scoping report may invite suggestions about impacts that have not yet been modelled. It is therefore inaccurate to describe every issue raised at scoping as already assessed or resolved. Translate words such as proposed, identified, considered, assessed, required and determined consistently with the procedural stage. Rules differ across countries, so a general glossary cannot substitute for the language of the applicable law. A plain-language note can explain the sequence, provided it is identified as an explanation rather than the authority’s original decision.
Map boundaries carry different meanings
A project’s physical footprint, construction buffer, ecological survey area, noise contour and long-term monitoring zone may be mapped using similar colours but serve very different functions. Translate the exact legend and layer rather than assuming all shaded areas are land to be acquired. Preserve coordinates, units, north arrows, projection information, source dates and map revision numbers. An ‘indicative corridor’ is not the same as an approved alignment. A flood-risk polygon is not the same as a property boundary. Readers should be able to locate their neighbourhood accurately and trace any claim back to the same spatial feature found in the source. A visual map audit is therefore essential, not merely a proofread of its labels.
Baseline data describe the starting point
An environmental baseline combines observation, earlier records and sometimes modelling to characterise current or reference conditions. It can include ecological surveys, water sampling, noise readings, air monitoring and seasonal observations. A sample collected in one month should not be translated as an annual average. A species not observed during a limited survey is not necessarily absent. Preserve the sampling location, timeframe, method, uncertainty and relationship to each table. An important distinction is whether a number is measured, estimated or predicted; fluent translation can blur these categories. When the source notes limited coverage, the target reader must see that qualification before using the data to judge an environmental impact.
Impact significance is a defined analytical judgment
Some assessment methods classify predicted effects by magnitude, likelihood, sensitivity, duration, reversibility and other factors. A category labelled minor may follow a method-specific matrix rather than mean ‘nobody will notice’. Similarly, significant can be a technical or regulatory term rather than a casual adjective. Translate the categories consistently and explain the particular study’s definitions where appropriate. An especially common error is to report only the expected residual impact after mitigation while omitting the stronger predicted effect before mitigation and the controls assumed to work. Preserve assumptions and source references. A reader should be able to understand why the analyst applied a category and what evidence or design measure the conclusion depends upon.
Possibility and confidence must remain distinct
An EIA may say that a rare event could occur under a modelled scenario, that a consequence is unlikely, or that experts have limited confidence in a local estimate. Those expressions do not mean inevitable, impossible or fully verified. A statement about a flood return period should not become a claim that the flood happens on a fixed calendar schedule. Equally, a low probability should not be described as zero risk. Keep the scenario, model assumptions, degree of confidence and event definition with the statement they qualify. A helpful review labels each consequential sentence as an observation, model output, judgment or commitment. That makes accidental certainty easier to catch before publication.
Alternatives must remain genuinely comparable
Assessments may compare different designs, routes, sites, construction approaches, technologies and sometimes a no-project scenario. Their comparative value depends on stable option identifiers, units, selection criteria and reporting periods. A preferred technical option is not necessarily legally approved; a route rejected for one reason might still be relevant to public discussion. Translating only the favoured option can obscure why the others were considered. Preserve alternatives and trade-offs, including whether impacts would affect different communities. If a table describes relative disturbance in hectares, converting only the units of the preferred route can make the options appear less comparable. A clear bilingual assessment lets readers weigh the same choices as the original.
Mitigation is not monitoring
Avoidance prevents an effect, minimisation reduces it, restoration may address conditions after disturbance, and offsets or compensation can be proposed under certain frameworks. Monitoring measures conditions and does not itself guarantee that harm cannot occur. A source stating that sediment levels will be checked monthly must not be translated as a promise that sediment will never reach a stream. Identify who will perform each measure, when it is due and whether it is only proposed, formally required or already delivered. A translated condition should retain any performance threshold, reporting duty and corrective trigger. These distinctions help readers compare the project’s commitments with actual follow-up evidence rather than treating every list of measures as proof of protection.
Technical quantities require their full units
Environmental reports contain concentrations, flows, decibels, areas, emissions, durations, percentages and confidence ranges. A change from a one-hour maximum to a daily average alters the meaning even if the number remains identical. Concentration per cubic metre is not a total quantity emitted, and hectares cannot become square metres merely by changing a column header. Preserve decimal separators, comparison signs, averaging periods, axes and units. When the target-language style requires numerical formatting changes, verify the actual values after rendering the final page. Data tables, map legends and explanatory paragraphs need cross-checking as a system, since a single shifted row can make an otherwise convincing assessment false.
Cumulative effects have a defined scope
A new project may interact with existing sources of noise, water demand, emissions or habitat pressure. A cumulative assessment may also consider reasonably foreseeable developments, depending on the rules and available evidence. A translation that attributes every regional impact to the proposed project misstates the model. So does a summary that omits existing development and treats a combined result as the isolated contribution of one operator. Keep the assessment boundary, included activities, time windows and probability of future developments clear. The translation should help readers understand what the model includes and excludes, without assuming every hypothetical development is certain to proceed.
Public participation is a two-way process
A translated summary is not enough if residents cannot find the full study, submit comments or ask questions in a usable language. Consultation material should include accurate dates, venues, meeting arrangements, submission channels, available documents and the responsible authority. Feedback translation needs equal care. Attendance does not mean consent, a question is not necessarily a formal objection, and an objection should not be softened into gratitude. Retain who said what, when and in connection with which report version. Where community knowledge uses local environmental terms or place names, preserve the source wording and clarify its meaning rather than replacing it with an invented technical measurement. Language access matters because the conversation may influence the environmental decision.
Local knowledge has its own evidentiary role
Residents may know fishing grounds, seasonal water flows, flood patterns, historic paths and ecologically important locations that are not obvious from a short survey. This information should be translated accurately and attributed, while remaining distinct from laboratory measurement or verified engineering data. A local name should not be automatically replaced with a familiar modern map label that points elsewhere. Certain knowledge may also be subject to community-specific permissions or cultural protocols. The translator’s job is not to decide which evidence wins, but to ensure assessors and residents can understand the statement, its context and any limits on disclosure. Respectful language use makes it possible to consider different knowledge sources without inventing either agreement or conflict.
Regulatory conditions are different from promises
A consultant’s recommendation, a developer’s proposed mitigation and an authority’s legally imposed permit condition are different kinds of statements. The translated document must preserve the identity of the person or institution speaking and the legal or practical status of the action. ‘Should be considered’ must not automatically become ‘must be implemented’, and an official monitoring requirement should not be weakened into optional advice. Keep responsible parties, deadlines, triggers and any conditions visible. Where a legal term has no exact equivalent in another language, use the applicable jurisdiction’s definition and explain the limitation rather than pretending one global regulatory formula applies everywhere.
Follow-up is how predictions are tested
An impact prediction made before construction can be compared with later observations. Monitoring may detect an unexpected result, show that controls performed as expected or trigger further action. Translation should distinguish expected from achieved and preliminary from confirmed. A measure planned for the future is not a completed installation; an accepted monitoring complaint is not a resolved one. Preserve monitoring station IDs, dates, thresholds, responsibilities and response status. When a report is revised, keep the change history instead of silently inserting later evidence into an earlier assessment. This allows readers to understand what authorities knew at the time of a decision and what later measurements revealed.
How to question an EIA constructively
Ask what environmental condition was measured, when the data were collected, how a model was constructed and what alternatives were considered. A good question is specific enough to be answerable: which sampling station and dry-season measurements support the predicted downstream water result? What threshold triggers additional monitoring? Which road alignment does the draft noise contour describe? By contrast, a broad assertion that every impact is harmless or catastrophic cannot be tested without identifying the evidence. The same principle applies in multiple languages: preserve the factual question and the uncertainty it raises rather than rewriting it as agreement or opposition.
Independent reference points
The International Association for Impact Assessment EIA principles describe purpose, rigour, transparency and participation. Its best-practice series includes biodiversity, climate change, assessment follow-up and participation. Readers should consult the competent environmental authority for the law and consultation steps applicable to a particular project.
Connected learning
See Why Translate: language and meaning, translation in GIS and mapping and translation in biodiversity conservation.
Thirty-two practical EIA translation errors
1. Proposed alignment described as approved
A map calls one corridor indicative, yet the target document says construction will follow that exact route. It makes later consultation appear meaningless.
Compare the drawing status and legend with the authority’s decision stage. Translate proposed, preferred, indicative and authorised separately so residents understand what can change.
2. A snapshot sample becomes the yearly average
A water-quality sample taken in a specific season is described in the translation as the usual condition throughout the year.
Preserve the sampling date, season and laboratory method. Explain an annual estimate only if the original provides one. Never convert limited evidence into broad certainty.
3. A noise contour becomes a land boundary
A coloured map shows predicted noise exposure, but the target legend says it marks land that will be acquired.
Distinguish impact models, legal parcels, project footprint and buffer zones. The translated legend must use the same layer as the original map.
4. A rare animal is declared absent
The baseline team did not observe a species during its survey, and the translated conclusion says no members live in the region.
Survey non-detection does not necessarily prove absence. Restore survey method, effort and uncertainty; ask an ecologist to review any technical inference.
5. Possible change becomes inevitable disaster
A model estimates that sediment might increase during a particular construction scenario, while the translated headline declares irreversible damage.
Retain may, scenario, magnitude and evidence status. A readable warning need not invent certainty or hide the difference between prediction and observation.
6. Monitoring is called prevention
A plan says water will be monitored, but its translation promises that contamination will be prevented completely.
Monitoring and mitigation have different purposes. Preserve the actual protective measures, thresholds and response procedures rather than claiming monitoring alone stops the hazard.
7. A preferred option becomes a permit
The consultant recommends an alignment for assessment; the target language implies a government has already granted approval.
Restore authorship and decision stage. A preferred design can still be subject to consultation, environmental review and conditions from a separate authority.
8. The no-project alternative disappears
The source compares building with not proceeding, but the target alternatives table includes only construction designs.
Retain every studied alternative and its identifier. Public readers need the full comparison even if the project proponent favours one option.
9. Cumulative result attributed to one operator
An air-quality model includes existing factories and a proposed plant. The translation describes the total as the new plant’s own emissions.
Preserve included sources and model boundaries. A cumulative environmental burden is different from an isolated project contribution.
10. Consultation deadline omitted
A translated notice explains the proposal but drops the final date and official channel for public comments.
Check date, time and submission instructions directly with the current source. The chance to respond is part of the notice’s essential meaning.
11. Attendance becomes approval
Meeting minutes record a public event, and the target summary calls the turnout proof that local people support the project.
Attendance, questions, concerns, objections and formal consent are distinct. Translate the actual statements made without adding agreement.
12. Traditional place name matched to the wrong bay
A community describes a fishing area by its local name. A translator chooses a modern landmark with a similar spelling.
Keep the original geographical term and seek appropriate verification. Misidentifying the place can distort the livelihood and land-use assessment.
13. Sensitive receptor misunderstood as a machine
An environmental report calls a school a sensitive noise receptor, and the translator substitutes a measurement sensor.
Explain the report’s defined meaning: a place or group exposed to an effect. Do not select a dictionary equivalent detached from context.
14. An hourly limit turns into a daily mean
A pollutant table refers to a one-hour concentration, but the translated column uses a full-day averaging period.
Preserve measurement duration, units and applicable comparator. A correct digit with the wrong time basis can still convey a false result.
15. Future barrier reported as installed
The developer plans to install a sediment barrier before earthworks. Its translated public summary says the barrier is already operational.
Keep future-tense commitments separate from implementation evidence. Ask who is responsible, what triggers action and when completion will be verified.
16. Residual impact loses its assumptions
An impact is assessed as low only after proposed controls, yet the target summary reports a low impact without conditions.
Retain the higher initial impact category where relevant and identify the mitigation assumptions. Readers need to know what the assessment depends upon.
17. Offset presented as restored original habitat
A developer proposes an off-site biodiversity offset; translation states the affected habitat has already been restored.
An offset, on-site restoration and avoided damage are not interchangeable. Describe type, location and implementation status accurately.
18. Health worry rewritten as diagnosis
Residents raise concern about dust near homes. The translated consultation record says the project caused a particular disease.
Preserve the residents’ worry and the source of any health evidence. A translator does not determine medical causality from an environmental complaint.
19. Confidential cultural knowledge appears in public
A restricted community consultation contains details omitted from the public report, but the translation inserts them into an online summary.
Verify the permitted disclosure level and any community protocols. A translation must not bypass the source’s privacy and cultural governance decisions.
20. Coordinates lose precision
The target appendix rounds field-site coordinates so aggressively that the map points to a different location.
Protect numeric values and coordinate reference information. Verify the point against the source map and sampling identifier.
21. A decibel change is described as a simple percentage
Noise data use a logarithmic scale, but the translation invents a direct percentage from an everyday arithmetic analogy.
Retain the source comparison and obtain a checked technical explanation if necessary. Do not add persuasive but incorrect calculations.
22. Baseline year becomes construction year
A table of measurements taken before development is described as a forecast of conditions during construction.
Separate observed baseline, predicted construction and future operational scenarios. Dates belong to the evidence, not just its presentation.
23. Flood return period becomes a fixed timetable
A statistical estimate is translated as meaning a flood will occur on a predictable calendar schedule.
Preserve probabilistic meaning, scenario and limitations. A technical term should not become a false deterministic promise.
24. Low likelihood becomes impossibility
The source says an event is unlikely under specified assumptions, but the translated text says it cannot occur.
Maintain the conditional assessment and avoid claims of zero risk unless the source genuinely establishes them.
25. Rows and scores become separated
The translator sorts impact alternatives alphabetically but leaves their numerical impact scores in the original row order.
Protect stable option identifiers and inspect the final table. Correct numbers attached to wrong labels are still serious errors.
26. An objection turns into appreciation
A resident says the route could affect access to a farm; the translated minutes record thanks for the meeting.
Keep concerns, questions and objections in their original force. The consultation authority should evaluate a genuine statement, not a rewritten one.
27. Acknowledged grievance becomes resolved
The project team receives a complaint but has not investigated it, while the translated status says the case is closed.
Received, assessed, planned, implemented and resolved are different stages. Keep dates, responsibilities and evidence of closure.
28. Consultant recommendation becomes regulation
A technical expert advises a further survey, and the translation says the government has legally required it.
Separate the author and authority of a recommendation from binding conditions. Do not invent legal obligations or weaken actual ones.
29. Hectares relabelled square metres
A table changes an area unit during localisation without changing the numeric values.
Retain the source unit or perform a checked conversion in every affected table and caption. Quantities must remain consistent across versions.
30. Wrong animal name selected
A regional common name can refer to different species, but a translator chooses the most familiar English animal.
Use the study’s taxonomic identification if documented; otherwise mark the ambiguity. Species names can change the assessed conservation significance.
31. Proposed outreach reported as completed
A document plans to consult affected communities, but its translation says those communities have already been interviewed.
Preserve the distinction between intended, scheduled, conducted and reviewed consultation, including dates and participant scope.
32. New evidence silently inserted into old EIA
Monitoring results produced after approval are added to the translated draft without a revision record.
Keep version history and the chronology of what was known before and after a decision. Later findings can strengthen accountability without rewriting history.
Using environmental assessment translations in practice
How to read an EIA in five minutes
Open with the project location, map, document status and responsible authority. Then identify the alternatives, predicted main effects and mitigation measures, keeping proposed and completed actions apart. If a headline result matters to you, follow its source reference into the technical table or figure. Check when and how that number was produced. Finally find the current consultation instructions, languages and deadline. Specific questions are useful: which station measured this water value, which season does it represent, and what measure will apply if a threshold is exceeded? A reliable translation makes the answers findable without forcing residents to become specialists.
What a good technical briefing contains
Before translating, identify the source version, decision stage, study boundaries, project alternatives and relevant environmental disciplines. Create a register of critical terms, data tables, model scenarios, geographic names, map legends, units and monitoring identifiers. Agree which material needs review by a hydrologist, ecologist, acoustics specialist or legal/regulatory adviser. Make clear which source phrases are defined by local law and which are ordinary explanation. A reader should not need to guess whether a category such as significant is a study threshold, an everyday word or a legal classification. Preserve uncertainty and the connection between each analysis and the underlying evidence.
Designing meaningful multilingual consultation
Provide a brief factual summary connected to the detailed source documents, then explain how affected people can ask questions and submit comments. Translate the map and practical participation details as carefully as the narrative. Use suitable interpreting arrangements when discussion is live, and give participants sufficient time to express their actual views. A community member’s question should not be translated as support, and an objection should not be erased to make the event sound harmonious. Record the original statement and its reviewed translation through the responsible process. If the design later changes, publish updated information and let readers know which version governs the current consultation.
Auditing the finished translation
Do four separate checks. First verify project identity, boundaries, alternatives and report status. Second review technical quantities, model assumptions, sources and figure legends. Third inspect conditional verbs, significance categories, proposed mitigation, regulatory conditions and implementation stages. Fourth test whether a target-language reader can find the source evidence, consultation route and latest project version. Review some technical appendices rather than only the executive summary, and examine the final rendered document because formatting can shift a legend or table value. Record issues and corrections transparently so that later source revisions can trigger the right changes across all languages.
Learning this skill without a real project
In week one, annotate an accessible public EIA and label baseline, prediction, alternative, mitigation and follow-up sections. In week two, work through a fictional dataset and deliberately introduce a wrong unit or swapped location code to see how interpretation changes. In week three, translate a model consultation notice and fictional resident questions, keeping the response deadline and each speaker’s position intact. In week four, write a concise source-linked summary that helps a reader distinguish observed facts, predictions, unresolved issues and next decisions. Have a second reader reconstruct the same chain from the target version. The exercise teaches evidence handling and language judgment, not professional environmental assessment by itself.
Why long-term access matters
Projects continue after a consultation closes. If construction proceeds, communities may need translated updates about monitoring results, schedule changes, complaints, corrective actions and compliance conditions. Translation memories can preserve terminology, but should never automatically reuse an outdated assertion that a control is only proposed when it has since been completed or altered. Likewise, a measure described as effective during design should not be treated as proved successful until appropriate evidence exists. Good language governance creates a dated source-of-truth record and a way for residents to find corrections. The objective is a continuing ability to compare predictions with measurements and public commitments with documented actions.
Preventing contradiction between summaries and appendices
A polished summary may accidentally say the project uses route A while the attached maps come from a newer design using route B. Another common problem is that the executive summary gives a low residual impact but the appendix explains this depends on a mitigation programme that is still proposed. Check the whole information chain, not only grammatical correctness. A source-aligned summary should preserve conditions and link to precise technical sections. Readers who need a fast answer can use the summary; readers who want evidence can follow it. These are complementary functions, not competing versions of the project’s truth.
Handling uncertain environmental terms
Some technical expressions lack a neat everyday equivalent. Rather than guess, identify how the source defines the term, whether it corresponds to a measured quantity or a judgment, and what alternative renderings imply. Ask the relevant specialist to confirm the concept. A translator’s note can explain a necessary distinction while leaving the original term or figure reference accessible. This approach is especially useful when local customary names and international scientific categories intersect. Do not force a community observation into laboratory language, nor dismiss a scientific threshold as a mere opinion. Preserve the kind of evidence each source provides.
Frequently asked questions
What is an EIA?
Environmental Impact Assessment is a process used in many jurisdictions to examine likely environmental effects before decisions; the governing rules differ by location.
Does a published EIA prove a project is approved?
No. Reports can be drafts, under review or final submissions; authorisation is a distinct regulatory decision.
What is baseline information?
Reference or existing conditions documented through evidence such as surveys, measurements and historical records, with methodological limits.
What is mitigation?
An action intended to avoid, reduce or address an identified impact. Monitoring checks conditions and is not the same function.
What is residual impact?
An impact remaining after the relevant mitigation assumptions or measures are considered; it is not automatic proof of completed protection.
Why should maps be checked separately?
Legends, boundaries, coordinates and scenario layers carry information that is easy to change by moving even one label.
Can automatic translation handle technical reports alone?
It can assist drafting, but environmental, numeric, mapping and regulatory claims require relevant specialist and language review.
Which rules apply to a specific project?
The applicable local environmental assessment laws and official authorities, not an international overview alone.
The principle that connects every example
Reliable environmental assessment translation allows people to trace the same proposal from geographical footprint to baseline measurement, from a predicted change to proposed mitigation and from public comment to an accountable decision. It preserves small but important distinctions: may rather than will, monitored rather than prevented, considered rather than authorised, and attended rather than supported. A useful explanation can be friendly and concise while still leaving a reader able to verify where its facts came from.
How to compare summaries with technical appendices
Take one headline statement from the executive summary, such as a predicted water-quality change. Identify the exact table and scenario that support it, including the sampling site, season, unit, baseline and modelling assumptions. A translator should perform this check before declaring the two language versions equivalent. A correct paragraph can still be misleading if it points to the wrong appendix or drops an important condition. Repeat the process with a map, a biodiversity finding and a mitigation commitment. Doing so tests whether the summary carries a faithful route into the evidence rather than merely sounding plausible. When a report is updated, these links should be checked again so the translated summary does not continue citing old data.
Risk words should explain what a reader can do
Readers often ask whether an effect is safe or unsafe, but an EIA may present a range of outcomes or a threshold linked to specified conditions. Rather than erase those distinctions, a useful translation makes the practical relationship explicit: what is expected, what remains uncertain, which controls are proposed, and what monitoring or regulatory action follows if a limit is exceeded. It should be possible to understand a technical category without believing that every local experience fits the same score. A resident can then ask specific questions of the responsible authority. A precise answer is more valuable than a generic assurance, because it shows what evidence would change the conclusion.
Why translation cannot substitute for consultation
A translated assessment gives access to information, while consultation allows people to respond to it. Both are required for meaningful multilingual communication where the governing process calls for public involvement. A resident may recognise an error in the baseline map, identify a seasonal use of a river or question whether mitigation is feasible. That contribution must be recorded as the person’s statement, not rewritten as a predetermined technical answer. Interpreters and translators should facilitate the exchange without judging which comment has merit. The project team and relevant authorities remain responsible for reviewing the evidence and decisions. Good language access preserves room for disagreement, correction and clarification without making participation seem like approval.
Avoid false global legal claims
Environmental assessment procedures differ across jurisdictions and may depend on project type, location, thresholds and public participation requirements. A translated article should not present one country’s screening criteria or consultation period as a universal rule. Where a document uses legal terms such as approval, authorisation, licence or consent, a reviewer familiar with the specific jurisdiction should check the operative meaning. International best-practice references can guide clarity and inclusion but do not override domestic processes. Readers should see the responsible authority and the current source document so they can confirm which obligations and deadlines actually apply. This approach makes an international guide broadly useful without inventing legal uniformity.
Build a correction loop that people can trust
If residents or technical reviewers identify a problem in a translated map, status label or table, there should be a way to report it and obtain a documented correction. Record the exact passage, source version and nature of the error. A change to a scientific conclusion should be authorised by the relevant report owner rather than quietly introduced by a language editor. An updated translation should show a clear revision date and remain linked to the original evidence. This protects both readers and project teams: public comments can be understood in their proper context, technical changes are traceable, and later users can see which version was available at a given decision stage.