Почему генеральных директоров в строительстве сажают по 159 УК РФ

High-level summary (business focus)

• Topic: Criminal risk for CEOs and in-house lawyers in construction and state procurement — why general directors get criminally charged (Article 159 “fraud” and related offenses) and how companies can reorganize decision‑making to reduce that risk.
• Core thesis:

  When management responsibilities and business‑process ownership are not clearly cascaded, law enforcement and courts treat the general director as responsible for all violations. A defined, auditable distribution of responsibilities (“cascading responsibility”) is the primary mitigation tool.

Cascading responsibility playbook (implementation stages)

1. Identify risk areas and map business processes (examples: sales/tenders, procurement, production, facility delivery, industrial safety).
2. Determine “who makes the decision” and assign a process owner/manager for each business process.
3. Draft and deploy an action plan for distribution of responsibilities:
   • Job descriptions
   • Delegated authorities
   • Employment contracts
   • Internal regulations
   • Acceptance/quality procedures
4. Implement changes and monitor compliance (audit trail, control points).
5. Produce evidentiary documentation showing delegated authority and segregation of duties to defend managers if investigated.

Risk-mapping & qualification process (for consultants)

• Document current business processes and actions.
• Legally qualify actions (identify objective/subjective signs of offenses).
• Identify triggers/factors that increase likelihood of law‑enforcement attention.
• Build a risk map showing probability and exposure and recommend mitigations.

Key legal/business diagnostic items

Distinguish business subprocesses that commonly contribute to alleged fraud:

• Sales / tender pricing — who sets commercial proposals.
• Production / volume estimation — who inflates volumes (chief engineer vs CEO).
• Supplier involvement in tender documents / technical specs — potential collusion.
• Acceptance / payment practices — paying before completion; false acceptance certificates.
• Industrial safety / training responsibilities.

Also determine which role signed off on the contested act (signature / certification risk).

Key metrics, KPIs, data points, targets, timelines

• Reviewed ~350 criminal sentences over the past five years.
• Sector distribution from the review:
  • Construction: ~50% of cases/sentences (highest‑risk sector).
  • Medicine and pharmaceuticals: second highest (no precise % given).
  • Others: ~25%.
• Criminal charge distribution:
  • Article 159 (fraud/theft by deception): ~72% of identified violations.
  • Article 291 (bribe giving): ~18%.
  • All other compositions: ~10%.
• Sentencing outcome for Article 159, part 4:
  • ~40% of sentences resulted in actual imprisonment (not suspended).
• Review materials:

  • 100 pages of analysis available (downloadable).

  • Telegram channel with >3,000 subscribers.
• Event: webinar on cascading responsibility scheduled (example date: Oct 29, 5:00 PM).

Concrete examples / case studies (actionable lessons)

• Moscow Metro sleepers case

  • Parties: SZK SPB (supplier and installer), Axion Rusru (seller).
  • Issue: Defects discovered; arbitration had earlier found products met technical specs, but defects arose during installation (violations in laying/install).
  • Result: Court treated acceptance certificates as false; metro’s damages = full contract amount; CEO received 2 years’ imprisonment.
  • Lesson: When acceptance and installation are separate functions, responsibility must be documented and cascaded; otherwise courts may impute knowledge/intent to the CEO.

• Industrial safety / explosion case

  • Issue: Dust‑air mixture explosion attributed to lack of process control.
  • Defense: Responsibility for compliance assigned to chief engineer; CEO acquitted (court accepted delegated, documented responsibility).
  • Lesson: Properly allocated, documented responsibilities can lead to acquittal of top management.

Actionable recommendations

Structural (organization & process)

• Create and maintain a responsibility matrix showing decision authorities for each critical process (RACI‑style: Responsible / Accountable).
• Write clear job descriptions that include specific operational duties and delegations (who inspects/accepts work, who signs acceptance certificates, who approves payments).
• Include delegated authorities and controls in employment contracts and local internal regulations.
• Implement monitoring and audit trails to demonstrate that line managers exercised control and that the CEO did not personally perform/authorize contested tasks.

For in-house lawyers and external counsel

• Limit the scope of sign‑off: when signing or stamping documents, explicitly state whether the sign‑off is limited to the “legal component” versus consenting to the business launch.
• Avoid accepting business decision authority if you cannot defend it; clearly document the scope of any “approval” you give.
• Be prepared to explain the meaning of a signature in investigative contexts; articulate that legal review ≠ operational consent to carry out work.
• Expect and support a process of business‑process mapping, legal qualification, trigger identification, and development of a risk mitigation map when engaged by consultants.

For engagements with consultants / law firms

• Typical engagement steps:
  1. Initial meeting
  2. Describe business processes
  3. Consultant/legal qualification of actions
  4. Identify triggers and estimate risk probability
  5. Create risk map
  6. Propose remediation (policies, roles, contracts)
  7. Implement and monitor
• Use forensic / expert opinions where necessary to support defense positions (e.g., arbitration decisions, technical reports).

Law enforcement & prosecutorial dynamics

• Prosecutorial oversight: prosecutors supervise legality of investigative bodies’ actions and may have separate assistants covering criminal proceedings vs oversight of legal entities — this duplication can increase risk.
• Investigators frequently focus on signatures and acceptance documents; false or incomplete documentation is a high trigger for criminal investigation.
• Common law‑enforcement triggers:
  • Paying before work completion.
  • Pre‑construction activity before tender launch.
  • Restrictive tender specs.
  • Supplier help drafting specs.
  • Acceptance of low‑quality or incomplete work.

Practical defensive outputs to prepare

• Formal delegation records showing who had authority to:
  • Define technical specifications.
  • Accept / approve completed works.
  • Sign acceptance certificates and authorize payments.
• Documented processes describing inspections, testing, and acceptance criteria.
• Internal controls preventing suppliers/customers from unduly influencing tender documentation.
• Training records and industrial‑safety documentation tied to responsible individuals (to avoid imputing CEO responsibility).

Sources, presenters, and referenced parties

• Primary program/presenter: legal team that conducted the review of ~350 sentences (unnamed).
• Panel / participants referenced: Sergey (risk maps), Mikhail (prosecutor oversight commentary), Vladimir (participant), Maria Smutok (criminal defense attorney).
• Case parties: SZK SPB, Axion Rusru (Moscow Metro sleepers case).
• Laws referenced: Article 159 (theft by deception / fraud), Article 291 (giving a bribe).
• Materials & channels: downloadable >100‑page review; Telegram channel with >3,000 subscribers; upcoming webinar on cascading responsibility.

Available deliverables (optional)

• One‑page RACI + document checklist for rapid implementation of cascading responsibility.
• Audit template to collect evidentiary documents law enforcement commonly requests (signatures, acceptance certificates, technical specs, training logs).