Explanation
Договор is a masculine noun and one of the most important business/legal words. It appears in заключить договор, подписать договор, исполнить договор, расторгнуть договор, условия договора, срок действия договора, стороны договора. Stress is commonly догово́р in standard speech. Avoid treating it as a casual “agreement” in every context. Соглашение may also be agreement, but the relationship between договор and соглашение depends on legal and business context.
Сторона means side or party. In contracts, стороны are the parties to the contract. A party may be исполнитель (the party performing services), заказчик (customer/client ordering services), поставщик (supplier), покупатель (buyer), продавец (seller), арендодатель (lessor/landlord), арендатор (lessee/tenant), подрядчик (contractor), субподрядчик (subcontractor). These labels define obligations. Do not translate them lazily as “company” or “person.”
Contract openings often use participial formulas: Общество с ограниченной ответственностью “...” , именуемое в дальнейшем “Исполнитель”, в лице директора..., действующего на основании Устава, с одной стороны, и.... This is intimidating but parseable. Именуемое в дальнейшем means “hereinafter referred to as.” В лице директора identifies the representative. Действующего на основании Устава explains authority. The actual point is: who are the parties and what labels will the contract use for them?
Обязуется is contract gold. Исполнитель обязуется оказать услуги; Заказчик обязуется оплатить. It imposes an undertaking. Pair it with вправе, which grants a right or entitlement: Заказчик вправе требовать отчёт, Исполнитель вправе привлекать третьих лиц. Обязан and имеет право may appear in more direct lists. The reader should mark obligations and rights separately.
Срок is dangerous because it can mean term, deadline, period, duration, or time limit. Contracts use срок действия договора, срок оказания услуг, срок оплаты, в течение, не позднее, до, с момента подписания, с даты получения уведомления. Most real consequences live in these phrases. Do not skip them.
Contract architecture
A typical contract section Предмет договора says what the contract is about. Права и обязанности сторон lists who must do what. Стоимость и порядок расчётов covers price and payment procedure. Ответственность сторон states consequences for breach, often with штраф, пеня, убытки, неустойка. Срок действия договора says when it begins and ends. Порядок разрешения споров says how disputes are handled. Реквизиты сторон gives legal/payment details.
Appendices matter. Приложение, акт выполненных работ, счёт, счёт-фактура, спецификация, and техническое задание may carry practical obligations. A main contract may say “services are described in Appendix 1.” If you do not read the appendix, you do not know the work.
Contrast sets
1. Party labels
- исполнитель — service provider/performer
- заказчик — customer/client ordering work or services
- подрядчик — contractor
- поставщик — supplier
- покупатель — buyer
- продавец — seller
- арендодатель — lessor/landlord
- арендатор — tenant/lessee
Labels define roles. The same company may be a buyer in one contract and supplier in another.
2. Obligation and right verbs
- обязуется — undertakes to
- обязан — is obliged
- вправе — is entitled to
- имеет право — has the right
- несёт ответственность — bears liability
- гарантирует — guarantees
Вправе is formal and common in legal-contract language; learn it as a unit.
3. Ending and breach
- исполнение договора — performance/fulfillment of the contract
- нарушение условий — breach/violation of terms
- расторжение — termination
- отказ от исполнения — refusal/non-performance depending context
- неустойка — penalty/liquidated damages, context-dependent
- убытки — losses/damages
Do not guess legal effect from English cognates; mark terms for expert review in real documents.
The first error is reading only the title. Договор оказания услуг tells the type, not the obligations. The obligations live in sections and appendices.
The second error is missing party labels after the opening formula. Once Исполнитель and Заказчик are defined, the contract may stop using real names. Make a two-column map.
The third error is skipping time phrases. Circle до, не позднее, в течение, с момента, с даты, по истечении. These control deadlines and consequences.
Map the parties before the verbs
This contract clause becomes easier once the role labels are fixed first:
Исполнитель обязуется оказать услуги согласно техническому заданию, а Заказчик обязуется оплатить услуги в течение пяти рабочих дней после подписания акта.
The first half gives the provider’s duty. The second gives the customer’s duty. If the reader loses track of Исполнитель and Заказчик, the whole sentence collapses into vague business language. If the reader skips согласно техническому заданию, the actual scope of the work disappears. If the reader skips после подписания акта, the payment trigger gets misread.
Contract Russian often looks repetitive, but the repetition is the structure. Party label, obligation verb, object, deadline, trigger document: each part carries legal and practical weight.
Useful study frames
Three contract patterns repay close attention:
- техническое задание: technical assignment or statement of work
- акт выполненных работ: completion or acceptance certificate
- в течение пяти рабочих дней: within five business days
These are not supporting details. They are the working machinery of the clause. The appendix or assignment may define the service. The act may start the payment clock. The time phrase may create the deadline that later controls liability.
A second contract clause
One more clause shows how timing and triggers interact:
Исполнитель обязуется оказать услуги в срок до 15 мая, а Заказчик обязуется принять и оплатить услуги в течение пяти рабочих дней после подписания акта.
The key reading habit here is not to flatten both halves into “one side does work, the other pays.” The sentence actually gives two obligations, two different time frames, and one crucial trigger. If после is ignored, the payment period can be misread as beginning after performance rather than after formal acceptance.
Final rule
A Russian contract is readable when you map party labels, obligations, deadlines, payment terms, liability, and appendices before trusting any translation.