Blog / 7 min read · 2026-08-16

Gemini Prompts for Electrical Engineering: Design Reviews, Calculation Checks, and Site Reports

Use a Gemini prompt for electrical engineering to structure design reviews, set up calculation checks, interpret specification clauses, and draft inspection and site reports.

gemini-prompts electrical-engineering technical prompt-templates

A good Gemini prompt for electrical engineering turns scattered inputs — single-line diagram notes, inspection observations, specification clauses, calculation sheets — into structured drafts you can review quickly. Use the prompts below for design reviews, calculation setup and checking, standards interpretation, site and inspection reporting, and project communication. Gemini can support the paperwork around electrical engineering; it cannot replace a licensed engineer’s judgment, your governing standards, or any formal verification and approval process. Electrical work carries life-safety consequences, and every boundary below is written with that in mind.

How to write a useful electrical engineering prompt

Give Gemini the system context before the question: voltage level, installation type, governing standard or jurisdiction, design stage, and the source material you actually have. Then constrain the output format and forbid invented parameters.

Avoid a vague request such as: “Check this cable sizing.”

Use a request like this:

Review the following LV feeder cable selection notes for missing design inputs only. Do not size the cable and do not invent parameters. Return a table: missing input, why it affects the selection (current capacity, voltage drop, fault withstand, or derating), likely source document, and the question to raise with the design engineer.

Habits that improve almost every result:

State the voltage level and installation context — a prompt that fits a 24 V control circuit is wrong for an 11 kV feeder.
Name the governing standard and paste the clause text when interpretation matters; do not rely on Gemini’s memory of any code.
Ask it to separate confirmed facts, assumptions, and unknowns in every output.
Request a specific deliverable: an issue log, a check worksheet, an RFI, a report section.
Treat outputs as drafts for engineering review, never as issued documents.

Prompt for design review and coordination

Gemini is useful for completeness and coordination questions before a review meeting — the missing-input hunt, the interface list, the assumptions register. It is not a design authority and must not be asked whether a design is safe or compliant.

Copy-paste prompt: design review issue log

Review the following electrical design package summary and identify missing information, coordination risks, and questions for the design team.

Installation type: [LV distribution / MV network / building services / solar PV / motor control, etc.]
Design stage: [concept, preliminary, detailed]
Governing standards stated on the package: [list as stated — do not add others]
Information provided:
[paste design notes, drawing list, load schedule extracts, key parameters]

Return an issue log with columns:
- Area or interface
- Issue or missing input
- Why it matters (one line)
- Required clarification
- Suggested owner
- Priority: high / medium / low

Focus on: load schedule completeness, supply arrangement and earthing system stated, discrimination/selectivity information, cable routes and derating conditions, interfaces with mechanical and civil works, spare capacity assumptions, and metering/protection information.

Do not assess adequacy or compliance. Where adequacy depends on a calculation or a standard, state which one and stop.

Copy-paste prompt: assumptions register

From the design notes below, extract every assumption — stated or implied.

[paste notes]

Return a table: assumption, where it appears (quote the phrase), what it affects, how it would be confirmed (measurement, supplier data, calculation, client decision), and the consequence if wrong.

Mark implied assumptions [IMPLIED] — for example, a diversity factor used without justification, an ambient temperature taken as standard, or a supply impedance assumed rather than obtained from the utility.

Prompt for calculation setup and checking

Never ask Gemini to produce a final electrical calculation — cable sizing, fault levels, protection settings, arc-flash energy — without independent verification against your standard method and tools. What it does well is the scaffolding: laying out the method, checking unit consistency, and building an independent-check worksheet.

Copy-paste prompt: calculation check worksheet

Help me prepare an independent-check worksheet for this electrical calculation. Do not perform the final calculation.

Calculation purpose: [e.g. verify voltage drop on a feeder / check maximum demand / review generator sizing inputs]
Known inputs and units:
[paste inputs]
Method or formula proposed:
[paste method if known]
Governing requirement:
[paste the project requirement or clause text]

Return:
1. Inputs listed with units and any conversions required
2. Assumptions needing confirmation, each with its source ("supplier data," "utility letter," "measurement")
3. A step-by-step framework in symbols before numbers
4. Common errors to check for this calculation type: unit mismatches, single-phase vs three-phase factors, per-unit-length values vs totals, temperature and grouping derating applied once and only once
5. A verification checklist ending with "checked against [method/tool] by [name]"

If the method depends on a parameter I have not provided, stop and list it. Do not substitute typical values.

Worked example: structuring a voltage-drop check

The value of the worksheet approach shows in a routine voltage-drop review. The three-phase relationship in terms of per-unit-length values is:

Vd = √3 × I × L × (R·cosφ + X·sinφ)

where I is line current, L the route length, and R and X the conductor resistance and reactance per unit length at the operating temperature. Most wrong answers come from bookkeeping, not electricity: mixing per-kilometre values with a length in metres, using resistance at 20 °C where the operating-temperature value is required, applying the √3 factor to a single-phase circuit, or quietly double-applying a derating factor.

I am reviewing a three-phase voltage-drop calculation. Here are the stated inputs:

[paste: current, length, conductor data with the temperature they are quoted at, power factor, allowable drop]

Do not calculate the final answer. Instead:
1. Check every input has consistent units; list required conversions explicitly.
2. State which temperature the resistance value is quoted at, and flag if the calculation needs a different one.
3. Confirm whether the formula matches the system (three-phase vs single-phase) and list the telltale signs of a mismatch.
4. List the questions an independent checker should ask before signing, in checking order.

The final number still comes from your calculation tool or hand method, verified per your procedure. Gemini’s job ended at the checklist.

Prompt for standards and specification interpretation

Standards text is conditional and cross-referenced, and project specifications amend it. Gemini can explain a clause you paste; the controlled document remains the authority, and clause numbers it recalls from memory are not to be trusted.

Copy-paste prompt: plain-language clause explanation

Explain the following electrical specification or standard clause in plain language for a project team.

Clause (pasted from the controlled document):
[paste clause text]

Project context: [installation type and jurisdiction, if relevant]

Provide:
- What the clause appears to require
- Conditions, exceptions, and "unless otherwise specified" hooks within it
- Terms needing definition
- Referenced clauses or documents to fetch (as stated in the text — do not fill in their content from memory)
- Questions for the engineer or contract administrator

Do not state that compliance is achieved or achievable. Do not quote requirements from standards not pasted here.

Prompt for site, inspection, and test reporting

Inspection and test paperwork benefits from the same treatment as any field reporting: structure fast, facts only, unknowns flagged — with the addition that test values and instrument details must come from your records, never from the model.

Copy-paste prompt: inspection visit report

Convert the field notes below into a factual electrical inspection visit report.

Project: [project]
Date and scope of visit: [paste]
Field notes:
[paste notes]

Sections:
1. Scope and areas inspected
2. Work observed in progress
3. Items inspected and outcome (state "witnessed" vs "reported by others" for each)
4. Test activities observed — record only values present in my notes, with instrument references if noted
5. Non-conformances and observations, factually stated
6. Actions, owners, and follow-ups
7. Photo log placeholders

Rules:
- Do not invent test values, instrument details, cable identifiers, or approval statements.
- Mark uncertain items "requires confirmation."
- Keep wording suitable for the project record; no blame, no speculation about causes.

Copy-paste prompt: concise technical RFI

Draft a request for information from the notes below.

Affected drawing/equipment: [reference]
Issue (facts and conflicting information):
[paste]
Potential impact: [paste]
Decision requested: [paste]

Structure: subject; existing information; conflict or uncertainty; effect on the work; specific response requested; response date if provided. Keep facts separate from assumptions, and flag any missing reference or measurement I should attach.

Human review boundaries for Gemini in electrical engineering

Use Gemini for drafting, structuring, extracting questions, and building check frameworks. Keep a qualified engineer responsible for everything with safety or compliance consequence:

Design adequacy and compliance conclusions — cable and equipment sizing, protection settings and discrimination, earthing design, arc-flash results.
Calculation results. The worksheet may come from Gemini; the numbers come from your verified method and tools.
Standards content. Paste clauses in; never accept clause text, numbers, or limit values recalled by the model.
Test values and certification. Only real, recorded values enter reports and certificates, under your jurisdiction’s rules about who may certify.
Anything energized. Isolation, switching, live-work decisions, and safety documents follow your procedures exclusively. No AI output belongs in that loop.

A useful internal rule, same as on any engineering project: if the output could cause someone to build, energize, approve, pay, or certify, it gets professional review first.

FAQ

Can Gemini do electrical calculations?

It can lay out a method, check unit consistency, and build an independent-check worksheet — and that is where to stop. Final values for sizing, fault levels, or protection settings must come from your verified tools and methods, because a confidently wrong number here has safety consequences.

Can Gemini check compliance with the NEC, IEC, or local wiring rules?

No. It can explain a clause you paste and list questions it raises, but its memory of code content and clause numbers is unreliable, and project specifications amend standards anyway. Compliance assessment belongs to a qualified engineer with the controlled documents.

What is the best Gemini prompt for an electrical design review?

Paste the package summary and ask for an issue log of missing inputs, interfaces, and assumptions — explicitly forbidding adequacy judgments. The model is genuinely useful at the completeness hunt; it is not a checker of engineering substance.

Can Gemini help with electrical inspection reports?

Yes, for structure: converting field notes into a factual report with witnessed/reported distinctions and flagged unknowns. Test values, instrument references, and certification statements come only from your records.

Is Gemini useful for electrical engineering students?

Yes — for explaining concepts in plain language, building study checklists, and structuring lab reports. Verify every formula and value against your textbook, and treat derivations it produces as something to check, not to cite.

Conclusion

The most useful Gemini prompt for electrical engineering states the system context, pastes the governing text, forbids invented parameters, and asks for structure — issue logs, worksheets, question lists — rather than answers. Start with the design-review, calculation-check, and reporting prompts above and adapt them to your project templates and verification procedures.

More ready-to-use sets: Gemini prompts for civil engineering, Gemini prompts for teachers, or the prompt gallery.