Once a project moves from completed drawings into construction, the design professional’s risk profile changes. The questions are no longer limited to whether the drawings and specifications satisfy the professional standard of care. The architect or engineer is now interacting with a contractor that is pricing changes, sequencing work, submitting shop drawings and product submittals, requesting clarifications or additional information, seeking payment, and building the project in real time. Decisions that may seem routine during construction administration can later become the central exhibits in a professional liability claim.
For design professionals practicing in the traditional design-bid-build model, three issues deserve particular attention because they repeatedly generate claims and misunderstandings: change orders or RFI procedures that are later characterized as errors and omissions; site observations that are later characterized as inspections or supervision or tacit acceptance of later discovered defective work; and pay-application certifications that are later treated as guarantees of the contractor’s work or finances. Each is manageable, but only if the design professional understands the limits of its role and develops disciplined project practices that reinforce those limits.
The practical theme running through all three areas is the same: define the role in the contract, perform consistently with that role, and create a contemporaneous project record that accurately describes what happened. A well-drafted agreement is important, but it will not help much if the project team uses different language, assumes broader responsibilities in practice, or fails to document why a decision was made.
A Change Order Is Not Automatically an E&O
Construction projects change. A change order may result from an owner decision, an unforeseen condition, a contractor request, a substitution, a code comment, a coordination issue, or an actual design error. The mere existence of a change order does not establish professional negligence. Yet on a troubled project, the change-order log may quickly convert into a de facto cost recovery effort against the design team if every modification is casually labeled a “design change” or “design error.”
When an alleged design issue does arise, three questions should remain separate. First, did the design professional depart from the applicable standard of care? Second, did that departure actually cause additional cost? Third, what portion of the claimed cost would the owner have incurred even if the documents had been perfect from the start? Those questions are related, but they are not the same.
Consider an omitted piece of equipment that costs $200,000 but was always necessary for the completed facility. If it had been shown on the bid documents, the owner likely would have paid for it as part of the original contract price. The potentially recoverable loss may therefore lie in the incremental consequences of the omission, premium pricing, demolition, rework, acceleration or delay, rather than automatically in the full value of the equipment. This is the practical importance of separating the cost of obtaining what the owner always needed from the additional cost actually caused by the alleged error. Commonly, this concept is referred to as “betterment,” and should not be considered a “damage.”
The same discipline should be applied to the change log. Owner-directed scope changes, unforeseen conditions, contractor substitutions, code-driven changes, coordination clarifications, and potential design corrections should be coded separately. If the contractor submits a proposal that attributes a cost to design, the design professional should not simply accept the label. Ask what changed, why it changed, whether the work was always required, whether the contractor has included betterment, whether there is rework, and whether schedule or sequencing decisions contributed to the amount.
A useful practice is to maintain a short contemporaneous change narrative for significant items. Identify the source of the change, the design documents involved, the reason for the revision, whether the owner would have incurred some or all of the base cost in any event, and any disputed contractor cost components. That narrative is far easier to prepare while the issue is fresh than several years later during litigation.
Design professionals should also be cautious about casually admitting fault in project communications. There is a significant difference between saying, “we need to revise this detail” and saying, “this was our error, and we will pay for it.” The first addresses the project problem; the second may make an unnecessary legal conclusion before causation and damages have been evaluated, and may jeopardize insurance coverage later. Project communications should be candid and solution-oriented, but precise.
Requests for Information (“RFIs”) are another construction-administration tool that can become a source of professional-liability exposure if they are not carefully managed. In principle, the RFI process is intended to obtain clarification where the contract documents are genuinely unclear, incomplete, or require interpretation. In practice, however, some contractors use RFIs more aggressively, submitting large numbers of questions, including questions whose answers already appear in the drawings or specifications, and then using the volume of RFIs as evidence that the design documents were defective or incomplete. That can create a misleading project record if every RFI is casually treated as a “design issue.”
Design professionals should resist that characterization and distinguish among true requests for clarification, contractor coordination questions, means-and-methods issues, substitution requests, field-condition questions, and actual design changes. Where the answer is already in the contract documents, the response should say so clearly and identify the applicable detail, note, specification section, or drawing reference. It is also helpful to track RFIs by category and cause, because a raw RFI count says very little about design quality. Just as importantly, the design professional should avoid allowing the RFI process to become an informal vehicle for redesign: if a response materially changes scope, cost, performance, or design intent, it should be routed through the project’s formal change process rather than buried in an RFI response. A disciplined RFI log and precise response language can prevent an ordinary project-management tool from becoming a manufactured record of alleged design deficiency.
Construction Administration: Observation Is Not Inspection
The construction phase is where contractual boundaries are most frequently tested. Periodic site observation is not the same as continuous inspection or supervision of construction. The architect may visit the site to become generally familiar with progress and quality of the work and to identify observed departures from the contract documents. That does not ordinarily make the architect responsible for the contractor’s workforce, sequencing, temporary works, construction means and methods, or site safety. Of course, all of this falls back to the language in the contract and what the responsibility will really be when the design professional is on site.
And while the distinction sounds straightforward in a contract, it can erode through everyday conduct. A project architect who begins directing trades, instructing the superintendent how to sequence work, approving temporary means and methods, or repeatedly resolving safety issues may create a factual record very different from the written agreement. The loss-prevention goal is not to disengage from the project; it is to remain engaged in the professional role the firm actually agreed to perform.
Terminology matters. If the contract calls for periodic observations, field reports should not casually state that the architect “inspected all work” or “verified compliance” unless that is truly the service being performed. Likewise, phrases such as “approved installation” or “everything appears correct” can be problematic when the professional observed only a limited portion of the work during a periodic visit.
A good field report should identify the date, persons present, general areas observed, material conditions noted, items requiring follow-up, and any limitations that matter. Photographs can be valuable, but they should be organized and retained with enough context to explain what they show. If a significant nonconforming condition is observed, it should be documented and communicated through the contractual process and chain of communication rather than left to an informal conversation in the field. The designer should bring any issues needing attention to the appropriate contractor personnel to resolve, as opposed to directing the resolution themselves.
At the same time, limited scope is not a license for willful blindness. If a design professional observes an obvious material nonconformity within the course of contracted services, it should be addressed appropriately. The point is to distinguish a reasonable professional response to what is actually observed from a guarantee that every defect will be discovered.
One particularly useful discipline is to distinguish design intent from contractor means and methods in conversations. The design professional can explain what result the documents require. The contractor should ordinarily determine how to achieve that result. When the line begins to blur, stop and clarify the respective roles before the project record suggests the design professional assumed responsibility for construction operations.
Pay Applications Require Similar Discipline
Payment certification is another area where an architect’s signature can later be made to mean more than it did at the time. The architect is typically making a professional judgment based on observations, the contractor’s application, and information reasonably available. That is not the same as conducting a financial audit, verifying every installed quantity, guaranteeing payment to subcontractors, or certifying that the work was done completely in accordance with the plans and specifications and no defective work exists anywhere on the project.
The risk is amplified because the certification directly affects money. Owners, lenders, and the contractor’s surety may view the architect’s signature as assurance that the percentage complete is exact, stored materials exist and are properly protected, all prior payments reached subcontractors, and the remaining contract balance is sufficient to finish the project. Unless the architect has expressly undertaken those responsibilities, the certification should not be allowed to imply them.
Stored materials deserve particular attention. If payment is requested for materials not yet incorporated into the work, understand what the contract requires concerning location, ownership, insurance, segregation, documentation, and protection. The architect should not make factual representations about off-site materials it has not seen unless the certification expressly permits reliance on documentation furnished by others.
Front-loading is another recurring problem. A schedule of values that allocates excessive value to early activities can make later payment applications appear mathematically supportable while leaving insufficient value in unfinished work. Contractors will always hope to “get ahead on the money,” and this is a common technique to do so. Reviewing the schedule of values at the beginning of construction is therefore a meaningful risk-management step, not merely an accounting exercise.
The architect should also document disputed quantities, incomplete work, observed deficiencies, and the reasons for reducing or withholding certification. If the contractor disagrees, the record should explain the professional judgment at the time rather than forcing everyone to reconstruct it later.
Special owner or lender forms require separate scrutiny. A broad certification prepared by a lender may contain statements about project cost, contractor payment, lien status, code compliance, or completion that go well beyond the architect’s contractual services and serve to enhance their standard of care. The fact that a form is described as “standard” does not mean it is appropriate for the design professional to sign.
The Common Thread: Match the Contract, the Conduct and the Record
Change orders, site observations and pay applications look like different construction-phase tasks, but the loss-prevention principles are remarkably consistent. First, know exactly what the contract requires. Second, perform the service in a manner consistent with that allocation of responsibility. Third, use project language that accurately describes what the professional did and did not do. Finally, create enough contemporaneous documentation that a later reviewer does not have to guess why a decision was made.
The design professional’s objective should not be to avoid involvement in the work of constructing the project. Thoughtful construction administration adds enormous value to a project and frequently prevents small issues from becoming large ones. The goal is instead to remain actively involved without unintentionally becoming the guarantor of contractor performance, construction cost, or every condition in the field.
Claims are often shaped less by one dramatic mistake than by dozens of ordinary project communications that slowly redefine the parties’ roles. A disciplined approach to these three recurring issues, change management, site observation, and payment certification, can keep those roles clear and give the project team a much better chance of solving problems before they become professional liability claims.