Loading field map
Every building, bridge, or tunnel is the product of a relationship among three parties: the owner who wants it, the designer who plans it, and the builder who assembles it. How those three parties are organized—who holds the contracts, when they enter the project, how risk is shared—determines not only the speed and cost of construction but also the quality of the final structure. Construction management is the subfield of civil engineering that studies and designs these delivery frameworks. Over the past century, five major frameworks have emerged, each responding to the limitations of its predecessors while carving out a distinct role in the contemporary landscape.
For most of the twentieth century, the dominant framework was Traditional Design-Bid-Build (DBB). In this model, the owner first hires a designer to produce complete construction documents. Only after the design is finished does the owner solicit bids from contractors, awarding the work to the lowest responsive bidder. The builder then constructs what the designer specified, with little formal input during the design phase.
DBB was a deliberate departure from the earlier master-builder tradition, in which a single craftsperson both designed and built. The separation of design and construction brought clear accountability: the designer was responsible for the drawings, and the contractor for executing them. For public agencies bound by procurement laws that demanded transparent, competitive bidding, DBB became the default. Its strength is a well-defined chain of responsibility and a clear baseline cost established through competition.
Yet the sequential handoff also created friction. Designers had little incentive to consider how their choices affected construction methods or schedules. Contractors, bound by a fixed price, often found themselves trying to build something that could have been designed more economically or practically. Change orders, disputes, and adversarial relationships became common. The very separation that ensured transparency also discouraged the early collaboration that could prevent problems.
By the mid-twentieth century, owners of large or complex projects began looking for a middle ground. Construction Management at Risk (CMAR), which emerged around 1950, inserts a construction manager into the project during the design phase. The CM acts as a consultant to the owner and designer, offering advice on constructability, cost estimating, and scheduling. Once the design is sufficiently advanced, the CM commits to a Guaranteed Maximum Price (GMP) and becomes the general contractor responsible for construction.
CMAR preserves the designer's independent role—the owner still contracts separately with the architect or engineer—but brings construction expertise into the design process. The CM's early involvement can reduce costly redesigns and help the team stay within budget. Compared with DBB, CMAR trades some of the simplicity of sequential bidding for the flexibility of phased input. The framework remains popular for institutional projects such as hospitals and university buildings, where the owner values both the designer's independence and the builder's practical guidance.
A more radical integration arrived with Design-Build (DB), which gained traction in the 1980s. In DB, the owner signs a single contract with a design-build entity that provides both design and construction services. That entity may be a firm that employs both architects and builders, a joint venture, or a contractor that subcontracts the design work. The key point is single-point accountability: the owner has one counterparty responsible for both the design and the finished building.
Where CMAR keeps the designer and builder in separate contracts, DB merges them into one team from the start. This structure can accelerate delivery because design and construction can overlap—a practice known as fast-tracking. Proponents argue that DB reduces adversarial friction because disputes between designer and builder become internal problems rather than legal battles. Critics worry that the owner loses control over design quality, since the designer now works for the builder rather than directly for the owner. DB has become especially common in the private sector and for projects where speed is a priority, such as industrial facilities and large housing developments.
By the 1990s, some researchers and practitioners argued that changing the contract structure alone was not enough. The real problem, they claimed, lay in how construction work was planned and executed on site. Inspired by the Toyota Production System, Lean Construction reframed construction as a flow of materials, information, and labor rather than a series of discrete transactions. Its central method, the Last Planner System, shifts planning authority to the crews who will do the work, using weekly work plans and a metric called Percent Plan Complete to reduce variability and improve reliability.
Lean Construction is not a delivery contract; it is a production philosophy that can operate within DBB, CMAR, or DB. Its distinctive commitment is to maximizing value while minimizing waste—waste being anything that does not directly contribute to the project's goals. Where earlier frameworks focused on who holds the contract, Lean focuses on how work is coordinated. It asks teams to stabilize their workflow, pull resources only when needed, and continuously improve their processes. The framework has been adopted by many large contractors and has influenced the development of building information modeling (BIM) tools that support more reliable planning.
The most recent framework, Integrated Project Delivery (IPD), emerged around 2000 and attempts to formalize the collaborative spirit of Lean into a legally binding structure. IPD uses a multi-party contract signed by the owner, designer, and builder (and often key subcontractors) that aligns their financial incentives. Instead of each party protecting its own profit, the contract creates a shared risk pool: if the project comes in under budget, the team shares the savings; if it goes over, they share the losses.
IPD goes beyond Design-Build's single-point accountability by making all major parties joint decision-makers. It goes beyond CMAR's early involvement by embedding the builder and key trades in the design process from the very first conceptual sketches. And it goes beyond Lean's philosophical guidance by providing a contractual mechanism that rewards collaboration. IPD is still relatively rare, used mostly on complex healthcare, research, and institutional projects where the potential savings from reduced disputes and faster delivery justify the effort of negotiating a multi-party agreement.
None of these five frameworks has displaced the others. Traditional Design-Bid-Build remains the standard for public projects where procurement laws require competitive bidding. Construction Management at Risk is a common choice for owners who want early builder input without surrendering the designer's independence. Design-Build dominates the private sector and is increasingly permitted for public infrastructure. Lean Construction has become a widely taught methodology that improves performance within any delivery model. Integrated Project Delivery, though still niche, represents the frontier of contractual integration.
What the leading frameworks agree on is that early collaboration among designers, builders, and owners improves project outcomes. The disagreement is about the primary lever for achieving that collaboration. Proponents of Lean argue that the key is changing how work is planned and measured on site; proponents of IPD argue that the key is aligning financial incentives through contract structure. Design-Build advocates point to single-point accountability as the simplest path to integration, while CMAR supporters value the checks and balances of separate contracts. The field today is a landscape of pluralism, where owners choose among frameworks based on project complexity, regulatory constraints, and their own tolerance for risk.
Digital tools have accelerated this pluralism. Building information modeling (BIM) enables teams to simulate construction sequences, detect clashes, and estimate quantities before breaking ground—capabilities that make early collaboration more valuable regardless of the delivery framework. As BIM and other technologies mature, the boundaries between frameworks may blur further, but the central question of construction management remains: how best to organize the relationship among those who design, those who build, and those who pay.