30 Claude Prompts Built for Manufacturing Teams

You are a senior manufacturing quality engineer setting up an incoming inspection process. <context> Raw materials or components from a supplier need a consistent incoming inspection before they're released to the production line, to catch defects before they become scrap. </context> <inputs> - Material or part name and supplier: [MATERIAL / SUPPLIER] - Critical specs to check (dimensions, tolerances, visual defects, certifications): [SPECS TO CHECK] - Acceptable quantity limit (AQL) or sampling rule used, if any: [SAMPLING RULE] </inputs> <task> Build an incoming inspection checklist listing each spec to check, the acceptance criteria, a pass/fail column, and a disposition section (accept, reject, hold for review). </task> <constraints> - List every spec provided with a clear numeric or visual acceptance criterion, flag [DEFINE CRITERION] if a spec has no stated limit. - State the sampling rule used at the top of the checklist. - Keep the disposition options limited to accept, reject, or hold for review. </constraints> <format> A printable inspection checklist with pass/fail columns and a disposition section. </format>

You are a senior manufacturing quality engineer completing a first article inspection. <context> A new part or a part from a new tool has produced its first units, and a formal first article inspection report is needed before full production runs. </context> <inputs> - Part number and revision: [PART NUMBER / REVISION] - Dimensions and characteristics to measure, with drawing tolerances: [DIMENSIONS / TOLERANCES] - Measured values from the first article: [MEASURED VALUES] </inputs> <task> Produce a first article inspection report listing each characteristic, its drawing tolerance, the measured value, and pass/fail status, with an overall disposition (approved for production, or hold pending correction). </task> <constraints> - Compare every measured value against its stated tolerance explicitly, mark fail if outside range. - Do not approve the overall disposition if any single characteristic fails, unless the input explicitly allows a use-as-is deviation. - Present tolerances as a range, not just a nominal value. </constraints> <format> A first article inspection report table with an overall disposition line. </format>

You are a senior manufacturing quality engineer writing a corrective and preventive action report. <context> A quality issue was found, either internally or from a customer complaint, and needs a formal CAPA documenting root cause and the fix, both immediate and long-term. </context> <inputs> - Issue description and how it was discovered: [ISSUE DESCRIPTION / DISCOVERY METHOD] - Scope affected (units, date range, lines): [SCOPE AFFECTED] - Root cause investigation notes, if started: [ROOT CAUSE NOTES] </inputs> <task> Draft a CAPA report with problem statement, scope affected, root cause analysis (5-whys), immediate containment action, and a preventive action to stop recurrence, each with an owner and due date. </task> <constraints> - Complete the 5-whys chain to an actual root cause, not just a symptom. - Separate containment (stops the bleeding now) from preventive action (stops it happening again), do not merge them. - Assign an owner and due date to every action, mark [ASSIGN OWNER] if not provided. </constraints> <format> A CAPA report with a 5-whys section and separate containment/preventive action tables. </format>

You are a senior manufacturing quality engineer reviewing process control data. <context> A critical dimension or parameter is being monitored on a control chart, and leadership wants a plain-language summary of whether the process is in control. </context> <inputs> - Parameter being measured and its target/spec limits: [PARAMETER / SPEC LIMITS] - Recent measured values (a series of numbers over time): [MEASURED VALUES SERIES] </inputs> <task> Summarize whether the process appears in control (values clustered near target, no runs or trends) or out of control (points outside limits, a run of points on one side of the mean, a clear trend), and state the process capability in plain terms. </task> <constraints> - Base the in-control/out-of-control call only on the data provided, note if there isn't enough data to conclude confidently. - Flag any individual value outside the stated spec limits explicitly. - Explain the finding in plain language a line supervisor could act on, not just statistical jargon. </constraints> <format> A short written summary plus a table of any flagged out-of-limit values. </format>

You are a senior manufacturing quality manager responding to a customer complaint. <context> A customer reported a quality issue with a shipped product and needs a formal, professional response covering what happened, why, and what's being done about it. </context> <inputs> - Customer name and complaint description: [CUSTOMER NAME / COMPLAINT DESCRIPTION] - Affected lot or batch numbers, if known: [LOT / BATCH NUMBERS] - Investigation findings and corrective action taken, if completed: [INVESTIGATION FINDINGS] </inputs> <task> Draft a customer response letter acknowledging the issue, summarizing the investigation findings in plain language, stating the corrective action taken, and offering a resolution (replacement, credit, or further investigation timeline). </task> <constraints> - Acknowledge the issue in the first paragraph, don't bury it under process explanation. - State findings factually, do not overpromise a root cause not yet confirmed by the input. - Keep the letter under 250 words. </constraints> <format> A ready-to-send customer response letter. </format>

You are a senior manufacturing production supervisor writing a daily shift report. <context> Each shift needs a clear handoff report so the next shift and management know what ran, what didn't, and what needs attention. </context> <inputs> - Shift date, line, and shift (e.g. day/night): [SHIFT DATE / LINE / SHIFT] - Units produced versus target, and scrap or rework count: [UNITS PRODUCED / TARGET / SCRAP] - Downtime events with duration and cause: [DOWNTIME EVENTS] - Notes for the next shift: [HANDOFF NOTES] </inputs> <task> Produce a shift report showing units produced versus target with percent attainment, scrap rate, a downtime log with total minutes lost by cause, and a handoff notes section for the next shift. </task> <constraints> - Calculate percent attainment and scrap rate explicitly, show the math. - Sort downtime causes by total minutes lost descending. - Keep handoff notes as short, specific bullets, not paragraphs. </constraints> <format> A one-page shift report with an attainment summary and a downtime table. </format>

You are a senior manufacturing operations analyst calculating weekly OEE. <context> Leadership wants a weekly OEE view per line to see whether availability, performance, or quality is dragging down output. </context> <inputs> - Per line: planned production time, actual run time, ideal cycle time, units produced, and good units: [LINE DATA] </inputs> <task> Calculate availability, performance, and quality rates per line, multiply them into an OEE percentage, and identify which of the three factors is the biggest drag on OEE for each line. Invent a realistic sample of 3 lines if no data is given. </task> <constraints> - Show the calculation for each of the three OEE components explicitly, not just the final percentage. - Rank lines by OEE ascending so the worst performer is first. - State the single biggest drag factor per line in one sentence. </constraints> <format> An OEE summary table per line with visible component calculations and a biggest-drag note. </format>

You are a senior manufacturing quality analyst reviewing scrap and rework data. <context> Scrap and rework costs are being reviewed and the team needs to know which causes account for most of the loss so effort goes to the right fix first. </context> <inputs> - Scrap or rework events with cause code and quantity or cost: [SCRAP EVENTS] - Time period covered: [TIME PERIOD] </inputs> <task> Build a Pareto-style ranking of scrap and rework causes by total quantity or cost, with cumulative percentage, identifying which causes make up roughly 80 percent of the total loss. Invent a realistic sample of 8 cause codes if none is given. </task> <constraints> - Sort causes by total impact descending. - Show cumulative percentage running down the list. - Explicitly call out the cut line where cumulative percentage crosses 80 percent. </constraints> <format> A ranked Pareto table with a cumulative percentage column and an 80 percent cut line noted. </format>

You are a senior manufacturing cost analyst preparing a monthly variance report. <context> Finance wants to know why actual production cost differed from the standard or budgeted cost this month, broken into labor, material, and overhead. </context> <inputs> - Standard cost versus actual cost by category (labor, material, overhead): [COST DATA] - Units produced this month versus plan: [UNITS PRODUCED / PLAN] </inputs> <task> Produce a variance report showing standard versus actual cost per category in dollars and percent, and a likely driver per unfavorable variance (e.g. overtime, material price increase, scrap, underutilization). </task> <constraints> - Show variance as both dollar amount and percent for each category. - Only label a variance driver if it's reasonably implied by the inputs, otherwise write [INVESTIGATE DRIVER]. - Sort categories by dollar variance descending. </constraints> <format> A variance table with a driver column and a short summary paragraph. </format>

You are a senior manufacturing industrial engineer analyzing line capacity. <context> A production line isn't hitting its output target and the team needs to know which station is the actual bottleneck before investing in a fix. </context> <inputs> - Stations on the line with cycle time per station: [STATION CYCLE TIMES] - Target line output rate: [TARGET RATE] </inputs> <task> Identify the bottleneck station (the one with the longest cycle time), calculate the theoretical maximum line output given that bottleneck, compare it to the target rate, and recommend where added capacity would help most. </task> <constraints> - Show the cycle time comparison across all stations, not just the bottleneck. - Calculate theoretical max output explicitly from the bottleneck cycle time. - State clearly whether the target rate is achievable given the current bottleneck, and by how much it falls short if not. </constraints> <format> A station cycle time table with a bottleneck call-out and an achievability statement. </format>

You are a senior manufacturing supplier quality engineer issuing a corrective action request. <context> A supplied part or material failed inspection or caused a line issue, and the supplier needs a formal corrective action request with a required response deadline. </context> <inputs> - Supplier name and part number: [SUPPLIER NAME / PART NUMBER] - Nonconformance description and lot or PO number affected: [NONCONFORMANCE DESCRIPTION / LOT-PO] - Impact on production (line stoppage, rework hours, scrap cost): [IMPACT] - Required response deadline: [RESPONSE DEADLINE] </inputs> <task> Draft a SCAR stating the nonconformance, the impact on your operation, and a request for root cause, containment action, and permanent corrective action from the supplier by the stated deadline. </task> <constraints> - State the nonconformance and lot/PO number precisely, do not generalize it. - Quantify the impact (hours, units, or cost) rather than describing it vaguely. - Include the response deadline prominently near the top. </constraints> <format> A formal SCAR document with a stated response deadline. </format>

You are a senior manufacturing procurement manager escalating a supplier lead time issue. <context> A supplier's promised lead time has slipped and it's now threatening a production schedule, requiring a firm escalation to get a committed date. </context> <inputs> - Supplier name and part or material affected: [SUPPLIER NAME / PART] - Original promised date and current status: [ORIGINAL DATE / CURRENT STATUS] - Production impact if the delay continues: [PRODUCTION IMPACT] </inputs> <task> Draft an escalation email to the supplier's account manager requesting a firm, committed delivery date and any expediting options available, plus an internal note to the production planner summarizing the risk. </task> <constraints> - Keep the supplier email under 180 words, professional but direct about the production risk. - State the specific production impact (line down date, order at risk) rather than a general urgency claim. - The internal note should be shorter than the supplier email and purely factual. </constraints> <format> A supplier escalation email plus a short internal risk note, clearly labeled. </format>

You are a senior manufacturing sourcing manager preparing an RFQ. <context> The team wants to qualify a second supplier for a critical part, either for cost or supply risk reasons, and needs a formal RFQ to send out. </context> <inputs> - Part number, description, and annual volume: [PART NUMBER / DESCRIPTION / VOLUME] - Required specs, certifications, or tolerances: [SPECS / CERTIFICATIONS] - Target lead time and quote due date: [LEAD TIME / QUOTE DUE DATE] </inputs> <task> Produce an RFQ document with part details, required specs, volume by year or quarter, lead time expectations, and a quote due date, plus a response template table for the supplier to fill in pricing at different volume tiers. </task> <constraints> - Include at least 2 volume tiers in the response template unless only one volume figure is given. - State required certifications explicitly as a pass/fail requirement, not a preference. - Keep the RFQ to one page plus the response template. </constraints> <format> An RFQ document with an attached supplier response template table. </format>

You are a senior manufacturing supplier quality manager preparing a quarterly supplier review. <context> Key suppliers are reviewed quarterly on quality, delivery, and cost performance, and a scorecard is needed for the review meeting. </context> <inputs> - Supplier list with on-time delivery rate, defect rate (PPM or percent), and cost trend: [SUPPLIER DATA] </inputs> <task> Build a supplier scorecard ranking suppliers on a weighted composite score across delivery, quality, and cost, with a one-line action per supplier (maintain, improve plan, or reduce volume). Invent a realistic sample of 6 suppliers if none is given. </task> <constraints> - State the weighting used for each metric. - Sort suppliers by composite score descending. - Flag any supplier with a defect rate above 500 PPM (or 0.05 percent) for a mandatory improvement plan, unless a different threshold is given. </constraints> <format> A supplier scorecard table with a weighted score and a recommended action column. </format>

You are a senior manufacturing supplier quality engineer onboarding a new approved supplier. <context> A new supplier is being added to the approved vendor list and needs to complete quality, compliance, and commercial steps before the first production order. </context> <inputs> - Supplier name and part or material category: [SUPPLIER NAME / CATEGORY] - Required certifications (e.g. ISO 9001, material certs): [REQUIRED CERTIFICATIONS] - Quality agreement and NDA status: [AGREEMENT STATUS] </inputs> <task> Produce an onboarding checklist covering certification verification, quality agreement signing, sample or first article approval, and system setup, with an owner and due date per step, flagging any step that blocks a first production order. </task> <constraints> - Sequence steps in the order they must happen, certifications and agreements before first article approval. - Flag first article approval and certification verification as blocking steps. - Keep the checklist to one page. </constraints> <format> A checklist table with columns for step, owner, due date, and status, blocking steps flagged. </format>

You are a senior manufacturing safety engineer writing a lockout/tagout procedure. <context> A specific machine needs a documented LOTO procedure so maintenance and operators isolate energy sources correctly before servicing it. </context> <inputs> - Machine or equipment name and location: [MACHINE / LOCATION] - Energy sources present (electrical, pneumatic, hydraulic, mechanical): [ENERGY SOURCES] - Isolation points and lock/tag locations: [ISOLATION POINTS] </inputs> <task> Draft a machine-specific LOTO procedure listing every energy source, its isolation point, the steps to de-energize and verify zero energy state, and the steps to safely restore power after service. </task> <constraints> - List every energy source provided with its own isolation and verification step, do not combine multiple sources into one step. - Include an explicit zero-energy verification step before work begins, not just isolation. - Note that this procedure requires authorized, trained personnel only. </constraints> <format> A machine-specific LOTO procedure document with separate de-energize and restore sections. </format>

You are a senior manufacturing safety engineer conducting a job hazard analysis. <context> A specific production task needs a documented job hazard analysis (JHA) breaking it into steps and identifying the hazard and control at each one. </context> <inputs> - Task name and equipment involved: [TASK NAME / EQUIPMENT] - Steps involved in performing the task: [TASK STEPS] - PPE currently required: [CURRENT PPE] </inputs> <task> Break the task into sequential steps and, for each step, identify the potential hazard and the required control measure or PPE, ending with a sign-off line for the safety reviewer and the operator performing the task. </task> <constraints> - Give every step at least one identified hazard and matching control, mark [NO SIGNIFICANT HAZARD] only if genuinely none applies. - Match PPE requirements to the specific hazard at that step, not a blanket PPE list for the whole task. - Keep each hazard and control description to one sentence. </constraints> <format> A step-by-step JHA table with hazard and control columns, ending in a sign-off line. </format>

You are a senior manufacturing EHS (environmental health and safety) coordinator. <context> Operators handling a chemical on the line need a quick-reference summary of the key safety information from the full SDS, since the full document is too long to read before every use. </context> <inputs> - Chemical or product name: [CHEMICAL NAME] - Key SDS sections (hazards, required PPE, first aid, spill response) copied or summarized: [SDS KEY SECTIONS] </inputs> <task> Produce a one-page operator quick-reference summarizing the primary hazards, required PPE, first aid steps, and spill response steps in plain, action-oriented language. </task> <constraints> - Use only the information provided from the SDS, do not add hazard claims not present in the input. - Write first aid and spill response as numbered action steps, not prose. - State clearly that this summary supplements, and does not replace, the full SDS kept on file. </constraints> <format> A one-page operator quick-reference sheet. </format>

You are a senior manufacturing safety engineer auditing machine guarding. <context> A periodic audit is needed to confirm that machine guards on the production floor are present, intact, and not bypassed. </context> <inputs> - Machines or stations to audit: [MACHINE LIST] - Known guarding concerns from prior audits, if any: [PRIOR CONCERNS] </inputs> <task> Build a machine guarding checklist per machine covering guard presence, guard condition, interlock function, and evidence of bypass or defeat, with a pass/fail column and a corrective action field for any fail. </task> <constraints> - Include an explicit check for guard bypass or defeat on every machine, not just presence and condition. - Carry forward any prior concern into this audit as a specific line item to re-check. - Require a corrective action entry for every failed item, no blank fails. </constraints> <format> A per-machine guarding checklist with pass/fail and corrective action columns. </format>

You are a senior manufacturing safety coordinator issuing a confined space entry permit. <context> A task requires entry into a confined space (tank, vessel, pit, or similar) and needs a formal entry permit completed before anyone enters. </context> <inputs> - Confined space location and description: [SPACE LOCATION / DESCRIPTION] - Atmospheric testing results (oxygen, toxic gas, flammability), if taken: [ATMOSPHERIC TEST RESULTS] - Entrants, attendant, and entry supervisor names: [PERSONNEL] - Rescue plan or standby rescue team: [RESCUE PLAN] </inputs> <task> Draft a confined space entry permit stating the space, hazards identified, atmospheric test results against acceptable limits, required PPE and equipment, named personnel and their roles, and the rescue plan, with a permit validity time window. </task> <constraints> - State atmospheric test results against explicit acceptable limits (e.g. oxygen 19.5 to 23.5 percent), flag [RETEST REQUIRED] if results are missing or out of range. - Require a named rescue plan, do not accept "call 911" alone as the rescue plan. - Include a permit validity time window, entry permits should not be open-ended. </constraints> <format> A formal confined space entry permit document with a stated validity window. </format>

You are a senior manufacturing maintenance planner building a preventive maintenance schedule. <context> Equipment on the floor needs a documented preventive maintenance schedule so servicing happens on a set interval instead of only after a breakdown. </context> <inputs> - Equipment list with maintenance task and recommended interval (hours, cycles, or calendar days): [EQUIPMENT / TASK / INTERVAL] - Current usage or run hours per machine, if tracked: [CURRENT USAGE] </inputs> <task> Build a preventive maintenance schedule showing each machine, task, interval, last completed date or usage, and next due date or usage, flagging anything already overdue. Invent a realistic sample of 10 machines if none is given. </task> <constraints> - Calculate next due date or usage explicitly from the interval and last completed value. - Flag any item where next due has already passed as "Overdue". - Sort overdue items to the top. </constraints> <format> A preventive maintenance schedule table with an overdue flag column. </format>

You are a senior manufacturing maintenance supervisor documenting an unplanned downtime event. <context> A machine went down unexpectedly during production and the event needs to be documented with cause, resolution, and time lost for tracking and future prevention. </context> <inputs> - Machine name, date, and time of failure: [MACHINE / DATE / TIME] - Symptoms observed and troubleshooting steps taken: [SYMPTOMS / TROUBLESHOOTING] - Root cause found and repair action, if completed: [ROOT CAUSE / REPAIR] - Total downtime duration: [DOWNTIME DURATION] </inputs> <task> Produce a downtime incident report stating the failure timeline, symptoms and troubleshooting steps taken, root cause, repair action, total downtime, and a recommended action to prevent recurrence. </task> <constraints> - Present the timeline in chronological order from failure to resolution. - State the total downtime in minutes, calculated from the timeline given. - Include a prevention recommendation only if a root cause was identified, otherwise state [ROOT CAUSE PENDING]. </constraints> <format> A chronological incident report with a total downtime figure and a prevention recommendation. </format>

You are a senior manufacturing maintenance planner managing spare parts inventory. <context> Critical spare parts need to stay in stock to avoid extended downtime waiting on a part, and the current inventory needs to be checked against reorder points. </context> <inputs> - Spare parts list with current quantity on hand, reorder point, and lead time to receive: [PARTS LIST] </inputs> <task> Build a reorder list flagging every part at or below its reorder point, showing quantity to order and the lead time risk if the part fails before the new stock arrives. Invent a realistic sample of 12 critical spare parts if none is given. </task> <constraints> - Flag every part at or below reorder point, sorted by lead time descending among flagged items. - Show the specific reorder point and current quantity side by side, not just a flag. - Note any part with a lead time over 30 days as a higher-risk item. </constraints> <format> A reorder list table with flagged items and a lead-time risk note. </format>

You are a senior manufacturing production supervisor submitting a maintenance work order. <context> A piece of equipment needs a repair that isn't an emergency but shouldn't wait indefinitely, and a formal work order needs to go to the maintenance team with the right priority level. </context> <inputs> - Equipment name and location: [EQUIPMENT / LOCATION] - Issue description and when it was first noticed: [ISSUE DESCRIPTION / DATE NOTICED] - Impact on production if not fixed (e.g. running at reduced speed, workaround in place): [PRODUCTION IMPACT] </inputs> <task> Draft a maintenance work order stating the issue, when it started, current production impact, and a recommended priority level (emergency, urgent, routine) with justification for that level. </task> <constraints> - Justify the priority level in one sentence tied to the stated production impact, don't just assign a level without reasoning. - State the workaround in place, if any, so maintenance knows the machine is still limping along versus fully down. - Keep the work order to one page. </constraints> <format> A one-page work order with a justified priority level. </format>

You are a senior manufacturing maintenance manager preparing a monthly KPI report. <context> Leadership wants a monthly view of maintenance performance, covering how much downtime was planned versus unplanned and how maintenance is trending against last month. </context> <inputs> - This month's planned and unplanned downtime hours, PM completion rate, and mean time to repair (MTTR): [MONTH DATA] - Prior month's figures for comparison: [PRIOR MONTH DATA] </inputs> <task> Produce a KPI report showing each metric this month versus last month with the direction of change, a PM compliance rate, and a short narrative on the biggest driver behind any metric that worsened. </task> <constraints> - Show percent change for every metric, not just the raw numbers. - State whether each change is favorable or unfavorable explicitly, don't leave it to interpretation. - Keep the narrative section to 3 sentences maximum, tied to the metric that moved the most. </constraints> <format> A KPI comparison table with a short narrative summary. </format>