# Documenting Engineering Judgment When The Draft Wasn't Yours **By Dan Cumberland** · Published August 25, 2026 · Categories: AI Strategy ![Featured image for Documenting Engineering Judgment When The Draft Wasn't Yours](https://cms.dancumberlandlabs.com/uploads/featured_image_f14bc03d10.webp) Illustration: Dan Cumberland Labs with Gemini. > AI-drafted engineering docs require the same documentation standards as human work. Here's what NSPE and EGBC say engineers must record — and the E&O question to check now. Your PE reviews an AI\-drafted structural report\. Two hours to review what a junior engineer would have spent a week drafting\. The review is thorough\. The stamp goes on\. Is it defensible— and can you prove it? The question isn't "can we stamp it?"— it's "what do we need to write down?" As the AIA Trust puts it, "when you seal a design, you certify your personal professional judgment, not the AI's\."[5](/blog/blog-documenting-engineering-judgment-when-the-draft-wasn-t-yours#ref-5) That judgment is yours\. The documentation proving it is yours too\. The framework for answering this question already exists\. Three independent regulatory bodies have weighed in, and their conclusion is consistent\. What it does require is a documentation practice most AEC firms haven't built yet\. This article provides that framework: six documentation elements for every piece of AI\-assisted work, and the one insurance question to ask before your next renewal\. ## The Professional Responsibility Framework Already Covers This Three independent regulatory bodies have each reached the same conclusion: the existing professional responsibility framework covers AI\-assisted engineering work\. NSPE, EGBC, and APEGA agree— no new regulations required\. AI in engineering follows the same legal logic as CAD in the 1990s and BIM coordination after that\. New tool, same accountability\. NSPE Professional Policy No\. 03 states it plainly: "Only a licensed Professional Engineer in responsible charge \(the engineer accountable for a defined scope of work\) can take responsibility for engineering work\."[1](/blog/blog-documenting-engineering-judgment-when-the-draft-wasn-t-yours#ref-1) That principle doesn't change because the tool got faster\. A solid [AI strategy for your firm](/services/ai-strategy) starts with understanding where that line sits: - **NSPE** requires that AI tools meet the same standard of care as any other instrument used in professional practice - **EGBC** states that "responsibility for the work product rests entirely with the engineering/geoscience professional regardless of whether AI\-based systems or tools are used"[2](/blog/blog-documenting-engineering-judgment-when-the-draft-wasn-t-yours#ref-2) - **APEGA** requires documentation of AI use to match what would be required for human\-completed work, with formal guidance issued as recently as March 2026[3](/blog/blog-documenting-engineering-judgment-when-the-draft-wasn-t-yours#ref-3) No US state engineering board has publicly prohibited a licensed Professional Engineer from stamping AI\-assisted work— though state guidance continues to evolve\. NSPE's 2025 survey found that 92% of engineers expect AI to play a significant role in the profession\.[4](/blog/blog-documenting-engineering-judgment-when-the-draft-wasn-t-yours#ref-4) The regulatory bodies are reading the room\. The framework is sufficient\. The gap isn't legal— it's practical, and it shows up the moment your engineer starts to document their review\. ## What "Engineering Judgment" Actually Means When AI Wrote the Draft Reviewing AI\-drafted engineering work requires the same professional judgment as reviewing work from a junior engineer— independent verification of calculations, review of assumptions, and documentation of what you checked and why\. The critical difference is that AI cannot explain its reasoning if you ask\. Every principal and PM reading this has reviewed junior staff work and put their name on it\. That's the job\. The obligation with AI is identical: look, check, verify, take responsibility\. What changes is the explainability gap\. A junior engineer can be called into the room\. AI cannot\. EGBC guidance requires "at least the same level of scrutiny as human\-created work\."[2](/blog/blog-documenting-engineering-judgment-when-the-draft-wasn-t-yours#ref-2) Peer\-reviewed research from Frontiers in Built Environment confirms that "AI functions as decision\-support tool rather than replacement for human expertise; engineers retain ultimate decision\-making authority\."[6](/blog/blog-documenting-engineering-judgment-when-the-draft-wasn-t-yours#ref-6) NSPE adds that AI recommendations "should not be blindly accepted but should be considered and challenged\."[1](/blog/blog-documenting-engineering-judgment-when-the-draft-wasn-t-yours#ref-1) This is where the documentation imperative comes from\. Aras put it in terms no engineer will misread: > "You cannot explain a certification issue, audit finding, or field failure by saying 'AI told me so\.'"[7](/blog/blog-documenting-engineering-judgment-when-the-draft-wasn-t-yours#ref-7) That's not a threat\. That's a design principle\. Professional accountability requires that someone, with a name and a license, can testify to what they checked and why they were satisfied\. The [AI governance frameworks](/blog/ai-governance-strategy) behind this shift make clear why verification burden doesn't shrink when AI speeds up drafting— if anything, it rises\. The question then becomes specific: what does a defensible documentation record look like? ## The Documentation Framework— What to Write Down When AI\-Drafted Work Gets Your Seal EGBC guidance is explicit: "If AI is used to generate results for a report or to make design decisions, then its use must be documented to the same extent as if an engineering professional had researched the sources or completed the calculations themselves\."[2](/blog/blog-documenting-engineering-judgment-when-the-draft-wasn-t-yours#ref-2) In practice, that means six specific elements for every piece of AI\-assisted work\. You can't read the label from inside the bottle\. The engineer must translate their understanding of what the AI system did into documentary form while that understanding is fresh— you cannot reconstruct in\-the\-moment reasoning after the fact\. The EGBC requirement for a "separate record" reflects this precisely\. Memory doesn't scale\. A record does\. Per Stanford Law School research cited in GotLaw \(2025\), general\-purpose AI tools generate plausible but false content at rates between 58% and 88%\.[8](/blog/blog-documenting-engineering-judgment-when-the-draft-wasn-t-yours#ref-8) That's not a reason to avoid AI— it's the reason each output requires independent verification, not just review\. **The six\-element documentation record:** 1. **Tool name and version**— Which AI system generated the draft, and which version was running at the time 2. **Inputs provided**— What prompts, drawings, specifications, or data were fed to the tool 3. **Outputs generated**— What the AI produced, or a summary if the output is the document itself 4. **Independent verification steps**— How the engineer checked the output: calculations rechecked, code references verified, assumptions challenged 5. **Judgment calls made**— Where the engineer's professional assessment differed from or supplemented the AI's output 6. **Reviewer name and date**— Who performed the review and when This record can take several forms— a project management entry, a QA checklist, a cover memo, a stamp with fields\. Whether you're building this into Deltek, a QA stamp template, or a shared project folder, what matters is that it exists and was created during the review\. Aras describes the traceability standard for AI\-heavy engineering environments as capturing why a change was made, what risks were accepted, what evidence supported the decision, and who signed off\.[7](/blog/blog-documenting-engineering-judgment-when-the-draft-wasn-t-yours#ref-7) Building [an AI adoption culture](/blog/building-ai-culture) means making this record a default workflow step, not an afterthought\. One more thing to verify before your next renewal: whether your E&O policy covers this work\. ## The Insurance Question to Ask Before Something Goes Wrong Most professional liability \(Errors and Omissions\) insurance policies currently in force cover AI\-assisted engineering work as a standard professional negligence matter\. But major carriers are filing to exclude AI\-related liabilities from future policies— and firms using AI now should verify their coverage before the next renewal, not after an incident\. Relm Insurance's analysis of the current market: "Most professional liability policies in force today still cover AI\-assisted design work as a standard professional negligence matter\. Unless a policy specifically excludes AI, professionals remain responsible for mistakes\."[9](/blog/blog-documenting-engineering-judgment-when-the-draft-wasn-t-yours#ref-9) Current coverage is mostly intact\. The exposure sits at renewal\. Major carriers— including Berkley, AIG, Great American, Philadelphia Insurance, and Hamilton Select— are filing for regulatory approval to exclude AI\-related liabilities from future policies\.[9](/blog/blog-documenting-engineering-judgment-when-the-draft-wasn-t-yours#ref-9) The gap opens at renewal, not at the moment of AI use\. That timing distinction matters\. Before your next renewal, ask your broker three questions: - Does our current policy cover AI\-assisted engineering work, and are there any existing exclusions? - Are you seeing exclusion endorsements filed on policies like ours at renewal? - Is there a dedicated AI coverage product we should evaluate alongside our standard E&O? The hallucination exposure— AI generating false or outdated building code references— is the specific scenario worth discussing\. That's the trigger most likely to surface in a claim, and the [hidden costs of AI projects](/blog/hidden-costs-ai-projects) often show up exactly there\. *Coverage terms are evolving rapidly\. Verify your firm's current position with your broker before next renewal\.* ## FAQ ### Can a PE legally stamp AI\-generated engineering documents? Yes\. No US state or Canadian province currently prohibits it\. When a PE seals the work, they certify their own professional judgment— not the AI's output— and accept full professional responsibility for the result\. NSPE Professional Policy No\. 03 and EGBC's Practice Advisory both confirm that the existing professional responsibility framework applies without modification\.[1](/blog/blog-documenting-engineering-judgment-when-the-draft-wasn-t-yours#ref-1)[2](/blog/blog-documenting-engineering-judgment-when-the-draft-wasn-t-yours#ref-2) ### What does an engineer need to document when reviewing AI\-drafted work? Six elements: the AI tool name and version, the inputs provided to the system, the outputs generated, the verification steps the engineer took, any judgment calls where the engineer's assessment differed from the AI's output, and the reviewer's name and date\. This record must be created during the review— not reconstructed from memory afterward\.[2](/blog/blog-documenting-engineering-judgment-when-the-draft-wasn-t-yours#ref-2)[8](/blog/blog-documenting-engineering-judgment-when-the-draft-wasn-t-yours#ref-8) ### Does E&O insurance cover AI\-assisted engineering work? Most policies currently in force still cover it as standard professional negligence\. However, major carriers including Berkley, AIG, and Great American are filing to exclude AI liabilities from future policies\. Verify your coverage before the next renewal— the gap opens at renewal, not at the moment of AI use\.[9](/blog/blog-documenting-engineering-judgment-when-the-draft-wasn-t-yours#ref-9) ### How is reviewing AI\-drafted work different from reviewing a junior engineer's work? The standard of care is identical: check calculations, review assumptions, apply independent engineering judgment\. The critical difference is that AI cannot explain why it made a choice if asked\. A junior engineer can be brought into the room; AI cannot\. So the engineer's written record must substitute for that explanation— which is exactly why the documentation framework exists\.[2](/blog/blog-documenting-engineering-judgment-when-the-draft-wasn-t-yours#ref-2)[7](/blog/blog-documenting-engineering-judgment-when-the-draft-wasn-t-yours#ref-7) ## Conclusion: Judgment Is the Bottleneck— By Design AI accelerates drafting\. That's real\. What it cannot accelerate is professional judgment— and that is exactly the point\. When you sealed your first structural report as the engineer of record, you were accountable for work that someone else drafted\. That's the job\. AI changes the speed at which drafts arrive\. It doesn't change what your seal certifies\. NSPE's own survey found that 92% of engineers expect AI to play a significant role in the profession in the near future\.[4](/blog/blog-documenting-engineering-judgment-when-the-draft-wasn-t-yours#ref-4) The profession is already there\. And the documentation practice needs to catch up\. Firms that build this into their workflows now— six\-element records, contemporaneous documentation, E&O verification before renewal— will be ahead of the curve when the first AEC AI liability cases reach a courtroom\. And they will\. Most AEC firms using AI today are one incident away from discovering their documentation practice doesn't hold up\. Building the six\-element record into your standard QA workflow— not as a post\-hoc check but as a required step before any AI\-assisted work gets sealed— is how you avoid being the test case\. That's the kind of [AI implementation work](/services/ai-implementation) that protects the firm's ability to keep using AI at all\. Regardless of how fast the regulatory landscape evolves, the fundamental truth doesn't change: the engineer's judgment is what the seal certifies\. Build the record that proves it\. *This article discusses publicly available regulatory guidance\. Consult legal counsel for jurisdiction\-specific advice\.* ## References 1. National Society of Professional Engineers, "Artificial Intelligence— Professional Policy No\. 03" \(2024\)— [https://www\.nspe\.org/nspe\-advocacy/explore\-issues/professional\-policies\-and\-position\-statements/artificial\-intelligence](https://www.nspe.org/nspe-advocacy/explore-issues/professional-policies-and-position-statements/artificial-intelligence) 2. Engineers and Geoscientists British Columbia, "Use of Artificial Intelligence in Professional Work— Practice Advisory" \(2024\)— [https://tools\.egbc\.ca/registrants/practice\-resources/guidelines\-advisories/Document/01525AMWZDBFA4VTKQBRHJXVI6AR4UUFGV/Use%20of%20Artificial%20Intelligence%20in%20Professional%20Work](https://tools.egbc.ca/registrants/practice-resources/guidelines-advisories/Document/01525AMWZDBFA4VTKQBRHJXVI6AR4UUFGV/Use%20of%20Artificial%20Intelligence%20in%20Professional%20Work) 3. Association of Professional Engineers and Geoscientists of Alberta, "Guidance for Registrants Regarding the Use of Artificial Intelligence Tools" \(2026\)— [https://www\.apega\.ca/news/2026/03/23/guidance\-for\-registrants\-regarding\-the\-use\-of\-artificial\-intelligence\-tools](https://www.apega.ca/news/2026/03/23/guidance-for-registrants-regarding-the-use-of-artificial-intelligence-tools) 4. National Society of Professional Engineers, "NSPE 2025 Survey on AI in Engineering Practice" \(2025\)— [https://www\.nspe\.org/nspe\-advocacy/explore\-issues/professional\-policies\-and\-position\-statements/artificial\-intelligence](https://www.nspe.org/nspe-advocacy/explore-issues/professional-policies-and-position-statements/artificial-intelligence) 5. AIA Trust, "When AI Legal Searches Become Exhibit A: Discovery Risk for Architects and Engineers" \(2024\)— [https://theaiatrust\.com/when\-ai\-legal\-searches\-become\-exhibit\-a\-discovery\-risk\-for\-architects\-and\-engineers/](https://theaiatrust.com/when-ai-legal-searches-become-exhibit-a-discovery-risk-for-architects-and-engineers/) 6. Frontiers in Built Environment, "Responsible AI in Structural Engineering: Ethical Framework and Best Practices" \(2025\)— [https://www\.frontiersin\.org/journals/built\-environment/articles/10\.3389/fbuil\.2025\.1612575/full](https://www.frontiersin.org/journals/built-environment/articles/10.3389/fbuil.2025.1612575/full) 7. Aras, "As AI Agents Move into Engineering, Judgment Becomes the Real Bottleneck" \(2025\)— [https://aras\.com/en/blog/as\-ai\-agents\-move\-into\-engineering\-judgment\-becomes\-the\-real\-bottleneck/](https://aras.com/en/blog/as-ai-agents-move-into-engineering-judgment-becomes-the-real-bottleneck/) 8. GotLaw, "When 'Smart' Tools Make Dumb Mistakes: AI's Hidden Risks in Construction Documents" \(2025\)— [https://gotlawstl\.com/when\-smart\-tools\-make\-dumb\-mistakes\-ais\-hidden\-risks\-in\-construction\-documents/](https://gotlawstl.com/when-smart-tools-make-dumb-mistakes-ais-hidden-risks-in-construction-documents/) 9. Relm Insurance, "Tech E&O for AI Products: What It Covers" \(2025\)— [https://relminsurance\.com/tech\-eo\-for\-ai\-products\-what\-it\-covers\-hallucinations\-model\-errors\-bad\-advice\-ip\-and\-training\-data\-and\-contractual\-liability/](https://relminsurance.com/tech-eo-for-ai-products-what-it-covers-hallucinations-model-errors-bad-advice-ip-and-training-data-and-contractual-liability/) --- **How we made this article:** We use AI in our research and writing so our small team can share more of what we learn. We verify the sources and take responsibility for every article we publish. [Read how we use AI.](https://dancumberlandlabs.com/how-we-use-ai/) --- ## About the author **Dan Cumberland** — Founder, Dan Cumberland Labs Dan Cumberland helps engineering and construction firms see where they stand with AI and decide what to build first. He created Pacemark, the AI maturity model behind that work, from research on more than 300 companies. - Take the assessment: https://pacemark.ai/signal/assessment/?track=aec&utm_source=dcl-site&utm_medium=link&utm_campaign=pacemark-assessment - Book a call: https://book.dancumberland.com/ai-strategy --- Source: https://dancumberlandlabs.com/blog/documenting-engineering-judgment-when-the-draft-wasn-t-yours/