Project Organization, Roles and Governance

Introduction

Construction projects are temporary organizations formed to transform a design, budget, site, materials, labour and technology into a completed facility. Their success depends not only on technical competence but also on clear authority, reliable information, ethical conduct and effective coordination. A project may have an excellent design and adequate finance yet fail because responsibilities overlap, decisions are delayed, records are incomplete or participants pursue conflicting interests.

Project organization describes how people, firms and institutions are arranged to deliver the work. Project governance establishes how the project is directed, controlled, monitored and held accountable. These subjects are closely related: organization answers “who does what and reports to whom?”, while governance answers “who may decide, according to which rules, with what evidence and under whose scrutiny?”

This chapter explains the principal roles of the client, consultants, contractor and regulatory authorities; compares common organizational structures; and develops practical principles for authority, accountability, reporting, documentation, ethics and governance.

Learning objectives

By the end of this chapter, a student should be able to:

1. Explain the roles and responsibilities of the client, consultant, contractor and regulators.
2. Distinguish authority, responsibility, accountability and liability.
3. Compare functional, projectized, matrix and construction supply-chain structures.
4. Develop a practical responsibility and reporting framework.
5. Explain how records, approvals, change control and escalation support governance.
6. Identify ethical risks and apply professional responses.
7. Analyse an organizational failure and recommend corrective actions.

1. The project environment and principal participants

A construction project usually contains several layers of participation. The client or owner identifies the need and provides, or arranges, the resources. Consultants convert the need into a design, specification and professional advice. Contractors organize labour, plant, materials and specialist firms to construct the facility. Regulators protect public interests through laws, permits, inspections and enforcement. Suppliers, subcontractors, financiers, insurers, communities and utility authorities may also influence project outcomes.

The parties may be separate legal entities or may be integrated through a design-and-build, management contracting or public–private partnership arrangement. The contract determines commercial obligations, but professional duties may also arise from legislation, licensing rules, codes of ethics and the standard of reasonable skill and care.

A useful distinction is between internal project control and external oversight. Internal control includes planning, scheduling, cost control, quality assurance, risk management and site supervision. External oversight includes building approval, environmental assessment, occupational safety inspection, utility approval and audit. Both are necessary. Regulatory approval does not replace the contractor’s duty to manage safety, and a client’s internal procedure does not remove the regulator’s authority.

2. Roles and responsibilities

2.1 The client

The client, also called the owner, employer or project sponsor, initiates the project and defines its business or social purpose. Typical responsibilities include:

• establishing the project brief, functional requirements and success criteria;
• securing land, funding and organizational support;
• appointing consultants and contractors through an appropriate procurement process;
• making timely decisions and providing accurate information;
• approving the baseline scope, budget, schedule and quality requirements;
• meeting contractual payment obligations;
• obtaining approvals that the contract assigns to the client;
• managing stakeholder expectations and accepting the completed work.

The client normally retains strategic accountability even when many tasks are delegated. Delegation transfers authority for specified actions, but it does not automatically eliminate the client’s duty to select competent agents, provide adequate resources or exercise reasonable oversight.

A client should appoint a project sponsor with authority to resolve major issues. It should also establish a governance board or steering committee for decisions involving significant cost, scope, risk, public impact or changes to the approved business case.

2.2 Consultants

Consultants provide professional advice and design services. The consultant team may include architects, civil, structural, mechanical and electrical engineers, quantity surveyors, geotechnical specialists, environmental professionals, project managers and cost advisers.

Their responsibilities may include:

• investigating site and user requirements;
• preparing drawings, specifications, calculations and schedules;
• coordinating different design disciplines;
• advising on materials, constructability, cost and programme;
• assisting procurement and evaluating tenders fairly;
• issuing design clarifications and administering specified contract procedures;
• inspecting work or reviewing quality evidence, where appointed to do so;
• identifying design risks and maintaining design records;
• certifying work, payment or completion only within their authority and professional competence.

A consultant is not automatically the contractor’s supervisor or the client’s unlimited representative. The exact scope of services must be stated in the appointment. Consultants must not approve work that they know is unsafe, defective or outside the approved design merely to protect a programme or commercial relationship.

2.3 The contractor

The contractor is responsible for executing the construction work in accordance with the contract, approved design information, laws and accepted professional practice. Main responsibilities commonly include:

• planning construction methods, resources, sequencing and temporary works;
• preparing the programme and updating it with actual progress;
• providing competent management, labour, plant and supervision;
• controlling subcontractors and suppliers;
• implementing the health and safety plan;
• establishing quality-control inspections, tests and records;
• protecting the site, public, existing services and completed work;
• identifying discrepancies, unforeseen conditions and constructability risks;
• notifying the client or contract administrator of matters requiring decision;
• maintaining as-built information, warranties, test certificates and handover records.

The contractor’s duty to follow drawings does not excuse obvious unsafe practices or failure to raise a serious design discrepancy. Conversely, a contractor should not alter the design without an authorized instruction or approved technical process.

2.4 Subcontractors and suppliers

Subcontractors perform defined packages such as foundations, steelwork, plumbing or finishes. Suppliers provide materials, equipment or fabricated components. They must comply with the prime contractor’s requirements, approved submittals, safety procedures and quality arrangements. The contractor remains responsible for coordinating their work unless the contract expressly establishes another allocation.

Early involvement of specialist subcontractors can improve constructability and reduce interface risk. However, it also requires clear design responsibility, confidentiality arrangements, procurement controls and approval procedures.

2.5 Regulatory and public authorities

Regulatory bodies protect interests that cannot be left solely to private contracting parties. Depending on the jurisdiction, these may include planning authorities, building-control departments, environmental agencies, labour and safety inspectors, fire authorities, utility agencies, heritage bodies and professional registration boards.

Their functions may include:

• issuing permits and approvals;
• reviewing plans against legislation and technical codes;
• inspecting construction at defined stages;
• investigating incidents, complaints and non-compliance;
• maintaining registers or licences;
• imposing notices, penalties, suspension or prosecution where permitted;
• requiring testing, reporting, remediation or demolition of unsafe work.

Regulators are not normally responsible for managing the contractor’s daily work. An inspection or permit should not be interpreted as a guarantee that every construction activity is safe or defect-free. Project participants must understand the applicable national and local legal framework rather than assuming that a general industry practice is lawful.

2.6 Stakeholders and the community

Neighbours, road users, future occupants, local authorities, workers, lenders and environmental groups can affect or be affected by a project. Stakeholder management includes identifying interests, communicating impacts, handling complaints, protecting vulnerable groups and documenting commitments. Community concerns about noise, dust, traffic, access or working hours can become programme and reputation risks if ignored.

3. Responsibility, authority, accountability and liability

These terms are related but not interchangeable.

• Responsibility is the duty to perform a task.
• Authority is the legitimate power to approve, direct, allocate resources or make a decision.
• Accountability is the obligation to explain and justify performance and accept consequences.
• Liability is legal responsibility for loss, damage, injury or breach.
• Delegation is the transfer of specified authority or work to another person, while retaining appropriate oversight.

A common project weakness is assigning responsibility without corresponding authority. For example, a site manager may be held responsible for programme performance but lack authority to obtain labour or approve overtime. Another weakness is allowing several people to approve the same matter without identifying who is finally accountable.

A practical allocation should answer four questions: who performs the work, who approves it, who must be consulted, and who must be informed. The commonly used RACI model expresses these relationships as Responsible, Accountable, Consulted and Informed. There should normally be one clearly accountable role for a decision, although several people may be responsible for contributing or executing.

The table is illustrative rather than universal. Contract conditions and legislation may allocate duties differently. It should therefore be converted into a project-specific responsibility matrix during mobilization.

4. Organizational structures

4.1 Functional structure

In a functional organization, specialists remain within departments such as design, procurement, finance, construction or operations. A project coordinator may have limited authority, while department managers control staff and resources.

Advantages: efficient use of specialists, strong technical communities and continuity after project completion. Limitations: departmental priorities may dominate project objectives, decisions may move slowly across boundaries and accountability can become fragmented.

4.2 Projectized structure

In a projectized organization, a project manager has substantial authority over a dedicated team. Personnel and resources are organized around the project until completion.

Advantages: clear authority, strong focus, rapid communication and integrated responsibility. Limitations: duplication of specialists, higher cost and uncertainty about staff roles after completion. This structure suits large, complex or time-critical projects where integration is essential.

4.3 Matrix structure

A matrix combines functional and project authority. An engineer may report technically to a discipline manager and operationally to a project manager. Matrix structures may be weak, balanced or strong depending on which manager controls resources and decisions.

They provide access to specialist expertise while preserving project focus, but dual reporting can create conflict. A written delegation schedule, escalation route and priority rule are essential. Without them, staff may receive incompatible instructions.

4.4 Contractual and supply-chain structures

Construction projects also have a contractual organization. In a traditional design–bid–build arrangement, the client appoints the consultant for design and the contractor for construction. The consultant often administers the construction contract, but the contractor remains responsible for means and methods.

In design-and-build, the contractor accepts greater responsibility for both design and construction, although the client may retain performance requirements and independent review. In management contracting, the client appoints a management contractor to coordinate trade contractors. In construction management, the client may contract directly with trade contractors while appointing a construction manager for coordination.

No procurement route is automatically best. Selection should consider design maturity, risk allocation, price certainty, time, client capability, market capacity, innovation and the need for early contractor involvement.

5. Governance framework

Governance is the system by which a project is directed, controlled and assured. It should establish:

1. Strategic alignment: the project supports an approved need and benefits.
2. Defined decision rights: authority limits and approval thresholds are documented.
3. Transparency: decisions are supported by traceable evidence.
4. Risk oversight: threats and opportunities are identified, assigned and reviewed.
5. Independent assurance: important controls are tested by persons sufficiently independent of the work.
6. Ethical conduct: bribery, conflicts of interest, discrimination and falsification are prohibited.
7. Escalation: unresolved or high-impact matters reach the appropriate authority promptly.
8. Learning: incidents, defects and claims are analysed to improve future performance.

A governance framework commonly includes a project charter, organization chart, responsibility matrix, delegation schedule, communication plan, risk register, change-control procedure, document-control procedure, procurement plan, quality plan, safety plan and reporting calendar.

Stage gates and assurance

A stage gate is a formal decision point at which authorized reviewers assess whether the project should proceed, change direction or stop. Typical gates occur after feasibility, concept design, developed design, procurement, mobilization, substantial completion and final closeout.

A gate review should consider scope, cost, schedule, safety, quality, risk, legal approvals, stakeholder effects and readiness for the next phase. A gate is not merely a meeting; it requires defined entry evidence, decision authority and recorded actions.

6. Reporting, communication and documentation

Information becomes useful only when it reaches the right person in a reliable form and at the right time. A communication plan should identify the audience, purpose, format, frequency, owner and escalation route.

Common reports include daily site records, weekly progress reports, monthly cost reports, safety statistics, quality inspection records, risk-register updates, design registers, procurement schedules, payment applications and forecast completion dates. Reports should distinguish facts, forecasts, assumptions, decisions and unresolved issues. Presenting an estimate as a confirmed fact is misleading and can distort management decisions.

Document control should provide:

• a unique document number and revision status;
• author, reviewer and approver identification;
• issue date and distribution list;
• secure storage and backup;
• control of superseded information;
• an audit trail of changes;
• retention and disposal rules;
• access controls for confidential or personal information.

A verbal instruction may be operationally necessary, especially during an emergency, but it should be confirmed in writing as soon as practicable. The record should state what was instructed, by whom, when, why and with what effect on cost, time, safety or quality.

Change control

A change may arise from a client request, design development, unforeseen condition, regulatory requirement, error or value-engineering proposal. A sound change process identifies the proposed change, evaluates technical and commercial effects, obtains the required approval and updates affected baselines and records.

A change-control log should include the change reference, description, initiator, reason, impact assessment, decision, approving authority, implementation date and status. Work should not proceed on a material change merely because participants assume that approval will follow, unless emergency procedures explicitly permit it.

7. Ethics and professional conduct

Construction decisions affect safety, public money, livelihoods and the environment. Ethical conduct therefore goes beyond obeying the contract. Fundamental principles include honesty, competence, impartiality, confidentiality, respect, sustainability and protection of public welfare.

Typical ethical risks include:

• undisclosed conflicts of interest;
• bribery, facilitation payments or gifts intended to influence decisions;
• collusive tendering or bid manipulation;
• falsification of test results, progress or labour records;
• concealment of defects or unsafe conditions;
• discrimination, harassment or exploitation of workers;
• misuse of confidential tender or personal information;
• pressure to certify incomplete or non-compliant work;
• deceptive claims for payment or extension of time.

A practical response is to disclose the issue, preserve evidence, consult the code of conduct or professional body, use the designated reporting channel and avoid retaliation against good-faith whistleblowers. Serious safety or corruption matters may require reporting to an external authority. Ethical reasoning should consider legality, professional duty, foreseeable harm, fairness and the integrity of the decision process.

8. Technology and contemporary practice

Common data environments, electronic approval workflows, building information modelling and mobile inspection systems can improve coordination and traceability. Digital tools are valuable when information standards, permissions, naming conventions and responsibility for data quality are defined. A model does not by itself establish legal design responsibility.

Artificial intelligence can assist with document classification, schedule-risk analysis, progress-image comparison and detection of inconsistent information. However, AI outputs require competent human review. Risks include biased data, fabricated text, insecure confidential information, unclear ownership of generated content and unjustified confidence in automated recommendations. The person approving a decision remains responsible for applying professional judgement and verifying the source evidence.

9. Illustrative case: the Riverside Community Health Centre

Background

The Riverside Community Health Centre was a medium-sized public project procured through design–bid–build. The client appointed an architect-led consultant team and a main contractor. The project included a busy public road, complex medical services and a fixed opening date.

Problem

During construction, the mechanical subcontractor discovered that a ceiling zone was too shallow for the specified ductwork. The site manager instructed the subcontractor verbally to reroute the ducts. The architect later issued a revised drawing, but the cost consultant did not receive the instruction. At the same time, the contractor’s weekly report stated that the design was fully coordinated.

A regulator then identified inadequate fire-stopping around service penetrations. The contractor argued that the consultant’s revised drawing caused the problem; the consultant argued that the contractor had changed the installation without approval. The client faced delay, additional cost and uncertainty about which information was current.

Analysis

The failure was organizational as well as technical. Responsibility for installation lay with the contractor, but authority for design change had not been clearly defined. The document register did not identify superseded drawings, and the reporting process encouraged optimistic progress statements. The parties also failed to escalate a design discrepancy before work proceeded.

Approach and solution

The client established a short-term governance review chaired by the project sponsor. The team:

1. stopped affected work and made the area safe;
2. identified all drawings, instructions, inspections and photographs;
3. appointed the relevant engineers to verify the fire-stopping and duct route;
4. recorded the non-conformance and assessed programme and cost effects;
5. issued one controlled revision through the document system;
6. required a signed change approval before further altered work;
7. introduced a design-query register with response deadlines;
8. required weekly reports to separate verified progress from forecast progress;
9. commissioned an independent inspection before concealment.

Outcome

The fire-stopping was corrected, the revised services route was approved and the opening date was protected through resequencing. The client accepted a documented cost adjustment based on the contract provisions. More importantly, the project adopted a single source of current design information and an escalation rule for unresolved technical queries.

Learning points

The case demonstrates that clear contracts cannot compensate for weak implementation. Verbal coordination is useful but must be recorded. A person may identify a problem without having authority to approve its solution. Accurate reporting, controlled information and early escalation protect all parties and reduce disputes.

10. Practical implementation checklist

At project start, the team should confirm:

• the project charter, scope and success criteria;
• the organization chart and named deputies;
• the responsibility matrix and delegation limits;
• contract interfaces and design responsibility;
• statutory approvals and inspection points;
• communication channels and meeting rules;
• document numbering, revision and access controls;
• risk, issue, change and decision registers;
• safety, quality and environmental responsibilities;
• ethical reporting and conflict-of-interest arrangements;
• stage-gate criteria and independent assurance requirements;
• handover, records and lessons-learned arrangements.

These controls should be reviewed when the project changes phase, a major participant changes, a serious incident occurs or the approved scope is altered.

Challenges and limitations

Organizational models are simplifications. Real projects contain informal influence, temporary alliances, cultural differences and changing legal or commercial conditions. A responsibility matrix can become obsolete if it is not updated. Excessive approval layers may slow urgent decisions, while inadequate control may permit unauthorized work. Independent assurance can be weakened if reviewers depend commercially on the team they are assessing. Digital systems improve traceability but can also multiply duplicate records or expose sensitive information.

Governance must therefore be proportionate. A small low-risk project does not require the same committee structure as a hospital or major bridge, but it still requires clear authority, safe work, legal compliance and reliable records. The objective is not bureaucracy; it is disciplined decision-making that protects people, value and public confidence.

Chapter Summary

Construction projects operate through a network of clients, consultants, contractors, subcontractors, suppliers, regulators and stakeholders. The client defines the need and provides strategic direction; consultants provide professional design and advice; contractors organize and execute construction; and regulators protect statutory and public interests. The precise allocation depends on the contract, procurement route and law.

Responsibility, authority, accountability and liability must be distinguished. RACI matrices, organization charts and delegation schedules help prevent gaps and conflicting instructions. Functional, projectized and matrix structures offer different balances of specialist efficiency, project focus and coordination. Procurement structures such as design–bid–build and design-and-build allocate interface and design risks differently.

Effective governance requires decision rights, stage gates, risk oversight, independent assurance, ethical conduct and escalation. Reporting and document control create the evidence needed for sound decisions, while change control prevents unauthorized scope, cost and quality consequences. Ethical practice protects safety, fairness, public funds and professional integrity. Technology and AI can improve coordination, but human accountability and verification remain essential.

Key Terms

Client: The person or organization that commissions, funds or owns the project.

Consultant: A professional adviser or design organization appointed to provide specialist services.

Contractor: The organization responsible for executing construction work under a contract.

Regulator: A public authority empowered to approve, inspect or enforce legal requirements.

Stakeholder: A person or organization that affects or is affected by the project.

Authority: Legitimate power to direct, approve or commit resources.

Responsibility: A duty to perform an assigned task.

Accountability: The obligation to explain performance and accept consequences.

Liability: Legal responsibility for loss, damage, injury or breach.

Delegation: Assignment of specified authority or work to another person.

RACI: A responsibility model using Responsible, Accountable, Consulted and Informed roles.

Governance: The system for directing, controlling and assuring a project.

Stage gate: A formal decision point between project phases.

Document control: Procedures for identifying, approving, distributing and retaining information.

Change control: The process for assessing and authorizing changes to approved baselines.

Design–bid–build: A procurement route with generally separate design and construction appointments.

Design-and-build: A procurement route in which the contractor has substantial design and construction responsibility.

Conflict of interest: A situation in which private interests could improperly influence professional judgement.

Assurance: An independent or structured review that provides confidence in controls and performance.

Non-conformance: Work or information that fails to meet a specified requirement.

Review Questions

Short Answer Questions

1. What is the difference between responsibility and accountability?
2. State four typical responsibilities of a construction client.
3. Why is document revision control important?
4. What are the four roles represented by RACI?
5. Identify two functions performed by construction regulators.

Long Answer Questions

1. Explain the roles of the client, consultant and contractor and discuss how their duties may change under design-and-build procurement.
2. Compare functional, projectized and matrix organizational structures, including one advantage and one limitation of each.
3. Describe the main components of an effective project governance framework.
4. Explain how reporting, document control and change control work together to reduce construction disputes.
5. Discuss ethical risks in construction and propose practical controls for preventing or reporting them.

Analytical / Application Questions

1. A site engineer discovers that an approved drawing conflicts with an existing underground service. Using authority, accountability, escalation and documentation principles, describe the steps that should follow before work continues.
2. A project manager has responsibility for schedule performance but cannot authorize additional labour or approve procurement changes. Analyse the organizational weakness and recommend a revised authority arrangement.
3. Using the Riverside Community Health Centre case, identify three governance failures and design a responsibility, reporting or document-control measure to prevent each recurrence.

Multiple Choice Questions with Answers

Question 1

Which participant normally has strategic accountability for defining the project need and securing project funding?

A. The client

B. The subcontractor

C. The regulator

D. The materials supplier

Correct Answer: A. The client

Question 2

In a RACI matrix, which role is responsible for accepting consequences and explaining the outcome of a decision?

A. Responsible

B. Accountable

C. Consulted

D. Informed

Correct Answer: B. Accountable

Question 3

What is a principal weakness of a matrix organization?

A. It eliminates specialist expertise

B. It prevents all project coordination

C. It may create conflicting instructions through dual reporting

D. It can be used only on small projects

Correct Answer: C. It may create conflicting instructions through dual reporting

Question 4

Which document-control feature most directly prevents people from using obsolete drawings?

A. A larger project office

B. A controlled revision and superseded-document process

C. More informal meetings

D. A longer construction programme

Correct Answer: B. A controlled revision and superseded-document process

Question 5

What is the main purpose of a stage gate?

A. To replace all regulatory inspections

B. To provide a formal decision on whether the project should proceed to the next phase

C. To transfer all contractor liability to the client

D. To eliminate the need for project records

Correct Answer: B. To provide a formal decision on whether the project should proceed to the next phase

Question 6

A contractor discovers a serious discrepancy between the design and site conditions. What is the most appropriate initial action?

A. Conceal the discrepancy and continue

B. Change the design without authorization

C. Record and escalate the discrepancy through the approved process

D. Wait until project completion to report it

Correct Answer: C. Record and escalate the discrepancy through the approved process

Question 7

Which procurement route generally gives the contractor substantial responsibility for both design and construction?

A. Design-and-build

B. Traditional design–bid–build

C. Direct material purchase

D. Regulatory inspection

Correct Answer: A. Design-and-build

Question 8

Which situation is an example of a conflict of interest?

A. A consultant reviews a drawing prepared by a colleague

B. A project manager records a site inspection

C. A tender evaluator owns shares in one of the bidding companies and does not disclose this

D. A contractor submits a test certificate

Correct Answer: C. A tender evaluator owns shares in one of the bidding companies and does not disclose this

Question 9

Why should a verbal site instruction normally be confirmed in writing?

A. To create a traceable record of the instruction and its effects

B. To remove the contractor’s duty to work safely

C. To avoid obtaining any approval

D. To make all instructions legally invalid

Correct Answer: A. To create a traceable record of the instruction and its effects

Question 10

Which statement about regulatory inspection is correct?

A. It guarantees that every construction activity is defect-free

B. It replaces the contractor’s safety management duties

C. It is one element of external oversight and does not eliminate project participants’ own duties

D. It transfers design responsibility to the regulator

Correct Answer: C. It is one element of external oversight and does not eliminate project participants’ own duties