16/04/2026
๐๐๐ฆ๐๐๐ก-๐๐จ๐๐๐ ๐๐ข๐๐ฆ ๐ก๐ข๐ง ๐ฅ๐๐ค๐จ๐๐ฅ๐ ๐ฌ๐ข๐จ ๐ง๐ข ๐๐๐๐ข๐ ๐ ๐ ๐๐ข๐ก๐ง๐ฅ๐๐๐ง๐ข๐ฅ
๐๐ก๐ ๐๐ข๐๐ฆ ๐ก๐ข๐ง ๐ฅ๐๐ค๐จ๐๐ฅ๐ ๐ ๐๐ข๐ก๐ง๐ฅ๐๐๐ง๐ข๐ฅโ๐ฆ ๐๐๐๐๐ก๐ฆ๐โ๐๐ ๐ฆ๐ง๐ฅ๐จ๐๐ง๐จ๐ฅ๐๐ ๐ฃ๐ฅ๐ข๐ฃ๐๐ฅ๐๐ฌ
Now, when we talk about Design-Build, most architects immediately interpret it as a shift into contracting. The assumption is that once you take on both design and construction, you must also take on pricing, delivery obligations, and commercial risk. That is the common industry mindsetโand that is precisely where the problem begins.
The issue here is not participation in construction. Under Republic Act No. 9266, the Architect is already authorized not only to design, but to plan, coordinate, and administer the implementation of construction works. That authority is part of the practice. It is not an extension of it.
So the question now is: where does the line get crossed?
Thatโs where Republic Act No. 4566 becomes relevant. Section 14 makes it clear that licensed professionals are not required to obtain a contractorโs license when acting solely in their professional capacity. In other words, the law already anticipates that architects will be involved in constructionโbut it draws a boundary around the nature of that involvement.
In practice, what happens is this: many architects structure Design-Build engagements as if they were contractors. They package the entire project into a lump sum price, embed margins into construction costs, and assume responsibility for delivering the project within that price. At that point, they are no longer operating as professionals managing a projectโthey are operating as commercial entities undertaking construction.
You might think that this is simply a more efficient way to deliver projects, but the reality is that it changes the entire risk profile. The moment you assume a lump sum obligation, you are no longer just managing design integrity or coordinating ex*****on. You are now exposed to cost overruns, procurement risks, labor inefficiencies, and cash flow pressures. That is not technical riskโthat is ๐ฐ๐ผ๐บ๐บ๐ฒ๐ฟ๐ฐ๐ถ๐ฎ๐น ๐ฐ๐ผ๐ป๐๐๐ฟ๐๐ฐ๐๐ถ๐ผ๐ป ๐ฟ๐ถ๐๐ธ.
And thatโs where the issue comes in.
๐๐ฒ๐๐ถ๐ด๐ป-๐๐๐ถ๐น๐ฑ ๐บ๐ฎ๐ ๐ฐ๐ผ๐ป๐๐ผ๐น๐ถ๐ฑ๐ฎ๐๐ฒ ๐น๐ถ๐ฎ๐ฏ๐ถ๐น๐ถ๐๐ ๐ณ๐ผ๐ฟ ๐ผ๐๐๐ฐ๐ผ๐บ๐ฒ, ๐ฏ๐๐ ๐ถ๐ ๐ฑ๐ผ๐ฒ๐ ๐ป๐ผ๐ ๐ฐ๐ผ๐น๐น๐ฎ๐ฝ๐๐ฒ ๐๐ต๐ฒ ๐ป๐ฎ๐๐๐ฟ๐ฒ ๐ผ๐ณ ๐ฟ๐ถ๐๐ธ. Technical and management responsibility remains within the professional domain. Commercial risk, on the other hand, belongs to the contractor as a regulated business entity. These are two different things, governed by two different frameworks.
Letโs take a simple example. An architect leads a project under a Design-Build arrangement but structures it so that the Owner directly carries construction costs, while the architect administers procurement, coordinates trades, and controls ex*****on. The architect is fully engaged in delivery, fully responsible for technical outcomes, and actively managing the projectโbut is not guaranteeing the project for a fixed price. In that scenario, the architect remains within professional practice. No contractorโs license is required, because no contracting activity, in the commercial sense, is being undertaken.
Compare that to a setup where the architect quotes a fixed project cost, absorbs cost fluctuations, and delivers the entire project as a priced package. The role has now shifted. Regardless of title, the function is that of a contractor.
At the end of the day, Design-Build is not defined by who signs the contract. It is defined by how the work is structured, how risk is allocated, and how compensation is derived.
The problem is not Design-Build itself.
The problem is how it is being practiced.
When properly structured, Design-Build allows the architect to lead, control, and deliver projects as a professional fiduciaryโwithout stepping outside the bounds of practice, and without assuming risks that belong to a different domain.
And that is the distinction most people are missing.