How do you translate fisheries stock assessments, fishing logbooks, catch documentation, quotas, vessel monitoring records and international fisheries notices without changing the scientific or legal meaning? Accurate fisheries translation must protect species identifiers, stock boundaries, fishing-effort units, catches versus landings, reference points for biomass and mortality, vessel identities, the authority of advice and regulation, and the difference between observations, estimates and conditional scenarios. Fluent language is not enough if a translation turns a modeled catch scenario into a legal quota or confuses a landing weight with its live-weight equivalent.
People searching for fisheries translation, fishery stock assessment terminology, FAO ASFIS species codes, fishing effort translation, fisheries catch certificate translation, IUU fishing records, ICES advice interpretation or UN/CEFACT FLUX data exchange are trying to move information between real scientific, administrative and business systems. This guide explains the hidden ambiguities, a repeatable translation workflow, verification failures, worked diagnostics and transfer exercises that make multilingual records intelligible without surrendering the original evidence.
The core method is to bind every translated claim to an entity, a measure, a time, a place or stock area, a status, an authority and a source record. Preserve identifiers and numbers; distinguish what has been caught, weighed, estimated, recommended, decided or reported; and add accessible explanations only after validating the underlying fields. The result should let a scientist, fisher, reviewer, data engineer, compliance professional or public reader reach the same justified conclusion as the source. This world-facing chapter is the next reserved-tens child, EDKSG-TRANS-MASTER-WORLD-670, of Master Art of Translation | The Complete System for Moving Meaning Between Languages.
All exercises below are fictional, with invented sample records. No illustrative vessel, quota or decision should be treated as an actual authorization or finding. Fisheries regimes and definitions vary, so use the competent authority’s controlling document for operational or legal decisions. The source trail links FAO CWP statistical concepts, the FAO ASFIS reference list, the Port State Measures Agreement, ICES advice formats, the UN/CEFACT FLUX standard and ISO 5060:2024 guidance on evaluating translation output.
Contents and reader routes
Search intent · Hidden problem · Mechanisms · Repeatable method · Failure modes · Worked diagnostics · Four-week practice · Glossary and FAQs · Sources and next routes
Search intent: the actual questions behind fisheries translation
A fishing crew documents operations. An observer or camera analyst documents evidence. A laboratory may establish species identity. A port official inspects a vessel or consignment. A national or regional agency records catch or issues a management rule. A stock-assessment scientist estimates an unobserved biological population from multiple forms of evidence. When their records travel between languages, the translator is carrying distinctions between these different acts. The first search-intent question is therefore not simply ‘What does this word mean?’ but ‘Which stage of which process does the word name?’
The most common misunderstanding begins with what can be counted. Catch is not necessarily the same as landings. Discarded animals can include intended target species, while retained bycatch can include non-target species. Landed product mass is not automatically live-weight equivalent. Fishing days may exclude days at sea devoted to transit; effort may refer to hooks, gear-days, trawl hours or another defined unit. These distinctions must not disappear in a short target-language label.
A second recurring question concerns models and advice. Fishing mortality F is a biological assessment parameter, not the number of hours worked by a vessel. Spawning-stock biomass refers to a defined reproductive component, not every organism in an ocean. F/FMSY and B/BMSY ratios have distinct denominators. Scientific advice is not automatically an enacted quota. A reader of a chart needs the scenario, reference period and units before deciding what a number claims.
A third question concerns accountable identifiers. Fishing vessels can change names, flags and operators while remaining the same physical vessel. FAO’s Global Record emphasizes unique vessel identifiers, with IMO numbers used for relevant vessels. A species can have a commercial label in one language and a statistical identity in another. A translation that removes the stable codes may look friendlier but destroy a record’s ability to be checked against a registry.
A fourth question concerns uncertainty, confidence and the language of permission. Observation, model estimate, projection, recommendation, rule, allegation, inspection finding and adjudicated decision are not synonyms. A target reader may rely on precisely these differences. The translation must retain them even if the public explanation needs simpler grammar. This chapter teaches how to explain complex evidence without quietly strengthening its claim.
Search engines often combine broad keywords such as fisheries data, seafood traceability, vessel records and stock status. But an answer that serves all those searches must keep different systems in their proper roles. A buyer may need a lot number; a scientist may need a stock code; a port official may need a vessel identity and entry request; a manager may need an adopted total allowable catch and implementation date. Proper routing starts by identifying the reader and the governing source.
The hidden problem: similar words can refer to different evidence
Translation errors cascade. If a landing product weight is mislabeled as live-weight catch, an aggregate can be exaggerated or understated. If a report omits a negative percentage-change sign, a decline may appear to be growth. If an assessment scenario is phrased as a rule, the reader may infer an immediate obligation that never existed. And if a stock code disappears, evidence about one population can be presented as a claim about all members of a species.
Timing is especially vulnerable. A stock assessment may be prepared in one year, advise catch in the next and project spawning biomass for a later year. Vessel activity may cross midnight or time zones; a port declaration may refer to a batch unloaded after an at-sea transfer. A translator should write a compact timeline of event time, reporting time, advice time, decision time and effective time before translating any clause that uses words such as current, next, previous or revised.
Authority is a separate control. The source may come from a scientific body, an intergovernmental statistics program, a voluntary industry initiative or a government agency. Official scientific advice must not be presented as a universal legal obligation. A marketing sustainability phrase is not an independent scientific stock assessment. A compliance allegation must not become a court-like finding merely because the target wording sounds more decisive.
Interoperability also changes what counts as language. A human-readable label can be localized; a numeric species code, FLUX message element, unit code, vessel identifier or stock reference normally cannot be freely renamed. The meaning of structured data depends on the schema and enumerations under which they were issued. Translations should preserve those keys, and any migration to a new code version must be documented as a data transformation rather than hidden in prose.
The core preservation model has nine fields: entity identity, event identity, geospatial context, time reference, quantity and unit, code/classification, evidence status, decision force and provenance. A missing field need not always make a translation unusable, but it must never be filled with a plausible guess. The editor should keep a list of omissions, ambiguities and unresolved source contradictions so that the publication is honest about what it cannot prove.
Thirty mechanisms that protect meaning
1. Species identity
What must remain true: Keep statistical species codes and scientific names linked even when market names vary. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Verify FAO ASFIS release and local display label. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For Species identity, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
2. Stock identity
What must remain true: A species and a separately assessed stock have different scope. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Retain stock code area and assessment component. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For Stock identity, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
3. Species grouping
What must remain true: A family or statistical group is not proof of species level identification. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Preserve group granularity and source classification. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For Species grouping, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
4. Capture and aquaculture
What must remain true: Wild-capture records and cultivated harvests belong to different reporting methods. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Check production-mode field. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For Capture and aquaculture, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
5. Catch and landing
What must remain true: The amount caught may differ from the amount brought ashore. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Reconcile catch disposition and landing events. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For Catch and landing, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
6. Bycatch and discard
What must remain true: Non-target status differs from a decision to discard or retain. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Keep target class and fate separately. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For Bycatch and discard, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
7. Product and live weight
What must remain true: Gutted or filleted weight is not live-weight equivalent. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Keep product presentation and conversion factor. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For Product and live weight, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
8. Fishing effort
What must remain true: Gear deployment depends on method and time, not a generic activity count. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Preserve hooks trawl hours sets or gear days. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For Fishing effort, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
9. Fishing mortality
What must remain true: F is a modeled population parameter rather than recorded vessel effort. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Keep reference-point and model notation. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For Fishing mortality, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
10. CPUE
What must remain true: Catch per unit effort is an index whose meaning depends on catchability. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Keep denominator and standardization. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For CPUE, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
11. SSB
What must remain true: Spawning biomass is not total biomass. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Preserve maturity assumption and year. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For SSB, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
12. Recruitment
What must remain true: Age-class entry is not recruitment of staff. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Retain cohort and model age. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For Recruitment, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
13. Blim and Bpa
What must remain true: Limits and precautionary buffers differ. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Keep reference point subscript and role. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For Blim and Bpa, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
14. FMSY and Fpa
What must remain true: Maximum sustainable yield and precautionary fishing-mortality references differ. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Preserve formula notation and approach. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For FMSY and Fpa, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
15. Advice and law
What must remain true: Scientific advice is not automatically binding. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Verify competent issuer and adopted measure. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For Advice and law, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
16. Quota and TAC
What must remain true: A fleet or vessel allocation is not the total allowable catch. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Keep allocation level and period. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For Quota and TAC, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
17. Reference years
What must remain true: Observation year advice year and projection year may differ. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Validate every table heading. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For Reference years, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
18. Scenario wording
What must remain true: Conditional projections are not unconditional predictions. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Retain assumptions such as F equals zero. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For Scenario wording, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
19. Persistent vessel ID
What must remain true: Names flags and callsigns may change. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Keep UVI or registered identity. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For Persistent vessel ID, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
20. Transshipment
What must remain true: Transfer between vessels is not a landing ashore. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Record both participating vessels and event. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For Transshipment, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
21. VMS and AIS
What must remain true: Different tracking systems may have distinct reporting purposes. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Keep system identity and coverage. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For VMS and AIS, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
22. PSMA decisions
What must remain true: Port entry request inspection and service decision are separate procedural states. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Check decision scope and status. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For PSMA decisions, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
23. IUU language
What must remain true: Suspicion investigation finding and legal outcome differ. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Retain due-process and authority status. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For IUU language, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
24. Product lot
What must remain true: A consignment may combine multiple original catches. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Keep batch genealogy and parent identifiers. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For Product lot, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
25. Coordinates
What must remain true: Latitude longitude and area codes carry official spatial meaning. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Verify datum axis order and longitude sign. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For Coordinates, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
26. Missing values
What must remain true: A missing figure does not signify zero. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Keep null and reporting status. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For Missing values, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
27. FLUX interoperability
What must remain true: Machine-readable message codes must survive language adaptation. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Validate schema and code lists. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For FLUX interoperability, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
28. Version control
What must remain true: Corrections must not create duplicate catches or new vessels. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Retain stable event ID and revision link. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For Version control, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
29. Public explanations
What must remain true: An accessible paraphrase still needs scope uncertainty and time. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Back-check every headline against source. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For Public explanations, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
30. Translation evaluation
What must remain true: A beautiful translation can still fail on units authority or identity. Before translating the relevant sentence, the editor identifies the named entity or analytical unit and searches for its definition inside the controlling report. If the source uses an abbreviation, acronym or code, capture its exact form and the source document’s version; never derive the term only from the way its letters resemble an everyday word. The target expression should preserve what the writer actually measured, classified, projected, recommended or decided, rather than what a nonspecialist might assume the term describes.
Operational evidence: Use error-severity review and independent source comparison. Put the result in a bilingual terminology card showing the source phrase, intended target phrase, context, authority and prohibited misleading equivalents. A reviewer should be able to open the cited record and check the classification, unit, time horizon and status. If a localization makes the statement easier to understand but changes any one of those conditions, the change belongs in an explanatory note and must not replace the official field or quoted result.
The decisive diagnostic is reverse reconstruction. Hide the source and give the translated section to another qualified reader; ask them to describe the actual fishery event, stock condition, data relationship or management action it represents. Then compare the reconstruction with the recorded source fields. A mismatch identifies a meaning failure that prose proofreading will miss. For Translation evaluation, require a correction not merely to the target words but also to any dependent caption, summary table, hyperlink or public instruction. This gives the team an accountable reason for accepting or rejecting the translation.
The repeatable translation method
Step 1: Capture source and version
At the capture source and version stage, document what is known, which source proves it, and what remains ambiguous. The goal is reproducibility: someone who was not involved in drafting should be able to follow the record from the original field through its target-language explanation and back again. Where the document combines fishing activities, stock-assessment outputs and official decisions, keep their sources and review criteria separate. Do not use confident paraphrase to make an incomplete dataset appear complete. A reviewer should note precisely whether a problem changes identity, amount, year, uncertainty, regulation, evidence or ordinary style.
Create a release gate with three questions: what claim could be misunderstood here, which identifier or definition prevents that misunderstanding, and what independent record would demonstrate that the chosen wording is valid? For this stage, record a field owner, a dated source reference and a test result. If the input conflicts with a published standard or its own tables, seek an authoritative correction rather than making the translation internally consistent by guesswork. When evidence arrives, record the correction as a versioned decision so the same issue cannot silently recur in the next translation batch.
Step 2: Determine document purpose
At the determine document purpose stage, document what is known, which source proves it, and what remains ambiguous. The goal is reproducibility: someone who was not involved in drafting should be able to follow the record from the original field through its target-language explanation and back again. Where the document combines fishing activities, stock-assessment outputs and official decisions, keep their sources and review criteria separate. Do not use confident paraphrase to make an incomplete dataset appear complete. A reviewer should note precisely whether a problem changes identity, amount, year, uncertainty, regulation, evidence or ordinary style.
Create a release gate with three questions: what claim could be misunderstood here, which identifier or definition prevents that misunderstanding, and what independent record would demonstrate that the chosen wording is valid? For this stage, record a field owner, a dated source reference and a test result. If the input conflicts with a published standard or its own tables, seek an authoritative correction rather than making the translation internally consistent by guesswork. When evidence arrives, record the correction as a versioned decision so the same issue cannot silently recur in the next translation batch.
Step 3: Identify issuer and authority
At the identify issuer and authority stage, document what is known, which source proves it, and what remains ambiguous. The goal is reproducibility: someone who was not involved in drafting should be able to follow the record from the original field through its target-language explanation and back again. Where the document combines fishing activities, stock-assessment outputs and official decisions, keep their sources and review criteria separate. Do not use confident paraphrase to make an incomplete dataset appear complete. A reviewer should note precisely whether a problem changes identity, amount, year, uncertainty, regulation, evidence or ordinary style.
Create a release gate with three questions: what claim could be misunderstood here, which identifier or definition prevents that misunderstanding, and what independent record would demonstrate that the chosen wording is valid? For this stage, record a field owner, a dated source reference and a test result. If the input conflicts with a published standard or its own tables, seek an authoritative correction rather than making the translation internally consistent by guesswork. When evidence arrives, record the correction as a versioned decision so the same issue cannot silently recur in the next translation batch.
Step 4: Mark legal versus scientific status
At the mark legal versus scientific status stage, document what is known, which source proves it, and what remains ambiguous. The goal is reproducibility: someone who was not involved in drafting should be able to follow the record from the original field through its target-language explanation and back again. Where the document combines fishing activities, stock-assessment outputs and official decisions, keep their sources and review criteria separate. Do not use confident paraphrase to make an incomplete dataset appear complete. A reviewer should note precisely whether a problem changes identity, amount, year, uncertainty, regulation, evidence or ordinary style.
Create a release gate with three questions: what claim could be misunderstood here, which identifier or definition prevents that misunderstanding, and what independent record would demonstrate that the chosen wording is valid? For this stage, record a field owner, a dated source reference and a test result. If the input conflicts with a published standard or its own tables, seek an authoritative correction rather than making the translation internally consistent by guesswork. When evidence arrives, record the correction as a versioned decision so the same issue cannot silently recur in the next translation batch.
Step 5: Extract species and stock codes
At the extract species and stock codes stage, document what is known, which source proves it, and what remains ambiguous. The goal is reproducibility: someone who was not involved in drafting should be able to follow the record from the original field through its target-language explanation and back again. Where the document combines fishing activities, stock-assessment outputs and official decisions, keep their sources and review criteria separate. Do not use confident paraphrase to make an incomplete dataset appear complete. A reviewer should note precisely whether a problem changes identity, amount, year, uncertainty, regulation, evidence or ordinary style.
Create a release gate with three questions: what claim could be misunderstood here, which identifier or definition prevents that misunderstanding, and what independent record would demonstrate that the chosen wording is valid? For this stage, record a field owner, a dated source reference and a test result. If the input conflicts with a published standard or its own tables, seek an authoritative correction rather than making the translation internally consistent by guesswork. When evidence arrives, record the correction as a versioned decision so the same issue cannot silently recur in the next translation batch.
Step 6: Extract vessel and trip identity
At the extract vessel and trip identity stage, document what is known, which source proves it, and what remains ambiguous. The goal is reproducibility: someone who was not involved in drafting should be able to follow the record from the original field through its target-language explanation and back again. Where the document combines fishing activities, stock-assessment outputs and official decisions, keep their sources and review criteria separate. Do not use confident paraphrase to make an incomplete dataset appear complete. A reviewer should note precisely whether a problem changes identity, amount, year, uncertainty, regulation, evidence or ordinary style.
Create a release gate with three questions: what claim could be misunderstood here, which identifier or definition prevents that misunderstanding, and what independent record would demonstrate that the chosen wording is valid? For this stage, record a field owner, a dated source reference and a test result. If the input conflicts with a published standard or its own tables, seek an authoritative correction rather than making the translation internally consistent by guesswork. When evidence arrives, record the correction as a versioned decision so the same issue cannot silently recur in the next translation batch.
Step 7: Inventory measures and units
At the inventory measures and units stage, document what is known, which source proves it, and what remains ambiguous. The goal is reproducibility: someone who was not involved in drafting should be able to follow the record from the original field through its target-language explanation and back again. Where the document combines fishing activities, stock-assessment outputs and official decisions, keep their sources and review criteria separate. Do not use confident paraphrase to make an incomplete dataset appear complete. A reviewer should note precisely whether a problem changes identity, amount, year, uncertainty, regulation, evidence or ordinary style.
Create a release gate with three questions: what claim could be misunderstood here, which identifier or definition prevents that misunderstanding, and what independent record would demonstrate that the chosen wording is valid? For this stage, record a field owner, a dated source reference and a test result. If the input conflicts with a published standard or its own tables, seek an authoritative correction rather than making the translation internally consistent by guesswork. When evidence arrives, record the correction as a versioned decision so the same issue cannot silently recur in the next translation batch.
Step 8: Record time and timezone
At the record time and timezone stage, document what is known, which source proves it, and what remains ambiguous. The goal is reproducibility: someone who was not involved in drafting should be able to follow the record from the original field through its target-language explanation and back again. Where the document combines fishing activities, stock-assessment outputs and official decisions, keep their sources and review criteria separate. Do not use confident paraphrase to make an incomplete dataset appear complete. A reviewer should note precisely whether a problem changes identity, amount, year, uncertainty, regulation, evidence or ordinary style.
Create a release gate with three questions: what claim could be misunderstood here, which identifier or definition prevents that misunderstanding, and what independent record would demonstrate that the chosen wording is valid? For this stage, record a field owner, a dated source reference and a test result. If the input conflicts with a published standard or its own tables, seek an authoritative correction rather than making the translation internally consistent by guesswork. When evidence arrives, record the correction as a versioned decision so the same issue cannot silently recur in the next translation batch.
Step 9: Record area and coordinate reference
At the record area and coordinate reference stage, document what is known, which source proves it, and what remains ambiguous. The goal is reproducibility: someone who was not involved in drafting should be able to follow the record from the original field through its target-language explanation and back again. Where the document combines fishing activities, stock-assessment outputs and official decisions, keep their sources and review criteria separate. Do not use confident paraphrase to make an incomplete dataset appear complete. A reviewer should note precisely whether a problem changes identity, amount, year, uncertainty, regulation, evidence or ordinary style.
Create a release gate with three questions: what claim could be misunderstood here, which identifier or definition prevents that misunderstanding, and what independent record would demonstrate that the chosen wording is valid? For this stage, record a field owner, a dated source reference and a test result. If the input conflicts with a published standard or its own tables, seek an authoritative correction rather than making the translation internally consistent by guesswork. When evidence arrives, record the correction as a versioned decision so the same issue cannot silently recur in the next translation batch.
Step 10: Reconstruct event sequence
At the reconstruct event sequence stage, document what is known, which source proves it, and what remains ambiguous. The goal is reproducibility: someone who was not involved in drafting should be able to follow the record from the original field through its target-language explanation and back again. Where the document combines fishing activities, stock-assessment outputs and official decisions, keep their sources and review criteria separate. Do not use confident paraphrase to make an incomplete dataset appear complete. A reviewer should note precisely whether a problem changes identity, amount, year, uncertainty, regulation, evidence or ordinary style.
Create a release gate with three questions: what claim could be misunderstood here, which identifier or definition prevents that misunderstanding, and what independent record would demonstrate that the chosen wording is valid? For this stage, record a field owner, a dated source reference and a test result. If the input conflicts with a published standard or its own tables, seek an authoritative correction rather than making the translation internally consistent by guesswork. When evidence arrives, record the correction as a versioned decision so the same issue cannot silently recur in the next translation batch.
Step 11: Define terminology cards
At the define terminology cards stage, document what is known, which source proves it, and what remains ambiguous. The goal is reproducibility: someone who was not involved in drafting should be able to follow the record from the original field through its target-language explanation and back again. Where the document combines fishing activities, stock-assessment outputs and official decisions, keep their sources and review criteria separate. Do not use confident paraphrase to make an incomplete dataset appear complete. A reviewer should note precisely whether a problem changes identity, amount, year, uncertainty, regulation, evidence or ordinary style.
Create a release gate with three questions: what claim could be misunderstood here, which identifier or definition prevents that misunderstanding, and what independent record would demonstrate that the chosen wording is valid? For this stage, record a field owner, a dated source reference and a test result. If the input conflicts with a published standard or its own tables, seek an authoritative correction rather than making the translation internally consistent by guesswork. When evidence arrives, record the correction as a versioned decision so the same issue cannot silently recur in the next translation batch.
Step 12: Separate observed and modeled values
At the separate observed and modeled values stage, document what is known, which source proves it, and what remains ambiguous. The goal is reproducibility: someone who was not involved in drafting should be able to follow the record from the original field through its target-language explanation and back again. Where the document combines fishing activities, stock-assessment outputs and official decisions, keep their sources and review criteria separate. Do not use confident paraphrase to make an incomplete dataset appear complete. A reviewer should note precisely whether a problem changes identity, amount, year, uncertainty, regulation, evidence or ordinary style.
Create a release gate with three questions: what claim could be misunderstood here, which identifier or definition prevents that misunderstanding, and what independent record would demonstrate that the chosen wording is valid? For this stage, record a field owner, a dated source reference and a test result. If the input conflicts with a published standard or its own tables, seek an authoritative correction rather than making the translation internally consistent by guesswork. When evidence arrives, record the correction as a versioned decision so the same issue cannot silently recur in the next translation batch.
Step 13: Translate first pass
At the translate first pass stage, document what is known, which source proves it, and what remains ambiguous. The goal is reproducibility: someone who was not involved in drafting should be able to follow the record from the original field through its target-language explanation and back again. Where the document combines fishing activities, stock-assessment outputs and official decisions, keep their sources and review criteria separate. Do not use confident paraphrase to make an incomplete dataset appear complete. A reviewer should note precisely whether a problem changes identity, amount, year, uncertainty, regulation, evidence or ordinary style.
Create a release gate with three questions: what claim could be misunderstood here, which identifier or definition prevents that misunderstanding, and what independent record would demonstrate that the chosen wording is valid? For this stage, record a field owner, a dated source reference and a test result. If the input conflicts with a published standard or its own tables, seek an authoritative correction rather than making the translation internally consistent by guesswork. When evidence arrives, record the correction as a versioned decision so the same issue cannot silently recur in the next translation batch.
Step 14: Check values and rounding
At the check values and rounding stage, document what is known, which source proves it, and what remains ambiguous. The goal is reproducibility: someone who was not involved in drafting should be able to follow the record from the original field through its target-language explanation and back again. Where the document combines fishing activities, stock-assessment outputs and official decisions, keep their sources and review criteria separate. Do not use confident paraphrase to make an incomplete dataset appear complete. A reviewer should note precisely whether a problem changes identity, amount, year, uncertainty, regulation, evidence or ordinary style.
Create a release gate with three questions: what claim could be misunderstood here, which identifier or definition prevents that misunderstanding, and what independent record would demonstrate that the chosen wording is valid? For this stage, record a field owner, a dated source reference and a test result. If the input conflicts with a published standard or its own tables, seek an authoritative correction rather than making the translation internally consistent by guesswork. When evidence arrives, record the correction as a versioned decision so the same issue cannot silently recur in the next translation batch.
Step 15: Reconcile supporting tables
At the reconcile supporting tables stage, document what is known, which source proves it, and what remains ambiguous. The goal is reproducibility: someone who was not involved in drafting should be able to follow the record from the original field through its target-language explanation and back again. Where the document combines fishing activities, stock-assessment outputs and official decisions, keep their sources and review criteria separate. Do not use confident paraphrase to make an incomplete dataset appear complete. A reviewer should note precisely whether a problem changes identity, amount, year, uncertainty, regulation, evidence or ordinary style.
Create a release gate with three questions: what claim could be misunderstood here, which identifier or definition prevents that misunderstanding, and what independent record would demonstrate that the chosen wording is valid? For this stage, record a field owner, a dated source reference and a test result. If the input conflicts with a published standard or its own tables, seek an authoritative correction rather than making the translation internally consistent by guesswork. When evidence arrives, record the correction as a versioned decision so the same issue cannot silently recur in the next translation batch.
Step 16: Validate structured fields
At the validate structured fields stage, document what is known, which source proves it, and what remains ambiguous. The goal is reproducibility: someone who was not involved in drafting should be able to follow the record from the original field through its target-language explanation and back again. Where the document combines fishing activities, stock-assessment outputs and official decisions, keep their sources and review criteria separate. Do not use confident paraphrase to make an incomplete dataset appear complete. A reviewer should note precisely whether a problem changes identity, amount, year, uncertainty, regulation, evidence or ordinary style.
Create a release gate with three questions: what claim could be misunderstood here, which identifier or definition prevents that misunderstanding, and what independent record would demonstrate that the chosen wording is valid? For this stage, record a field owner, a dated source reference and a test result. If the input conflicts with a published standard or its own tables, seek an authoritative correction rather than making the translation internally consistent by guesswork. When evidence arrives, record the correction as a versioned decision so the same issue cannot silently recur in the next translation batch.
Step 17: Review domain science
At the review domain science stage, document what is known, which source proves it, and what remains ambiguous. The goal is reproducibility: someone who was not involved in drafting should be able to follow the record from the original field through its target-language explanation and back again. Where the document combines fishing activities, stock-assessment outputs and official decisions, keep their sources and review criteria separate. Do not use confident paraphrase to make an incomplete dataset appear complete. A reviewer should note precisely whether a problem changes identity, amount, year, uncertainty, regulation, evidence or ordinary style.
Create a release gate with three questions: what claim could be misunderstood here, which identifier or definition prevents that misunderstanding, and what independent record would demonstrate that the chosen wording is valid? For this stage, record a field owner, a dated source reference and a test result. If the input conflicts with a published standard or its own tables, seek an authoritative correction rather than making the translation internally consistent by guesswork. When evidence arrives, record the correction as a versioned decision so the same issue cannot silently recur in the next translation batch.
Step 18: Review authority and legal force
At the review authority and legal force stage, document what is known, which source proves it, and what remains ambiguous. The goal is reproducibility: someone who was not involved in drafting should be able to follow the record from the original field through its target-language explanation and back again. Where the document combines fishing activities, stock-assessment outputs and official decisions, keep their sources and review criteria separate. Do not use confident paraphrase to make an incomplete dataset appear complete. A reviewer should note precisely whether a problem changes identity, amount, year, uncertainty, regulation, evidence or ordinary style.
Create a release gate with three questions: what claim could be misunderstood here, which identifier or definition prevents that misunderstanding, and what independent record would demonstrate that the chosen wording is valid? For this stage, record a field owner, a dated source reference and a test result. If the input conflicts with a published standard or its own tables, seek an authoritative correction rather than making the translation internally consistent by guesswork. When evidence arrives, record the correction as a versioned decision so the same issue cannot silently recur in the next translation batch.
Step 19: Test public action
At the test public action stage, document what is known, which source proves it, and what remains ambiguous. The goal is reproducibility: someone who was not involved in drafting should be able to follow the record from the original field through its target-language explanation and back again. Where the document combines fishing activities, stock-assessment outputs and official decisions, keep their sources and review criteria separate. Do not use confident paraphrase to make an incomplete dataset appear complete. A reviewer should note precisely whether a problem changes identity, amount, year, uncertainty, regulation, evidence or ordinary style.
Create a release gate with three questions: what claim could be misunderstood here, which identifier or definition prevents that misunderstanding, and what independent record would demonstrate that the chosen wording is valid? For this stage, record a field owner, a dated source reference and a test result. If the input conflicts with a published standard or its own tables, seek an authoritative correction rather than making the translation internally consistent by guesswork. When evidence arrives, record the correction as a versioned decision so the same issue cannot silently recur in the next translation batch.
Step 20: Record corrections and release
At the record corrections and release stage, document what is known, which source proves it, and what remains ambiguous. The goal is reproducibility: someone who was not involved in drafting should be able to follow the record from the original field through its target-language explanation and back again. Where the document combines fishing activities, stock-assessment outputs and official decisions, keep their sources and review criteria separate. Do not use confident paraphrase to make an incomplete dataset appear complete. A reviewer should note precisely whether a problem changes identity, amount, year, uncertainty, regulation, evidence or ordinary style.
Create a release gate with three questions: what claim could be misunderstood here, which identifier or definition prevents that misunderstanding, and what independent record would demonstrate that the chosen wording is valid? For this stage, record a field owner, a dated source reference and a test result. If the input conflicts with a published standard or its own tables, seek an authoritative correction rather than making the translation internally consistent by guesswork. When evidence arrives, record the correction as a versioned decision so the same issue cannot silently recur in the next translation batch.
Failure modes: diagnose the changed claim, not merely the typo
Failure 1: Species label mapped to wrong taxon. The immediate repair is to reconcile scientific name and code. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 2: Stock code deleted. The immediate repair is to restore assessed stock component. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 3: Fishery conflated with fleet. The immediate repair is to restore source analytical unit. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 4: Wild catch called aquaculture. The immediate repair is to recover production mode. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 5: Gross catch called landing. The immediate repair is to separate catch and unloading event. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 6: Bycatch called discard. The immediate repair is to differentiate target status from disposition. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 7: Processed weight called live weight. The immediate repair is to retain presentation and factor. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 8: Sea days called fishing days. The immediate repair is to check activity and trip definitions. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 9: Hook count called fish count. The immediate repair is to preserve effort denominator. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 10: Nominal effort called standardized effort. The immediate repair is to restore model qualification. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 11: F treated as effort count. The immediate repair is to keep mortality parameter. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 12: CPUE described as population census. The immediate repair is to qualify index and catchability. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 13: SSB called total biomass. The immediate repair is to restore mature-spawner definition. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 14: Blim called guaranteed safe level. The immediate repair is to keep model limit context. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 15: F/FMSY called proportion of fish removed. The immediate repair is to preserve ratio. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 16: Projection called observation. The immediate repair is to restore modeled status. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 17: Advice called enforceable quota. The immediate repair is to verify adoption document. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 18: Proposed closure called active. The immediate repair is to restore decision and commencement date. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 19: Annual quota called vessel allocation. The immediate repair is to preserve quantity level. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 20: Cross-year column headings merged. The immediate repair is to restore year matrix. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 21: Vessel flag assumed permanent. The immediate repair is to preserve timeline and UVI. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 22: Calls sign treated as UVI. The immediate repair is to preserve identity fields. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 23: Carrier treated as catcher. The immediate repair is to reconstruct vessel role. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 24: Transshipment called landing. The immediate repair is to restore transfer event. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 25: Port request called approval. The immediate repair is to retain procedural status. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 26: Investigation called conviction. The immediate repair is to restore evidential and legal state. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 27: Missing quantity changed to zero. The immediate repair is to retain null semantics. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 28: Corrected event counted twice. The immediate repair is to deduplicate by event and version. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 29: FLUX code translated as prose. The immediate repair is to preserve schema value. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 30: Latitude and longitude reversed. The immediate repair is to check coordinate order. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 31: Public summary deletes uncertainty. The immediate repair is to restore confidence and assumption. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
Failure 32: Chart axes lose units. The immediate repair is to check visual evidence. But the editor should also inspect whether the wrong term has entered charts, summaries, cross-references, data feeds or downstream decisions. Classify the consequence by entity identity, evidence status, measurement, spatial scope, time or authority. A correction is complete only when another reader can reconstruct the original claim from the translated result and trace its basis to the same dated record. If a dependent numerical aggregate changes, recalculate it from approved source fields rather than editing the target sentence alone.
100 worked examples and diagnostics: preserve the actual claim
All these examples are fictional teaching records, not real catches, quotas, violations or vessel identities. Each begins with the relevant source context, then demonstrates a plausible tempting error and a controlled repair. The purpose is diagnostic: read each example as a test of whether the translation remains true, not as a set of phrases to copy uncritically.
Diagnostic 001: Species identifier
Source situation. FAO statistical species item with a three-letter code. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Replace code with a local fish market nickname. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep identifier and verified scientific name. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a scientist to inspect the line. The scientific reviewer checks whether a parameter, stock component, sampling convention or scenario changes meaning. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 002: Common label
Source situation. Single commercial label covers several species. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Claim exact species without laboratory evidence. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep commercial class and uncertain taxonomic status. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a port officer to inspect the line. The officer checks whether the target has created an authorization or outcome that the source never recorded. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 003: Stock code
Source situation. One species has two assessed populations. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Generalize one stock trend to the whole species. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Preserve distinct stock code and area. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a data steward to inspect the line. The steward tests codes, field types, versions, null semantics, units and persistent identifiers. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 004: Group-level ID
Source situation. Observer records fish family not species. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Upgrade to an exact scientific species. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep original identification resolution. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a public reader to inspect the line. The reader checks whether a clear summary preserves the decision status, limitations, timing and location scope. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 005: Historic synonym
Source situation. Source uses old scientific name. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Erase historical determination. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep original and annotate accepted synonym. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a vessel operator to inspect the line. The operator asks whether they would take a different action from the target wording than they could justifiably take from the source. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 006: Hybrid production
Source situation. Aquaculture sheet lists hybrid species item. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Present hybrid as a wild stock. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Retain production and identity. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a translator-editor to inspect the line. The editor back-translates the controlled claim and inspects captions and surrounding clauses for consistency. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 007: Juvenile catch
Source situation. Survey measures juveniles under threshold length. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Describe mature spawners. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Preserve life stage and threshold. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask an auditor to inspect the line. The auditor traces quantities and identities through the original register, trip log, batch event and decision trail. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 008: Shellfish trade
Source situation. Shipment label and laboratory taxon differ. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Replace laboratory identity with invoice label. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep distinct source roles. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a management analyst to inspect the line. The analyst separates observed history, model projection, scientific advice, adopted regulation and quota uptake. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 009: Species-list edition
Source situation. Codes update between two datasets. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Count the same item twice under labels. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Track versioned code map. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a scientist to inspect the line. The scientific reviewer checks whether a parameter, stock component, sampling convention or scenario changes meaning. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 010: Taxonomic uncertainty
Source situation. Sample identifies genus only. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Assert definite species. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Retain uncertainty and specimen evidence. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a port officer to inspect the line. The officer checks whether the target has created an authorization or outcome that the source never recorded. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 011: Trip duration
Source situation. Boat absent six days but fishes four. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call six sea days active fishing. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Record trip days and fishing days. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a data steward to inspect the line. The steward tests codes, field types, versions, null semantics, units and persistent identifiers. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 012: Trawl hours
Source situation. Net spends three hours on bottom. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call that engine running hours. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep gear-operating time. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a public reader to inspect the line. The reader checks whether a clear summary preserves the decision status, limitations, timing and location scope. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 013: Longline effort
Source situation. Log lists twelve thousand hooks. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Translate as twelve thousand caught fish. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Preserve hooks as effort unit. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a vessel operator to inspect the line. The operator asks whether they would take a different action from the target wording than they could justifiably take from the source. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 014: Pot soak
Source situation. Forty pots deployed for three nights. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Report only forty gear days. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Compute and label units properly. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a translator-editor to inspect the line. The editor back-translates the controlled claim and inspects captions and surrounding clauses for consistency. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 015: Zero catch haul
Source situation. Valid haul catches no fish. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Remove event as unproductive. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep fishing activity and zero catch. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask an auditor to inspect the line. The auditor traces quantities and identities through the original register, trip log, batch event and decision trail. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 016: Search interval
Source situation. Crew searches without setting gear. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Invent a successful catch event. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Separate searching from capture. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a management analyst to inspect the line. The analyst separates observed history, model projection, scientific advice, adopted regulation and quota uptake. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 017: Nominal effort
Source situation. Fleets have different vessel powers. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call raw hours comparable impact. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep nominal effort label. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a scientist to inspect the line. The scientific reviewer checks whether a parameter, stock component, sampling convention or scenario changes meaning. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 018: Standardized effort
Source situation. Model adjusts effort for gear. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Describe adjusted index as raw time. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Retain standardization method. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a port officer to inspect the line. The officer checks whether the target has created an authorization or outcome that the source never recorded. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 019: Lost nets
Source situation. Abandoned gear may continue fishing. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Record all effort stopped at departure. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Separate vessel activity from ghost fishing. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a data steward to inspect the line. The steward tests codes, field types, versions, null semantics, units and persistent identifiers. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 020: Mixed gears
Source situation. Voyage uses gillnets and longline. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Aggregate as one generic set count. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Segment effort by gear type. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a public reader to inspect the line. The reader checks whether a clear summary preserves the decision status, limitations, timing and location scope. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 021: Gross catch
Source situation. A haul captures mixed organisms. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call entire mass fish landed. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Separate disposition components. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a vessel operator to inspect the line. The operator asks whether they would take a different action from the target wording than they could justifiably take from the source. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 022: On-board retention
Source situation. Fish retained before reaching port. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Describe as already landed. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Wait for unloading evidence. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a translator-editor to inspect the line. The editor back-translates the controlled claim and inspects captions and surrounding clauses for consistency. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 023: Target discard
Source situation. Target fish are discarded for damage. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Describe all discarded fish as bycatch. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep target and fate fields. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask an auditor to inspect the line. The auditor traces quantities and identities through the original register, trip log, batch event and decision trail. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 024: Retained bycatch
Source situation. Non-target fish kept for sale. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Describe as discarded waste. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep retained status and species. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a management analyst to inspect the line. The analyst separates observed history, model projection, scientific advice, adopted regulation and quota uptake. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 025: Gutted mass
Source situation. Landing measured after gutting. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call weight whole fish. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep product presentation. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a scientist to inspect the line. The scientific reviewer checks whether a parameter, stock component, sampling convention or scenario changes meaning. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 026: Live-weight conversion
Source situation. Statistics convert processed mass. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Claim amount directly weighed. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Document factor and calculation. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a port officer to inspect the line. The officer checks whether the target has created an authorization or outcome that the source never recorded. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 027: Transfer vessel
Source situation. Carrier receives catch at sea. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Mark event a port landing. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep transshipment event and IDs. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a data steward to inspect the line. The steward tests codes, field types, versions, null semantics, units and persistent identifiers. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 028: Partial landing
Source situation. Only half onboard cargo unloaded. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Say entire catch landed. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Track remaining inventory. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a public reader to inspect the line. The reader checks whether a clear summary preserves the decision status, limitations, timing and location scope. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 029: Confidential cell
Source situation. Statistics suppress small fleet amount. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Replace suppressed value by zero. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep suppression marker. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a vessel operator to inspect the line. The operator asks whether they would take a different action from the target wording than they could justifiably take from the source. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 030: Recreational release
Source situation. Survey includes catch and release. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call released fish retail landings. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep recreational disposition. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a translator-editor to inspect the line. The editor back-translates the controlled claim and inspects captions and surrounding clauses for consistency. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 031: Spawning biomass
Source situation. Model estimates mature spawning fish. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call it total marine biomass. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Retain SSB definition. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask an auditor to inspect the line. The auditor traces quantities and identities through the original register, trip log, batch event and decision trail. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 032: Recruit age
Source situation. Fish enter modeled cohort at age one. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call recruitment new fishing workers. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep cohort and age. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a management analyst to inspect the line. The analyst separates observed history, model projection, scientific advice, adopted regulation and quota uptake. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 033: CPUE
Source situation. Survey reports kilograms per hour. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call rate absolute abundance. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep index denominator. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a scientist to inspect the line. The scientific reviewer checks whether a parameter, stock component, sampling convention or scenario changes meaning. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 034: Selectivity L50
Source situation. Gear retains half at a modeled length. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Say half the stock is caught. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Explain retention curve and length. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a port officer to inspect the line. The officer checks whether the target has created an authorization or outcome that the source never recorded. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 035: Natural mortality
Source situation. Model reports M parameter. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call it fishing quota. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep non-fishing mortality. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a data steward to inspect the line. The steward tests codes, field types, versions, null semantics, units and persistent identifiers. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 036: F ratio
Source situation. F/FMSY equals 0.85. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Say 85 percent of fish caught. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep reference-point comparison. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a public reader to inspect the line. The reader checks whether a clear summary preserves the decision status, limitations, timing and location scope. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 037: Biomass ratio
Source situation. B/BMSY equals 1.2. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Say biomass rose 20 percent this year. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Distinguish level ratio from growth. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a vessel operator to inspect the line. The operator asks whether they would take a different action from the target wording than they could justifiably take from the source. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 038: Confidence bounds
Source situation. Survey gives interval around estimate. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Publish only point as exact. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep uncertainty statement. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a translator-editor to inspect the line. The editor back-translates the controlled claim and inspects captions and surrounding clauses for consistency. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 039: Retrospective model
Source situation. New assessment revises older estimates. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call two versions new observations. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep model revision provenance. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask an auditor to inspect the line. The auditor traces quantities and identities through the original register, trip log, batch event and decision trail. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 040: Survey index
Source situation. Acoustic survey reports index units. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Translate to tonnes without calibration. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Retain measurement scale. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a management analyst to inspect the line. The analyst separates observed history, model projection, scientific advice, adopted regulation and quota uptake. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 041: Scientific ceiling
Source situation. ICES-style advice says catches should not exceed figure. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Present figure as enacted TAC. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Preserve issuer and advice force. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a scientist to inspect the line. The scientific reviewer checks whether a parameter, stock component, sampling convention or scenario changes meaning. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 042: Adopted TAC
Source situation. Government adopts a catch limit. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Describe as unapproved discussion. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep adopted decision date. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a port officer to inspect the line. The officer checks whether the target has created an authorization or outcome that the source never recorded. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 043: Allocation share
Source situation. Quota split between license holders. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call share global stock biomass. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep quota holder and amount. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a data steward to inspect the line. The steward tests codes, field types, versions, null semantics, units and persistent identifiers. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 044: Quota uptake
Source situation. Report says 65 percent allocation used. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call 65 percent of stock exploited. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep allocation denominator. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a public reader to inspect the line. The reader checks whether a clear summary preserves the decision status, limitations, timing and location scope. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 045: Future year
Source situation. 2027 advice includes 2028 biomass. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Put all figures under 2027. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep column years. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a vessel operator to inspect the line. The operator asks whether they would take a different action from the target wording than they could justifiably take from the source. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 046: Zero-F scenario
Source situation. Table models fishing mortality zero. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Announce universal fishing ban. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep hypothetical scenario label. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a translator-editor to inspect the line. The editor back-translates the controlled claim and inspects captions and surrounding clauses for consistency. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 047: Closure consultation
Source situation. Public draft proposes closed area. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Describe closure as already active. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep proposal status. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask an auditor to inspect the line. The auditor traces quantities and identities through the original register, trip log, batch event and decision trail. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 048: Biomass trigger
Source situation. Reference point changes advice pressure. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call it minimum fish length. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep reference quantity and role. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a management analyst to inspect the line. The analyst separates observed history, model projection, scientific advice, adopted regulation and quota uptake. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 049: Risk probability
Source situation. Chance SSB falls below Blim. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call probability of extinction. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep event and horizon. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a scientist to inspect the line. The scientific reviewer checks whether a parameter, stock component, sampling convention or scenario changes meaning. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 050: Exemption rule
Source situation. Conditional gear exemption is proposed. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Grant unconditional exemption. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep all qualifications. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a port officer to inspect the line. The officer checks whether the target has created an authorization or outcome that the source never recorded. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 051: Vessel rename
Source situation. Same hull changes display name. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Create a second vessel identity. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep permanent UVI. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a data steward to inspect the line. The steward tests codes, field types, versions, null semantics, units and persistent identifiers. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 052: Flag switch
Source situation. Registry changes national flag. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Assume old flag remains current. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Date-stamp flag fields. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a public reader to inspect the line. The reader checks whether a clear summary preserves the decision status, limitations, timing and location scope. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 053: Radio callsign
Source situation. Record has callsign and UVI. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Treat callsign as permanent UVI. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep distinct identifiers. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a vessel operator to inspect the line. The operator asks whether they would take a different action from the target wording than they could justifiably take from the source. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 054: Vessel length
Source situation. Registry supplies LOA. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call it waterline length. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Preserve dimension field. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a translator-editor to inspect the line. The editor back-translates the controlled claim and inspects captions and surrounding clauses for consistency. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 055: Gross tonnage
Source situation. Vessel GT listed as regulatory measure. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Interpret as cargo tonnes. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep gross tonnage. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask an auditor to inspect the line. The auditor traces quantities and identities through the original register, trip log, batch event and decision trail. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 056: Owner and operator
Source situation. Vessel lists both parties. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Merge into single owner. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Preserve each legal role. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a management analyst to inspect the line. The analyst separates observed history, model projection, scientific advice, adopted regulation and quota uptake. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 057: Carrier vessel
Source situation. Refrigerated carrier transships seafood. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call carrier fishing vessel that caught it. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep vessel type and role. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a scientist to inspect the line. The scientific reviewer checks whether a parameter, stock component, sampling convention or scenario changes meaning. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 058: Authorization expiry
Source situation. Fishing authorization expired yesterday. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Describe vessel currently licensed. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep expiry and status. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a port officer to inspect the line. The officer checks whether the target has created an authorization or outcome that the source never recorded. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 059: Similar names
Source situation. Two ships share near-identical names. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Merge inspection dossiers. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Cross-match UVI and register. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a data steward to inspect the line. The steward tests codes, field types, versions, null semantics, units and persistent identifiers. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 060: Beneficial owner
Source situation. Registry distinguishes beneficial owner. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Replace with operating manager. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep disclosure role. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a public reader to inspect the line. The reader checks whether a clear summary preserves the decision status, limitations, timing and location scope. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 061: Observer coverage
Source situation. Observer on one in five trips. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Say whole fleet directly observed. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep coverage denominator. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a vessel operator to inspect the line. The operator asks whether they would take a different action from the target wording than they could justifiably take from the source. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 062: Camera flag
Source situation. Electronic monitoring flags suspicious set. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Translate as confirmed violation. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep flagged and adjudicated states. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a translator-editor to inspect the line. The editor back-translates the controlled claim and inspects captions and surrounding clauses for consistency. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 063: VMS gap
Source situation. Satellite messages absent for hours. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Assert certain illegal entry. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Report data gap only. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask an auditor to inspect the line. The auditor traces quantities and identities through the original register, trip log, batch event and decision trail. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 064: AIS and VMS
Source situation. Two tracking feeds with different mandates. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Treat as one universal system. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep system provenance. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a management analyst to inspect the line. The analyst separates observed history, model projection, scientific advice, adopted regulation and quota uptake. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 065: Port entry
Source situation. Vessel requests permission to enter. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Describe request as granted. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep request status. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a scientist to inspect the line. The scientific reviewer checks whether a parameter, stock component, sampling convention or scenario changes meaning. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 066: Port service denial
Source situation. One service is refused after inspection. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Claim all port access banned. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep exact service scope. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a port officer to inspect the line. The officer checks whether the target has created an authorization or outcome that the source never recorded. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 067: IUU suspicion
Source situation. Analyst flags inconsistent catch record. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call vessel convicted. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Preserve allegation stage. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a data steward to inspect the line. The steward tests codes, field types, versions, null semantics, units and persistent identifiers. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 068: Inspection note
Source situation. Inspector records unresolved gear issue. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Present as final financial penalty. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Preserve finding and decision. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a public reader to inspect the line. The reader checks whether a clear summary preserves the decision status, limitations, timing and location scope. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 069: Catch certificate
Source situation. Origin document supports verification. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call unlimited import permission. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep certificate purpose. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a vessel operator to inspect the line. The operator asks whether they would take a different action from the target wording than they could justifiably take from the source. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 070: PSMA scope
Source situation. Port State Measures apply under defined scope. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Say all ports and vessels covered equally. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Use source jurisdiction condition. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a translator-editor to inspect the line. The editor back-translates the controlled claim and inspects captions and surrounding clauses for consistency. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 071: Mixed batch
Source situation. One lot contains catch from two vessels. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Attribute everything to one ship. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Maintain parent lot links. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask an auditor to inspect the line. The auditor traces quantities and identities through the original register, trip log, batch event and decision trail. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 072: Conversion yield
Source situation. Packed fish weighs less than live equivalent. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Force figures to match without factor. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Preserve presentation and yield. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a management analyst to inspect the line. The analyst separates observed history, model projection, scientific advice, adopted regulation and quota uptake. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 073: Product species
Source situation. Invoice uses trade label while lab gives taxon. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Override lab with invoice. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Maintain separate evidence. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a scientist to inspect the line. The scientific reviewer checks whether a parameter, stock component, sampling convention or scenario changes meaning. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 074: Cold chain
Source situation. A container had a temperature excursion. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Assert product cleared safe. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep incident versus release status. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a port officer to inspect the line. The officer checks whether the target has created an authorization or outcome that the source never recorded. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 075: Corrected certificate
Source situation. Certificate corrected for ID typo. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Count as another catch event. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep revision and same event. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a data steward to inspect the line. The steward tests codes, field types, versions, null semantics, units and persistent identifiers. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 076: Import clearance
Source situation. Border agency clears import procedure. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Claim marine sustainability certified. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep decision’s actual scope. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a public reader to inspect the line. The reader checks whether a clear summary preserves the decision status, limitations, timing and location scope. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 077: Custody gap
Source situation. One shipment transfer lacks documentation. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Invent uninterrupted chain. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Mark missing link. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a vessel operator to inspect the line. The operator asks whether they would take a different action from the target wording than they could justifiably take from the source. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 078: Mixed origin
Source situation. Retail lot combines three source catches. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Assign all to one landing. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Link every source consignment. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a translator-editor to inspect the line. The editor back-translates the controlled claim and inspects captions and surrounding clauses for consistency. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 079: Marketing claim
Source situation. Package states responsibly sourced. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Say every related fish stock sustainable. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Separate marketing and stock evidence. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask an auditor to inspect the line. The auditor traces quantities and identities through the original register, trip log, batch event and decision trail. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 080: Return event
Source situation. Shipment returns to processor. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call it second harvest. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep linked return event. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a management analyst to inspect the line. The analyst separates observed history, model projection, scientific advice, adopted regulation and quota uptake. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 081: FLUX key
Source situation. Data message holds UVI in stable field. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Translate identifier letters. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep machine field value. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a scientist to inspect the line. The scientific reviewer checks whether a parameter, stock component, sampling convention or scenario changes meaning. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 082: FLUX operations
Source situation. Schema distinguishes haul and landing. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Use generic activity for both. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep event types. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a port officer to inspect the line. The officer checks whether the target has created an authorization or outcome that the source never recorded. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 083: Code revision
Source situation. Old gear code list used in message. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Guess modern equivalent. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Use official version mapping. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a data steward to inspect the line. The steward tests codes, field types, versions, null semantics, units and persistent identifiers. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 084: Null quantity
Source situation. Catch amount not reported. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Replace null by zero. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep unknown marker. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a public reader to inspect the line. The reader checks whether a clear summary preserves the decision status, limitations, timing and location scope. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 085: Time offset
Source situation. Landing crosses midnight in UTC. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Drop timezone and reorder events. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Preserve offset and instant. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a vessel operator to inspect the line. The operator asks whether they would take a different action from the target wording than they could justifiably take from the source. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 086: Coordinate order
Source situation. Payload requires longitude then latitude. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Reverse pair silently. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Verify CRS axis order. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a translator-editor to inspect the line. The editor back-translates the controlled claim and inspects captions and surrounding clauses for consistency. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 087: Unit code
Source situation. Message records kilograms. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Rename label tonnes without conversion. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Change value and unit only together. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask an auditor to inspect the line. The auditor traces quantities and identities through the original register, trip log, batch event and decision trail. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 088: Network receipt
Source situation. Message was transported but not approved. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call it accepted catch declaration. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Separate technical and business acknowledgement. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a management analyst to inspect the line. The analyst separates observed history, model projection, scientific advice, adopted regulation and quota uptake. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 089: Resubmission
Source situation. Duplicate haul event sent twice. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Count two hauls. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Deduplicate event identifier. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a scientist to inspect the line. The scientific reviewer checks whether a parameter, stock component, sampling convention or scenario changes meaning. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 090: Validation rejection
Source situation. Mandatory field missing. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Claim successful submission. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep failure and remedy. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a port officer to inspect the line. The officer checks whether the target has created an authorization or outcome that the source never recorded. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 091: Sector production
Source situation. Global report separates aquaculture from wild catch. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call all harvest capture fisheries. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep production taxonomy. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a data steward to inspect the line. The steward tests codes, field types, versions, null semantics, units and persistent identifiers. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 092: Stock percentage
Source situation. Percentage of stocks sustainable. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call percentage of landings. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Preserve denominator. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a public reader to inspect the line. The reader checks whether a clear summary preserves the decision status, limitations, timing and location scope. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 093: Landings share
Source situation. Percentage of landings from sustainable stocks. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call percentage of stocks. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Preserve weighting. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a vessel operator to inspect the line. The operator asks whether they would take a different action from the target wording than they could justifiably take from the source. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 094: Small-scale sample
Source situation. Survey covers registered small boats. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Claim complete global census. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. State sampling limitation. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a translator-editor to inspect the line. The editor back-translates the controlled claim and inspects captions and surrounding clauses for consistency. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 095: Shared stock
Source situation. One population crosses jurisdictions. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Assign entire stock to one authority. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep biology and governance separate. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask an auditor to inspect the line. The auditor traces quantities and identities through the original register, trip log, batch event and decision trail. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 096: Inland catch
Source situation. Dataset includes rivers and seas. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Describe all harvest as ocean catch. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Preserve environment. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a management analyst to inspect the line. The analyst separates observed history, model projection, scientific advice, adopted regulation and quota uptake. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 097: Livelihood count
Source situation. Stat includes direct and indirect livelihoods. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Call count licensed crews. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Preserve definition of population. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a scientist to inspect the line. The scientific reviewer checks whether a parameter, stock component, sampling convention or scenario changes meaning. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 098: Preliminary assessment
Source situation. Panel posts tentative estimate. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Turn into final rule. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Retain provisional status. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a port officer to inspect the line. The officer checks whether the target has created an authorization or outcome that the source never recorded. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 099: Public closure
Source situation. Notice covers one fishery for a month. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Announce worldwide permanent closure. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Keep scope and effective dates. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a data steward to inspect the line. The steward tests codes, field types, versions, null semantics, units and persistent identifiers. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Diagnostic 100: Uncertain decline
Source situation. Index trend has broad interval. Before writing the target text, name the entity and event this sentence concerns, and note what has actually been observed versus inferred or declared. A fisheries report is usually a set of connected fields, not free-standing prose. Its numbers have denominators, its labels have controlled definitions, and its assertions carry authority and time limits. Treat this fictional record as an opportunity to reconstruct those dependencies. If another paragraph or footnote supplies a missing definition, include it in the translator’s working record before choosing a polished phrase.
Failure to avoid. Predict certain collapse. The error may sound natural because it borrows everyday vocabulary, but it changes what a careful reader is entitled to conclude. This is a material accuracy risk rather than a stylistic preference. Determine whether the mistake changes a species or vessel identity, a mass or rate, a date or boundary, a scientific hypothesis, a legal status, or the record’s provenance. An editor should not conceal that risk by using softer wording in the same ambiguous sentence; the underlying relationship must be restored first.
Controlled translation decision. Preserve estimate and uncertainty. Retain the original field labels or their authorized target equivalents, along with the relevant code and units. If the target language needs explanatory wording, add a plain-language description after preserving the formal concept and its scope. The translation may reorganize sentence structure but must not introduce a new population, record, quantity, source or decision. Mark an unresolved ambiguity explicitly rather than pretending to know which of two interpretations the source intended. It is better for a technical translation to request clarification than to transmit a precise but invented claim.
Who should verify it? Ask a public reader to inspect the line. The reader checks whether a clear summary preserves the decision status, limitations, timing and location scope. The independent reviewer should have access to the dated source, supporting register or model definition, units and adjacent table notes. Ask that reviewer to reconstruct the original meaning using only the target and its documented references. If the reconstruction adds or removes a condition, reopen the translation, document the choice and run the relevant numeric or identity check. This example demonstrates why ordinary grammatical fluency cannot substitute for traceable agreement about what the source evidence says.
Transfer test. Imagine a second document with the same class of ambiguity but a different fishery, language, gear, vessel or reporting system. Would the chosen correction still be justified? Transfer the checking rule, not the accidental sample number. Keep the role of the source author, status of the evidence, date, entity, denominator and reference framework visible. If a code or term is system-specific, carry the principle of identifier protection without falsely imposing one authority’s label on every other authority. Write the final decision into the terminology ledger so the next revision can be audited rather than rediscovered from scratch.
Four-week training system and transfer workshops
Week one: distinguish identity and record type
Build ten paired terminology cards for species, stock, fleet, vessel, trip and area; demonstrate why labels without identifiers are vulnerable. Test common-name ambiguity, taxonomic scope and source versions. Deliver a field ledger rather than an unordered vocabulary list. Begin each session by showing the source identifier, not by presenting an isolated term. A learner should explain why the proposed meaning is warranted and how a different definition would alter a real calculation or operational decision. Ask for one corrected version, one independently checked version and one short explanation suitable for a nonspecialist without making it more certain than the evidence.
The deliverable for this week includes a source snapshot, a term definition with a dated authority, a numeric and identifier comparison, a record of unresolved problems and a clear approval or hold outcome. Create a deliberate fault in at least one sample: a shifted year, swapped unit, incorrect vessel name or misleading modal verb. Require the learner to identify which downstream sentence would become inaccurate. The exercise passes when the correction repairs both the local line and the surrounding conclusion.
Week two: reconcile quantitative evidence
Use fictional catch, discards, landing, effort, CPUE, SSB and mortality data. Track units and denominators, rebuild two model scenarios, and explain why processed mass differs from live-weight equivalent. Deliver a signed-off comparison sheet. Begin each session by showing the source identifier, not by presenting an isolated term. A learner should explain why the proposed meaning is warranted and how a different definition would alter a real calculation or operational decision. Ask for one corrected version, one independently checked version and one short explanation suitable for a nonspecialist without making it more certain than the evidence.
The deliverable for this week includes a source snapshot, a term definition with a dated authority, a numeric and identifier comparison, a record of unresolved problems and a clear approval or hold outcome. Create a deliberate fault in at least one sample: a shifted year, swapped unit, incorrect vessel name or misleading modal verb. Require the learner to identify which downstream sentence would become inaccurate. The exercise passes when the correction repairs both the local line and the surrounding conclusion.
Week three: preserve regulatory and event status
Compare scientific advice with enacted quota, proposals with final rules, allegations with findings, and requests with authorizations. Check FLUX message labels and vessel registry changes. Deliver an error-severity report that names the action a mistranslation might induce. Begin each session by showing the source identifier, not by presenting an isolated term. A learner should explain why the proposed meaning is warranted and how a different definition would alter a real calculation or operational decision. Ask for one corrected version, one independently checked version and one short explanation suitable for a nonspecialist without making it more certain than the evidence.
The deliverable for this week includes a source snapshot, a term definition with a dated authority, a numeric and identifier comparison, a record of unresolved problems and a clear approval or hold outcome. Create a deliberate fault in at least one sample: a shifted year, swapped unit, incorrect vessel name or misleading modal verb. Require the learner to identify which downstream sentence would become inaccurate. The exercise passes when the correction repairs both the local line and the surrounding conclusion.
Week four: publish, retest and govern correction
Prepare a multilingual article or report with source snapshot, approved termbase, evidence references, plain-language explanation, numerically checked tables, release sign-off and change log. Give the target to an independent reviewer and see if the original source claim can be reconstructed. Begin each session by showing the source identifier, not by presenting an isolated term. A learner should explain why the proposed meaning is warranted and how a different definition would alter a real calculation or operational decision. Ask for one corrected version, one independently checked version and one short explanation suitable for a nonspecialist without making it more certain than the evidence.
The deliverable for this week includes a source snapshot, a term definition with a dated authority, a numeric and identifier comparison, a record of unresolved problems and a clear approval or hold outcome. Create a deliberate fault in at least one sample: a shifted year, swapped unit, incorrect vessel name or misleading modal verb. Require the learner to identify which downstream sentence would become inaccurate. The exercise passes when the correction repairs both the local line and the surrounding conclusion.
Glossary and frequently asked questions
ASFIS means FAO list of statistical species items and identifiers. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
ISSCAAP means international aquatic animals and plants statistical grouping. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Stock means defined biological or assessment population unit. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Stock code means identifier of one assessment component. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Fishery means operational or statistical unit defined by specified scope. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Fleet means group of vessels chosen for analysis. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Aquaculture means cultivation or farming of aquatic organisms. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Capture fisheries means harvest from naturally occurring aquatic populations. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Gross catch means quantity captured under stated catch convention. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Retained catch means captured organisms held rather than discarded. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Bycatch means non-target catch under a defined system. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Discards means catch returned or disposed under reporting convention. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Landings means fish or product unloaded under defined event and measure. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Landed weight means product mass at landing in stated presentation. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Nominal catch means often live-weight equivalent of landings in FAO usage. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Live-weight equivalent means conversion to whole or live mass convention. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Transshipment means transfer from one vessel to another. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Haul means gear-retrieval or catch operation. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Set means gear deployment or operation. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Fishing effort means gear activity over defined period. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Nominal effort means unadjusted activity measure. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Effective effort means standardized or adjusted effort. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
CPUE means catch divided by defined effort. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
F means fishing mortality in stock assessment. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
M means natural mortality in stock assessment. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
FMSY means fishing-mortality reference under MSY approach. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
SSB means spawning-stock biomass. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Blim means biomass limit reference point. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Bpa means precautionary biomass reference point. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
BMSY means biomass reference under MSY. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Recruitment means entry into an assessed cohort or class. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Cohort means group of animals born in a period. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Selectivity means capture or retention response of gear. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
L50 means modeled length at fifty-percent retention threshold. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
TAC means total allowable catch from competent authority. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Quota means defined allowed or allocated quantity. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Advice means scientific recommendation distinct from enacted regulation. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Scenario means conditional modeled projection. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
CWP means FAO Coordinating Working Party on Fishery Statistics. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
ICES means scientific advisory organization with defined remit. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
RFMO means regional fisheries management organization. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
PSMA means FAO Agreement on Port State Measures. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
IUU means illegal unreported and unregulated fishing. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
UVI means unique vessel identifier intended to persist. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
IMO number means identifier used for UVI within relevant arrangements. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
VMS means fisheries vessel monitoring system. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
AIS means automatic identification system. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
FLUX means Fisheries Language for Universal eXchange. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Event ID means reference to a particular recorded operation. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Code list means controlled catalog of permitted data values. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Schema means defined structure of machine data. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Null means missing or unavailable value not equal to zero. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
UTC means Coordinated Universal Time. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Provenance means trace of data origin and change. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Uncertainty means qualification of estimate or measurement. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Revision means versioned correction of source content. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Translation evaluation means review of target text against defined quality requirements. In translation, check the specific source definition, jurisdiction, period and field before selecting a target equivalent. Preserve original identifiers, unit labels and model notation, and do not substitute a familiar phrase if it changes the evidence’s meaning.
Is catch the same as landings?
Not necessarily. Catch accounting includes captured organisms under defined conventions, whereas landings relate to offloading and can involve a different quantity or presentation. Where a document gives its own definition, use that governing context. A reliable translation distinguishes a source-backed field from a helpful explanation. It never makes an estimate more precise, a proposed rule more binding, an unidentified organism more specific or a missing datum into an observed zero. Recheck the surrounding caption or table, because errors can survive even after the main sentence is repaired.
Is bycatch the same as discards?
No. Bycatch describes non-target status and discards describe disposition. Each can occur without the other. Where a document gives its own definition, use that governing context. A reliable translation distinguishes a source-backed field from a helpful explanation. It never makes an estimate more precise, a proposed rule more binding, an unidentified organism more specific or a missing datum into an observed zero. Recheck the surrounding caption or table, because errors can survive even after the main sentence is repaired.
What is nominal catch?
In commonly used FAO statistics this refers to live-weight equivalent of landings, not necessarily the weighed mass of a processed product. Where a document gives its own definition, use that governing context. A reliable translation distinguishes a source-backed field from a helpful explanation. It never makes an estimate more precise, a proposed rule more binding, an unidentified organism more specific or a missing datum into an observed zero. Recheck the surrounding caption or table, because errors can survive even after the main sentence is repaired.
Why are species codes needed?
Names vary between languages and markets. A controlled code helps preserve the intended statistical species item across exchanges. Where a document gives its own definition, use that governing context. A reliable translation distinguishes a source-backed field from a helpful explanation. It never makes an estimate more precise, a proposed rule more binding, an unidentified organism more specific or a missing datum into an observed zero. Recheck the surrounding caption or table, because errors can survive even after the main sentence is repaired.
Why preserve stock codes?
A species can have several assessed stocks with different boundaries and biological conditions; stock-specific advice must not be generalized. Where a document gives its own definition, use that governing context. A reliable translation distinguishes a source-backed field from a helpful explanation. It never makes an estimate more precise, a proposed rule more binding, an unidentified organism more specific or a missing datum into an observed zero. Recheck the surrounding caption or table, because errors can survive even after the main sentence is repaired.
Can I translate scientific names?
Preserve the taxonomic name in its recognized form and add a verified common label if useful. Treat taxonomic changes as annotations, not silent substitutions. Where a document gives its own definition, use that governing context. A reliable translation distinguishes a source-backed field from a helpful explanation. It never makes an estimate more precise, a proposed rule more binding, an unidentified organism more specific or a missing datum into an observed zero. Recheck the surrounding caption or table, because errors can survive even after the main sentence is repaired.
What is fishing effort?
It is activity or gear deployment over a defined period, such as trawl hours or hooks; the unit must be specified. Where a document gives its own definition, use that governing context. A reliable translation distinguishes a source-backed field from a helpful explanation. It never makes an estimate more precise, a proposed rule more binding, an unidentified organism more specific or a missing datum into an observed zero. Recheck the surrounding caption or table, because errors can survive even after the main sentence is repaired.
Is effort the same as fishing mortality?
No. F is a modeled stock parameter, while effort describes fishing activity. Their relationship is conditional, not lexical identity. Where a document gives its own definition, use that governing context. A reliable translation distinguishes a source-backed field from a helpful explanation. It never makes an estimate more precise, a proposed rule more binding, an unidentified organism more specific or a missing datum into an observed zero. Recheck the surrounding caption or table, because errors can survive even after the main sentence is repaired.
Does CPUE equal fish abundance?
Not automatically. CPUE can be an index, but catchability, gear, location and sampling changes matter. Where a document gives its own definition, use that governing context. A reliable translation distinguishes a source-backed field from a helpful explanation. It never makes an estimate more precise, a proposed rule more binding, an unidentified organism more specific or a missing datum into an observed zero. Recheck the surrounding caption or table, because errors can survive even after the main sentence is repaired.
What does SSB mean?
Spawning-stock biomass under the model’s defined mature population, distinct from every organism’s combined mass. Where a document gives its own definition, use that governing context. A reliable translation distinguishes a source-backed field from a helpful explanation. It never makes an estimate more precise, a proposed rule more binding, an unidentified organism more specific or a missing datum into an observed zero. Recheck the surrounding caption or table, because errors can survive even after the main sentence is repaired.
Does F/FMSY equal percentage caught?
No. It compares an estimated fishing-mortality measure with a reference value. Where a document gives its own definition, use that governing context. A reliable translation distinguishes a source-backed field from a helpful explanation. It never makes an estimate more precise, a proposed rule more binding, an unidentified organism more specific or a missing datum into an observed zero. Recheck the surrounding caption or table, because errors can survive even after the main sentence is repaired.
Is scientific advice a binding quota?
Not by itself. Verify formal adoption by the competent management authority and the effective period. Where a document gives its own definition, use that governing context. A reliable translation distinguishes a source-backed field from a helpful explanation. It never makes an estimate more precise, a proposed rule more binding, an unidentified organism more specific or a missing datum into an observed zero. Recheck the surrounding caption or table, because errors can survive even after the main sentence is repaired.
Why preserve vessel UVI?
Names and flags change; the permanent ID provides a more reliable link between records. Where a document gives its own definition, use that governing context. A reliable translation distinguishes a source-backed field from a helpful explanation. It never makes an estimate more precise, a proposed rule more binding, an unidentified organism more specific or a missing datum into an observed zero. Recheck the surrounding caption or table, because errors can survive even after the main sentence is repaired.
What is FLUX used for?
Structured exchanges of fisheries-related information; machine code values should remain interoperable. Where a document gives its own definition, use that governing context. A reliable translation distinguishes a source-backed field from a helpful explanation. It never makes an estimate more precise, a proposed rule more binding, an unidentified organism more specific or a missing datum into an observed zero. Recheck the surrounding caption or table, because errors can survive even after the main sentence is repaired.
Why is an absent value not zero?
Unknown or unreported data cannot be turned into evidence of no catch or no activity. Where a document gives its own definition, use that governing context. A reliable translation distinguishes a source-backed field from a helpful explanation. It never makes an estimate more precise, a proposed rule more binding, an unidentified organism more specific or a missing datum into an observed zero. Recheck the surrounding caption or table, because errors can survive even after the main sentence is repaired.
Can machine translation handle fisheries documents?
It can assist, but a qualified reviewer must verify technical content, units, identifiers and authority. Where a document gives its own definition, use that governing context. A reliable translation distinguishes a source-backed field from a helpful explanation. It never makes an estimate more precise, a proposed rule more binding, an unidentified organism more specific or a missing datum into an observed zero. Recheck the surrounding caption or table, because errors can survive even after the main sentence is repaired.
How should I report a possible IUU problem?
Preserve whether it is an allegation, inquiry, official finding, sanction or appeal rather than assuming final guilt. Where a document gives its own definition, use that governing context. A reliable translation distinguishes a source-backed field from a helpful explanation. It never makes an estimate more precise, a proposed rule more binding, an unidentified organism more specific or a missing datum into an observed zero. Recheck the surrounding caption or table, because errors can survive even after the main sentence is repaired.
How should tables be translated?
Retain year headings, source footnotes, symbols, units, scenario names and the correct data series. Where a document gives its own definition, use that governing context. A reliable translation distinguishes a source-backed field from a helpful explanation. It never makes an estimate more precise, a proposed rule more binding, an unidentified organism more specific or a missing datum into an observed zero. Recheck the surrounding caption or table, because errors can survive even after the main sentence is repaired.
What should a public summary say?
Explain the central finding plainly without removing uncertainty, date limits, applicability or decision authority. Where a document gives its own definition, use that governing context. A reliable translation distinguishes a source-backed field from a helpful explanation. It never makes an estimate more precise, a proposed rule more binding, an unidentified organism more specific or a missing datum into an observed zero. Recheck the surrounding caption or table, because errors can survive even after the main sentence is repaired.
What changes after a source correction?
Reconcile source versions, recheck dependent translations and log the replacement without counting a corrected record twice. Where a document gives its own definition, use that governing context. A reliable translation distinguishes a source-backed field from a helpful explanation. It never makes an estimate more precise, a proposed rule more binding, an unidentified organism more specific or a missing datum into an observed zero. Recheck the surrounding caption or table, because errors can survive even after the main sentence is repaired.
Authoritative sources and next routes
FAO Coordinating Working Party Handbook
FAO CWP fishing effort definitions
FAO statistical species and ASFIS list
FAO Global Record vessel identifiers
FAO Port State Measures Agreement
FAO May 20 2025 FLUX exchange announcement
UN/CEFACT FLUX standard overview
ICES fisheries advice scenarios
FAO SOFIA 2026 sector findings
ISO 5060:2024 translation evaluation
Evidence checked on 31 October 2026. FAO’s 2026 sector update summarizes 2024 fisheries and aquaculture production and reports biological-sustainability indicators for specific earlier reference periods. The 2025 ASFIS release on the FAO classification page lists 13,708 species items. FAO’s FLUX connection announcement is dated 20 May 2025. These dates are stated so readers do not confuse a page’s publication date with the underlying biological observation year, nor a documented technical deployment with a new binding legal obligation.
Return to Master Art of Translation | The Complete System for Moving Meaning Between Languages for the translation root. For general vocabulary acquisition use the existing protected Vocabulary Learning Hub. For English paraphrase, semantic distinctions and cross-language meaning use How English Works | Translation and Meaning Across Languages. These are references to existing owner pages, not rewritten or displaced content.
A fisheries translation is successful only when an independent reader can tell who issued a claim; exactly which species, stock, vessel, event, place and period it covers; what quantity or model the claim uses; whether it is observation, estimate, advice or law; and where its source and corrections can be checked. Meaning survives across languages when those relationships survive.