Project roles and areas of responsibility

Project conflicts can start with simple questions: who approves changes, who pays, and who accepts the result? While the answers remain in a couple of people's heads, the project holds together. Once more participants join, agreements become scattered across chats, and the team spends time guessing.

You can assign project roles without 30-page rulebooks. Agree on areas of responsibility, decision-making rules, and a way to record agreements. This helps keep the project manageable even under a heavy workload.

Below is a set of roles suitable for most project teams. On smaller projects, one person can take on several roles. What matters is naming the roles explicitly and recording them in one place.

Why do roles break down midway through a project?

At the start, everyone is enthusiastic: the goal is clear, the work is understood, and people are in touch. Problems emerge when the project enters a period of change: requirements are refined, constraints surface, the team changes, and additional work begins.

This is when roles are put to the test. Without someone assigned to make the final decision on changes and acceptance, the project becomes a series of lengthy approvals. Its pace depends on the speed of decision-making.

Sponsor: owner of the goal

The sponsor is responsible for why the project is being undertaken: its business goal, priority, resources, and resolving situations beyond the project manager's authority.

• Defines the goal and success criteria: what should change and how the team will know the project is complete.
• Provides resources: budget, people, access, and time from key participants.
• Resolves conflicting priorities and removes roadblocks when a decision needs senior authority.
• Makes decisions on changes that affect financial outcomes and strategy.

A common mistake is involving the sponsor only when problems arise. Agreeing on decision thresholds in advance is much less costly: what the project manager can decide independently and what must go to the sponsor.

Customer and owner of the result: acceptance authority

The internal customer or external client sets expectations and accepts the result. Companies often confuse the roles: the customer says what they want, while the person responsible for acceptance defines what counts as completed.

• Sets requirements and constraints: deadlines, budget limits, and the required quality level.
• Approves changes: additional work, substitutions, rescheduling, and revisions to scope.
• Accepts stages and the final result: signs acceptance documents and confirms completion against agreed criteria.

If a project has several stakeholders, such as the owner, commercial team, and production team, appointing one person to own acceptance of the result is useful. This prevents requirements from changing independently across different departments.

Project manager

The project manager maintains the plan, communications, risks, and progress monitoring. In construction and renovation, a site foreman often takes on this role. That is a valid arrangement, provided the role is explicitly identified.

For a closer comparison of responsibilities on site, see who a project manager is.

• Builds the work plan and sequence: who does what, when, and with which inputs and outputs.
• Organises communications: status updates, decisions, and records of changes.
• Manages the interfaces between procurement, contractors, technical supervision, and the customer.
• Monitors actual progress, gathers reports, and prepares work for acceptance.

The role has a boundary: the project manager should avoid becoming a bottleneck through which everything must pass. That leads to micromanagement and slows work down. See the article on micromanagement in construction and renovation (in Russian) for more guidance.

Technical lead: technical director or chief engineer

The technical lead is responsible for engineering and methods: construction-detail decisions, quality standards, selecting materials to suit the method, and handling complaints about completed work.

In companies managing several sites, the technical director often also reduces the owner's workload by helping establish repeatable rules, train project managers, and support complex cases.

For more on management roles, see who a technical director is and who a chief operating officer is.

• Approves technical decisions and standards for carrying out work.
• Resolves disputes over quality and methods.
• Helps the project manager plan complex stages and assess risks.
• Checks that technical decisions match the agreements and cost estimate.

Supply and procurement

Procurement ensures that materials and services reach the site on time, in the required configuration, and on agreed terms. It often becomes a source of conflict when rules are unclear: who approves a substitution, who confirms the budget, and who accepts a delivery?

• Receives requests from the project manager and those carrying out the work according to agreed rules for format, timing, and completeness.
• Compares offers, records terms, and arranges delivery.
• Gets approval for substitutions arising from availability and lead times through a predefined decision-making route.
• Provides supporting documents and information for financial records.

Finance: accounting and financial control

Project finance covers payments, documents, advance-payment controls, and visibility of the project's financial balance. In a project-based business, this directly affects stability: finances can drift out of control even when production is going well if there are no rules for advances and supporting evidence.

Related reading: funds issued to employees to account for (in Russian) and how to avoid a cash-flow gap in a construction company.

• Checks the grounds for payments: contract, invoice, request, and approval.
• Monitors advances and the reporting for them: who received money, who has accounted for it, and what evidence supports the expense.
• Collects supporting documents and checks that payment purposes are stated correctly.
• Prepares a management overview across projects: balances, commitments, and payment risks.

When the team records events and supporting evidence in one place, financial control is less dependent on constant requests for clarification or documents. The article on project financial management in the 101 app explains this approach.

Specialists: estimator, analyst, and legal adviser

Specialists join when a project needs specific expertise. Integrate the specialist into the decision-making process: who requests their input, what form the output takes, and who approves it.

• Estimator or economist: calculates quantities, assesses variances, and prepares calculations for changes and additional work.
• Legal or contracts specialist: checks wording and prepares supplementary agreements, records of disagreements, and correspondence concerning disputed situations.
• Analyst or engineer: clarifies requirements and helps establish acceptance criteria and measurable indicators.

For construction, the article on variances from the cost estimate (in Russian) is particularly useful: it shows where boundaries of responsibility are often lost when changes occur.

Quality control and acceptance

Quality control protects the project from work being completed according to someone's own interpretation. Technical supervision, an internal quality department, or the technical lead can perform this role. Its essence is checking against criteria and recording the result.

• Defines acceptance criteria for each stage: checklists, photographic records, and tolerances.
• Carries out checks and records findings and deadlines for corrections.
• Confirms that a stage is complete so subsequent work and payments can proceed.

To see how this role works in practice, read the dedicated article on the technical supervision engineer (in Russian).

Those carrying out the work: tradespeople, crews, and specialists

Those carrying out the work are responsible for production and actual completion. A simple point is often overlooked: those carrying out the work are manageable when they understand the work area, acceptance criteria, and how to record the result.

• Carry out the assigned work using the required methods and report risks identified on site.
• Record actual progress: stage photographs, quantities, comments, and material consumption according to the project's rules.
• Hand the result over to the project manager and quality control for acceptance.

The role has a boundary: those carrying out the work cannot revise the project's terms as they go. Changes follow the agreed procedure through the project manager.

Contractors and subcontractors

External contractors strengthen the team when internal resources are insufficient or specialised expertise is needed. Risks arise when contractors are integrated only through a contract, without management rules defining who assigns tasks, who accepts the result, and how changes and supporting documents are handled.

• Provide an execution plan and requirements for inputs: materials, site access, and readiness of the work area.
• Deliver results against agreed criteria and provide documents and supporting evidence.
• Participate in approvals that affect the timing, cost, and quality of their part of the work.

If you regularly work with external crews, the article on types of construction contractors (in Russian) can help you choose an arrangement suited to the task.

How can you establish areas of responsibility in one meeting?

You can set aside 45–60 minutes for discussion with key participants. The meeting's purpose is to assign decisions to roles.

Step 1. List 10–15 typical project decisions: additional work, a deadline change, a material substitution, choosing a supplier, accepting a stage, paying an advance, and a quality dispute.

Step 2. Assign one person to give the final go-ahead for each decision. A RACI matrix assigns one Accountable person to each task, making ownership of the final responsibility clear. This principle is described in Atlassian's RACI guide.

Step 3. Identify who does the work (Responsible), who provides input (Consulted), and who needs to be kept up to date (Informed).

Step 4. Record approval thresholds: the amount involved, the impact on deadlines, and the impact on quality.

Step 5. Test the arrangement against stressful scenarios: a delivery delay, a complaint, renegotiating the budget, and replacing a crew. If a decision has no owner, clarify the role.

Where should you record agreements to prevent disputes a month later?

If project participants work across different sites, chats, and schedules, agreements should remain accessible a week later and after personnel changes.

The minimum set of records:

• Roles and decision thresholds on one page.
• Communication plan: who updates whom, how often, and on status, decisions, and changes.
• Change procedure: request → calculation → approval → implementation.
• One source of truth for facts: stage photographs, documents, and payments.

To put together a clear communication plan, see the article on managing project communications (in Russian).