Safety, Liability, and Professional Sign-Off in AI-Assisted Engineering Work
Deliberate Academy Editorial Team
Reviewed for accuracy and professional relevance
You're 9 lessons in — don't lose your progress.
Sign up free to save where you are and earn a verified certificate when you pass.
- Explain why the engineer of record's stamp, seal, or signature cannot be transferred to an AI tool regardless of how the underlying content was produced
- Apply the standard-of-care framework that licensure boards and courts use to evaluate AI-assisted engineering work when something goes wrong
- Design a firm-level AI use policy covering disclosure, documentation, and audit trail requirements for AI-assisted engineering deliverables
- Identify what changes and what does not change about professional liability exposure when a stamped deliverable has AI-assisted content behind it
A licensed structural engineer stamped a set of calculations for a mezzanine addition that included a load table drafted with AI assistance from his own verified inputs, reviewed and confirmed against his independent hand calculations before stamping. Two years later, a separate incident on an unrelated project made industry news: a different engineer at another firm had stamped a calculation package where an AI-drafted load table contained an error that was never independently checked, and the mezzanine it supported required emergency reinforcement after a partial deflection failure was discovered during a routine inspection. The licensure board's finding in that second case was unambiguous: the engineer's stamp attached full personal responsibility for the calculation regardless of which tool produced the initial draft. This lesson is about making sure your practice looks like the first engineer, not the second.
The Sign-Off Principle: What Does Not Change
Every prior lesson in this course has repeated a version of the same principle, because it is the load-bearing idea of this entire course: AI output in engineering is a draft for a licensed professional to verify, never a finished, stamped, or certified deliverable. This lesson makes that principle explicit and complete.
The stamp, seal, or signature is non-delegable. When a professional engineer stamps a drawing, calculation package, or report, they are certifying -- to the client, the authority having jurisdiction, and the public -- that the work meets the applicable standard of care and that they take personal professional responsibility for it. No tool, vendor, or AI provider shares in that certification. The engineer of record's professional and legal exposure is identical whether an error originated from a hand calculation, a junior engineer's mistake, outdated reference material, or an AI-drafted section that was not independently verified.
The standard of care does not have an AI exception. Licensure boards and courts evaluate engineering conduct against what a reasonably prudent engineer in the same discipline and circumstances would have done. Using AI tools to draft, research, or accelerate work is not itself a violation of the standard of care -- using AI output without the verification a reasonably prudent engineer would apply is. The tool used does not change the standard; it changes what verification steps are available and expected.
If your firm's current practice would not survive the question "would this hold up if a licensure board reviewed exactly what was AI-generated and exactly what was independently verified before stamping," your practice needs to change before your next project, not after your next incident. This is the single most important sentence in this course.
Two Engineers, One Tool, Two Outcomes
Context
A structural engineer used an AI tool to draft the narrative and a supporting load table for a mezzanine addition calculation package, providing his own verified load inputs and design assumptions. Around the same period, a licensure board investigation became public involving a different engineer at another firm who had stamped a similar mezzanine calculation package containing an AI-drafted load table that was never independently checked against the actual design inputs -- an arithmetic error in the AI's table understated the governing load by a margin that was not caught before stamping.
Action
The first engineer's practice included a firm-wide policy requiring every AI-assisted numeric output to be independently reproduced by hand or in verified calculation software before appearing in a stamped package, with the verification documented and retained in the project file. He followed that process: reproducing the load table independently, confirming it matched the AI draft's structure but correcting two minor rounding discrepancies, and retaining his verification worksheet in the project record before stamping.
Outcome
The licensure board's finding on the second engineer's case was that the stamp attached full personal professional responsibility for the calculation error regardless of which tool had produced the initial draft, and that the absence of a documented independent verification step was itself indicative of a standard-of-care failure -- not merely the arithmetic error itself. The first engineer's project file, structured around documented independent verification, is the model this lesson asks you to build your own practice around.
A firm's principal argues that because an AI tool produced a calculation error, the firm's professional liability insurer or the AI vendor should bear responsibility, not the stamping engineer. How does this lesson's framework address that argument?
Select one answer.
Building a Firm-Level AI Use Policy
A defensible AI use policy for an engineering practice should address four elements directly. Disclosure: whether and how AI use is disclosed to clients, and under what circumstances a client would reasonably expect to be told AI tools contributed to a deliverable. Scope boundaries: an explicit list of task categories where AI drafting is permitted (documentation, research orientation, report drafting) and categories where it is not permitted to produce or verify content without a defined independent check (calculations, code compliance determinations, safety-critical judgments) -- built from the risk framework in Lesson 1. Documentation and audit trail: a requirement that AI-assisted numeric content be independently reproduced and that verification be documented and retained in the project file, exactly as in this lesson's case study. Insurance and contractual review: confirmation with the firm's professional liability insurer that current AI use practices are consistent with policy terms, since some insurers have begun asking specific questions about AI use in underwriting and claims.
Treat your firm's AI use policy as a living document tied to your existing quality assurance process, not a separate compliance exercise. The most effective version of this policy is usually an addition to an existing QA checklist -- adding "AI-assisted content independently verified and documented" as a required sign-off line next to the checks your firm already performs, rather than creating a parallel process nobody actually follows under deadline pressure.
Do not treat AI use disclosure as optional simply because no regulation currently mandates it in your jurisdiction. Client trust and defensibility in a dispute both benefit from a documented, consistent practice around when and how AI contributed to a deliverable -- retroactively explaining your AI use for the first time during a claim investigation is a materially weaker position than having a standing, documented policy the client already understood.
A structural engineering firm is drafting its first AI use policy. Which combination of elements does this lesson identify as necessary for the policy to be defensible?
Select one answer.
What Actually Changes With AI in the Workflow
Nothing about the standard of care, the meaning of a stamp, or the engineer's personal professional responsibility changes because AI tools are involved. What changes is practical: the volume of first-draft content a practice can produce increases, which means the verification workload -- not the drafting workload -- becomes the practice's actual bottleneck and the place where quality assurance investment belongs. Firms that treat AI adoption purely as a drafting speed gain, without a corresponding investment in verification capacity and documented process, are the ones most likely to produce the second outcome in this lesson's case study rather than the first.
Exercise
Your Task
Draft the first version of an AI use policy for your own practice or team, covering the four elements from this lesson: (1) a disclosure approach -- when and how you would tell a client AI contributed to a deliverable; (2) scope boundaries -- which task categories are permitted for AI drafting and which require independent, non-AI verification, using the risk framework from Lesson 1; (3) a documentation requirement -- what gets recorded in the project file to show independent verification occurred; (4) a note on what you would need to confirm with your professional liability insurer before finalizing the policy. This does not need to be a finished, firm-approved document -- it needs to be specific enough that a colleague could follow it.
Your reflection
Did you complete this exercise? What did you find? (Saved locally in your browser)
- The engineer of record's stamp, seal, or signature is non-delegable -- professional and legal responsibility for a deliverable attaches to the certifying engineer personally, regardless of which tool, person, or process produced the underlying content.
- The standard of care licensure boards and courts apply has no AI exception -- using AI to draft or research is not itself a standard-of-care violation, but using AI output without the verification a reasonably prudent engineer would apply is.
- A defensible firm-level AI use policy addresses four elements: disclosure to clients, scope boundaries built from a risk framework, documented independent verification for numeric content, and confirmation with the firm's professional liability insurer.
- Document independent verification of AI-assisted numeric content in the project file as a standing practice, not an incident-response measure -- the presence or absence of that documentation is itself something licensure boards weigh when evaluating a standard-of-care question.
- AI adoption increases drafting speed, not verification capacity -- the practices that invest in verification capability alongside AI adoption are the ones that convert speed into safe, defensible output rather than into undetected risk.