Civil and structural engineers spend a significant portion of every project on documentation that is not structural analysis. Calculation narratives, geotechnical report sections, permit package narratives, construction administration correspondence, CSI specification sections, feasibility studies — this is the written layer around every project, and it consumes hours that could go toward engineering work. Claude AI drafts that written layer. Two adjacent posts on this blog cover related ground: Claude AI for software engineers owns code, systems architecture, and technical documentation for software products; Claude AI for engineering managers and CTOs owns team leadership, RFC writing, and technical strategy for engineering organizations. This post owns the civil/structural documentation pipeline: calculation narratives, engineering reports, permit package writing, construction administration letters, and technical specifications for civil, structural, geotechnical, transportation, and water/wastewater engineering work.
This post is written for civil engineers, structural engineers, geotechnical engineers, transportation engineers, water and wastewater engineers, licensed Professional Engineers, EITs, and engineering consultants. Read the hard limits section first — this is a licensed profession with real liability exposure, and the use cases only make sense within those constraints.
What Claude Cannot Do for Civil and Structural Engineers
These are hard limits. Read them before using any prompt in this post.
- No structural analysis software: Claude has no connection to SAP2000, ETABS, RISA, RAM Structural, STAAD, or any other structural analysis platform. It cannot perform structural calculations, run load analyses, size members, check deflection, or produce anything that constitutes a structural analysis output. It is a language model.
- No code lookup: Claude cannot access ASCE 7, IBC, ACI 318, AISC 360, AASHTO, NDS, or any current edition of engineering standards. It may reference code provisions from its training data — those references may be outdated, paraphrased, or incorrect. Do not rely on Claude to cite specific code sections, load tables, or design values. Verify every code reference against the current adopted edition independently.
- No site-specific data: Claude has no access to soil boring data, geotechnical parameters, seismic zone maps, wind speed maps, flood zone determinations, USGS data, or any site-specific engineering information. Every site parameter must come from your actual investigation and authoritative sources.
- Not a licensed engineer: Claude is not a Professional Engineer and cannot provide engineering judgment, evaluate structural adequacy, or offer professional opinions on design decisions. All outputs are draft text only. Every document produced using these prompts must be reviewed, stamped, and signed by a licensed Professional Engineer before submission or use.
- No permit or regulatory submission: Outputs are draft narratives only. All permit submittals, regulatory filings, and formal engineering documents require PE review, official stamp, and submission per the requirements of the authority having jurisdiction.
- No real project data in prompts: Never input real client names, project addresses, proprietary structural calculations, actual boring data, or any confidential project information into Claude prompts. Use placeholders throughout. Claude provides structure and language; you supply verified project data at review.
What Claude does for civil and structural engineers: drafts the language, structure, and formatting of engineering documentation. The technical content, site-specific parameters, code verification, engineering judgment, and licensed professional sign-off are yours.
6 Use Cases for Claude AI in Civil and Structural Engineering
1. Calculation Narrative / Basis of Design Memo
The calculation narrative — or basis of design memo — is the written explanation of what you designed, why you designed it that way, and what codes and assumptions govern the work. It is required documentation for most structural permit submissions and is the document that tells the plan checker, the peer reviewer, or a future engineer what you were thinking. Claude takes your project summary and design inputs and produces the complete structured memo format, with every numerical value clearly marked as a placeholder requiring actual calculated data.
Draft a calculation narrative / basis of design memo for a structural engineering project.
Use placeholder values for all numerical parameters — no actual engineering calculations.
Project type: [e.g., 3-story wood-frame residential / 4-story steel moment frame office /
single-story concrete tilt-up warehouse]
Applicable codes: [INSERT CODE EDITIONS USED — e.g., IBC 2021, ASCE 7-22, ACI 318-19,
AISC 360-22 — verify against jurisdiction requirements]
Design loads (all values are placeholders — insert actual calculated values):
Dead load: [INSERT]
Live load: [INSERT]
Roof live load: [INSERT]
Wind: [INSERT — basic wind speed, exposure category]
Seismic: [INSERT — Ss, S1, SDC, occupancy category]
Governing load combinations: [INSERT APPLICABLE LOAD COMBINATIONS FROM CODE]
Key design assumptions: [list 3–5 primary structural design assumptions]
Structure the memo as follows:
1. PROJECT DESCRIPTION
Project type, location (placeholder), scope of structural work.
2. DESIGN CRITERIA
Codes and standards: [LIST — mark each: VERIFY ALL CODE REFERENCES AGAINST
CURRENT ADOPTED EDITIONS]
Occupancy category / risk category: [INSERT]
Exposure categories: [INSERT]
3. DESIGN LOADS SUMMARY
Formatted table: Load Type | Value | Reference
All values: [INSERT ACTUAL CALCULATED VALUES — DO NOT USE PLACEHOLDER NUMBERS]
4. GOVERNING LOAD COMBINATIONS
List applicable combinations — mark each [VERIFY AGAINST CURRENT CODE EDITION]
5. DESIGN ASSUMPTIONS
Numbered list of structural assumptions governing the design.
6. STRUCTURAL SYSTEM DESCRIPTION
Brief narrative of the lateral and gravity system selected.
7. METHODOLOGY SUMMARY
How the structure was analyzed and designed — software, methods, approach.
Software used: [INSERT — e.g., SAP2000 vXX, RISA-3D vXX, hand calculations]
8. REFERENCES
Codes, standards, and reference documents used. [VERIFY CURRENT EDITIONS]
[ALL NUMERICAL VALUES IN THIS DOCUMENT ARE PLACEHOLDERS]
[DO NOT USE WITHOUT INDEPENDENT STRUCTURAL ANALYSIS BY A LICENSED PE]
[PE MUST REVIEW AND STAMP BEFORE SUBMISSION]
[VERIFY ALL CODE EDITIONS AGAINST JURISDICTION REQUIREMENTS]
CALCULATION NARRATIVE — BASIS OF DESIGN
[PROJECT NAME — PLACEHOLDER] | [PROJECT NUMBER — PLACEHOLDER]
Prepared by: [ENGINEER NAME — PLACEHOLDER] | Date: [INSERT] | Revision: [INSERT]
[PE MUST REVIEW AND STAMP BEFORE SUBMISSION]
[ALL NUMERICAL VALUES ARE PLACEHOLDERS — DO NOT USE WITHOUT INDEPENDENT
STRUCTURAL ANALYSIS]
---
1. PROJECT DESCRIPTION
This calculation narrative documents the basis of design for the structural systems
of a [3-story wood-frame residential building — INSERT ACTUAL PROJECT TYPE]. The
project consists of [INSERT SCOPE — e.g., three stories of light wood-frame
construction over a concrete podium slab]. Structural work includes design of the
gravity system (floor and roof framing, columns, footings) and lateral force-
resisting system.
2. DESIGN CRITERIA
The following codes govern the structural design. Verify all editions against
the currently adopted requirements of the authority having jurisdiction.
[VERIFY ALL CODE REFERENCES AGAINST CURRENT ADOPTED EDITIONS]
- International Building Code: [INSERT EDITION]
- ASCE 7, Minimum Design Loads: [INSERT EDITION]
- ACI 318 (if applicable): [INSERT EDITION]
- AISC 360 (if applicable): [INSERT EDITION]
- NDS (if applicable): [INSERT EDITION]
Occupancy / Risk Category: [INSERT]
Seismic Design Category: [INSERT — VERIFY WITH ASCE 7 AND SITE-SPECIFIC DATA]
Wind Exposure Category: [INSERT]
3. DESIGN LOADS SUMMARY
[ALL VALUES IN THIS TABLE ARE PLACEHOLDERS — INSERT ACTUAL CALCULATED VALUES]
[DO NOT USE PLACEHOLDER NUMBERS FOR ANY ENGINEERING PURPOSE]
Load Type | Value | Code Reference
---------------------|--------------------|-----------------
Roof dead load | [INSERT] psf | [VERIFY]
Floor dead load | [INSERT] psf | [VERIFY]
Roof live load | [INSERT] psf | [VERIFY]
Floor live load | [INSERT] psf | [VERIFY]
Basic wind speed | [INSERT] mph | [VERIFY — ASCE 7 wind maps]
Seismic Ss | [INSERT] g | [VERIFY — USGS/ASCE 7]
Seismic S1 | [INSERT] g | [VERIFY — USGS/ASCE 7]
SDS | [INSERT] g | [VERIFY — calculated]
SD1 | [INSERT] g | [VERIFY — calculated]
4. GOVERNING LOAD COMBINATIONS
Load combinations per [INSERT CODE EDITION]:
[VERIFY AGAINST CURRENT CODE EDITION — list applicable strength and ASD combinations]
- [INSERT LOAD COMBINATION 1]
- [INSERT LOAD COMBINATION 2]
- [INSERT ADDITIONAL COMBINATIONS AS APPLICABLE]
5. DESIGN ASSUMPTIONS
1. Foundation soil bearing capacity assumed at [INSERT] psf — [VERIFY AGAINST
GEOTECHNICAL REPORT AND ACTUAL BORING DATA]
2. [INSERT ASSUMPTION 2]
3. [INSERT ASSUMPTION 3]
4. Diaphragms assumed [rigid / flexible / semi-rigid — INSERT AND VERIFY]
5. [INSERT ADDITIONAL ASSUMPTIONS]
6. STRUCTURAL SYSTEM DESCRIPTION
Gravity System: [INSERT — describe floor and roof framing, columns, bearing walls,
foundation type]
Lateral Force-Resisting System: [INSERT — describe shear walls, moment frames,
braced frames, or other LFRS, with locations]
7. METHODOLOGY SUMMARY
Structural analysis performed using [INSERT SOFTWARE AND VERSION / hand calculations].
[INSERT BRIEF DESCRIPTION OF ANALYSIS METHODOLOGY]
8. REFERENCES
[VERIFY ALL EDITIONS AGAINST CURRENTLY ADOPTED STANDARDS]
1. [INSERT CODE/STANDARD — EDITION]
2. [INSERT CODE/STANDARD — EDITION]
3. Geotechnical Report: [INSERT — FIRM, DATE, PROJECT NUMBER]
4. [INSERT ADDITIONAL REFERENCES]
[ALL NUMERICAL VALUES ARE PLACEHOLDERS — DO NOT USE WITHOUT INDEPENDENT
STRUCTURAL ANALYSIS]
[PE MUST REVIEW AND STAMP BEFORE SUBMISSION]
[VERIFY ALL CODE EDITIONS AGAINST JURISDICTION REQUIREMENTS]
The output gives you a complete, formatted calculation narrative structure with every numerical value clearly flagged as a placeholder. The engineering content — load values, code editions, analysis results, foundation parameters — all comes from your actual work. Claude provides the document architecture that takes those inputs and makes them plan-check-ready.
2. Geotechnical / Soils Report Narrative
Geotechnical reports follow a standard narrative structure — site description, subsurface conditions, groundwater, engineering properties summary, foundation recommendations, construction considerations — but writing clear, professionally formatted prose around actual boring data and lab results is time-consuming. Claude drafts the narrative structure and section language, with all geotechnical values clearly marked as placeholders requiring data from the actual site investigation.
Draft a geotechnical report narrative using the project and site information below.
All geotechnical parameters must come from actual site investigation data — use
placeholder brackets for every value.
Site description: [describe site location generically — no real address or client info]
Project type: [e.g., 3-story office building / residential subdivision /
highway bridge abutment]
Number of borings: [INSERT]
Boring depths: [INSERT RANGE — e.g., 20–50 ft]
Boring log summary: [INSERT ACTUAL BORING DATA — describe soil profile from logs,
e.g., "0–5 ft: fill/topsoil; 5–15 ft: medium dense silty sand; 15–50 ft: dense
gravelly sand" — or use [INSERT ACTUAL BORING DATA] if not yet available]
Lab test results: [INSERT LAB TEST RESULTS — e.g., grain size, Atterberg limits,
moisture content, consolidation data]
Key geotechnical parameters: [INSERT VALUES FROM SOILS INVESTIGATION — e.g.,
allowable bearing capacity, friction angle, cohesion, liquefaction potential]
Structure the report as follows:
1. SITE DESCRIPTION AND PROJECT OVERVIEW
2. SCOPE OF INVESTIGATION
Number and depth of borings, sampling methods, lab testing program.
3. SUBSURFACE CONDITIONS NARRATIVE
Soil profile by layer — based on boring data provided.
All thicknesses and depths: [INSERT FROM BORING LOGS]
4. GROUNDWATER OBSERVATIONS
Depth and conditions during investigation.
[INSERT ACTUAL GROUNDWATER DEPTHS FROM BORING LOGS]
5. ENGINEERING PROPERTIES SUMMARY
Table format. All values: [INSERT FROM SOILS INVESTIGATION — DO NOT FABRICATE]
6. FOUNDATION RECOMMENDATIONS NARRATIVE
Narrative text only — describe foundation type, depth, and approach.
Do not include calculated bearing capacity values — mark all numerical
recommendations [INSERT FROM GEOTECHNICAL ANALYSIS].
7. CONSTRUCTION CONSIDERATIONS
Earthwork, groundwater control, structural fill, special inspection requirements.
[ALL GEOTECHNICAL PARAMETERS MUST COME FROM ACTUAL SITE INVESTIGATION DATA]
[DO NOT FABRICATE SOIL PROPERTIES, BEARING CAPACITIES, OR GROUNDWATER CONDITIONS]
[LICENSED GEOTECHNICAL ENGINEER MUST REVIEW AND STAMP]
[VERIFY AGAINST ACTUAL BORING LOGS AND LAB RESULTS BEFORE ISSUING]
GEOTECHNICAL REPORT — DRAFT NARRATIVE
[PROJECT NAME — PLACEHOLDER] | [PROJECT NUMBER — PLACEHOLDER]
Prepared by: [GEOTECHNICAL ENGINEER NAME AND FIRM — PLACEHOLDER]
Date: [INSERT] | Revision: [INSERT]
[LICENSED GEOTECHNICAL ENGINEER MUST REVIEW AND STAMP BEFORE ISSUANCE]
[ALL VALUES ARE PLACEHOLDERS — VERIFY AGAINST ACTUAL BORING LOGS AND LAB DATA]
---
1. SITE DESCRIPTION AND PROJECT OVERVIEW
The subject site is located at [SITE LOCATION — GENERAL DESCRIPTION ONLY]. The
project consists of [INSERT PROJECT TYPE AND SCOPE]. The site topography is
[INSERT — e.g., relatively flat / gently sloping / variable]. Existing site
conditions include [INSERT — e.g., existing structures, vegetation, fill areas,
evidence of prior grading].
2. SCOPE OF INVESTIGATION
The subsurface investigation consisted of [INSERT NUMBER] soil borings advanced
to depths of [INSERT RANGE] feet below existing grade. Sampling was performed
at [INSERT INTERVALS] using [INSERT SAMPLING METHOD — e.g., Standard Penetration
Test (ASTM D1586), thin-wall tube sampling].
Laboratory testing performed on selected samples included:
- [INSERT LAB TEST TYPES — e.g., grain size analysis, Atterberg limits,
moisture content, consolidation testing, unconfined compressive strength]
3. SUBSURFACE CONDITIONS NARRATIVE
[ALL DEPTHS, THICKNESSES, AND DESCRIPTIONS MUST BE VERIFIED AGAINST ACTUAL
BORING LOGS]
Layer 1 — [INSERT SOIL DESCRIPTION]: Encountered from approximately [INSERT]
to [INSERT] feet below existing grade. [INSERT BLOW COUNTS AND FIELD
OBSERVATIONS FROM BORING LOGS]
Layer 2 — [INSERT SOIL DESCRIPTION]: Encountered from approximately [INSERT]
to [INSERT] feet. [INSERT DESCRIPTION AND FIELD DATA]
[INSERT ADDITIONAL LAYERS AS ENCOUNTERED — VERIFY AGAINST BORING LOGS]
4. GROUNDWATER OBSERVATIONS
Groundwater was encountered at depths of approximately [INSERT ACTUAL GROUNDWATER
DEPTHS FROM BORING LOGS — DO NOT FABRICATE] feet below existing grade during the
investigation. Conditions may vary seasonally. [INSERT ADDITIONAL OBSERVATIONS]
5. ENGINEERING PROPERTIES SUMMARY
[ALL VALUES MUST COME FROM ACTUAL LABORATORY TESTING AND FIELD DATA]
[DO NOT USE THESE PLACEHOLDERS FOR ANY ENGINEERING CALCULATION PURPOSE]
Parameter | Value | Source
----------------------------------|------------------------|------------------
Allowable soil bearing capacity | [INSERT FROM ANALYSIS] | [INSERT]
Internal friction angle (φ) | [INSERT]° | [INSERT]
Cohesion (c) | [INSERT] psf | [INSERT]
Unit weight | [INSERT] pcf | [INSERT]
Liquefaction potential | [INSERT — see analysis]| [INSERT]
6. FOUNDATION RECOMMENDATIONS NARRATIVE
Based on the subsurface conditions encountered, [INSERT FOUNDATION TYPE — e.g.,
conventional spread footings / mat foundation / deep foundation system] is
considered feasible for the proposed structure at this site, subject to the
conditions described in this report. Foundations should be embedded to a minimum
depth of [INSERT FROM GEOTECHNICAL ANALYSIS] feet below [INSERT REFERENCE —
finished grade / existing grade].
[INSERT ADDITIONAL FOUNDATION GUIDANCE — drainage, bearing stratum confirmation,
overexcavation requirements, structural fill as warranted]
7. CONSTRUCTION CONSIDERATIONS
Earthwork: [INSERT — cut/fill requirements, moisture conditioning, compaction
requirements based on actual soil data]
Groundwater Control: [INSERT — dewatering requirements based on groundwater data]
Structural Fill: [INSERT — acceptable fill materials, placement, and compaction]
Special Inspections: [INSERT — verify requirements per IBC with structural EOR
and AHJ]
[ALL GEOTECHNICAL PARAMETERS MUST COME FROM ACTUAL SITE INVESTIGATION DATA]
[DO NOT FABRICATE SOIL PROPERTIES OR BEARING CAPACITIES]
[LICENSED GEOTECHNICAL ENGINEER MUST REVIEW AND STAMP BEFORE ISSUANCE]
[VERIFY ALL CONTENT AGAINST ACTUAL BORING LOGS AND LAB RESULTS]
This prompt is most useful at the report-drafting stage, after boring logs and lab data are in hand. The narrative structure Claude produces absorbs your actual data quickly during the fill-in pass, cutting report production time without compromising the technical integrity of the final document.
3. Permit Package Technical Narrative
Permit submittal narratives serve a specific purpose: they orient the plan checker, document code compliance intent, and summarize the design for the authority having jurisdiction. Claude produces a complete permit narrative with code compliance statements, design parameter summaries, and special inspection notes, with all numerical values and code editions marked as placeholders requiring verification before submission.
Draft a permit package technical narrative for a structural engineering submittal.
Use placeholder values for all design parameters — no actual engineering calculations.
Project type: [e.g., 4-story mixed-use building / commercial tenant improvement /
new single-family residence]
Jurisdiction: [INSERT GENERAL JURISDICTION TYPE — e.g., California Title 24
jurisdiction / general IBC jurisdiction — do not include actual jurisdiction name]
Scope of structural work: [describe scope — e.g., new construction of gravity and
lateral system / structural modifications to existing building / foundation only]
Applicable codes: [INSERT ADOPTED CODE EDITIONS — verify with AHJ]
Key design parameters: [INSERT FROM CALCULATIONS — or use placeholders]
Structure the narrative as follows:
1. PROJECT DESCRIPTION
2. SCOPE AND INTENT
3. CODE COMPLIANCE STATEMENT
List applicable codes and standards.
[VERIFY ADOPTED CODES WITH AUTHORITY HAVING JURISDICTION BEFORE SUBMISSION]
4. DESIGN PARAMETERS SUMMARY
Risk/occupancy category, seismic design category, wind design parameters,
soil parameters. All values: [INSERT FROM CALCULATIONS — VERIFY WITH AHJ]
5. STRUCTURAL SYSTEM DESCRIPTION
6. SPECIAL INSPECTIONS
[VERIFY SPECIAL INSPECTION REQUIREMENTS WITH AHJ BEFORE SUBMISSION]
7. STRUCTURAL NOTES SUMMARY
[VERIFY ALL CODE REFERENCES WITH AUTHORITY HAVING JURISDICTION BEFORE SUBMISSION]
[ALL DESIGN VALUES ARE PLACEHOLDERS — MUST BE CONFIRMED BY LICENSED PE]
[DO NOT SUBMIT WITHOUT PE STAMP AND SIGNATURE]
STRUCTURAL PERMIT NARRATIVE — DRAFT
[PROJECT NAME — PLACEHOLDER] | [PERMIT NUMBER — PLACEHOLDER]
Prepared by: [ENGINEER OF RECORD — NAME AND LICENSE NUMBER — PLACEHOLDER]
Date: [INSERT]
[DO NOT SUBMIT WITHOUT PE STAMP AND SIGNATURE]
[VERIFY ALL CODE REFERENCES WITH AUTHORITY HAVING JURISDICTION]
---
1. PROJECT DESCRIPTION
The proposed project consists of [INSERT PROJECT TYPE AND USE — e.g., a four-story
mixed-use building with ground-floor commercial and three levels of residential
above]. The structure is approximately [INSERT GROSS AREA — PLACEHOLDER] square
feet, [INSERT HEIGHT — PLACEHOLDER] stories. Construction type is [INSERT PER IBC].
2. SCOPE AND INTENT
This structural permit package includes design documents and calculations for:
- [INSERT SCOPE ITEM 1 — e.g., Foundations and grade beams]
- [INSERT SCOPE ITEM 2 — e.g., Gravity framing system — floor and roof]
- [INSERT SCOPE ITEM 3 — e.g., Lateral force-resisting system]
- [INSERT ADDITIONAL SCOPE ITEMS AS APPLICABLE]
3. CODE COMPLIANCE STATEMENT
The structural design is in accordance with the following codes and standards, as
adopted by the authority having jurisdiction.
[VERIFY ADOPTED CODE EDITIONS WITH AHJ BEFORE SUBMISSION]
- Building Code: [INSERT EDITION — IBC or local equivalent]
- Structural Loads: [INSERT EDITION — e.g., ASCE 7]
- Concrete: [INSERT EDITION — e.g., ACI 318 — if applicable]
- Steel: [INSERT EDITION — e.g., AISC 360 — if applicable]
- Wood: [INSERT EDITION — e.g., NDS — if applicable]
4. DESIGN PARAMETERS SUMMARY
[ALL VALUES ARE PLACEHOLDERS — INSERT FROM CALCULATIONS AND VERIFY WITH AHJ]
Risk Category: [INSERT]
Occupancy: [INSERT]
Seismic Design Category (SDC): [INSERT — VERIFY AGAINST ASCE 7 AND SITE DATA]
Basic Wind Speed (Vult): [INSERT] mph [VERIFY AGAINST CURRENT WIND MAPS]
Wind Exposure Category: [INSERT]
Soil Site Class: [INSERT — VERIFY AGAINST GEOTECHNICAL REPORT]
Allowable Soil Bearing Pressure: [INSERT] psf [VERIFY AGAINST GEOTECH REPORT]
5. STRUCTURAL SYSTEM DESCRIPTION
Gravity System: [INSERT — describe floor framing, roof framing, columns, walls,
foundation type and depth]
Lateral Force-Resisting System (LFRS): [INSERT — describe shear wall locations,
frame types, or other LFRS elements; note any irregularities]
6. SPECIAL INSPECTIONS
The following special inspections are required per IBC and project specifications.
Verify requirements with the authority having jurisdiction.
[VERIFY SPECIAL INSPECTION REQUIREMENTS WITH AHJ BEFORE SUBMISSION]
- Concrete: [INSERT — e.g., continuous special inspection of concrete placement
for [element types]]
- Reinforcement: [INSERT — periodic inspection of reinforcing placement]
- [INSERT ADDITIONAL SI ITEMS — e.g., steel, masonry, soils, high-strength bolts,
welding, as applicable]
A Special Inspection Program will be submitted as required by the AHJ.
7. STRUCTURAL NOTES SUMMARY
Key structural notes governing construction are listed on the structural drawings:
- [INSERT STRUCTURAL NOTE 1 — e.g., All concrete shall achieve minimum f'c =
[INSERT] psi at 28 days per specifications]
- [INSERT STRUCTURAL NOTE 2]
- [INSERT ADDITIONAL NOTES — refer to structural drawing notes sheet]
[VERIFY ALL CODE REFERENCES WITH AUTHORITY HAVING JURISDICTION BEFORE SUBMISSION]
[ALL DESIGN VALUES ARE PLACEHOLDERS — MUST BE CONFIRMED BY LICENSED PE]
[DO NOT SUBMIT WITHOUT PE STAMP AND SIGNATURE]
The permit narrative prompt works best when you have completed your calculations and can replace the placeholders with actual design parameters before the PE review. A well-organized narrative reduces first-round plan check comments on administrative items and lets the structural review focus on the engineering.
4. Construction Administration Correspondence
Construction administration generates a consistent stream of written documents: RFI responses, field observation reports, non-conformance notices, change order justifications, and substantial completion letters. Each type has distinct format and tone requirements. The prompt below generates all five CA document types in one session — useful when setting up template language for a project or clearing a CA backlog.
Generate construction administration correspondence templates for the project below.
Use placeholder information throughout — no real project numbers, client names,
or proprietary data.
Project description: [INSERT — e.g., 3-story office building, steel moment frame]
Engineer of record: [PLACEHOLDER]
Contractor: [PLACEHOLDER]
Project number: [PLACEHOLDER]
Generate all five document templates below. For each, produce a complete,
professionally formatted, ready-to-edit structure. Mark all fields requiring
project-specific input with [INSERT] or [ENGINEER OF RECORD TO COMPLETE].
---
TEMPLATE 1: RFI RESPONSE LETTER
Sections: Date / RFI Number / Project number / RFI Subject / Contractor's
question (paraphrase) / Engineering Response [ENGINEER OF RECORD TO COMPLETE]
/ Conditions or Clarifications / Drawing and Spec references affected [INSERT]
/ PE Signature Block [PE SIGNATURE REQUIRED BEFORE ISSUING]
TEMPLATE 2: FIELD OBSERVATION REPORT
Sections: Project / Date [INSERT] / Time [INSERT] / Weather [INSERT] / Site
contact [INSERT] / Work observed [INSERT] / Conformance observations /
Items Requiring Attention (numbered list) / Follow-up required [INSERT] /
Next scheduled visit [INSERT] / PE signature block
TEMPLATE 3: STRUCTURAL NON-CONFORMANCE NOTICE
Formal written notice — factual, no editorializing.
Sections: Date / Notice Number / To: Contractor / From: EOR /
Description of Non-Conformance [INSERT — objective, with drawing/spec ref] /
Required Corrective Action [INSERT] / Required Documentation /
Response Deadline [INSERT] / Distribution
[DISTRIBUTE ONLY AFTER PE REVIEW AND AUTHORIZATION]
TEMPLATE 4: CHANGE ORDER TECHNICAL JUSTIFICATION
Sections: Date / Change Order Number / Description of Change [INSERT] /
Technical Basis [INSERT — engineering justification] /
Code / Design References [INSERT — VERIFY ALL REFERENCES] /
Impact on Structural System [INSERT] /
Cost / Schedule Impact Narrative [CONFIRM WITH CONTRACTOR — placeholder only]
[VERIFY ALL CODE AND DESIGN REFERENCES BEFORE ISSUING]
TEMPLATE 5: SUBSTANTIAL COMPLETION / PUNCH LIST COVER LETTER
Sections: Date / To: Owner / From: EOR / Project Summary /
Basis of Substantial Completion Determination [INSERT] /
Outstanding Items — Punch List [INSERT ACTUAL PUNCH LIST — do not fabricate] /
PE Observations [ENGINEER OF RECORD TO COMPLETE] /
Next Steps / PE Signature Block
[ALL CA DOCUMENTS MUST BE REVIEWED AND ISSUED BY THE ENGINEER OF RECORD]
[NO CA DOCUMENT MAY BE ISSUED WITHOUT PE REVIEW AND SIGNATURE]
RFI RESPONSE — REPRESENTATIVE TEMPLATE
(Generate the full five-template set using the prompt above)
Project: [PROJECT NAME — PLACEHOLDER] Date: [INSERT]
Project No.: [PLACEHOLDER] RFI No.: [INSERT]
From: [ENGINEER FIRM — PLACEHOLDER] To: [CONTRACTOR — PLACEHOLDER]
Re: [RFI SUBJECT — INSERT BRIEF DESCRIPTION]
[PE SIGNATURE REQUIRED BEFORE ISSUING TO CONTRACTOR]
CONTRACTOR'S QUESTION:
[Paraphrase of the contractor's RFI question — INSERT]
ENGINEERING RESPONSE:
[ENGINEER OF RECORD TO COMPLETE — Insert technical response or clarification here.
Do not leave placeholder text in issued document.]
CONDITIONS AND CLARIFICATIONS:
[INSERT any limitations on this response — e.g., "This response addresses the
condition as described in the RFI. If field conditions differ, contact the
engineer prior to proceeding."]
DRAWING / SPECIFICATION REFERENCES AFFECTED:
[INSERT — e.g., S-201, S-301; Spec Section 03 30 00 — or "None"]
ATTACHMENTS: [INSERT — sketches, revised details, or "None"]
_______________________________________________
[ENGINEER NAME], PE | License No.: [INSERT]
[FIRM NAME] | Date: [INSERT]
[PE SIGNATURE REQUIRED BEFORE ISSUING]
[ALL CA DOCUMENTS MUST BE REVIEWED AND ISSUED BY THE ENGINEER OF RECORD]
---
FIELD OBSERVATION REPORT — TEMPLATE
Project: [PROJECT NAME — PLACEHOLDER] Report No.: [INSERT]
Date of Visit: [INSERT] Time: [INSERT]
Weather: [INSERT] Site Contact: [INSERT]
Work Observed:
[INSERT — describe structural work in place and in progress at time of visit]
Conformance Observations:
[General conformance with contract documents was observed / The following
items were noted for contractor attention:]
Items Requiring Attention:
1. [INSERT — Location: [INSERT]. Observation: [INSERT]. Required Action: [INSERT].]
2. [INSERT]
[ADD ITEMS AS OBSERVED — NUMBER SEQUENTIALLY]
Follow-up Required:
[INSERT — reinspection required / contractor response required by [DATE]]
Next Scheduled Visit: [INSERT]
_______________________________________________
[ENGINEER NAME], PE | Date: [INSERT]
[ALL CA DOCUMENTS MUST BE REVIEWED AND ISSUED BY THE ENGINEER OF RECORD]
The five-template CA set is most efficient to set up at project kickoff — establish the template language and placeholder structure once, then reuse each template throughout the construction phase. Project managers coordinate the overall project documentation flow; the CA correspondence lane is specific to the engineer of record and requires PE review before anything is issued.
5. Engineering Specification Section Drafting
Writing a specification section from scratch — or tailoring an existing section for a project with specific material requirements — is time-consuming detail work. The 3-part CSI MasterFormat structure is consistent, but the technical content varies by project type, design requirements, and applicable standards. Claude produces a complete 3-part spec section with placeholder brackets for all project-specific values and standards references flagged for edition verification.
Draft a CSI MasterFormat 3-part specification section using the inputs below.
Use placeholder brackets for all project-specific values and material specifications.
Flag all standards references for edition verification.
Spec section number and title: [e.g., 03 30 00 Cast-in-Place Concrete /
05 12 00 Structural Steel Framing / 31 23 00 Excavation and Fill]
Project type: [INSERT]
Key material requirements: [INSERT PROJECT-SPECIFIC REQUIREMENTS — e.g.,
"f'c = [INSERT] psi / ASTM A36 structural steel / Class [INSERT] structural fill"]
Applicable standards: [INSERT STANDARDS USED — or use [INSERT STANDARDS USED]]
Special requirements: [INSERT — e.g., exposure conditions, durability requirements,
sustainability specs — or "none"]
Structure the output as a complete 3-part CSI MasterFormat section:
PART 1 — GENERAL
1.01 SCOPE OF WORK
1.02 RELATED SECTIONS: [INSERT RELATED SECTION NUMBERS]
1.03 REFERENCES — mark each standard: [VERIFY CURRENT EDITION]
1.04 SUBMITTALS — required submittals list
1.05 QUALITY ASSURANCE — qualification requirements, testing agency
PART 2 — PRODUCTS
2.01 MATERIALS — [INSERT PROJECT-SPECIFIC VALUES throughout — do not
fabricate performance values or omit placeholders]
2.02 FABRICATION (if applicable)
PART 3 — EXECUTION
3.01 INSTALLATION / CONSTRUCTION
3.02 FIELD QUALITY CONTROL
3.03 INSPECTION
[VERIFY ALL REFERENCED STANDARDS AGAINST CURRENT PUBLISHED EDITIONS]
[ALL MATERIAL SPECIFICATIONS MUST BE CONFIRMED BY ENGINEER OF RECORD]
[DO NOT INCORPORATE INTO CONTRACT DOCUMENTS WITHOUT PE REVIEW AND APPROVAL]
SECTION 03 30 00 — CAST-IN-PLACE CONCRETE
[DRAFT — FOR REVIEW ONLY — DO NOT INCORPORATE INTO CONTRACT DOCUMENTS
WITHOUT PE REVIEW AND APPROVAL]
PART 1 — GENERAL
1.01 SCOPE OF WORK
A. Provide cast-in-place concrete for all elements shown on structural drawings,
including [INSERT — e.g., footings, grade beams, slabs on grade, elevated slabs].
B. Related work not included: [INSERT — e.g., architectural concrete formwork].
1.02 RELATED SECTIONS
A. Section [INSERT] — Reinforcing Steel
B. Section [INSERT] — Concrete Formwork
C. [INSERT ADDITIONAL RELATED SECTIONS]
1.03 REFERENCES
[VERIFY CURRENT EDITION OF ALL STANDARDS LISTED BELOW]
A. ACI 301 — Specifications for Structural Concrete — [VERIFY CURRENT EDITION]
B. ACI 318 — Building Code Requirements for Structural Concrete — [VERIFY CURRENT EDITION]
C. ASTM C31 — Making and Curing Concrete Test Specimens — [VERIFY CURRENT EDITION]
D. ASTM C33 — Concrete Aggregates — [VERIFY CURRENT EDITION]
E. ASTM C39 — Compressive Strength of Cylindrical Specimens — [VERIFY CURRENT EDITION]
F. ASTM C94 — Ready-Mixed Concrete — [VERIFY CURRENT EDITION]
G. ASTM C150 — Portland Cement — [VERIFY CURRENT EDITION]
H. [INSERT ADDITIONAL APPLICABLE STANDARDS]
1.04 SUBMITTALS
A. Concrete mix design(s) for each concrete class specified.
B. Admixture product data sheets.
C. Aggregate test reports from approved source.
D. [INSERT ADDITIONAL SUBMITTAL REQUIREMENTS]
1.05 QUALITY ASSURANCE
A. Concrete producer: [INSERT — e.g., NRMCA-certified plant]
B. Testing agency: Owner-furnished, independent of contractor.
[INSERT TESTING AGENCY QUALIFICATION REQUIREMENTS]
PART 2 — PRODUCTS
[ALL VALUES IN THIS SECTION ARE PLACEHOLDERS — INSERT PROJECT-SPECIFIC REQUIREMENTS]
[DO NOT USE PLACEHOLDER VALUES IN ISSUED CONTRACT DOCUMENTS]
2.01 MATERIALS
A. Cement: Portland cement conforming to ASTM C150 [VERIFY EDITION], Type [INSERT].
B. Aggregates: Conforming to ASTM C33 [VERIFY EDITION].
Maximum aggregate size: [INSERT — verify per ACI 318 for member dimensions]
C. Water: Potable, free from injurious substances.
D. Admixtures (if used):
Water-reducing: [INSERT — ASTM C494, Type [INSERT] — if applicable]
Air-entraining: [INSERT — ASTM C260 — if applicable; required for exposed
concrete in freeze-thaw environments]
E. Reinforcing steel: Per Section [INSERT].
2.02 CONCRETE MIX DESIGN
[ALL MIX DESIGN PARAMETERS ARE PLACEHOLDERS — CONFIRM WITH CONCRETE PRODUCER
AND VERIFY AGAINST ACI 318 EXPOSURE REQUIREMENTS]
Class | Location | f'c (28-day) | Max w/cm | Air
------|--------------------|---------------|----------|--------
[INS] | [INSERT ELEMENTS] | [INSERT] psi | [INSERT] | [INS]%
[INS] | [INSERT ELEMENTS] | [INSERT] psi | [INSERT] | [INS]%
PART 3 — EXECUTION
3.01 INSTALLATION
A. Formwork: Per ACI 347 [VERIFY EDITION]. Min. stripping times: [INSERT]
B. Reinforcement: Per structural drawings and ACI 318 [VERIFY EDITION].
Concrete cover: [INSERT] in. [VERIFY AGAINST STRUCTURAL DRAWINGS AND ACI 318]
C. Placement: Per ACI 301 [VERIFY EDITION].
[INSERT SPECIAL REQUIREMENTS — hot/cold weather, pump placement, as applicable]
D. Curing: Per ACI 308 [VERIFY EDITION], minimum [INSERT] days.
3.02 FIELD QUALITY CONTROL
A. Compressive strength cylinders: [INSERT] sets per [INSERT FREQUENCY].
Slump, air content, and temperature: [INSERT FREQUENCY]
B. Failing tests: [INSERT PROCEDURE FOR NON-CONFORMING RESULTS]
3.03 INSPECTION
A. Special inspection per IBC and project Special Inspection Program.
[VERIFY SPECIAL INSPECTION REQUIREMENTS WITH ENGINEER OF RECORD AND AHJ]
[VERIFY ALL REFERENCED STANDARDS AGAINST CURRENT PUBLISHED EDITIONS]
[ALL MATERIAL SPECIFICATIONS MUST BE CONFIRMED BY ENGINEER OF RECORD]
[DO NOT INCORPORATE INTO CONTRACT DOCUMENTS WITHOUT PE REVIEW AND APPROVAL]
END OF SECTION 03 30 00
The spec section output is a draft framework. Material values, exposure class requirements, mix design parameters, and special inspection requirements all require the engineer of record to insert project-specific data and verify against current code requirements. Technical writers who work in AEC may encounter this CSI format; the 3-part structure is specific to construction contract documents and differs significantly from software or product documentation.
6. Technical Report Writing: Feasibility, Condition Assessment, and Alternatives Analysis
Feasibility studies, facility condition assessments, and alternatives analyses require consistent structure and substantial prose writing. The findings and analysis sections — translating site observations or study data into readable engineering narrative — are time-intensive. Claude takes your study inputs and produces a complete technical report structure with placeholders throughout, letting you focus your writing time on the sections that require engineering judgment.
Draft a technical engineering report using the inputs below.
Use placeholder brackets for all quantitative data, findings, and recommendations —
no fabricated cost estimates, performance metrics, or engineering conclusions.
Study type: [feasibility study / condition assessment / alternatives analysis]
Project description: [INSERT — e.g., "Evaluation of three bridge repair alternatives
for a 1960s-era highway overpass" / "Condition assessment of municipal water
storage tank" / "Feasibility of industrial site development"]
Evaluation criteria: [INSERT CRITERIA — e.g., structural adequacy, service life,
cost-effectiveness, constructability, environmental impact]
Findings summary: [INSERT ACTUAL FINDINGS — or [INSERT ACTUAL FINDINGS FROM
SITE INVESTIGATION] if study is in progress]
Alternatives: [INSERT 2–3 ALTERNATIVES — brief description of each]
Structure the report as follows:
1. EXECUTIVE SUMMARY (3–5 bullet points)
2. PROJECT BACKGROUND AND SCOPE
3. METHODOLOGY — site visits, data collection, analysis methods
4. FINDINGS AND ANALYSIS
[INSERT ACTUAL DATA AND ANALYSIS — placeholder for all quantitative values]
5. ALTERNATIVES COMPARISON
Qualitative table: Alternative | Criterion 1 | Criterion 2 | Criterion N
[DO NOT FABRICATE COST ESTIMATES OR PERFORMANCE METRICS — qualitative only]
6. RECOMMENDATIONS
[ENGINEER OF RECORD TO COMPLETE — Claude provides structure, not conclusions]
7. LIMITATIONS AND ASSUMPTIONS
8. REFERENCES
[ALL QUANTITATIVE DATA MUST COME FROM ACTUAL SITE INVESTIGATION AND ANALYSIS]
[DO NOT FABRICATE COST ESTIMATES, PERFORMANCE METRICS, OR ENGINEERING CONCLUSIONS]
[PEER REVIEW RECOMMENDED BEFORE CLIENT DELIVERY]
[PROJECT NAME — PLACEHOLDER] | [REPORT TITLE]
Prepared for: [CLIENT — PLACEHOLDER]
Prepared by: [ENGINEER / FIRM — PLACEHOLDER]
Date: [INSERT] | Report No.: [INSERT]
[DRAFT — FOR REVIEW ONLY — PEER REVIEW RECOMMENDED BEFORE CLIENT DELIVERY]
[ALL QUANTITATIVE DATA MUST COME FROM ACTUAL SITE INVESTIGATION AND ANALYSIS]
---
EXECUTIVE SUMMARY
• [INSERT FINDING 1 — e.g., "The facility was assessed as [INSERT CONDITION
RATING] based on [INSERT BASIS OF ASSESSMENT]"]
• [INSERT FINDING 2]
• [INSERT ALTERNATIVES SUMMARY — e.g., "Three alternatives were evaluated;
[INSERT PREFERRED ALTERNATIVE] is recommended based on [INSERT CRITERIA]"]
• [INSERT KEY CONSTRAINT OR RISK]
• [INSERT ACTION ITEM OR NEXT STEP]
1. PROJECT BACKGROUND AND SCOPE
[INSERT PROJECT DESCRIPTION — project history, context, reason for the study]
The scope of this [feasibility study / condition assessment / alternatives analysis]
includes:
- [INSERT SCOPE ITEM 1]
- [INSERT SCOPE ITEM 2]
- [INSERT SCOPE ITEM 3]
This report does not include: [INSERT EXCLUSIONS — scope limitations, deferred studies].
2. METHODOLOGY
[INSERT — describe how the study was conducted: site visit dates, access conditions,
data collection methods, reference documents reviewed, analysis software used,
standards applied]
Data sources:
- [INSERT — e.g., as-built drawings, previous reports, inspection data]
- [INSERT]
3. FINDINGS AND ANALYSIS
[INSERT ACTUAL DATA AND ANALYSIS — Claude provides structure only]
[ALL QUANTITATIVE VALUES MUST COME FROM ACTUAL INVESTIGATION AND ANALYSIS]
3.1 [INSERT SUBSECTION — e.g., Structural Condition / Existing Facility Assessment]
[INSERT FINDINGS NARRATIVE — reference actual inspection data, test results,
or analysis output. Mark all values: [INSERT FROM INVESTIGATION DATA]]
3.2 [INSERT SUBSECTION — repeat as needed]
[INSERT ADDITIONAL FINDINGS AS WARRANTED BY SCOPE]
4. ALTERNATIVES COMPARISON
[QUALITATIVE COMPARISON ONLY — DO NOT FABRICATE COST ESTIMATES OR PERFORMANCE VALUES]
Alternative | [Criterion 1] | [Criterion 2] | [Criterion 3] | Notes
-----------------|-------------------|----------------|----------------|-------
Alt. 1: [INSERT] | [INSERT — qual.] | [INSERT] | [INSERT] | [INSERT]
Alt. 2: [INSERT] | [INSERT — qual.] | [INSERT] | [INSERT] | [INSERT]
Alt. 3: [INSERT] | [INSERT — qual.] | [INSERT] | [INSERT] | [INSERT]
Cost estimates must be prepared by a qualified cost estimator and are not included
in this structure. [DO NOT FABRICATE COST ESTIMATES OR PERFORMANCE METRICS]
5. RECOMMENDATIONS
[ENGINEER OF RECORD TO COMPLETE — based on actual findings and engineering judgment.
Claude provides structure; recommendations require professional engineering review.]
Based on the findings and alternatives evaluation, [INSERT RECOMMENDATION AND
RATIONALE — engineer of record to complete].
Recommended next steps:
1. [INSERT — e.g., Preliminary design of recommended alternative]
2. [INSERT — e.g., Additional investigation to address [specific data gap]]
3. [INSERT ADDITIONAL NEXT STEPS]
6. LIMITATIONS AND ASSUMPTIONS
- [INSERT — e.g., "Report is based on visual observation and available as-built
drawings. No destructive investigation was performed."]
- [INSERT ASSUMPTION / LIMITATION 2]
- [INSERT ADDITIONAL LIMITATIONS]
7. REFERENCES
1. [INSERT — Title, author, date, document number]
2. [INSERT]
[ALL QUANTITATIVE DATA MUST COME FROM ACTUAL SITE INVESTIGATION AND ANALYSIS]
[DO NOT FABRICATE COST ESTIMATES, PERFORMANCE METRICS, OR ENGINEERING CONCLUSIONS]
[PEER REVIEW RECOMMENDED BEFORE CLIENT DELIVERY]
The technical report structure is designed to be completed in a single editing pass: replace every [INSERT] with your actual findings, plug in the quantitative data from your site investigation and analysis, and the document is ready for PE review. The qualitative-only alternatives comparison table is intentional — cost estimates belong in a separate cost study with appropriate assumptions documented, not embedded in a placeholder column.
Why Claude Over ChatGPT for Engineering Documentation
The Claude vs. ChatGPT comparison covers the general case. For civil and structural engineering documentation specifically, a few points are worth calling out.
Projects keep design criteria and code basis persistent. Claude's Projects feature lets you create a dedicated workspace per project type — a "Structural Permit Documents" project or a "Bridge Condition Assessment" project. Within a project, your code editions, design criteria, and standard language stay loaded across sessions. That matters when you are producing multiple documents for the same project: the calculation narrative, the permit narrative, the spec sections, and the CA correspondence templates can all draw from the same project context without re-entering the code basis each time.
Structured output discipline for CA correspondence. Proper RFI response format, non-conformance notice structure, field observation report layout — Claude applies consistent structure across every CA document type. ChatGPT has a tendency to prose-ify document types that should be structured, producing output that is less usable as a template and less professional when issued.
Conservative on code citations. ChatGPT is documented for confidently fabricating code section numbers, table values, and standards references that don't exist. Claude is more conservative on fabricated code citations — not immune to hallucination, but less likely to invent an ASCE 7 table number or ACI 318 section that doesn't exist. For engineering documentation, where a wrong code citation is a professional liability issue, that behavioral difference is meaningful.
No internet access means use Claude for drafting, not code research. Claude cannot look up current code editions, retrieve USGS seismic hazard data, access AASHTO standards, or check any real-time engineering reference. For code lookup and standards research, use your engineering references directly. For documentation drafting — turning your engineering work into organized, professionally formatted narratives and correspondence — Claude's structured output quality is the relevant capability.
4 Practical Tips for Civil and Structural Engineers Using Claude
1. One Project per project type, not per job. Set up Claude Projects organized around document type or project phase: "Structural Permit Documents," "Geotechnical Report Narratives," "CA Correspondence Templates." Load your code basis, standard language, and design criteria once per project; reuse across all documents in that workspace. This is more efficient than per-job projects and avoids accumulating confidential project data in the tool.
2. Never input real project data. Real client names, actual project addresses, proprietary structural calculation results, actual boring log data, or any confidential project information should not be pasted into Claude. Use placeholder brackets throughout. The workflow is consistent: Claude drafts the structure and language, you insert verified project data at the PE review step.
3. Use Claude for document structure; insert your calculated values yourself. Claude produces the narrative framework, section headers, placeholder tables, and standard language. Your job is to replace every [INSERT] and [PLACEHOLDER] with data from your actual calculations, site investigation, and engineering analysis. The document only becomes an engineering deliverable when your verified technical data is in it.
4. Every output is a working draft. All reports, specification sections, permit narratives, and CA documents produced using these prompts are first drafts. They require PE review, verification of all technical content and code references, licensed professional signature, and — where applicable — official stamp before they are issued, submitted, or incorporated into any project document. That requirement does not change based on how polished the first draft looks. For a deeper look at building this kind of systematic workflow, the Claude AI prompts post covers the underlying system.
Get the Complete Claude Playbook
If you're serious about using Claude for engineering documentation, the Complete Claude Playbook covers the exact system — how to set up Projects, build reusable templates, and get consistent professional output every time. $27, instant PDF download.