16 AI Prompts for Manufacturing Operations: Quality, Downtime, and SOPs

Turn these verified shift notes into a handoff. Include plan versus actual,
downtime by reason, quality holds, open maintenance items, material constraints,
safety observations, actions in progress, owner, and next checkpoint. Preserve
lot, line, and ticket IDs. Do not infer causes.

Shift notes: [APPROVED NOTES]

Analyze this production variance. Separate measured contributors from possible
contributors. Quantify only from supplied data, show calculation assumptions,
and recommend the next data check with highest information value.

Plan: [PLAN]
Actual: [ACTUAL]
Downtime, speed, scrap, staffing, and material data: [DATA]

Create a 10-minute tier-meeting agenda from these inputs. Surface safety first,
then quality, delivery, cost, and people. For each exception show current state,
containment, owner, due time, and escalation needed. Omit items that are on plan.

Write a decision brief for this constraint. Include affected products, current
capacity, demand, duration uncertainty, feasible options, tradeoffs, required
approvals, and the next decision deadline. Do not promise a ship date.

Draft a nonconformance record from verified evidence. Include requirement,
observed condition, quantity and lots affected, detection point, immediate
containment, traceability, and missing information. Do not assign root cause or
disposition.

Evidence: [EVIDENCE WITH IDS]

Facilitate, do not complete, a five-whys investigation. Start from the verified
problem statement. For each why, show current evidence, competing hypotheses,
and the evidence or test needed before proceeding. Stop when support is missing;
never invent the next answer.

Organize potential contributors under machine, method, material, measurement,
people, and environment. Label each as observed, plausible, or contradicted.
For plausible items, propose a safe test and required owner. A category does
not need an entry if evidence does not support one.

Review this CAPA plan for containment-versus-correction confusion, weak root-
cause evidence, actions that only retrain people, missing owners, unverifiable
effectiveness checks, and recurrence risk. Quote the exact weak statement and
ask a clarifying question.

Organize the approved maintenance information into a work-package draft:
asset, symptom, scope, prerequisites, approved procedure references, parts and
tools, permits, operational coordination, verification, and closeout evidence.
Do not create technical steps or safety instructions absent from an approved
procedure.

Summarize this downtime export by asset, reason code, duration, recurrence, and
production impact. Identify data-quality problems separately. Suggest three
investigation priorities using a stated rule such as total lost time or repeat
frequency; do not label correlation as cause.

Compare the PM task list with verified failure history. Flag tasks with no clear
failure mode, failure modes with no task, intervals that need engineering review,
and fields needed to judge effectiveness. Do not change an interval or procedure.

Draft a concise escalation for [ASSET]. Include observable symptom, operating
condition, first occurrence, recurrence, production and quality impact, safe
checks completed, evidence attached, and support requested. Exclude diagnosis
unless confirmed by the responsible technician or engineer.

Convert this approved process description into a work-instruction draft. Use
numbered atomic steps with actor, action, approved parameter reference, expected
result, quality check, and exception path. Mark any missing information as
[OWNER INPUT REQUIRED]. Never invent settings, tolerances, PPE, or safety steps.

Review this SOP for vague verbs, missing owners, undefined terms, hidden handoffs,
unverified completion, conflicting sequence, missing exceptions, and references
without revision numbers. Return a table with quoted text, risk, and question
for the process owner.

Create a kaizen event brief for [PROCESS]. Include problem statement, boundary,
baseline measures, customer impact, team roles, observations to collect, agenda,
experiment rules, and follow-up measures. Do not preselect a solution.

Convert these review notes into actions with problem addressed, action, owner,
due date, dependency, evidence of completion, and effectiveness measure. Separate
immediate containment from systemic improvement and preserve unresolved items.