Artificial Intelligence (AI) is increasingly part of the engineer’s toolkit. Not because it replaces engineers, but because it helps us make better decisions faster, especially when working under pressure, with complex regulations, or constrained resources.

This guide introduces the principles and practices of using general-purpose AI tools (such as ChatGPT, Bing, Claude, Bard and ChatPDF) in a responsible, professional and compliant way across engineering disciplines in Aotearoa.

On this page:

The role of AI in engineering practice

AI is best seen as an assistant, not a decision-maker.

It can:

  • Summarise long technical reports, standards, or site logs
  • Suggest corrective actions based on incident data or historical failures
  • Perform repetitive calculations, like factored loads or infiltration rates
  • Draft risk reports, safety summaries, or compliance statements
  • Check for overlooked load combinations or code clauses
  • Interpret council guidance or Building Code clauses when uploaded

AI can't:

  • Make engineering judgments
  • Sign off work
  • Automatically ensure code compliance
  • Replace site investigation, physical inspection, or peer review

Used appropriately, AI tools help engineers focus on complex reasoning and creative problem-solving, while reducing the time spent on mechanical tasks like document searching or first-draft preparation.

Guidance for integrating AI tools into your practice

Start with clear intent and good prompts
AI works best when you are precise. Always:

  • Set the context (e.g. “You are reviewing a fire incident for New Zealand compliance.”)
    Include relevant data or excerpts (e.g. your load combination sheet or percolation test results)
  • Be specific (e.g. “Check if this matches NZS 1170 ultimate limit state combos.”)
  • Ask for structure (e.g. “Provide in bullet points” or “Include clause references.”)

Good prompting turns AI from a generic chatbot into a capable assistant aligned to your task.

Stay grounded in New Zealand codes and standards
AI can hallucinate or oversimplify. It may invent clauses or misquote data unless grounded in the actual document.

  • Use tools like ChatPDF, Claude, or Gemini to:
  • Upload New Zealand standards or Building Code excerpts
  • Ask for citations from within the actual document
  • Cross-check AI suggestions with the official wording

Always read the referenced clause yourself before accepting a recommendation.

Maintain professional oversight and ethical control
Treat AI like a junior colleague:

  • Review all outputs before use
  • Correct factual errors or oversights
  • Add contextual knowledge the AI might not have (e.g. site-specific risks, past failures, soil conditions)


Never:

  • Input confidential client data into public AI tools
  • Rely solely on AI for code compliance or safety assessments
  • Use AI to generate false, misleading, or fictitious content

Follow your company’s policies on data handling and seek client consent before using AI on project data.

Use AI to support, not skip, critical engineering steps

AI can support:

  • Drafting sections of technical reports
  • Generating checklists
  • Interpreting historical maintenance logs
  • Creating calculation templates

AI cannot replace:

  • Geotechnical judgement in soak pit siting
  • Manual review of incident trends for root cause analysis
  • Physical inspection of asset deterioration
  • Confirmation that control systems meet performance requirements

Engineers must verify all key outputs and remain liable for decisions under the Building Act, HSWA 2015 and Engineering New Zealand Code of Ethical Conduct.

Working with New Zealand standards in AI tools (July 2025)

  1. No automatic right to upload standards
    Buying a PDF or hard-copy standard gives you a reading licence only. Copyright in every NZS remains with Standards New Zealand (SNZ); joint AS/NZS titles are co-owned with Standards Australia. You may not reproduce, store, or upload any part of a standard to any third-party platform, including private or “internal-only” AI tools, unless SNZ has granted that exact use in writing. At present SNZ will not approve AI uploads of joint AS/NZS standards.

  2. Check for a formal AI-use licence

    If your organisation believes it needs to upload a standard into an AI system, first obtain a specific licence agreement from SNZ. Without it, even storing a standard’s PDF on the AI vendor’s secure server breaches copyright.

  3. Use an alternative that avoid text uploads

    Manual summaries     – Prepare a human-written summary or checklist outside the AI tool, then feed that summary to the model.

    Published guidance – Applying technical guidance documents that incorporate or interpret relevant New Zealand standards

    Note: Not every alternative or summary will provide an adequate reproduction of the requirements in the relevant standards, which will impact the AI’s output. Using such a method will require a degree of professional judgement in terms of what you are uploading to the AI, and the degree of reliance you place on the AI’s output.

  4. Verify every AI output against the official text

    AI can hallucinate or oversimplify. Before you rely on a clause, table, figure, or limit, open your licensed copy of the standard and confirm the wording, context, and any cross-references.

  5. Record your compliance trail

    Keep a project note that shows:
    – which standard and edition you used
    – how the content was introduced to the AI tool (paraphrase, short extract, or licensed upload)
    – the date and reference of any written permission from SNZ.

  6. Building Code documents

    NZ Building Code documents are Crown copyright but freely available from MBIE. You may upload extracts provided you respect MBIE’s copyright statement and avoid wholesale republication. Always cite the clause reference and revision date.

  7. Overseas material

    If you draw on Australian, European, or US standards, state that explicitly and explain why the recommendation still meets New Zealand legal and practice requirements.

Prompting frameworks

The following are three prompting frameworks that can be used for engineering applications:

RTF: Role, Task, Format

The RTF framework is a widely used and beginner-friendly structure for crafting effective prompts. It consists of:

  • Role: Defines who the AI should act as (e.g., "a structural engineer", "act as a consenting authority")
  • Task: Specifies what the AI should do (e.g., "summarise key risks in a geotech report", "explain how this clause applies to residential retaining walls")
  • Format: Indicates how the response should be structured (e.g., "respond in bullet points", "give a table comparing options", or "provide a short paragraph")

Use cases:

  • Rapid summaries of technical documents or meeting notes
  • Generating step-by-step procedures or design workflows
  • Structured explanations of standards, codes, or engineering concepts
  • Drafting report sections (e.g. scope, assumptions, methodology)
  • Comparing options or approaches in table form
  • Extracting action items or risks from project content

Examples: 

  • "As a structural engineer (role), outline 5 key considerations when designing a suspension bridge (task) in a numbered list format (format)."
  • "As a civil engineer, explain the steps involved in load analysis for a pedestrian bridge using bullet points."
  • "As a bridge design consultant, summarize the pros and cons of using cable-stayed vs. arch bridges in a table format."

For more information visit.

CREATE: Character, Request, Examples, Adjustments, Type, Extras

The CREATE framework is a more advanced and flexible approach to prompting, suited for technical or iterative engineering workflows. It helps you guide the AI through complex tasks with more control over tone, structure, and output quality. It includes:

  • Character: Define the AI’s role or technical lens (e.g., “a chartered civil engineer”, “a regulatory compliance advisor”)
  • Request: State the task clearly (e.g., “Review this methodology for clarity and completeness”)
  • Examples: Include sample outputs, such as a sample report section or example of tone/style you want matched
  • Adjustments: Build in space for iteration (e.g., “Refine for clarity”, “Make more concise”, “Now adapt for non-technical stakeholders”)
  • Type: Specify the structure you want (e.g., “summary table”, “bullet list of risks”, “briefing paragraph”)
  • Extras: Add any relevant context or constraints (e.g., “NZ-specific terminology”, “Keep under 150 words”, “Assume the audience is non-specialist”)

Use Cases:

  • Drafting and refining technical report sections or proposals
  • Iterative explanation of complex concepts for different audiences
  • Generating structured outputs with tone, scope or format constraints
  • Converting raw notes or technical content into publishable formats

Example:

"As a senior structural engineer (Character), draft a conceptual design brief for a new highway bridge (Request), similar to the example provided below (Examples), but adapted for a coastal environment with high wind loads (Adjustments). Format it as a technical report summary (Type). Include sustainability considerations and material selection rationale (Extras)."

For more information visit.

CRAFT: Context, Role, Action, Format, Tone

The CRAFT framework is a practical and structured approach to prompt writing, particularly useful for professionals aiming to generate clear, relevant and fit-for-purpose outputs. It works well for technical, analytical, and communication tasks where tone and precision matter. It consists of:

  • Context: Provides background or situational detail (e.g. "You're assisting with a design review", "This is for a client-facing report").
  • Role: Defines who the AI should act as (e.g. "a senior engineer", "a technical editor").
  • Action: States the task clearly (e.g. "review this summary", "generate a risk register").
  • Format: Specifies how the output should be presented (e.g. table, checklist, email).
  • Tone: Indicates the desired style or formality (e.g. "professional", "plain English", "advice to a peer").

Use cases:

  • Drafting emails or reports
  • Reviewing technical content
  • Preparing stakeholder communications
  • Documenting assumptions or risks

Examples:

  • "Context: This is for a proposal to a local council. Role: You are a senior civil engineer. Action: Write a summary of the drainage strategy. Format: Use plain English in paragraph form. Tone: Professional but accessible."
  • "You're reviewing the structural design summary of a timber building (context). As a building consent authority reviewer (role), identify potential red flags or missing checks (action), and list them in bullet points (format) using a neutral and constructive tone (tone)."

For more information visit.

Capabilities across engineering disciplines

Discipline

Typical AI applications

Professional considerations and limits

Discipline Building Services / HVAC

Typical AI applications Analysing operational data, assisting in control logic development, estimating energy savings

Professional considerations and limits Requires manual validation of comfort outcomes and compliance with ventilation standards

Discipline Structural Engineering

Typical AI applications Drafting documentation, interpreting code clauses, checking combination logic

Professional considerations and limits Structural safety decisions must be verified against standards and engineering judgement

Discipline Civil / Stormwater

Typical AI applications Performing runoff and soakage calculations, summarising guidelines, sizing detention systems

Professional considerations and limits Final designs depend on site-specific testing, local rules, and peer review

Discipline Geotechnical Engineering

Typical AI applications Explaining soil behaviour concepts, generating draft summaries of site investigation logs

Professional considerations and limits Cannot interpret field or lab test results or replace geotechnical modelling

Discipline Infrastructure Asset Management

Typical AI applications Prioritising maintenance based on condition logs, forecasting lifecycle risk

Professional considerations and limits Must be calibrated to local conditions and reviewed against physical inspection records

Discipline Fire Safety

Typical AI applications Summarising incident logs, referencing regulatory clauses, drafting “lessons learned” content

Professional considerations and limits Fire scenarios must be assessed by qualified personnel; AI cannot determine causality

Discipline Environmental Engineering

Typical AI applications Summarising environmental assessments, suggesting monitoring strategies, interpreting rules

Professional considerations and limits Regulatory advice must be confirmed; environmental impacts require empirical evidence

Discipline Transportation / Roads

Typical AI applications Scheduling pavement renewals, analysing traffic volume data, summarising asset performance

Professional considerations and limits Designs and forecasts must consider geographic, safety, and human behavioural factors

Discipline Water and Wastewater

Typical AI applications Drafting O&M plans, summarising treatment system requirements, assisting with regulatory queries

Professional considerations and limits Operational design and compliance decisions must be based on expert review

Discipline Utilities (Electricity, Gas)

Typical AI applications Interpreting control system documentation, assisting with fault log reviews

Professional considerations and limits Safety-critical systems require extensive validation and testing procedures

Discipline Project and Construction Management

Typical AI applications Generating task checklists, tracking issue logs, producing status summaries

Professional considerations and limits Outputs must be aligned with site reality, team roles, and health and safety protocols

Discipline Engineering Education and Training

Typical AI applications Creating training content, generating quiz questions, simplifying technical concepts

Professional considerations and limits Content should be reviewed for technical accuracy and aligned with curriculum standards

Discipline Policy and Regulation Support

Typical AI applications Drafting regulatory summaries, comparing statutory requirements across jurisdictions

Professional considerations and limits Outputs must be checked for currency, authority, and legal compliance

Check out AI engineering tools for additional information on specific AI tools for your engineering discipline.

Building your company’s AI maturity

Start simple:

  • Use free tools like ChatGPT, Gemini, Bard, or Claude. Note: These tools are constantly being updated, and you need to ensure your data remains secure.
  • If you find a tool you prefer, build your experience and confidence in this tool
  • Trial AI on internal documents or non-client-facing workflows (e.g. summarising a previous report)
  • Develop internal prompting templates for repeatable tasks
  • Hold a team session on AI do’s and don’ts

Then grow:

  • Assign a staff member to stay across updates and new tools
  • Create a shared log of useful prompts or example successes
  • Trial ChatPDF or Claude using technical guides.
  • Always verify AI outputs – engineers keep liability, not the AI
  • Document where and how AI was used in project files (for audit and transparency)

If confidentiality is critical:

  • Consider open-source AI like LLaMA 2 or GPT4
  • Mask identifiable data in AI prompts
  • Use opt-out features to prevent training on your data

Our use of AI

Content creation

Artificial Intelligence is a powerful tool that can help Engineering New Zealand Te Ao Rangahau in our work, including creating content.

We take a managed approach to how we use AI in content creation. We do so with the aim of enhancing our productivity and creativity, and allowing us to better serve our members, the engineering profession, and the public.

Read more

Our AI use policy
Help inform your own AI use policy by checking out our one.
View the policy

Contact us

Your thoughts and insights matter to us. Engage with us as we explore AI's role in engineering together.
Get in touch

Note

Due to the rapid advancements in AI technology, new tools are frequently being introduced while existing ones continue to improve or become obsolete. You’re encouraged to verify tool availability, features and relevance periodically to ensure you’re leveraging the most up-to-date and effective solutions.

Disclaimer

The information provided on this webpage is for general informational purposes only. While we have made every attempt to ensure that the information contained herein is accurate and up to date as of July 2025, Engineering New Zealand makes no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability, or availability with respect to the information contained in this document. As always, professional judgement and discretion must be applied and exercised.