Monday, January 13, 2020

Architects and Civil Engineers: Clarifying Professional Roles Without Turning Collaboration Into Conflict

Why do disputes between architects and civil engineers become so heated? Part of the answer is practical. Both professions contribute to buildings, and clients often encounter them at the same table. Confusion begins when collaboration is mistaken for interchangeability.

A building is one project, but it contains several bodies of professional responsibility. Architectural planning, spatial organization, building character, environmental response, structural systems, utilities, construction methods, and regulatory compliance must be coordinated. Coordination does not erase the legal scope or accountability of each professional.

Start with the law, not professional folklore

Republic Act No. 9266 defines architecture and the scope of architectural practice. It also addresses the preparation, authorship, signing, and sealing of architectural documents. Civil engineers, for their part, have an established and indispensable role in structural and civil engineering work under their governing law and applicable regulations.

The public controversy over Section 302 of the 2004 Revised Implementing Rules of the National Building Code reached the Supreme Court. In its 15 March 2023 decision in G.R. Nos. 200015 and 205846, the Court granted the consolidated petitions, reversed the Court of Appeals, reinstated the trial court ruling that upheld the relevant provisions, and identified architectural documents that only registered and licensed architects may prepare, sign, and seal.

That holding deserves accurate reporting. It should not be inflated into a claim that architects can perform every engineering service, nor should it be minimized into a matter of professional pride. The point is responsibility. A signature and seal identify the professional who prepared or directly supervised the work and who accepts accountability within the applicable scope.


Professional boundaries serve the public

Licensure boundaries can sound territorial when explained badly. Their proper purpose is not to protect egos. They help the client, contractor, building official, court, and public determine who was competent and responsible for a particular decision.

An architectural floor plan, a structural analysis, an electrical design, and a plumbing design may appear in one permit set, but they are not the same professional instrument. The sheets must agree with one another, yet agreement does not mean that any one signatory may absorb every discipline.

This is why competent teams coordinate. The architect should understand enough about structure and building systems to organize the whole, detect conflicts, and communicate design intent. Engineers should understand the architectural requirements that their systems must support. Each professional should resist signing work that was not actually prepared under the required responsibility and supervision.

What should clients and students learn from the dispute?

First, ask who is the architect-of-record and who are the engineers of record. Second, check that the written appointments and drawings identify their respective services. Third, do not treat the permit set as a collection of signatures acquired after the design is finished. Genuine coordination should happen while the design is developing.

Students should also learn a harder lesson. Professional advocacy loses force when it becomes contempt for another profession. If architects want the public to respect architectural responsibility, we must explain it with evidence, do our own work well, and collaborate without surrendering our lawful duties.

The public does not need another turf war. It needs buildings whose decisions can be traced to qualified people working within clear scopes. That is a stronger basis for professional respect than rivalry will ever be.

Read other articles:

No comments:

Post a Comment