Start with the purpose of your project
Documents in the same industry can have different audiences, purposes and deadlines. Define the task before agreeing source material, staffing and review.
Establish sites and system relationships
For station technical communication, procurement and design documentation, establish the site, unit, system and equipment levels first, mapping supplier descriptions to the names used in the project.
- Useful input
- Provide system lists, single-line diagrams, equipment specifications and the project document register, identifying sites, disciplines and document revisions included in the current scope.
- Work focus
- Distinguish system names, equipment tags, circuit identifiers and function descriptions. Link drawing references to text without treating generic supplier documentation as the actual station configuration.
- Agreed output
- Agreed outputs may include system terminology, translated technical files and a reference list, preserving discipline divisions and document numbers for design and procurement review.
Preserve logic and record status
For control narratives, protection documents and project check records, distinguish function descriptions, conditional relationships and recorded observations, without strengthening conclusions through the translated wording.
- Useful input
- Supply complete control narratives, related figures, check sheets and responses, mapping equipment to systems and including project terminology and abbreviation definitions.
- Work focus
- Check conditional subjects, negation, conjunctions and exceptions. Distinguish state, command and feedback names, referring conflicting source logic to the client’s specialists for explanation.
- Agreed output
- Outputs can retain tables and figure references with queries and decisions on wording. Protection and control settings are conveyed as supplied, without recommendations to adjust them.
Keep operating documents maintainable
For operating procedures, maintenance material and project handover files, use applicable systems and current revisions as references while keeping historical records distinct from revised descriptions.
- Useful input
- Provide operating and maintenance files, equipment change records, prior translations and handover registers, identifying documents currently used and those supplied only for traceability.
- Work focus
- Check system and equipment names, section references, roles and document status. Review additions and replacements separately; the client confirms technical applicability.
- Agreed output
- Deliverables may include system-organized translations, revision comparisons and handover indexes with outstanding client queries, establishing a clear language baseline for later equipment modifications.
Different documents need different checks
Define translation, review, layout and supporting explanations from the actual file list. The following scopes can be combined as agreed; they are not an automatically included package.
System descriptions and single-line diagrams
Translate generation, substation and station auxiliary system descriptions using single-line diagrams and system lists, preserving the hierarchy between sites, units, systems and circuits.
Review focus: Check drawing numbers, equipment tags, busbar names and circuit descriptions across figures and text, without deriving system functions that the source does not state.
Equipment specifications and technical clarifications
Translate procurement specifications, equipment data sheets, supplier replies and technical clarifications, preserving item numbers and response relationships while distinguishing project requirements from supplier explanations.
Review focus: Check equipment names, rating descriptions, units and exceptions. Query conflicting parameters from different sources rather than choosing a replacement value for the source.
Control and protection documentation
Translate control narratives, protection descriptions, state tables and event descriptions, retaining logical conditions and references and interpreting similarly named signals within their respective systems.
Review focus: Check distinctions between states, commands, feedback and acting subjects, preserving negation and exceptions. Specialists separately confirm logic correctness and setting suitability.
Check and commissioning records
Translate check sheets, commissioning reports, issue lists and corrective responses, keeping record subjects, observations and subsequent status distinct and preserving the original chronology.
Review focus: Check item identifiers, witnesses, dates and attachments. Distinguish planned checks, actual records and open items without adding acceptance conclusions.
Operating and maintenance documents
Translate operating procedures, maintenance descriptions, handover records and training materials using consistent system and role names, preserving source warnings and conditional relationships.
Review focus: Check step references, responsible roles and limitations. Convey operating-state and safety-isolation statements completely without writing additional execution requirements.
Project handover and modification notes
Translate handover registers, modification descriptions, revision pages and archive indexes, distinguishing replaced documents from retained attachments and preserving document status markings.
Review focus: Check document numbers, revisions, applicable systems and reference chains, keeping historical versions identifiable and old equipment material distinct from updated operating documents.
Adapt the approach to the document’s use
Consider the subject, audience and relationship between files together, so that terms remain traceable across different documents.
Land-based generation projects
Organize documentation around generating units, main systems and auxiliary systems. Distinguish supplier descriptions from station documentation, checking cross-discipline terminology and drawing references together.
Substation and distribution facilities
Align names across busbars, circuits, equipment and control documents, distinguishing station equipment identifiers from external system names and preserving references between single-line diagrams and manuals.
Onshore renewable energy projects
Translate onshore wind, photovoltaic and associated station documentation, distinguishing sites, individual equipment units and system interfaces. Identify the actual configuration from client documents within the project scope.
Energy storage and system coordination
Organize storage equipment descriptions, system interfaces and project correspondence, distinguishing equipment statements from station-level operating descriptions without extending product functionality into claims about the entire station.
Languages, regions and review references
Include the source and target languages, destination and recipient. Supply approved terminology, prior translations, document conventions or required templates. The client’s designated specialist confirms questions of professional applicability.
Explore languages ↗Professional care in practical document details
These fictional Chinese–English examples illustrate review methods. They are not client originals, actual deliveries, professional findings or fixed translations.
系统说明SYS-A将回路FD-B列入辅助系统AUX-C；设备表EQ-D保留该回路编号。
ILLUSTRATIVE TRANSLATIONSystem description SYS-A lists circuit FD-B under auxiliary system AUX-C; equipment list EQ-D retains that circuit identifier.
What the reviewer checks
This fictional translation retains separate system, circuit and equipment-list identifiers. It expresses a documentary relationship, without implying actual wiring or an operating arrangement.
本表中的“已记录”表示意见已录入清单，不表示该意见已关闭。
ILLUSTRATIVE TRANSLATIONIn this table, “recorded” means that a comment has been entered in the list; it does not mean that the comment is closed.
What the reviewer checks
This fictional translation preserves the definition’s scope and negation, distinguishing entry in a record from issue resolution rather than implying that a listed comment has been resolved.
移交索引HI-A修订D引用运行文件OM-B修订C；附件R保留为历史参考。
ILLUSTRATIVE TRANSLATIONHandover index HI-A, Revision D, references operating document OM-B, Revision C; Appendix R is retained as historical reference.
What the reviewer checks
This fictional translation preserves each document’s revision and the historical role of the appendix. Inclusion in a handover register does not make it the current execution version.
Actual work follows the complete source, approved terminology and specialist feedback. Queries are documented rather than resolved by inventing missing facts.
From linguistic review to final-file checks
Agree review coverage for the purpose and risk of this set of documents, distinguishing language issues, source queries and matters needing specialist confirmation.
System hierarchy and naming
Check names across system lists, drawings and equipment schedules, distinguishing sites, units, equipment and circuits. Identify similarly named equipment by tags rather than substituting a shortened description for its identifier.
Conditions and state relationships
Review negation, conjunctions, exceptions and conditional subjects, preserving distinctions between states, commands and feedback in control narratives. Refer ambiguous wording with its surrounding context.
Figures and data context
Check figures, units, rating descriptions and headings together, retaining data categories and applicable subjects. Raise discrepancies between sources rather than harmonizing them through conversion.
Record and revision status
Check report dates, comment status, revisions and indexes. Distinguish planned, recorded and confirmed statements, maintaining traceable records of linguistic review and the client’s technical decisions.
Keep queries traceable
The project manager links queries to responses. The client’s specialist confirms factual, business or technical decisions; linguists apply those decisions and check related affected content.
The language service preserves meaning, system relationships, data and document status in power and energy material, organizing agreed review and revision handover. The client’s designated specialists review system design, protection and control settings, commissioning judgments, operating arrangements and site safety decisions. Deliverables follow the project scope; translation does not constitute engineering design, operating instructions or technical acceptance findings.
A workflow from receipt to a usable file set
Agree inputs, approvers and outputs at each step. Phased delivery and source changes continue to use the same file identifiers and revision baseline.
- 01
Map the station document structure
Register files by site, discipline, system and document type. Confirm languages, purpose and revision status, identifying generic supplier manuals and historical records supplied only as references.
- 02
Establish system terminology references
Use single-line diagrams and equipment lists to establish system names, tags, circuits and roles. Review representative sections and record abbreviation definitions and their applicable disciplines.
- 03
Translate in discipline batches
Package technical descriptions, control documents and operating records separately while preserving references. Locate source conflicts in queries identifying the relevant system, drawing and section.
- 04
Review connected documents
Compare names, figures, logic and status across text and diagrams. Check terminology differences between supplier and station documents, linking review findings to specific files and revisions.
- 05
Integrate client specialist review
Designated contacts confirm technical queries. Log language corrections separately from source changes, and establish the wider impact of comments before synchronizing translations in other documents.
- 06
Hand over and maintain by system
At handover, identify systems, languages, document numbers and revisions with query status and change records. Assess later modifications against a new baseline while retaining the identity of historical translations.
A delivery list your team can work from
Agree outputs, review levels, formats and revision arrangements at the outset. Supporting records are scoped rather than assumed to be included in every service.
Translated system documents
Provide technical descriptions, operating materials or records in agreed formats, retaining contents, figures and appendix relationships and identifying applicable sites, systems and source revisions.
System and circuit terminology
Prepare agreed mappings of system, equipment, circuit and role names with project identifiers and confirmation references. Retain equipment codes and record the applicability of general names.
Queries and specialist responses
Locate queries by document number, section or table row. Retain client explanations and wording decisions, distinguishing outstanding replies, confirmed items and material requiring later updates.
Revision and difference comparisons
Where revision work is included, list additions, changes and retained content, linking affected system documents and drawing references so reviewers can check the scope of the current update.
Handover register and review records
An agreed system-based index and review record can list filenames, revisions, attachments and delivery batches, enabling recipients to locate the complete document package.
Assign responsibilities around the task
Project manager
Coordinates scope, batches, timing and queries, maintaining the delivery register and revision history.
Translator
Assigned after assessment of language direction, field and files, working to approved terminology and references.
Review and file checks
Reviews meaning, completeness, key information and file format within the agreed scope, recording matters for client confirmation.
Client specialist reviewer
Confirms source facts, professional applicability and disputed terms, consolidating feedback and owning business decisions.
Experience supported by records and a clear method
Plan the service around the actual documents and required outputs. Existing records describe participation, not a promise based on a client’s business results.
Build the discussion around your documents
Share a redacted representative sample, audience and delivery requirements so the team can identify language, formatting and specialist-review needs. Existing project records can support a discussion of comparable document scopes.
Browse existing project records ↗ISO 9001:2015
Quality-management certification for translation services, excluding branches, with briefing, review and delivery checks defined in the project scope.
ISO/IEC 27001:2022
Information-security management certification associated with translation services, excluding branches.
TAC institutional membership
Staffing is assessed by language, document type and scope, with specialist-review and linguistic responsibilities agreed before work begins.
Agree access, transfer, tool use and retention before confidential work begins. Confidential files are not entered into external AI or other online services without prior agreement. Read about confidentiality · Credentials and scope
Scope the work before price and timing
Review files before agreeing inclusions and separate charges, distinguishing language work, client review, additional services and any shipping.
System coverage and review scope
Systems, disciplines and document types affect preparation and cross-reference work. Assess language combinations, available terminology and review levels together against the actual materials.
Figures and file editability
Complex single-line diagrams, scanned tables and editable text require different handling. Bilingual layout, caption work and register preparation are priced against a defined task list.
Batches and client review windows
Discipline-based deliveries, parallel revisions and departmental feedback affect scheduling. Allow for specialist responses and review, reassessing scope when systems are added or baselines replaced.
A clear brief makes assessment more useful
Start with a non-confidential description or redacted sample, then agree how to transfer complete files. This list helps organize the key details; an initial discussion is also welcome if material is incomplete.
- Sites and systems in scopeDescribe generating, substation or distribution facilities and their systems. Map site, unit and equipment names, defining the disciplines and recipient purposes covered by the project.
- Complete technical filesSupply text, single-line diagrams, equipment schedules and complete attachments. Identify editable drawing sources and scans, and indicate whether missing referenced documents can be supplied.
- Revisions and equipment changesIdentify current baselines, historical references and equipment change notes. Match previous translations to sources, distinguishing document revisions, equipment replacements and changes to applicable systems.
- Terminology and language conventionsSupply project terminology, abbreviations, role names and approved translations. Specify languages and bilingual formats, with source references for proprietary supplier names.
- Specialist review contactsIdentify confirmation channels for electrical, control and operating queries. Agree consolidated feedback and the handling of disputed items so departmental revisions do not overwrite one another.
- Delivery milestones and confidentialityProvide initial and final milestones, review windows and handover rules. Agree document access, transfer and retention arrangements, including plans for continuing revisions.
Questions before work begins
How does this differ from electronics translation?
This scope focuses on station and power system documents, especially relationships between sites, systems, equipment and circuits. Component specifications, pins and product interfaces can form separate packages organized at product level.
Can single-line diagrams and manuals be handled together?
They can share system terminology and equipment references, with separate checks for drawing annotations and manual text. Figure text replacement, editable drawing work and layout requirements are agreed after reviewing the files.
How are protection and control documents reviewed?
Linguistic review checks conditions, negation, states and subjects, preserving source values and references. Client specialists confirm logic, settings and equipment applicability; translation does not recommend operating or setting adjustments.
What if supplier and station names differ?
Map them through equipment tags, system lists and drawings, retaining supplier wording where needed. The project contact confirms conflicts before different objects could be combined under a single name.
Can translation begin while technical files are changing?
Agree an interim baseline and translate in system batches. Each revision should identify changes and affected files so additional review and timing can be confirmed; the delivery register identifies each source revision.
Can operating procedures be shortened?
Sentence structure and readability can improve while prerequisites, warnings, exceptions and roles remain complete. Reorganizing sections or deleting content requires client confirmation of the source changes and a separately agreed editing scope.
