Reading Russian-Language Tender Documents: TZ, Lots and Standard Forms
Quick Answer: A Russian-language cable tender arrives as a fixed set of papers: a technical assignment (ТЗ) that describes what the works and materials must achieve, a lot schedule that slices the scope into numbered packages, drawings and single-line diagrams, a commercial proposal form, and a draft contract with annexes. Each paper answers a different question, and reviewers read them as one chain. Translate the whole folder and you still lose points, because the marks sit in the fields, not in the prose.
Introduction
The first folder a foreign cable supplier receives from Kazakhstan, Uzbekistan or Kyrgyzstan usually arrives in Russian, and it does not read like the tender documents an IEC-trained bid team expects. The scope is not one narrative; it is a stack of numbered papers, each written by a different hand, and the evaluation is scored against fields inside them. Teams that treat the package as one document to be translated lose marks to teams that read it as a set of forms to be answered.
This guide walks the package for EPC bid teams and distributors buying cable into the region: what the technical assignment fixes, how the lot structure works, what the drawings and standard forms carry, and where the draft contract hides its leverage. The full tender path sits in our Central Asian cable tender guide; this page stays one layer down, with the papers themselves. Country and supplier context is collected in our Central Asian cable buying hub.
What Arrives in the Tender Folder
A typical package contains five working parts. The invitation and instructions tell you how to submit. The technical assignment, usually abbreviated ТЗ, describes the objects, the cable families and the acceptance regime. The lot schedule, or ЛОТ list, divides the scope into separately priced packages, each with its own quantities and often its own delivery point. Then come the drawings, the commercial form and the draft contract.
The papers are not written by one author. The ТЗ usually comes from a design institute, the lot schedule from the purchaser’s commercial side, and the draft contract from the legal department. Each layer uses its own vocabulary, and a designation written one way in the ТЗ can appear in shortened form in the schedule. The differences are not errors; they are the seams every bid team has to manage.
One practical habit separates winners early: number every paper on arrival, against the folder’s own numbering where it exists. Clarification questions are filed by document and clause, the commercial form is completed exactly as issued, and the compliance table quotes the annex row it answers.
The Technical Assignment: How the ТЗ Is Built
The ТЗ opens with the project frame: objects, purpose, site conditions and the split of responsibility. For a cable bid the load-bearing parts come next: the cable families, the voltage classes, the route environments, the fire requirements and the standards list. The sections are written against GOST, so the voltage strings arrive in Russian formatting even when the purchaser also reads IEC.
Read the standards list first, then the environments, then the acceptance regime. The list tells you which editions govern; the environments tell you which constructions the quantities imply; the acceptance regime tells you what documentation each delivery must carry.
Watch for the sections that are silent. A ТЗ that fixes drum lengths nowhere, that leaves the sheath colour unspecified, or that omits the certificate scheme for imported cable is not being generous; it is pushing the decision into your offer. Those silences become clarification questions while the window is open, and priced risks afterwards. The construction vocabulary behind the designations is set out in our note on medium voltage cable standards.
Lots and the Bill of Quantities
The lot structure decides where your price competes. One tender may slice the same cable volume into lots by object, by voltage class or by delivery phase, and a bidder can usually win one lot without the others. How the slices were cut decides how the price should be built.
Inside each lot, the bill of quantities fixes the lines: designation, cross-section, unit and volume. Read each line against the ТЗ section that governs it and against the drawing that shows where it runs. The three sources agree most of the time, and the exceptions are exactly where clarification questions belong. A quantity line that no drawing supports, or a drawing that shows a construction the schedule does not list, is worth asking about before you price it.
Lot structure also decides logistics: separate delivery points and phased handovers change drum planning, storage and the documentation set per consignment, and late delivery clauses in the draft contract are written against those windows.
Drawings and Single-Line Diagrams
The drawings in a cable tender do two jobs. Route plans and layouts show lengths, entries and environments, and they let you check the quantities instead of trusting them. Single-line diagrams, such as the pair of substation schemes that often accompany a distribution package, fix the topology: incomers, metering points, protection and the cable routes between panels.
Check the diagrams against the schedule line by line for the cable-relevant items. A feeder drawn as a reserve circuit may carry a quantity line, and a metering connection may appear on the drawing but not in the bill. Where the drawing shows a construction the schedule omits, price it with a stated assumption or ask; where the schedule lists a length no drawing supports, the quantity is a question, not a rounding.
Drawings also settle arguments about terminology. The symbol set in a Russian single-line diagram is its own dialect, and a general translator will flatten it. The practical fix is a one-page legend you build yourself in the first days: symbol, meaning, schedule line affected. That page becomes the reference your engineers and your translator both work from.
Standard Forms and the Draft Contract
The commercial proposal form is not a template suggestion; it is the answer sheet. Purchasers build their comparison tables from the fields in the form, and a bid that reorganises them makes the evaluator rebuild your numbers by hand. Complete the form exactly as issued, add rows only where the instructions allow, and attach your own price breakdown as a separate annex rather than rewriting the form’s structure. The mechanics of a defensible breakdown sit in our note on the cable price breakdown.
The draft contract deserves a technical read, not only a legal one. Delivery terms, title transfer, storage obligations, documentation language, the acceptance regime and the liquidated damages schedule all land on the delivery organisation. A contract annex that requires documentation in Russian per consignment, for example, is a production instruction as much as a legal one.
Annexes are where the concrete lives: delivery schedules, certificate requirements, warranty terms and sometimes a specimen of the guarantee instruments. Our notes on cable payment terms and the quotation path from China to Central Asia cover the parts that most often move the number.
A Field-Level Reading Method
Build one working file from the whole folder, with one line per cable family. Each line carries: the ТЗ clause that governs it, the lot and quantity line, the drawing reference, the voltage string as written, the fire requirement, the standard and edition, and the delivery documents named. That file becomes the compliance table, the pricing skeleton and the delivery plan in one.
Translate fields, not pages. A full translation of a hundred-page folder produces fluency nobody scores; a terminology table that fixes designation, cross-section, voltage, standard and drum terms in both languages produces a bid your reviewer can check. Keep the original Cyrillic designations inside your compliance table; the reviewer looks for the original strings.
Log every assumption next to the line it belongs to. When the clarification window closes, the log is the difference between a risk you priced deliberately and a gap you discover at delivery.
The Tender Package at a Glance
The table lines up the five working parts of a Russian-language cable tender, what each one fixes and where foreign bidders most often misread it.
| Component | Written By | What It Fixes | First Read Priority | Typical Misread |
|---|---|---|---|---|
| Technical assignment (ТЗ) | Design institute | Objects, cable families, environments, standards, acceptance regime | Standards list, then environments, then acceptance | Treated as background prose instead of a requirements source |
| Lot schedule (ЛОТ) | Purchaser commercial side | Scope slices, quantities, units, delivery windows per lot | How the slices were cut, then line-level check | Pricing one blended volume instead of the lot as cut |
| Drawings and diagrams | Design institute | Routes, lengths, topology, earthing, reserve circuits | Single-line diagram, then route plan per lot | Trusting the bill of quantities without a drawing check |
| Commercial proposal form | Purchaser | The fields the comparison table is built from | Instructions, then field structure | Reorganising the form and forcing manual re-entry |
| Draft contract and annexes | Legal department | Delivery terms, documentation language, penalties, guarantees | Delivery and documentation annexes | Reading it as legal text only and missing production instructions |
Where Foreign Bids Lose Paper Points
The recurring failures are administrative, not technical. A compliance table that answers in paraphrase instead of quoting the annex row. A designation transliterated where the reviewer looks for the Cyrillic string. A commercial form returned with merged cells or added columns. Each one costs marks that no price advantage recovers.
Documentation requirements are the second leak. Where the ТЗ or the contract annex names per-consignment documents in Russian format, bidders who discover the requirement after the award buy it in a hurry, and the hurry shows. The per-drum paper chain behind those requirements is described in our notes on cable marking and traceability and cable labelling and documentation.
The third leak is silence management. Bids that answer only what was asked leave the purchaser’s unstated needs unpriced, and they surface as clarification questions you answer under time pressure, or as contract clauses you accept without cost.
Reading Decisions to Freeze Early
These are the decisions to settle in the first week of a Russian-language tender, before pricing starts, in the order the arguments usually arrive.
| Decision to Freeze | How to Do It | Output to Keep | Cost of Skipping |
|---|---|---|---|
| Working translation scope | Translate ТЗ requirements, schedule fields and form instructions; skim the rest | Terminology table in both languages | Fluent prose that misses the scored fields |
| Compliance mapping | One line per cable family, keyed to ТЗ clause and annex row | Compliance table used in the technical envelope | Answers the evaluator cannot locate and cannot score |
| Quantity verification | Every bill line checked against drawing and ТЗ section | List of discrepancies, each resolved or asked | Priced quantities that do not survive clarification |
| Form discipline | Commercial form completed as issued, extras annexed separately | Submitted form plus own breakdown annex | Manual re-entry by the evaluator and silent mistrust |
| Clarification log | Numbered questions filed by document and clause, sent in the window | Log with the purchaser's written answers | Unpriced assumptions surfacing at delivery |
| Documentation plan | Per-consignment document list drafted from ТЗ and contract annexes | Document plan agreed with the factory before production | Paper bought in a hurry after the award |
| Price basis page | Currency, validity and copper basis stated on one page of the offer | Price basis annex referenced by the commercial form | A copper move inside validity that only you pay for |
When a Translation Is Not the Answer
When the failure is structural. A tender package read as one document cannot be fixed by better translation. The five components answer different questions, and until the bid team works from one keyed file, translation quality changes nothing the evaluator scores.
When the designation strings carry the meaning. A GOST designation compressed or transliterated loses the construction information inside it. Keep the original string everywhere the reviewer will look, and attach your decoding as a support annex. The letter-by-letter method is in our note on industrial cable RFQs.
When the drawings disagree with the schedule. No translation resolves a quantity that no drawing supports. That is a clarification question, and the window for asking it closes early. Bids that price unresolved discrepancies either lose on price or win a problem.
When the form is the contract of the offer. Rewriting the commercial form to look tidier is not a presentation improvement; it is a scoring risk. Fill it as issued, and put every improvement into an annex the evaluator can choose to read.
When the package is bilingual already. Some IFI-funded tenders issue in two languages with an English version available. Even then, the Russian schedule usually remains the governing technical text, and the fields worth checking are the ones where the two versions drift.
RFQ Checklist
- Every tender paper numbered on arrival, against the folder’s own numbering
- Terminology table fixed in both languages before translation starts
- One working line per cable family, keyed to ТЗ clause, lot and drawing
- Bill of quantities checked line by line against the single-line diagrams
- Commercial proposal form completed exactly as issued, extras annexed
- Clarification questions numbered, filed by clause and sent inside the window
- Assumption log kept next to each priced line
- Per-consignment documentation list drafted before the offer, not after award
- Original Cyrillic designations kept in the compliance table
- Price basis page: currency, validity and copper adjustment in one annex
Conclusion
A Russian-language tender package rewards a reading method, not a reading speed. The ТЗ fixes what must be true, the lot schedule fixes where you compete, the drawings verify both, and the forms and contract decide how your answers get scored. Teams that build one keyed working file in the first week answer faster, price cleaner and leave fewer marks on the table.
Kexingyu Cable Group (KXYE) works from the original Cyrillic schedule lines and returns a compliance table keyed to the annex rows. Send the tender folder and the destination country. A request for quotation is the fastest start, and the offer fields we work from are in our Central Asian quotation comparison guide.


