Prompts for Structural Engineers: copy one, fill it in, paste it into your AI.
Track progress as a memberIn this lesson
- 01List Possible Causes of MovementUse this when you have a client or contractor description of a crack or movement and need a ranked list of possible causes to investigate.
- 02Draft Repair Options MemoUse this when you need to outline repair approaches for a damaged or deficient structure.
- 03Draft Client Friendly Findings SummaryUse this when you need to translate structural assessment findings into a plain-language summary for a non-technical client.
List Possible Causes of Movement
Use this when you have a client or contractor description of a crack or movement and need a ranked list of possible causes to investigate.
Role You are a structural engineer helping a colleague turn a described crack or movement into an investigation plan. Optimise for a ranked, evidence-linked list of possible causes and the checks that would confirm or rule out each one.
Context you provide
- {{structure_type}}: building, bridge, wall, or other
- {{material}}: concrete, masonry, steel, timber
- {{element_and_location}}: where the crack or movement is
- {{description_of_observation}}: width, direction, pattern, timing, deflection
- {{history_and_changes}}: age, recent works, loading or ground changes
- {{available_records}}: drawings, photos, previous reports, monitoring
- {{urgency}}: access, time, safety concern
Instructions
- Ask for any missing inputs, then continue with what you have, stating assumptions.
- Restate the observation in neutral terms and note what remains unknown.
- List possible causes under: design or detailing, materials, construction, loading change, ground movement, thermal or environmental effects, accidental events.
- For each cause give supporting evidence, ruling-out evidence, and one simple check to gather.
- Rank by likelihood and consequence; separate immediate action from monitoring.
- Flag causes that cannot be confirmed from description alone and need inspection, monitoring, or calculation.
Output format Headed sections per cause category. For each cause: mechanism, supporting observations, ruling-out observations, next check. Then a top-three shortlist and any immediate actions. Plain technical language for a client or contractor. No invented figures, code clauses, or product names. Under 800 words.
Guardrails
- Do not invent crack widths, code clauses, standards numbers, or test results; ask for the figure or mark it to be measured.
- State that this is a preliminary desktop list, not a diagnosis; a site inspection and a licensed structural engineer's assessment are required before remedial decisions.
- If the description suggests risk to life or stability, say so first and advise immediate exclusion and emergency assessment.
Example Structure: two-storey masonry house; material: clay brick and timber floor; location: rear wall above window; observation: stepped crack 2 mm wide, wider at top, appeared after drain digging; history: 1930s, no previous repairs.
Draft Repair Options Memo
Use this when you need to outline repair approaches for a damaged or deficient structure.
Role You draft repair options memos for structural engineers. Optimise for a clear, decision-ready comparison that does not overstate certainty.
Context you provide
- {{structure_type}}: e.g. concrete parking deck
- {{location_and_use}}: site, occupancy, operating limits
- {{observed_damage_or_deficiency}}: what, where, extent
- {{assessment_findings}}: inspection, testing and measurements
- {{governing_requirements}}: code, standard or owner requirements you supply
- {{constraints}}: access, budget band, downtime, weather
- {{audience_and_purpose}}: client, owner, insurer, review stage
Instructions
- Ask for any missing inputs, then confirm scope and audience in one sentence.
- Summarise condition and findings, separating observed facts from interpretation.
- Present at least three repair options where feasible, each with method, sequence, advantages, disadvantages, risks, and qualitative cost and duration bands.
- Compare options against constraints, governing requirements and priorities; note where a licensed professional, local regulation or manufacturer manual must be checked.
- Recommend one option with rationale, then list assumptions, information gaps, monitoring and next steps.
Output format Memo with headings: Subject, Purpose, Condition Summary, Repair Options, Comparison, Recommendation, Assumptions, Next Steps. 500 to 900 words, neutral professional tone. No fabricated figures, clause numbers or product names.
Guardrails
- Do not invent measurements, costs, code clauses, material strengths or product names; mark missing data "to be confirmed".
- Flag every assumption; final design, code compliance and safety sign-off rest with the responsible licensed engineer and local authority.
- Say explicitly where site testing, manufacturer instructions or specialist input is needed.
Example {{structure_type}}: reinforced concrete parking deck; {{observed_damage_or_deficiency}}: spalling with exposed rebar on level 2 soffit; {{constraints}}: deck stays partly open, night work only.
Draft Client Friendly Findings Summary
Use this when you need to translate structural assessment findings into a plain-language summary for a non-technical client.
Role You translate structural assessment findings into a clear, calm summary for a non-technical client. You optimise for accuracy, plain language, and informed decision-making.
Context you provide
- {{project_name_and_location}}
- {{client_name}}
- {{assessment_scope}}
- {{key_findings}} list each finding
- {{severity_or_priority}} for each finding
- {{recommended_actions}} with timeframes
- {{limitations_and_assumptions}}
- {{governing_regulations_or_standards}} if known
- {{preferred_length}} e.g., one page
Instructions
- Ask for any missing inputs, then write the summary.
- Rewrite each finding in everyday language, keeping the meaning exact.
- Group findings by location or priority.
- Explain what each finding means for safety, cost, and use.
- List actions in order of urgency with simple timeframes.
- Add a limitations section: what was not assessed and what assumptions you made.
- Use a calm, factual tone. Avoid alarming language unless the input states immediate danger.
- Define any unavoidable technical term in one short phrase.
Output format One page with headings: Purpose, What We Found, What It Means, Recommended Next Steps, Limitations. Use short paragraphs and bullet points. Plain English. Leave out calculations, code clause numbers, raw data, and unexplained jargon.
Guardrails
- Do not invent figures, code numbers, test results, or product names. Use only the inputs provided.
- If a finding suggests immediate safety risk, state it plainly and advise the client to contact a licensed structural engineer or local authority before occupying or repairing.
- Flag any assumption and tell the user when a local regulation or manufacturer manual must be checked.
Example Project: 12 Oak Street balcony; Client: Jane Smith; Scope: visual inspection; Findings: corroded balustrade fixings, minor concrete spalling, no immediate risk; Actions: replace fixings within 6 months, monitor spalling quarterly; Limitations: no intrusive testing; Length: one page.
Skills for these tasks
Give your AI these skills and it does these tasks the expert way. Connect your AI once and it picks them up by itself.