# The 10-Minute AI Pre-Job Brief for Electrical Service Calls > Turn scattered intake notes, messages, and photos into a reviewed pre-job brief so technicians arrive with clearer scope, access, and safety context. - **URL:** https://trymorgan.ai/blog/the-10-minute-ai-pre-job-brief-for-electrical-service-calls - **Published:** 2026-10-17 - **Category:** Business tips --- ## Stop sending technicians out with half the story A service call may look complete on the calendar: customer name, address, time, and a short note such as “breaker keeps tripping.” But the useful details are often scattered across text messages, intake notes, emails, photos, and a phone conversation nobody documented. The technician arrives without knowing which circuit is affected, whether the panel is accessible, what the customer approved, or whether another trade has already looked at the problem. That weak field service handoff creates avoidable calls back to the office. It can also turn a repair appointment into an unplanned diagnostic visit. A short, reviewed pre-job brief gives the field technician one reliable place to start. AI can help organize the information, but it should never make the final call on scope, price, safety, or electrical requirements. ### Pre-dispatch checklist Before the technician leaves, confirm that the brief includes: - Verified customer name, service address, and contact method - Customer’s main problem and priority, in their own words where useful - Approved scope, quoted price or pricing status, and exclusions - Relevant photos, labels, previous notes, and equipment information - Parking, entry, gate, tenant, pet, and panel-access instructions - Known safety concerns without assumptions about site conditions - Missing information that still needs an answer - A named person who reviewed and approved the brief ## What an AI pre-job brief should do The purpose is not to diagnose the electrical problem from the office. It is to turn existing information into a concise electrician job briefing. A useful brief answers four practical questions: 1. **Where are we going and who are we meeting?** 2. **What does the customer believe is wrong?** 3. **What work, price, and expectations have actually been approved?** 4. **What must the technician verify before starting?** This is a sensible use of AI for electricians because the task is mostly sorting, summarizing, and identifying gaps. It is not a suitable place to let AI invent technical conclusions. The [NIST AI Risk Management Framework](https://www.nist.gov/itl/ai-risk-management-framework) recommends defining human roles and responsibilities when AI is used in operational settings. NIST’s [Generative AI Profile](https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.600-1.pdf) also notes that generative AI use may require human review, documentation, and management oversight. For a small electrical contractor, that can be translated into one simple rule: **AI drafts the brief; a responsible person approves it.** ## The 10-minute pre-job briefing workflow This workflow can be run by an owner, dispatcher, office administrator, or lead electrician. It works with an approved AI tool, including Morgan AI where appropriate, but it also works manually with a standard document template. ### Minutes 1–2: Gather the source material Pull together only the information needed for the call: - Booking or intake form - Customer messages and emails - Call notes - Estimate or approved work order - Site and equipment photos - Notes from previous visits - Access instructions Do not paste full customer histories into an AI tool just because they are available. The Federal Trade Commission advises businesses to collect and retain only the sensitive information they need, restrict access, and protect what they keep. Its [small-business cybersecurity guidance](https://www.ftc.gov/business-guidance/small-businesses/cybersecurity) offers practical steps for handling customer information. Never put card numbers, bank details, Social Security numbers, driver’s license images, account passwords, alarm codes, or unnecessary identity documents into the prompt. Use your approved payment and identity-verification processes instead. ### Minutes 3–4: Separate facts from assumptions Mark each item as one of the following: - **Confirmed:** verified by the customer, estimate, photo, or previous job record - **Customer-reported:** useful context that has not been technically verified - **Unknown:** missing or unclear For example, “customer reports the breaker trips when the dryer starts” is useful. “Dryer circuit is overloaded” is a diagnosis and should not appear as fact unless a qualified person has established it. This distinction keeps the brief honest. It also tells the technician what must be checked on site. ### Minutes 5–6: Generate a structured draft Give the AI a fixed format rather than asking it to “summarize everything.” A practical prompt is: > Create a concise pre-job brief using only the information provided. Separate confirmed facts, customer-reported information, and unknowns. Do not diagnose the fault, recommend electrical work, invent equipment details, or assume code requirements. Flag conflicts involving the customer, address, scope, price, access, or safety. If you are preparing the brief manually, use the same instructions as an editing checklist. ### Minutes 7–8: Review the high-risk fields A human reviewer must compare the draft with the original records. Check these fields one by one: - Customer identity - Exact service address and unit number - Contact person on site - Approved scope and exclusions - Price, deposit, or authorization status - Appointment window - Access and parking details - Photos and equipment labels - Safety information - Required license, permit, inspection, or utility coordination questions Do not ask the AI to decide which local code applies. Requirements can depend on the jurisdiction, property, equipment, and work being performed. Confirm them through your normal process. The brief should also match the commercial paperwork. If the scope changes later, document the change and update the estimate or invoice rather than relying on a text thread. Morgan’s guide to [simple invoicing for service businesses](/blog/simple-invoicing-for-service-businesses) explains how to keep customer-facing records clear. ### Minutes 9–10: Resolve gaps or label them clearly Call or message the customer if one missing answer could change the visit. Useful questions include: - Which room, device, outlet, or circuit is affected? - When did the issue start? - Is the problem constant or intermittent? - Is there visible damage, heat, smoke, water, or a burning smell? - Can the technician reach the panel and affected area? - Is the property occupied by the owner, tenant, or site manager? - Has the quoted scope been approved? If the customer cannot answer a technical question, do not pressure them to open equipment or approach a suspected hazard. Record the answer as unknown and escalate appropriately. ## A reusable electrician pre-job brief template Copy this into your job-management system, notes app, or shared document: ### Job identification - Job number: - Date and arrival window: - Assigned technician: - Customer name verified: Yes / No - Service address verified: Yes / No - On-site contact and preferred contact method: ### Customer priority - Main problem, as reported: - When it started: - What triggers it: - What the customer needs resolved today: ### Confirmed job details - Approved scope: - Explicit exclusions: - Price or pricing status: - Authorization status: - Relevant previous work: ### Site and access - Parking or loading notes: - Gate, reception, tenant, or key instructions: - Panel and work-area access: - Pets or occupancy considerations: - Photos and documents attached: ### Safety and technical context - Customer-reported warning signs: - Known equipment information: - Shutdown or operational constraints reported by customer: - Information requiring on-site verification: ### Gaps and escalation - Missing information: - Conflicting information: - Questions for the customer: - Supervisor or licensed-electrician review required: Yes / No - Reviewed by and time: ## Stop conditions: do not treat the brief as permission to proceed A pre-job brief is an information handoff, not a safety assessment or work authorization by itself. Pause the dispatch plan or escalate to the responsible licensed electrician, qualified lead, supervisor, or a separate diagnostic site visit when: - The customer identity, address, or unit does not match the work order - Nobody can confirm who has authority to approve the work - The requested work differs from the approved scope - Price or change-order expectations are unresolved - Photos, notes, and customer messages contradict one another - The assigned technician may not have the qualifications required for the task - The customer reports smoke, fire, arcing, heat, water exposure, damaged service equipment, or another immediate hazard - Safe access, shutdown conditions, or responsibility for site control is unclear - Permit, inspection, utility, or local code questions could change the planned work - The issue cannot be responsibly scoped without seeing the site AI must not determine that equipment is deenergized or safe to approach. OSHA’s standard on [electrical safety-related work practices](https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.333) addresses precautions around equipment or circuits that are or may be energized, including verification duties for qualified persons. Follow the requirements that apply to your work, jurisdiction, employees, and company procedures. ## Make the brief part of normal electrical contractor operations The workflow becomes useful when it is routine, not when somebody remembers it for a difficult call. Use the same template for every service dispatch. Assign one person to approve it. Keep the final version with the job record, and make corrections visible rather than silently replacing old information. After the visit, compare the brief with what the technician found. Update reusable customer details such as access instructions, but avoid building an unnecessary store of personal information. Good records can also support better follow-up and stronger [customer relationships](/blog/how-to-build-customer-relationships-as-a-solo-business). Finally, connect completed work to your basic financial records. Morgan’s guide to [tracking service-business income](/blog/how-service-businesses-can-track-income) provides a straightforward starting point. The goal is simple: the technician should know what is confirmed, what is only customer-reported, what remains unknown, and who approved the handoff. That is how a short AI-assisted draft becomes a practical field document instead of another source of confident mistakes. ## References - [NIST AI Risk Management Framework](https://www.nist.gov/itl/ai-risk-management-framework) - [NIST Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile](https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.600-1.pdf) - [FTC Cybersecurity for Small Business](https://www.ftc.gov/business-guidance/small-businesses/cybersecurity) - [FTC Protecting Personal Information: A Guide for Business](https://www.ftc.gov/business-guidance/resources/protecting-personal-information-guide-business) - [OSHA 29 CFR 1910.333: Selection and Use of Work Practices](https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.333)