In an engineering firm AI arrives in four places before anyone decides anything: the design and drafting group that summarises the client's drawings and drafts the calculation narrative, the project managers who write the meeting minutes, the response to the contractor's request for information and the change-order justification, the proposal desk that writes the fee proposal and the statement of qualifications, and the quality group that checks the package before it goes out. The principal's job is not to pick the tool. It is to decide three things before a tool touches a client's drawings, a calculation package or a fee proposal: who in the firm owns the question, what may never go into an outside tool, and what the firm will never let a machine do alone. This article is for the principal, partner or owner of a civil, structural, mechanical-electrical-plumbing or other consulting engineering and design firm with a few dozen to a few hundred people, independent or newly backed by private equity.
I was COO and then President of a public company that closed more than forty acquisitions, and I ran the integration on most of them. I am a lawyer by training. Now I write fixed-fee AI plans for CEOs of private-equity-backed and owner-led mid-market companies through 013 Labs, and engineering firms are a group where a tool's mistake can end up under a licensed engineer's seal, in a client's building and in a professional-liability claim at the same time.
Where AI already is in your firm
Ask a senior designer what the free tools on the staff's phones are doing this week and the honest answer is: summarising the client's drawing set and specification, drafting the narrative of the calculation package. Ask the project managers and it is the meeting minutes, the first draft of the answer to the contractor's request for information, and the change-order justification. Ask the proposal desk and it is the scope of services, the fee proposal assembled from last year's, the statement of qualifications. Ask the quality group and it is the checklist run against the package. Ask the office and it is the job posting and last year's subconsultant agreement with the dates changed. And the design-software vendor and the project-management vendor each switched on an assistant with their last release. None of it was approved. Some of it has already told a client why a member is adequate with nobody's name on it, and some of it has carried a client's drawings, a site survey or a building-information file onto a vendor's server under no agreement at all.
The three decisions, in the order a firm makes them
Who owns the question. Not the IT provider, not the design-software vendor and not a new hire. In most firms it is the quality manager, the director of operations or a senior principal who also holds the professional-liability file, as they are the people the staff already ask when something new shows up. Give that person a written scope of half a page: what they may approve alone, what comes to the principals, when the page is reviewed. The article on AI for a company with no IT department draws the line between their column and yours.
The data rule. One sentence. For an engineering firm it usually reads: no client's drawings, design files, specifications, survey or geotechnical data, no calculation package, no stamped or unstamped deliverable, no subconsultant's work and nothing about an employee go into a tool the firm has not approved, and no tool is approved to hold project information without the written vendor terms the firm's contracts with its clients require. The principal writes it. The client's project information is held under the client's contract, often with a confidentiality clause, and the vendor's terms are the firm's to sign.
The never-build list. The three things the firm will never let a machine do alone. For an engineering firm the list writes itself: no drawing, calculation or report is sealed or issued without the licensed engineer who is responsible for it having personally reviewed the work; no opinion on code compliance, structural adequacy or the safety of a design leaves the firm from a tool without a licensed engineer's name on it; no proposal, fee, scope of services or change-order price is sent by a tool. Everything else is a question of fit. These three are not.
What fits at fifty people, and what does not yet
The first project is the work your people already do by hand, the same way, on every job: the client's drawing set and specification read into a summary for the designer to check against the source, the calculation narrative for the engineer to finish, the meeting minutes drafted from the project manager's notes, the first draft of the answer to a request for information for the engineer of record, the statement of qualifications assembled from the firm's own write-ups. The article on picking your first AI project has the five tests. What does not fit yet, in most firms this size, is anything that decides or seals: the design, the sizing, the code opinion, the stamped sheet, the fee. A tool can prepare any of those for a licensed engineer. It should not finish them.
The licensing board, the liability insurer, the client and the buyer will ask
The AI question reaches an engineering firm from four directions that have nothing to do with technology. The state licensing board and the profession's own rules ask it in their words: an engineer who seals work is responsible for it, and a tool's draft is not a defence. The professional-liability insurer's renewal form asks whether automated tools produce design work, calculations or opinions in the firm's name, because work a tool produced is work the firm produced. The client asks it in the contract, increasingly, with a clause about what may be run through outside tools and who owns what the firm delivers. And a buyer, a larger firm or private equity, asks it in diligence, because engineering and design firms are bought into platforms; the article on whether AI makes a business worth more when you sell has that version, and the one on what to tell your bank about AI covers the bank behind the partner buyouts. One dated page answers all of them.
The contractor's side of the same job has its own version of the question. The article on AI for a plumbing, HVAC or electrical business covers the estimate, the submittal and the payroll, and the one on AI for a construction business covers the general contractor.
Picture a regional engineering firm of one hundred forty people with three offices and a new private-equity partner. A structural group at the largest office has been running client drawings and its own calculation narratives through a free tool on the designers' own logins for a season. The principal finds out when the client's counsel asks, during a dispute over a response to a contractor's request for information, which system wrote the response and who checked it, and then finds that the response went out under a project engineer's name without the engineer of record reading it, that it described a connection as acceptable when the detail had been revised, and that the client's drawing set and design files went into the same tool. The fix takes two weeks and a call to the firm's liability carrier. The quality manager is named as the person who owns the question, with a half-page scope. The principal writes the data rule: no client drawing, design file or calculation, no subconsultant file, no employee file into an outside tool, and no tool without written vendor terms. The never-build list goes on the page, starting with no opinion on a design without a licensed name on it. The free tool is replaced by the firm's plan the same month, the contractor gets a corrected response in writing from the engineer of record, the files are deleted from the vendor's account with the deletion confirmed in writing, and the client's counsel gets the page. This is a hypothesis, a composite and not a client.
The one page
What is in use, by group and task, including the free tools and the assistants the design-software and project-management vendors switched on. Who owns the question, with the written scope. The data rule in one sentence, with the vendor terms listed. The never-build list, the three items above. The review date and who signs. The principal signs it, the quality manager keeps it with the firm's quality procedures, and the director of operations has it ready for the insurer's renewal. The board-briefing template has the same page in a form a firm can fill in. If you want to see which of the three is missing before anyone writes the page, the AI readiness scorecard asks the questions a principal can answer from memory.
Mistakes that repeat
Letting the software vendor switch it on. An assistant arrives in a release, defaults to on, and the next calculation narrative carries a statement nobody checked against the design. The principal decides, feature by feature.
The client's drawings in a free tool. The one mistake that puts the firm in front of the client's counsel and, if work is sealed on the strength of it, the licensing board. The data rule exists for this.
An opinion no licensed engineer read. A tool drafts the answer to the contractor's question or the architect's; a project engineer sends it at the end of a long day. The reader relies on it. A licensed engineer reads every opinion that leaves.
A proposal the template wrote. A tool rolls last year's fee proposal forward with the dates changed; the scope has changed, the fee does not cover it and nobody noticed. A principal reads every proposal before it goes.
No review date. Clients change their contract language and insurers change their forms. A page without a date is a page nobody opens.
Frequently asked questions
Should an engineering firm use AI?
It already does, through the design group, the project managers and the proposal desk. The decision worth making is who owns the question, what may never go into an outside tool, and the three things the firm never lets a machine do alone: a drawing or calculation sealed unread, a code or design opinion without a licensed name, and a proposal or fee sent by a tool.
Who should own AI in a consulting engineering firm?
The person the staff already ask when a new tool shows up, usually the quality manager, the director of operations or the senior principal who holds the liability file, with a written scope of half a page and a review date. Not the IT provider and not the design-software vendor.
Can AI draft our calculation narratives and responses to requests for information?
It can draft from documents a person has given it, for the designer to check against the source and the code and for the licensed engineer to seal or sign. It should not make the call. The seal is the engineer's, and the client's counsel or the board will ask who checked it.
What about client drawings and design files in these tools?
They are first in the data rule. No client's drawings, design files, specifications, survey or geotechnical data and no calculation package go into a tool the firm has not approved, and no tool is approved to hold project information without the written vendor terms the firm's client contracts require. If client files have already gone into a free tool, delete them from the vendor's account, get the deletion confirmed in writing, and tell the firm's liability carrier the same week.
Why does my insurer or my client ask about AI?
Because each carries the risk when a drawing, a calculation or an answer that a tool touched turns out to be wrong, and each wants to know whether a licensed engineer stands behind it. One dated page with names on it is the answer, and the same page answers the licensing board, a buyer and the bank.
Not sure where you stand? Take the 3-minute AI readiness scorecard.