Construction risks: responsibility matrix and priorities

Updated: 2026 · Reading time: ~6 min

In practice, most “critical” problems on site arise not because technologies are missing, but because roles are not clearly defined: who makes decisions, who controls, who is responsible for documents, and who is only informed. That is why for a manageable result the client needs two baseline tools: a responsibility matrix (RACI) and risk priorities (what is unacceptable under any conditions, and what can be optimized).

In a PRO approach, priorities are always the same: 1) safety and compliance with standards and permitting procedures, 2) load‑bearing capacity / reliability of structures and engineering systems, 3) controlled change (design/cost/schedule), 4) workmanship quality and as‑built documentation. Below is a short responsibility matrix for key stakeholders — it helps remove disputes before they appear.

1) Client responsibilities

The Client defines project goals and bears the ultimate responsibility for organizing delivery: budget, timeline, quality requirements, functionality, acceptable risk level, procurement and contract model. In risk management, the Client is responsible for: providing complete baseline data (land rights/constraints, initial conditions, technical conditions/utility connections, surveys, geology/geodesy where required), timely decision making, approving design solutions and changes, appointing proper control participants (technical supervision, author’s supervision), defining a communication protocol (who is authorized to give instructions to the contractor), and ensuring procedures required for legal execution of works and subsequent commissioning. A typical client‑side risk is “blurred requirements” or delayed decisions — this almost always turns into downtime, rework and extra costs even with strong contractors.

2) Lead designer (general designer) responsibilities

The lead designer is responsible for integrity and consistency of the design documentation: coordination between disciplines, correctness of technical solutions, compliance with standards, baseline data and the design brief. In risk terms, their responsibility is to minimize “paper errors” that become the most expensive on site: clashes between structures and MEP, incomplete details, incompatible specifications, incorrect levels, uncoordinated technological solutions. The lead designer also supports changes: promptly processes contractor RFIs, issues clarifications/corrections, and releases updated drawings and specifications according to procedure. If the project goes through expert review, it is critical that the lead designer manages the correction process while preserving the logic and coordination of decisions instead of “patching” remarks in fragments.

3) Contractor responsibilities

The contractor is responsible for performing construction and installation works in accordance with the design, technologies, occupational safety and quality requirements, as well as for organizing the construction process on site. The key risk area for the contractor is workmanship quality and evidence of execution: timely maintenance of as‑built documentation, hidden works acts, executive schemes, logs, material certificates/passports, test protocols, and quality control records. The contractor is also responsible for managing subcontractors and suppliers so that material substitutions, technological deviations or “optimizations” do not pass without approval. A typical conflict is when the contractor tries to solve everything by speed (“we’ll do it and formalize later”): this leads to non‑acceptance of works, rework, payment delays and issues at commissioning.

4) Author’s supervision responsibilities

Author’s supervision protects design decisions on site. It controls compliance of works with design solutions, provides clarifications, participates in reviewing details and prevents uncontrolled deviations. A key part is change management: author’s supervision assesses whether a change is permissible, whether it degrades safety, reliability, fire‑safety/operational performance, and whether it creates conflicts with adjacent disciplines. Proper author’s supervision does not “slow down” construction; on the contrary, it reduces rework risks by quickly providing technically correct solutions and formalizing them so they are acceptable for the client and later for control procedures. A typical mistake is replacing author’s supervision with “consultations without records”: verbal approvals without documenting changes create legal and technical risk for all parties.

5) Technical supervision responsibilities

Technical supervision is the client’s on‑site control tool: verification of quality, quantities, compliance with design and standards, and control of documentary evidence of executed works. In the risk matrix, supervision ensures the client does not pay for “unproven” work: verifies acts, hidden works, logs, material certificates vs. actual materials, executive schemes, test results, plan vs. actual quantities and photo fixation of critical stages. Technical supervision is also a key element of defect management: records non‑conformities, sets deadlines, controls re‑inspection and documentary close‑out. A PRO approach means regular reporting to the client (risks/changes/status), not “signing acts at the end”. A typical risk is formal engagement of supervision: control is shifted to the end and corrections become expensive or impossible without dismantling.

6) DIAM representatives’ role

DIAM representatives act within state control in construction and verify compliance with established requirements and procedures. For the project this means: any “grey zones” in documents, deviations without approvals, missing proper logs/acts/quality confirmations or violations of the permitting regime may result in an order, work suspension, penalties or mandatory remediation. From a risk‑management perspective, DIAM is a “final filter” of process legality, therefore the best strategy for the client and team is to build systematic compliance: complete baseline package, transparent approvals chain, change procedure, as‑built documentation discipline, and quality confirmations of materials and works. This is not only about inspection — it is about the ability of the project to be document‑defensible at any moment.

PRO practical tip: fix the responsibility matrix (RACI) in the kick‑off protocol/contract and maintain three registers continuously: a risk register, change register, and non‑conformity register. These three documents best “hold” the construction within quality, schedule and budget.