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.
Map locations and technical names
For investigation reports, design narratives and drawing text, establish project zones, source structural-system names and drawing registers. Connect locations across reports, tables and figures while distinguishing similarly named members.
- Useful input
- Provide full reports, drawing registers, location identifiers, material and structural terminology and cited references supplied by the client.
- Work focus
- Check described objects, distinctions between observations and design information, references and abbreviations; query missing context first.
- Agreed output
- Outputs may include translated reports, location and member terminology, drawing-text mappings and reference queries.
Preserve objects and sequence relationships
For construction organization, method descriptions and site files, distinguish work descriptions, prerequisites, records and notes. Preserve structural locations, activity names and section relationships without adding construction methods.
- Useful input
- Provide applicable descriptions, related drawings, zone lists, existing records and established project wording.
- Work focus
- Cross-check activity references, locations, material names and source conditions; refer unclear engineering relationships to specialists.
- Agreed output
- Agreed outputs may include translations grouped by zone or file type, shared terminology and located query records.
Trace changes by drawing and location
For design changes, as-built documentation and updates, distinguish original design wording, change records and records of actual conditions. Preserve their status and chronology without combining sources into a new engineering conclusion.
- Useful input
- Provide old and new drawings and notes, change registers, earlier translations, handover lists and recipient formats.
- Work focus
- Check affected locations, drawings and sections; distinguish document revisions from site status and revisit affected references.
- Agreed output
- Outputs may include incremental translations, drawing-revision mappings, document registers and matters awaiting specialist responses.
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.
Investigation reports and tables
Translate strata descriptions, investigation records and tables with locations, identifiers and source classifications intact. Distinguish observations, references and author interpretations. Use client-provided naming references without reclassifying soil or rock layers.
Review focus: Check investigation points, layers, figure and table references and descriptions, retaining the source degree of uncertainty.
Structural and design narratives
Translate structural systems, members, material descriptions and design notes with drawing-register context. Retain cited standard identifiers and editions, querying unsupported translated titles rather than selecting alternative standards for the project.
Review focus: Check members, grid lines, levels, material grades and references without assessing design suitability.
Engineering drawing text
Agreed work may cover titles, captions, notes, title blocks and legends, retaining drawing numbers, revisions and indexes. Interpret abbreviations within their drawings and distinguish short labels from full descriptions; agree extraction and reinsertion methods beforehand.
Review focus: Check detail references, title-block information, label alignment and unedited content; scope graphical changes separately.
Quantities and material schedules
Translate item names, work descriptions, material entries and notes within existing fields, separating quantity information from descriptions. Preserve item codes, units, quantities and blanks without harmonizing or recalculating different source measurement bases.
Review focus: Check codes, units, quantity fields, scope qualifications and distinctions between similar items.
Method descriptions and construction organization
Translate activity descriptions, organizational arrangements, illustrations and tables, preserving source sequence and location applicability. Locate and query incomplete steps or conditions rather than filling them with common practice.
Review focus: Check activity names, referenced objects, sequence conditions, warnings and drawings without adding instructions.
Test records and handover documentation
Translate test reports, checklists, material records and handover notes with sample, location and document relationships intact. Preserve results, evaluation wording and signature fields separately, leaving blanks unfilled; translation does not determine conformity.
Review focus: Check sample identifiers, dates, result fields, attachments and status wording without recasting records as acceptance findings.
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.
Building and structural documentation
Interpret beam, column, wall and slab names alongside floors, grid lines and drawings. Preserve member hierarchy and location clues, distinguishing general notes from local drawing notes so names remain traceable.
Road and bridge documentation
Alignments, sections, piers, abutments and members are linked by location identifiers. Retain project chainage and numbering conventions and check references in prose and tables, keeping nearby sections and structural locations distinct.
Underground and geotechnical documentation
Investigation descriptions, underground structures and site records may use different classification levels. Preserve distinctions between observations, interpretations and qualifications, linking locations and identifiers without adding geological or structural judgments.
Municipal works and existing facilities
Distinguish existing, new and relocated assets. Preserve ownership, location and interface wording for utilities and facilities, identifying repeated names by drawing and zone and keeping changes traceable to original files.
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.
构件C-07的名称见图ST-11第B版，其位置标识为区域Z-2。
ILLUSTRATIVE TRANSLATIONThe name of member C-07 is given in drawing ST-11, Revision B; its location identifier is Zone Z-2.
What the reviewer checks
This fictional example preserves the member, drawing and zone identifiers separately, demonstrating name-to-location relationships without providing structural design information.
本报告中的“场地区域”仅指图LOC-03标示的范围。
ILLUSTRATIVE TRANSLATIONIn this report, “site area” refers only to the area indicated in drawing LOC-03.
What the reviewer checks
This fictional translation confines the definition to the report and a specified drawing, without interpreting the term as the project boundary in other files.
记录REC-15第C版更新了附件名称，表中所列结果未在本次修订中更改。
ILLUSTRATIVE TRANSLATIONRecord REC-15, Revision C, updates the attachment names; the results listed in the table are unchanged in this revision.
What the reviewer checks
This fictional example distinguishes updated names from retained results, without interpreting the results or making test or acceptance judgments.
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.
Check locations together with members
Check names together with zones, floors or location identifiers. Preserve identifying information for repeated names and review pronouns and detail references so terminology alignment does not remove location distinctions.
Keep values and symbols distinct
Check dimensions, levels, quantities, units, signs and superscripts or subscripts, including scan-recognition errors. Review wording and data separately without converting units or correcting technical values independently.
Use referenced editions faithfully
Retain standard titles, identifiers, years and clause references against the source and client references. Query incomplete citations rather than supplying an assumed edition or substituting a similarly titled reference.
Preserve record status
Review wording for plans, observations, records, opinions and conclusions, distinguishing unfilled fields, not-applicable entries and negative results. Cross-check tables and prose and retain signature information without implying additional confirmation.
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.
Translation covers meaning, terminology and location alignment, data transcription and agreed checks. The client and designated specialists make investigation, design, construction, standards-applicability and acceptance judgments. Language queries identify drawings, files and passages; processing and delivery follow the project agreement.
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
Agree disciplines and document purposes
Agree investigation, structural, construction or handover scope and readers, language direction, document status and specialist reviewers, separating drawing text from graphical work.
- 02
Map reports and drawings
Register drawings, files, revisions and zones and check supporting tables and references. Resolve missing pages, unclear images and illegible location identifiers first.
- 03
Prepare location terms and samples
Prepare member, material, activity and location names; agree wording using representative passages with tables and references, including abbreviations, level symbols and bilingual treatment.
- 04
Translate and locate queries
Work by report chapter or project zone, locating queries with sentences, pages, drawings and locations. Designated personnel answer technical questions; record language decisions separately from engineering revisions.
- 05
Review data and cross-references
After language review, check identifiers, symbols, units and references. Review contents, captions and tables in output files for shifted data rows or broken references.
- 06
Hand over and maintain revisions
Deliver translations, registers and query status with source revisions and coverage. Trace later drawings or changes into affected chapters and terms, assessing updates without merging historical records.
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 reports and narratives
Provide agreed editable or reading files with sections, identifiers, figures and attachment relationships, identifying source revisions and target languages for specialist comparison.
Drawing text and indexes
Provide drawing-text mappings or agreed files with drawing numbers, title blocks and text locations, identifying excluded graphical work and unprocessed content in handover records.
Member and material terminology
Organize structural, material, activity and location names with identifiers, sources and applicability, preserving differences between repeated terms or zones.
References and query records
Record references, naming queries, client answers and status, retaining engineering questions so later review can return to specific drawings or passages.
Revision and handover register
List sources, translations and formats by document and drawing number, distinguishing additions, replacements and retained files while preserving each record’s original status.
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.
Disciplines and document relationships
The mix of reports, drawings, schedules and records determines terminology and reference work. Language direction, disciplines and earlier translation alignment affect scope; assess repetition with location and revision context.
Drawing and file handling
Assess drawing-text extraction, scan recognition, table reconstruction, bilingual layout and reinsertion separately. Complexity depends on annotation density, symbols and editability as well as page count.
Revisions and review timing
Schedules depend on source stability, specialist answers and client review windows. Assess related impacts before adjusting current and later work for added drawings, changed zones or revised design files.
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.
- Project context and zonesProvide project type, disciplines and zones, identifying location, grid or chainage conventions to establish shared retrieval references.
- Complete reports and drawingsSupply prose, tables, drawings and registers with applicable revisions; scans should show small labels, tables, signs and footnotes.
- References and translated titlesProvide cited references, confirmed terminology and earlier translations, including client-specified standard titles where available.
- Drawing-text handlingIdentify editable drawings, fonts or exported text, mapping, reinsertion or reading-file needs and who manages graphical files.
- Specialist queries and reviewIdentify investigation, design or construction-document contacts and language and technical approvers, with recipient review methods.
- Delivery batches and permissionsSpecify batch order, milestones, confidentiality and transfer requirements, retaining change notes and agreeing tool use and file retention.
Questions before work begins
Can drawing PDFs be translated without editable files?
Assess clarity, extraction and annotation density first, then agree text mappings or laid-out files. Small labels, symbols and identifiers need checking. Without editable drawings, complete reinsertion into the original graphical format cannot be assumed.
Should standards be replaced with local equivalents?
Retain the standard actually cited, including its identifier and edition, using client-specified titles where supplied. Equivalence and applicability require specialist judgment; do not substitute another standard in translation. Query unclear citations first.
What if drawings and reports use different names?
Check drawings, locations and member identifiers to establish whether names refer to the same object. Record name mappings and sources. Specialists resolve differences in entity or scope; terminology consistency does not justify erasing source distinctions.
Will quantities be recalculated?
Language services preserve source figures, units and item relationships without remeasuring or recalculating quantities. Checks can cover transcription and field alignment. Refer suspected source issues to the client with their exact line items.
How are design changes reflected in translations?
Provide change notes, old and new files and applicable drawings. Separate added wording, data changes and reference changes before updating affected chapters and terms. Record source revisions to avoid combining records from different dates into one version.
Does test-report translation include assessment?
Preserve results, existing evaluations, notes and signatures without adding conformity or acceptance findings. Locate discrepancies between records and prose for queries. Designated specialists handle technical interpretation, document approval and engineering acceptance.
