PE Versus QP Liability in Construction Disputes

A retaining-wall movement, tunnel water ingress, or foundation settlement can move quickly from a technical incident to a board-level dispute. PE versus QP liability becomes central when parties must establish who made the critical professional judgment, who accepted responsibility for the design or works, and whether decisions were supported by an adequate process.

For developers, contractors, consultants, investors, and directors, the issue is not merely one of professional titles. It affects insurance recovery, contractual allocation of risk, regulatory exposure, project financing, and the credibility of evidence in arbitration or court proceedings. The analysis is especially consequential in geotechnical and underground works, where uncertain ground conditions and fast-moving site decisions can expose weaknesses in governance as well as engineering.

PE versus QP liability: the distinction that changes the case

The precise legal meaning of Professional Engineer (PE) and Qualified Person (QP) is jurisdiction-specific. In Singapore, for example, a QP role can carry statutory responsibilities connected with submissions, supervision, and regulatory compliance, while a PE is a licensed professional whose scope of practice and duties arise under the applicable professional registration framework. Other markets use different statutory definitions, licensing rules, and terminology.

The practical point is that the titles may overlap, but they should not be treated as interchangeable. A PE may have designed, reviewed, endorsed, or supervised a technical component. A QP may have undertaken distinct responsibilities in relation to submissions, site supervision, certification, or compliance. Liability turns on the governing statute, the appointment, the actual work performed, delegated functions, and the representations made to the authority and project parties.

A dispute should therefore begin with a role map, not a conclusion. Identify the legal entity and individual engaged, the scope of services, the person who held the relevant appointment, the limits of authority, and the decisions reserved to the client, contractor, or specialist designer. In complex projects, responsibility is often fragmented. A structural engineer, geotechnical engineer, temporary-works designer, and site supervisor may each have material but different duties.

Duty is defined by more than the contract

Consultancy agreements are a starting point. They may define deliverables, inspection frequencies, exclusions, reliance on third-party data, and caps on liability. Yet contracts do not necessarily displace professional, statutory, or tortious duties. A broad disclaimer will not reliably protect a professional who signs off on work without a reasonable technical basis, ignores material warning signs, or acts outside an agreed or authorized scope.

Conversely, an adverse outcome does not by itself establish negligence. Underground construction and geotechnical design involve inherent uncertainty. Borehole data samples limited locations; groundwater conditions can change; adjacent structures may respond unpredictably. The central question is usually whether the professional exercised the standard of reasonable skill, care, and diligence expected in the circumstances, rather than whether the project encountered difficulty.

That inquiry is intensely factual. Did the design account for available site investigation data? Was there a reasoned basis for assumptions? Were instrumentation thresholds appropriate? Did monitoring results trigger escalation? Was the response to observed movement proportionate? The contemporaneous record often answers these questions more persuasively than recollection offered years later.

Delegation does not end accountability

Major projects depend on delegation. A QP or lead PE cannot personally perform every calculation, inspection, and site review. Proper delegation to competent staff and specialist consultants is commercially necessary. The risk arises when delegation is undocumented, poorly supervised, or used as a substitute for professional judgment.

An effective delegation framework identifies the task, the responsible individual, required competence, review points, and escalation thresholds. It also records what the appointing professional actually reviewed before approving a submission, certificate, or design change. A signature should represent an informed act, not an administrative formality.

This applies equally to corporate governance. A board should not assume that an external appointment transfers all project risk away from the company. Directors must ensure that management has appointed capable professionals, funded appropriate investigations and monitoring, and maintained an escalation route for material safety, cost, schedule, and regulatory issues. Inadequate resourcing can become a governance issue when a project team is pressured to proceed despite unresolved technical risk.

The moments when liability usually crystallizes

In contentious matters, the disputed act is rarely the original design alone. Liability often crystallizes at a decision point after new information became available: a revised excavation sequence, an unexpected groundwater condition, a monitoring alarm, a request to depart from the approved method, or a decision to continue works pending further assessment.

At those points, parties should distinguish between a design change, a construction method issue, and an operational response. A contractor may be responsible for execution and temporary works, while the design professional remains responsible for the adequacy of a design within the retained scope. But the line can blur if the professional directs the means and methods of construction or if the contractor proceeds with a variation that changes the engineering basis.

Causation introduces another layer of complexity. A claimant must generally show more than a breach of duty. It must connect the alleged failure to the loss claimed. Where settlement results from a combination of incomplete ground investigation, contractor sequencing, delayed monitoring data, and a developer-approved value-engineering decision, a tribunal may need to apportion responsibility among several parties. This is why technical analysis must be integrated with contract review, chronology, and damages assessment.

Records are a dispute-control system

Good recordkeeping is not defensive bureaucracy. It is part of competent project delivery. In a later dispute, the most persuasive documents are usually those created before claims positions hardened.

For high-risk engineering work, the project file should preserve the basis for key assumptions, design calculations and revisions, site investigation data, inspection records, instrumentation readings, photographs, meeting minutes, instructions, nonconformance reports, and correspondence on deviations or risk acceptance. It should also show when information was received, who reviewed it, what decision was made, and why.

Four records deserve particular discipline:

• A decision log for material technical and commercial choices, including alternatives considered and the person authorized to decide.

• A change-control register linking every significant design or method revision to supporting analysis, approvals, and any regulatory submission requirement.

• An escalation log recording threshold breaches, safety concerns, authority notifications, and the closure of corrective actions.

• A document-retention protocol that preserves original versions, metadata, and controlled access once a dispute, incident, or investigation is reasonably anticipated.

Informal messaging is a recurring weakness. Project decisions made through chat applications or personal email accounts can be incomplete, difficult to retrieve, and vulnerable to competing interpretations. The answer is not to eliminate rapid communication during an incident. It is to formalize material decisions promptly in the controlled project record.

Expert evidence must explain decisions, not merely criticize outcomes

PE versus QP liability disputes frequently require expert evidence. However, a useful expert report does more than identify a technical imperfection with hindsight. It reconstructs the information reasonably available at the time, tests the decision against applicable professional standards, considers alternative causal explanations, and separates fact from opinion.

For boards and counsel, independence is as important as technical credentials. The expert should be given a clear mandate, complete source material, and freedom to reach an opinion that may not align perfectly with the commissioning party's preferred narrative. Selective disclosure can impair both the analysis and the credibility of the eventual evidence.

A disciplined early review can also protect commercial value. Before parties commit to a prolonged arbitration or litigation process, they should quantify likely remediation costs, delay exposure, insurance implications, counterparty recoverability, and reputational consequences. A technically strong claim may still warrant a negotiated resolution where evidence is incomplete, causation is shared, or the project requires ongoing cooperation.

A board-level response after an incident

Once a significant incident occurs, management should separate immediate safety and stabilization work from the investigation of responsibility. Both are necessary, but combining them without controls can compromise evidence or create unhelpful communications. The board should establish clear reporting lines, preserve relevant documents, appoint appropriately independent technical and legal advisers, and ensure that external statements are accurate and authorized.

The investigation should be structured around a chronology: what was known, by whom, when, what was decided, and whether the decision was within the responsible party's scope and standard of care. It should also test corporate decisions that may have influenced technical outcomes, including budget constraints, scope reductions, or pressure to accelerate works.

For organizations operating across Singapore, Malaysia, Hong Kong, and other regional markets, this approach must be adjusted for the governing professional and construction regime. The terminology may be similar, but the regulatory consequences, limitation periods, contractual norms, and available remedies may not be.

The most defensible position is built long before a claim letter arrives: defined appointments, competent delegation, timely escalation, and records that show not only what the team decided, but the disciplined reasoning behind it.