Engineering, Architecture and Construction Consulting

01Purpose and scope

• This manual supports the course Engineering, Architecture and Construction Consulting. It describes how consultants who advise owners, developers, public agencies and contractors actually work on projects from early feasibility through construction closeout. It is written as a working reference, so it focuses on the activities, decisions, deliverables and records that appear on real assignments rather than on theory.
• Consulting in this field covers a wide range of roles. A consultant may act as an independent reviewer of designs produced by another firm, a technical adviser on a single discipline such as structural, mechanical or geotechnical work, a cost or schedule analyst, a commissioning lead, or an owner's representative who watches over the whole delivery effort on the client's behalf. The same person may hold several of these roles on one job, and the contract language defines which role carries which liability.
• The manual covers the common activities that most of these roles share: defining the question to be answered, gathering information, reviewing work, reporting findings, tracking risk, and handing over a usable record. It does not replace the contract, the professional license held by the individuals involved, or the instructions of the engineer or architect of record. Where a statement depends on local law or on the licensing rules of a particular state or province, check the current requirements with the licensing board or the authority having jurisdiction.

02Core principles

• The first principle is that a consultant answers the question the client actually needs answered, and writes that question down before doing any work. A request to review drawings may really be a request to find out whether a building can be occupied by a certain date, or whether a foundation change will trigger a permit resubmittal. Confirming the question at the start prevents a large volume of review comments that nobody can act on.
• The second principle is independence in judgment combined with respect for the design authority. A consultant who finds a problem reports it with the evidence, the affected sheet or specification section, the consequence if nothing changes, and a suggested path to resolution. The consultant does not quietly redesign the work, and does not stay silent because the design team is under pressure.
• The third principle is traceability. Every recommendation should be linked to a document, a measurement, a site observation or a calculation that a second person can check. Opinions without a trail are hard to defend later, and they are the most common source of disputes about who knew what and when.
• The fourth principle is proportion. A cladding review on a four-story office building calls for a different depth than the same review on a hospital or a high-rise residential tower. Consultants who apply the same level of scrutiny to every job either run out of budget or miss the risks that matter most.

03Planning and preparation

• Before accepting an assignment, confirm the scope in writing. Identify the client, the contracting parties, the phase of the project, the deliverables expected, the review standards to be applied, and the decision-makers who will receive the findings. Note any exclusions, such as means and methods of construction, which usually belong to the contractor, or code compliance determinations, which belong to the authority having jurisdiction.
• Gather the baseline documents early. For design reviews this means the current drawing set with revision history, the project manual or specifications, the basis of design, prior review comments and responses, and the applicable codes and amendments adopted for the location. For construction phase work it means the approved submittals log, the request for information log, the schedule baseline, the change order register and the most recent progress photographs or site reports.
• Set up the tools and records before the work begins. Most consultants use a document management platform or project portal, a comment tracking log that records each finding with a unique number, status, responsible party and closure evidence, and a shared calendar for review cycles. If the project uses building information modeling, agree on the model coordination protocol, the level of development expected for each element, and who owns the federated model. The ISO 19650 series is a widely used reference for information management in building projects, and many public clients and large private owners require alignment with it, although the exact requirements are set by the contract.
• Agree on review turnaround times and the decision path for disputes. A review that takes three weeks in a fast-track project can be as damaging as a review that misses an error. Write the response time for each review cycle into the consulting agreement, and define who has authority to accept, reject or defer a comment.

04Recommended workflow

1. 1
   : Confirm the question, deliverables and boundaries with the client and the design or construction team in a short kickoff meeting, then record the agreed list in the project file. Ask each party to name its decision-maker for the review.
2. 2
   : Build a review or observation plan that maps each scope item to a method. For a structural drawing review, the method may be a check of load paths, connection details and a sample of calculations. For a construction observation, it may be a walk of the site on a set frequency, plus review of test reports for concrete, soils and welds.
3. 3
   : Collect and organize the source documents, then confirm that you have the current revision. A large share of wasted effort in consulting comes from reviewing a superseded sheet or a specification addendum that was issued after the review started.
4. 4
   : Perform the review or observation against the stated criteria. Record each observation with its location, the reference document, the evidence, and a severity rating agreed in advance, such as critical, major or minor. Separate facts from opinions in the write-up.
5. 5
   : Issue the findings in a structured report or comment log. Group comments by discipline or by work package, and state what action is requested and by when. Where a finding depends on an assumption, say what the assumption is and how it could be verified.
6. 6
   : Track responses, verify closure on site or in the revised documents, and update the log. Do not close a comment because a response says it has been addressed. Close it only after you have seen the revised drawing, the installed condition, or the test result that proves the correction.
7. 7
   : At the end of the phase or project, prepare a closeout summary of open items, lessons learned, and the records that should transfer to the owner. Archive the final versions of reports and the complete comment history together.

05Quality checks, risk controls and compliance

• Quality checks in consulting work come in two forms. The first is a review of the consultant's own output. Before a report leaves the office, a second qualified person should check the calculations, cross-reference the cited sheets and specification sections, confirm the revision numbers, and read the findings for tone and clarity. A simple peer review sign-off on the cover sheet makes this step visible.
• The second form is verification of the work being reviewed. Site observations should be recorded with photographs that show the location, the date and time stamp, and a reference point. Test results should be compared against the specified acceptance criteria rather than against the previous test. Samples should be representative, and the sampling method should be stated.
• Risk controls focus on the places where errors are most costly. Common high-risk items include temporary works, excavation support, fire and life safety systems, structural connections in seismic or wind-prone regions, building envelope transitions, and any change that affects the permit or the certificate of occupancy. Maintain a risk register for the project, assign each item an owner, and review it at each progress meeting.
• Compliance depends on jurisdiction. Building codes, energy codes, accessibility requirements, environmental permits and licensing rules differ by country, state, province and sometimes by city. Name the code edition and any local amendments in the review basis, and confirm the current version with the authority having jurisdiction before relying on it. Standards such as those published by ASCE, ACI, AISC or ASHRAE are often referenced in contracts, but the edition and the scope of adoption must be confirmed for the specific project.
• This guidance does not replace qualified professional judgment, approved procedures or required authorization. Structural, geotechnical, fire protection, medical facility and similar work requires review by appropriately licensed professionals, and the consultant's role must be defined so that responsibility for final design decisions is clear.

06Collaboration and documentation

• Consulting succeeds or fails on the quality of working relationships. The consultant usually has no authority over the design team or the contractor, so influence comes from clear communication, timely information and fair treatment of comments. Meet regularly with the design lead, the contractor's project manager and the owner's representative. Keep the agenda short and send minutes within a day or two.
• Documentation serves three purposes: it guides the current work, it protects the parties if a dispute arises, and it supports the owner after handover. Each comment, observation and decision should be written in plain language. Avoid words like obviously or clearly, since readers who disagree will focus on those words instead of the substance. Use the project's naming conventions for files and numbering for comments.
• Specify the format for deliverables in the consulting agreement. Common formats include PDF reports with bookmarks, native spreadsheets for logs, and marked-up drawing sets that reference the comment number at each location. Where building information modeling is used, deliver issue-ready model extracts with the coordination issues listed separately.
• Be careful about what the consultant writes into the official record. Informal messages, text threads and personal notes can become discoverable in a dispute. Route formal findings through the project's document control system, and keep informal advice clearly labeled as informal.

07Measures and continuous improvement

• Useful measures are specific to the consulting role and should be defined at the start of the assignment. Common indicators include the percentage of review comments closed within the agreed response period, the number of critical findings discovered after a design phase was reported complete, the number of change orders that trace back to a review gap, the average age of open items, and the share of site observations that resulted in corrective action. Measures should be used to improve the process, not to rank individuals.
• Track the costs of rework and delay when the data is available. A consultant can show value by identifying a design clash before fabrication, or by catching a deficient connection before concrete is placed. Be honest about the limits of these measures, since many avoided problems are never recorded and it is hard to prove what would have happened.
• Review completed projects with the team. Ask which review criteria were too broad, which checks produced few useful findings, which documents arrived late, and which decisions were made without enough information. Update the firm's templates, checklists and comment categories based on those answers. Keep a short list of changes rather than rewriting the entire method each time.
• Practice differs across contexts. A public agency may require formal review logs and public meeting records, while a private developer may want faster, less formal comments. A design-build project may limit the consultant's role to owner-side review, while a design-bid-build project may place more emphasis on construction observation. Adjust the depth, format and authority of the work to the contract and the risk profile.

08Common mistakes and how to prevent them

• One common mistake is reviewing the wrong revision. Prevent it by stamping each review with the drawing set number, issue date and addenda list, and by confirming the current set with the document controller before starting. Another is accepting a response that restates the comment without showing a change. Require a reference to the revised sheet, detail or calculation before closure.
• A second mistake is mixing scope. A consultant asked to review mechanical systems may start commenting on architectural layouts that clash with them, and the client may then assume that the entire architecture set has been reviewed. Prevent this by stating the disciplines covered in the cover letter and listing excluded items.
• Another frequent problem is weak evidence. Comments such as the detail looks inadequate give the design team nothing to act on. Replace them with a statement of the requirement, the reference, the observed condition and the requested action.
• Consultants also lose effectiveness by waiting too long to raise serious issues. When a critical finding appears, notify the responsible parties promptly, in writing, and do not hold it for the next scheduled report. Confirm the notification was received.

09Practical checklist

• Confirm the question, scope, exclusions and decision-makers in writing before starting work.
• Verify that the document set is the current revision and that all addenda are included.
• Prepare a review or observation plan that links each scope item to a method and criteria.
• Record every finding with location, reference, evidence, severity and requested action.
• Separate verified facts from professional opinions and state any assumptions.
• Have a second qualified person check calculations, references and revision numbers before issue.
• Close comments only after seeing the revised document or the corrected condition.
• Maintain a project risk register with named owners and review it at each progress meeting.
• Confirm applicable codes, standards and amendments with the authority having jurisdiction.
• Send minutes after coordination meetings and keep formal findings in the document control system.
• Track response times, open items and rework trends, and review them at project closeout.

★Learning sources

• Micro Degree: Engineering, Architecture and Construction Consulting
• Micro Degree: Leadership and Team Management
• Micro Degree: Business Intelligence Management
• Micro Degree: ESG Advisory Services