01
Check the Evidence
Confirm that the record can identify the condition without guessing about its cause or required correction.
Made for Electricians
Document a Hidden Electrical Condition
Also useful for: people in Skilled Trades
20 min
Intermediate
Customers
Capture concealed electrical problems, separate facts from assumptions, and prepare a record that supports the next safe decision.
We'll use them to write your prompt.
Completed ✓
Make Your Play
Give us the situation. We’ll build the prompt.
Protect the job, the customer, and the electrical crew by recording hidden conditions before the original scope changes or extra work begins.
Your answers save as you type.
What you'll do
This is the plan inside your prompt. Add your details first. Then follow these steps with ChatGPT or Claude.
02
Draft the Hidden-Condition Record
Turn the verified field facts into an internal record and a customer-ready notice.
03
Verify Before Sharing
Compare the draft with the site, original scope, photos, and company documentation rules before saving or sending it.
Make Your Play
Document a Hidden Electrical Condition
Tell us what the prompt needs to know
Start with the questions below. Each answer personalizes the playbook and builds the prompt you’ll use at the end.
Your situation
Enter the job name or work order number and when the condition was found.
Describe the exact room, equipment, circuit, enclosure, pathway, or wall area where the condition was found.
0/10000
State the electrical work originally included in the approved scope.
0/10000
Select the category that best matches the hidden condition.
List only what was seen, measured, tested, or photographed, and upload supporting images or documents.
0/10000
Describe any immediate hazard, protective action, access limit, stopped work, and unaffected work that may continue.
0/10000
This playbook was updated. Review your inputs before copying.
What you'll do
Check a step when you finish it.
01
Check the Evidence
Confirm that the record can identify the condition without guessing about its cause or required correction.
02
Draft the Hidden-Condition Record
Turn the verified field facts into an internal record and a customer-ready notice.
03
Verify Before Sharing
Compare the draft with the site, original scope, photos, and company documentation rules before saving or sending it.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
Write only what was seen, measured, tested, or photographed. If the cause is uncertain, say so. Don’t use the AI draft as a code ruling or authorization to continue work.
Advanced instructions
Add test results, circuit identifiers, drawing references, equipment labels, access limits, and the effect on unaffected scope. Replace broad statements with exact field facts before issuing the record.
Use this when
You uncover damaged wiring, blocked pathways, overloaded circuits, missing grounding, unsafe alterations, or existing work that may not meet current requirements.
You'll need
- Project Reference
- Condition Location
- Original Scope
- Condition Category
- Field Observations
- Safety and Work Status
You'll get
- Condition location and original scope identified
- Photos and field observations attached or referenced
- Observed facts, inferences, and unknowns separated
- Safety and work-status concerns flagged for qualified review
- Final record checked against field conditions and saved.
By the end of this playbook
You will have:
- Condition location and original scope identified
- Photos and field observations attached or referenced
- Observed facts, inferences, and unknowns separated
- Safety and work-status concerns flagged for qualified review
- Final record checked against field conditions and saved.
Examples
Progress 1 of 3