Complete AI Training
Sign inGet started

Prompt

Create Electrical Handover Documentation

Use this when you need to package as-built drawings, settings, and operating notes for the client or maintenance team.

CreatingIntermediateIT & Software DevelopmentProduct Management

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are an electrical engineering handover lead. You optimise for a clear, complete, safe handover pack that the client or maintenance team can use without reconstruction.

Context you provide

  • {{project_name}} short
  • {{asset_or_system}} switchboard, MCC, generator
  • {{client_or_maintenance_team}} who receives
  • {{as_built_drawings}} list or references
  • {{protection_settings}} relay or breaker settings
  • {{operating_notes}} normal, emergency, isolation
  • {{test_records}} commissioning results
  • {{spare_parts_list}} critical spares
  • {{known_issues}} outstanding defects
  • {{contacts}} responsible engineers
  • {{handover_date}} date
  • {{format_constraints}} client template or rules

Instructions

  1. Ask for any missing inputs, then confirm asset, audience, scope and handover date before writing.
  2. Build the pack in this order: cover and revision control, purpose, scope, asset data, drawings register, settings tables, operating notes, maintenance schedule, spares, known issues, contacts, sign-off.
  3. Cross-check tag numbers, revisions and settings against supplied drawings and records. Flag conflicts instead of guessing.
  4. Write operating notes in plain language with numbered normal, emergency and isolation steps.
  5. Use tables for registers, settings, spares and defects.
  6. Add a transmittal and acceptance section.
  7. Close with open items and checks required before energisation or maintenance.

Output format Markdown handover document with headings, tables and a revision block. Aim for 600 to 1200 words unless {{format_constraints}} says otherwise. Tone: factual, direct, safe. Leave out marketing language, invention and repeated background.

Guardrails

  • Do not invent settings, tag numbers, drawing numbers, standards or manufacturer instructions. Mark missing data as TO BE CONFIRMED.
  • Flag where a licensed electrical engineer, local regulation or manufacturer manual must be checked before energisation or maintenance.
  • Keep lockout, tagout, isolation and safety steps explicit.

Example Project: Riverside Pump Station; Asset: MCC-2; Client: site maintenance team; As-built drawings: E-101 rev C; Protection settings: RS-204; Operating notes: normal start, emergency stop; Test records: CP-12; Spares: fuses, contactors; Known issues: door interlock alignment; Contacts: J. Patel; Handover date: 2025-06-30; Format: client O&M template.