Energy Translation
Translate technical reports, safety procedures, environmental material, and infrastructure documentation.
Why the subject matters
What changes in this kind of work
Energy projects bring engineering, operations, environmental reporting, and regulation into the same file. A domain glossary can settle the project vocabulary, while reviewers check units, asset names, regulatory references, and safety language against the source.
An energy document is rarely about one subject. An environmental impact assessment for a wind farm can move from bird surveys to noise modelling to the grid connection within ten pages, and each part has its own vocabulary. The translation has to follow those shifts without carrying the terms of one discipline into another.
Much of the meaning sits in units and figures. Confusing MW with MWh turns a statement about capacity into a statement about output, and kV, kVA and kW are easy to mix up in a dense table. Safety procedures add a different risk: in a lockout/tagout procedure, the order of the steps matters as much as the wording.
In DeepReference, the translation model drafts on DeepReference's own servers in the EU, and the approved terms from your glossary are sent with each sentence that contains them. Quality checks flag segments where numbers differ from the source, missing glossary terms and untranslated text, and your reviewer decides what to change. The file comes back in its original format, so tables of readings, headings and Excel formulas stay in place.
How it works
A project from upload to delivery
- 1
Agree the terminology first
Import the client's term list (CSV, XLSX, TMX or TBX) into a glossary, available from Starter. If you only have an earlier report and its translation, terminology extraction (Freelance and up) can draw candidate terms from the pair; you approve or dismiss each one before it goes into the glossary.
How to do it, step by step: 2.6 Import terms into a glossary
- 2
Upload the document
Upload DOCX, PDF, PPTX or XLSX up to 50 MB (75 MB on Business), or paste text. A PDF needs selectable text; labels inside images, such as those on a scanned single-line diagram, are not translated.
How to do it, step by step: 6. Document translation
- 3
Let the model draft
Choose a tone; the technical tone suits most engineering documents. The model translates each sentence together with the glossary terms that occur in it. On Translator Pro, exact matches from your translation memory are reused, so repeated safety notes and standard clauses come back as they were approved before.
How to do it, step by step: 5. Text translation, tones and glossary
- 4
Review segment by segment
In the segment editor, source and target sit side by side with translation memory matches, glossary hits and quality-check flags. Your reviewer works through the flags, edits where needed and approves each segment. Every segment keeps a version history.
How to do it, step by step: 7. Translation Editor
- 5
Handle revisions without starting again
When the client issues a revised report, revision comparison (Freelance and up) shows what changed in the DOCX. In “With translation” mode, only the segments the revision affected are retranslated, and nothing is charged until you confirm.
How to do it, step by step: 9. Revision comparison
- 6
Download and sign off
Download the file in its original format, with tables, numbering, headers and footers. Your reviewer, or the client's engineer, gives the final approval before the document is used on site or submitted.
How to do it, step by step: 8. Document Editor
Document types
What we translate
- Environmental impact assessmentsLong reports that combine ecology, noise, water and grid topics, so terms must stay consistent across chapters written by different specialists.
- Feasibility studies and technical reportsYield estimates, capacity factors and cost figures carry the argument, so every number and unit is checked against the source.
- Grid connection documentsVoltage levels, connection points and references to grid code sections must appear exactly as in the source.
- Safety procedures and method statementsSignal words such as DANGER and WARNING must keep their level, and the steps must stay in the same order.
- Operation and maintenance manualsRepeated instructions benefit from translation memory, and equipment tags must stay exactly as written.
- Permit applications and regulatory submissionsReferences to laws, permits and authorities stay as cited in the source; the translation does not replace them with the rules of the target country.
- Sustainability and emissions reportsScope 1, 2 and 3 figures, baselines and reporting years must match the source, table by table.
- Contracts and tender documentsPPAs and EPC contracts combine technical and legal language; the legal parts also need a legal reviewer.
- Data sheets and spreadsheetsIn XLSX files the formulas are kept; check that the translated labels still match the columns they describe.
How to do it, step by step: 6. Document translation
Quality controls
Checks available during review
Domain terminology
A domain glossary or termbase can be applied to keep preferred vocabulary consistent during review.
How to do it, step by step: 3. Terminology extraction
Format and structure checks
Document structure, numbering, tables, and section conventions remain visible for reviewer checks.
How to do it, step by step: 8. Document Editor
Translation memory
Approved translations can be reused when the same or similar text appears again.
How to do it, step by step: 4. Translation memory
Review records
Reviewer actions, translation settings, and approval timestamps are kept where the workflow supports them.
How to do it, step by step: 7.3 Project tools
Glossary filtering
Only glossary terms found in the current text are sent with the translation request.
How to do it, step by step: 2.15 Use a glossary correctly
Recommended settings
How to set up a job in this field
Domain for terminology extraction
Choose Energy when you extract terms from these documents. The domain is used for extraction only.
Step by step in the user guideGlossary
Add the approved terms for this client and language pair, one translation per term, and select the glossary when you translate.
Step by step in the user guideTerminology examples
How key terms are handled
Capacity factor
Actual output divided by the maximum possible output over a period. Keep it apart from load factor and availability, and put the client's preferred rendering in the glossary so it is sent with every sentence that contains it.
Installed capacity and generation (MW and MWh)
Capacity is power; generation is energy. Quality checks flag numbers for review, but whether the unit is right is the reviewer's call.
Load balancing
In grid operation it means matching supply and demand; in IT it means spreading traffic across servers. Context usually decides, but fix the term in the glossary when a document mixes both, as data-centre energy reports often do.
Transmission and distribution
Two levels of the grid, each with its own operator (TSO and DSO). Local names differ by country, for example Übertragungsnetz and Verteilnetz in German, so record them in the glossary.
Curtailment
A reduction of output ordered by the grid operator or forced by grid limits. Compensation clauses often depend on it, so it needs one agreed rendering across contracts and reports.
Lockout/tagout (LOTO)
Many companies keep the English abbreviation on site. The glossary records whether to keep LOTO or use the local term, and a rendering the client does not want can be added as a forbidden term, which the quality check flags.
Scope 1, 2 and 3 emissions
Greenhouse-gas reporting categories. Keep each figure with its scope number and check it against the source table.
Power purchase agreement (PPA)
Often kept as an abbreviation after the first mention. Related contract terms, such as take-or-pay, belong in the glossary, and the contract text needs a legal reviewer.
Commissioning
Testing a plant and putting it into service. Keep it distinct from start-up and handover, which appear in the same schedules with a different contractual meaning.
How to do it, step by step: 2.4 Add terms · 2.15 Use a glossary correctly
Who uses this
Industries served
Utilities, renewables, oil and gas, engineering firms, regulators, and infrastructure teams.
Standards and references
What reviewers can check
Reviewers can check units, asset names, grid terminology, emissions language, safety warnings, and regulatory references.
Before delivery
What your reviewer checks
- Units match the source: MW and MWh, kV and kVA, Nm³ and m³ have not been swapped.
- Every figure, range, tolerance and date matches the source, and decimal separators follow the convention agreed with the client.
- Equipment tags, asset IDs and drawing numbers are unchanged.
- Safety signal words and the order of procedure steps are the same as in the source.
- References to laws, permits, standards and grid code sections are cited as in the source.
- Emissions figures, scopes and reporting years are consistent between text and tables.
- Every segment flagged for a missing glossary term has been checked and resolved.
- Abbreviations such as LOTO, PPA and TSO are kept or expanded as the client's glossary specifies.
- After download, tables, headings, numbering and Excel formulas are in place, and any text inside images or drawings has been handled separately.
How to do it, step by step: 7. Translation Editor
Transparency
What DeepReference does not do
- DeepReference does not certify translations. If an authority requires a certified or sworn translation, a qualified translator must provide it.
- There is no model specialised in energy. The Energy domain setting guides terminology extraction only; it does not change how the model translates.
- DeepReference does not convert units or number formats. Quality checks flag numbers for review, and the reviewer decides what is correct in the target language.
- Text inside images, such as labels on a scanned drawing, is not translated. An image-only PDF is refused; upload a searchable PDF or the original file.
- DeepReference does not check documents against grid codes, permits or safety regulations, and it does not provide translators or reviewers. Technical and safety content must be approved by a qualified person on your side.
Questions
Frequently asked questions
Is there a model trained specifically for energy?
No. The same translation model handles every field. What makes the result fit your project is your glossary, your translation memory and your reviewer. The Energy domain setting guides terminology extraction only.
Will MW be converted to another unit, or 1.5 to 1,5?
DeepReference does not convert units. The model translates the text, and quality checks flag numbers for review. Agree the number format with your client and check it during review.
Can we translate drawings and diagrams in PDF?
Text that is selectable in the PDF is translated; labels that are part of an image are not. Dense drawings count as complex layouts, so check the result by hand. Some fonts may be replaced by a similar one.
Where is our project data processed?
On DeepReference's own servers in the EU. No outside AI company sees the text, and customer content is never used to train the model. Uploads are encrypted in the browser before sending, and stored files are encrypted at rest.
Can several people work on a long assessment?
On Business, team members share translation memories, glossaries and termbases, projects can be shared with reviewers, and reviewers can leave comments. There is no real-time co-editing of the same document, so agree who reviews which chapter.
Review framework
Open the platform from the dashboard when you are ready to work on files.
View quality documentationBegin projects: Energy Translation
Open the platform from the dashboard when you are ready to work on files.