ChatGPT Prompts Built for Engineers

Generate a comprehensive design review checklist for a [design phase: conceptual, preliminary, critical, detailed] review of a [type of system: mechanical assembly, PCB, structural element, control system, piping system, embedded firmware]. The checklist should cover: requirements traceability (is every requirement addressed?), interface compatibility (do all connections fit and function?), manufacturability and assembly considerations, reliability and maintainability, safety and regulatory compliance, environmental and operational envelope, test and verification approach, documentation completeness, and cost and schedule impacts. For each checklist item, provide: the question to ask, what a satisfactory answer looks like, and a red flag that indicates a problem. Tailor the checklist to [industry: aerospace, automotive, consumer electronics, construction, energy, medical devices] standards and typical failure modes.

Create a Failure Mode and Effects Analysis (FMEA) worksheet for [component/system/process]. List at least [number] potential failure modes. For each failure mode, provide: the function being analyzed, the potential failure mode (how it could fail), the potential effect of the failure on the system and end user, the severity rating (1-10 using [SAE J1739 / AIAG / MIL-STD-1629] criteria), the potential cause or mechanism of the failure, the occurrence rating (1-10), current design controls for detection, the detection rating (1-10), the Risk Priority Number (RPN = S x O x D), and recommended actions to reduce the RPN. Sort the completed FMEA by RPN descending so the highest-risk items are addressed first. Include column headers that match [automotive/aerospace/medical device] FMEA standards.

Build a trade-off matrix to compare [number] design alternatives for [component/system]. The alternatives are: [Option A description], [Option B description], [Option C description]. The evaluation criteria are: [list criteria such as cost, weight, reliability, manufacturability, lead time, performance, maintainability, scalability, regulatory compliance]. For each criterion, assign a weight (1-5) reflecting its importance for this project. Then score each option against each criterion (1-5). Calculate the weighted score for each option and provide a recommendation with rationale. Include a sensitivity analysis showing how the recommendation changes if the top 2 criteria weights are swapped. Present the matrix in a clean table format.

I need to provide peer review feedback on a [document type: design document, technical specification, test plan, analysis report, drawing package] for a [system/component]. The document was written by a [junior/mid-level/senior] engineer. Help me structure my feedback using this format: for each comment, include the document section and page number, classify the comment as [Critical: must fix before approval / Major: should fix, affects quality / Minor: suggestion for improvement / Editorial: formatting or typo], state the specific issue, explain why it matters (impact on design, safety, schedule, or cost), and suggest a resolution. Also include 2-3 positive observations about what the document does well. Organize comments by severity (critical first) and limit total comments to the [10/15/20] most important to avoid overwhelming the author.

Write a lessons learned report for [project/phase/incident]. The context is: [describe what happened, whether it was a success, failure, or mixed outcome]. Structure the report as: project overview and objectives, what went well (minimum 5 items with specific examples), what did not go well (minimum 5 items with root cause analysis for each), what we would do differently (actionable recommendations, not vague statements), quantitative impact where measurable (schedule deviation, cost variance, quality metrics), process improvements to implement on future projects, and a responsibility matrix for implementing each improvement. For each lesson, categorize it as: technical, process, communication, resource, or vendor-related. The report should be useful to a team starting a similar project who has never spoken with our team.

Create a Work Breakdown Structure (WBS) for a [project type: product development, facility construction, system integration, manufacturing line setup, infrastructure upgrade] project. The project scope is [describe scope]. Break the work down to at least 3 levels: Level 1 (project phases), Level 2 (major deliverables within each phase), Level 3 (work packages with estimated duration, responsible discipline, and dependencies). Include these phases at minimum: requirements and planning, design, procurement, fabrication/development, integration and testing, deployment/installation, and closeout. For each work package, note: estimated hours, required skill set, and key risks that could affect the estimate. Use WBS numbering convention [1.1.1 format]. Identify the critical path through the project.

Create a detailed cost estimate for [project/system/component]. Break costs into: engineering labor (by discipline, hours, and rate), materials and components (itemized with quantities, unit costs, and suppliers), manufacturing and fabrication (processes, time, and rates), testing and qualification, tooling and fixtures, vendor and subcontractor costs, overhead and indirect costs, and management reserve (contingency). For each line item, provide: a basis of estimate (how was this number derived: historical data, vendor quote, parametric model, engineering judgment), a confidence level (low/medium/high), and a risk-adjusted range (optimistic, most likely, pessimistic). Calculate the total using both most likely and P80 (80th percentile) values. Present the estimate in a tabular format suitable for import into a spreadsheet.

Perform a schedule risk assessment for a project with the following milestones and durations: [list milestones with planned dates and durations]. For each activity, provide: a three-point estimate (optimistic, most likely, pessimistic duration), the primary schedule risk and its likelihood, the impact if the risk materializes (days of delay), a mitigation strategy, and a trigger for escalation. Identify which activities are on the critical path and which have float. Calculate the overall project completion date using both the deterministic (most likely) schedule and a Monte Carlo-style range (P50, P80, P95 completion dates). Recommend schedule buffers and where to place them. Flag any activities where the pessimistic estimate exceeds [X] times the most likely estimate as high-risk.

Create a resource loading plan for [project] spanning [duration]. The available team includes: [list roles and headcount for each]. The project phases and their approximate durations are: [list phases]. For each phase, estimate the full-time equivalent (FTE) demand by role per month. Identify: months where demand exceeds available headcount (resource conflicts), skills gaps where no current team member can perform the work, peak loading periods and strategies to flatten the curve (shifting work, overtime, temporary staff, subcontracting), and minimum team size needed to maintain the critical path. Present the plan as a table with roles on rows and months on columns, with FTE values in each cell. Highlight cells where demand exceeds capacity in a separate section.

Conduct a make-versus-buy analysis for [component/subsystem/service]. We currently [make/buy] this item and are evaluating the alternative. Analyze: total cost comparison over [timeframe] including non-recurring engineering, tooling, unit cost, quality costs, and logistics, strategic considerations (intellectual property, supply chain control, core competency alignment), quality and reliability comparison, lead time and schedule flexibility, capacity and scalability, risk assessment for each option (single-source risk, technology obsolescence, workforce availability), and a recommendation with break-even volume if applicable. Include both quantitative (cost model) and qualitative (strategic fit) factors. Weight the decision criteria and provide a final scored recommendation. Document assumptions explicitly so the analysis can be updated when conditions change.

Create a regulatory compliance matrix for a [product/system/facility] that must comply with [list applicable standards, codes, and regulations, e.g., IEC 61508, ASME B31.3, NEC 2023, ISO 13485, EN 1090, OSHA 29 CFR 1910]. For each standard, list: the specific clauses or sections applicable to our product, the requirement in plain language, how we currently comply (or plan to comply), evidence required to demonstrate compliance (test reports, analysis, inspection records, certifications), responsible engineer or department, status (compliant, in progress, gap identified, not applicable), and target completion date for any open items. Organize the matrix by standard, then by clause number. Flag any conflicting requirements between standards and recommend how to resolve them.

Perform a risk assessment following [ISO 14971 / ISO 12100 / IEC 62443 / MIL-STD-882] methodology for [product/system]. Identify at least [number] hazards across these categories: [electrical, mechanical, thermal, radiation, chemical, biological, software, use error, environmental]. For each hazard, document: the hazard description, the foreseeable sequence of events leading to harm, the severity of harm (using the standard severity classification), the probability of occurrence (using the standard probability classification), the risk level (using the standard risk matrix), risk control measures (inherent safety, protective measures, information for safety), the residual risk after controls are applied, and whether the residual risk is acceptable per [standard] criteria. Include the risk acceptability matrix and the overall benefit-risk determination.

Develop a certification test plan for [product] to achieve [certification: CE marking, UL listing, FCC compliance, ATEX certification, medical device 510(k), automotive IATF 16949]. The test plan should cover: all test requirements mapped to the specific standard clauses, test laboratory requirements (accreditation, equipment, environment), sample requirements (quantity, configuration, conditioning), test sequence (order matters for destructive tests), detailed test procedure for each test, pass/fail criteria from the standard, documentation requirements for the certification body, timeline and cost estimate for the full test campaign, pre-testing recommendations to reduce the risk of failures during certification testing, and a contingency plan for each test if the product fails (redesign options, retest scope, schedule impact).

Draft an Engineering Change Notice (ECN) for [describe the change: material substitution, dimension modification, software update, process change, supplier change]. Include: ECN number and date, affected part numbers and revision levels, description of the change in technical detail, reason for the change (corrective action, cost reduction, performance improvement, obsolescence, customer request), impact analysis covering: form/fit/function, interchangeability with previous revision, effect on inventory and work in progress, impact on tooling and fixtures, impact on test procedures and acceptance criteria, regulatory or certification impact, affected documentation (drawings, specs, BOMs, work instructions, test procedures) with new revision levels, implementation plan (immediate, at next build, effectivity point), required approvals and signatures, and customer notification requirements if applicable.

Create an audit preparation checklist for an upcoming [audit type: ISO 9001, ISO 14001, AS9100, IATF 16949, OSHA, customer, internal] audit of [department/facility/process]. The audit scope covers [describe scope]. The checklist should include: documents the auditor will likely request (organized by standard clause), records that must be available with retention period verification, process areas to be observed and who should be present, common nonconformity areas for this standard and our current status on each, interview preparation for staff who may be questioned (key topics by role), physical areas to inspect and housekeeping standards, corrective actions from previous audits and their closure status, management review meeting minutes availability, and a day-of logistics plan (auditor arrival, conference room, escorts, lunch). Include a timeline with preparation milestones starting [number] weeks before the audit.

Conduct a root cause analysis using the 8D methodology for the following problem: [describe the failure, defect, or incident in detail, including when it was discovered, the affected product/system, and the immediate impact]. Complete all eight disciplines: D1 (Team: who should be on the problem-solving team and why), D2 (Problem Description: define the problem using IS/IS NOT analysis), D3 (Interim Containment: what immediate actions prevent the problem from reaching the customer), D4 (Root Cause: use 5-Why analysis and an Ishikawa diagram to identify root causes), D5 (Corrective Actions: permanent fixes for each root cause), D6 (Implementation: plan for implementing corrective actions with timeline and verification), D7 (Prevention: systemic changes to prevent recurrence across similar products/processes), D8 (Closure: how to verify effectiveness and recognize the team). Include data requirements for each step.

I am facing this engineering problem: [describe the problem in detail, including constraints, objectives, and what you have already tried]. Help me decompose this problem systematically. First, restate the problem as a clear problem statement separating the current state from the desired state. Then break it into sub-problems that can be solved independently. For each sub-problem: define the boundary conditions and constraints, identify the governing physics or principles, suggest 2-3 solution approaches with trade-offs, flag any sub-problems that are coupled (solving one affects another), and identify what information or data is missing to solve it. Finally, recommend the sequence for tackling the sub-problems based on dependencies and which solutions provide the most learning for the remaining problems.

Write a failure investigation report for [describe the failure: component fracture, system malfunction, field return, test failure, process deviation]. Include: executive summary (what failed, when, impact, and conclusion in 3 sentences), failure description with photographs placeholder and physical evidence documentation, timeline of events leading to the failure, environmental and operating conditions at the time of failure, failure analysis methodology used (visual inspection, metallurgical analysis, circuit analysis, simulation, etc.), findings from the analysis with supporting data, root cause determination with evidence supporting the conclusion, contributing factors, corrective actions (immediate, short-term, long-term), effectiveness verification plan, and distribution list. Classify the failure as [design, manufacturing, material, maintenance, operational, or external cause]. Rate the severity and likelihood of recurrence.

Perform a design-for-reliability analysis on [system/product]. The reliability target is [target, e.g., MTBF > 50,000 hours, failure rate < 0.1% per year, design life of 20 years]. The operating environment is [describe: temperature range, duty cycle, vibration, humidity, chemical exposure]. For each major subsystem or component, analyze: the dominant failure mechanism (fatigue, wear, corrosion, electrical overstress, software bug, etc.), the expected life based on materials and loading, derating applied vs component ratings, redundancy or fault tolerance built in, the weakest link in the subsystem, and recommended design changes to meet the reliability target. Calculate the system-level reliability using a reliability block diagram approach (series, parallel, or k-of-n). Identify the top 3 reliability risks and their mitigation strategies.

Create a troubleshooting guide for [system/equipment/process] that covers the [number] most common failure symptoms. For each symptom: describe exactly what the operator or technician observes (what they see, hear, measure, or notice), list the possible causes ranked by likelihood (most common first), provide a diagnostic flowchart (if symptom A and reading B, then check C), specify the corrective action for each cause with step-by-step instructions, list tools and parts needed for each repair, estimate the repair time, and flag any symptoms that indicate a safety hazard requiring immediate shutdown. Include a section on intermittent faults and how to capture diagnostic data when the problem is not currently present. The guide should be usable by a [skill level: technician, operator, field engineer] without contacting engineering support.

I need to present [technical topic: project status, design decision, test results, failure analysis, technology recommendation] to [audience: executive leadership, board of directors, non-technical stakeholders, customer management]. The key technical content is: [describe the technical details]. Translate this into a one-page executive summary that: leads with the business impact or decision needed (not the technical background), presents the technical situation in non-technical language without losing accuracy, uses analogies where helpful but avoids being condescending, includes 2-3 key data points that support the conclusion (not 20), clearly states the recommendation and what you need from the audience, quantifies the impact in terms the audience cares about (cost, schedule, revenue, risk, customer satisfaction), and ends with a specific ask or decision point. Assume the audience will spend 3 minutes reading this.

Create a presentation outline for a [duration]-minute technical presentation on [topic] to an audience of [describe audience: fellow engineers, cross-functional team, customer engineers, academic conference]. The presentation goal is [inform, persuade, get approval, teach, report results]. Structure the outline with: opening hook that establishes why this matters to this specific audience, agenda slide content, content slides organized by [chronological, problem-solution, comparison, process flow] structure, key data visualizations needed (describe what each chart should show, not the data itself), a technical demonstration or example if applicable, potential audience questions and prepared answers, closing with clear takeaway and next steps, and backup slides for anticipated deep-dive questions. For each content slide, provide: the main message (one sentence), supporting points (2-3), and speaker notes on what to emphasize verbally. Total slide count should be [1 slide per 2 minutes of presentation].

Write a technical email to [recipient role: project manager, procurement, manufacturing, quality, customer] about [topic: design change impact, schedule delay, technical issue, test results, specification clarification]. The technical details are: [provide the technical content]. The email should: open with the action needed from the recipient and by when, provide only enough technical context for them to understand and act (not everything you know), explain the impact on their work specifically (schedule, cost, quality, deliverables), avoid jargon they would not know (translate for their discipline), include a clear decision point or response needed, attach or reference supporting documents for detail without dumping them into the email body, and close with next steps and your availability for questions. Keep it under 200 words for the main body. Use bullet points for multiple items.

Write a patent disclosure (invention disclosure form) for [describe the invention: what it is, what problem it solves, how it works]. Include: title of the invention, inventor names and dates of conception, problem statement (what existing solutions fail to do), description of the invention in technical detail sufficient for a patent attorney to evaluate novelty, how it differs from prior art (list known existing solutions and explain the differentiation), advantages over existing approaches, at least 3 embodiments or variations of the invention, potential applications and commercial value, supporting figures descriptions (describe what diagrams or illustrations should show), development stage (concept, prototype, tested, production), and any public disclosures or publications that may affect patentability (with dates). Write in clear technical language, not legal language. The patent attorney will handle the claims.

Write a technical requirements document to send to vendors bidding on [component/service/system]. We need [describe what we are procuring]. Include: scope of supply (what the vendor must deliver), technical requirements organized by category (performance, environmental, interface, quality, documentation), applicable standards and certifications the vendor must hold, qualification testing the vendor must complete (and who pays for it), deliverable documentation (test reports, certificates of conformity, material certifications, manuals), quality requirements (inspection plan, non-conformance process, traceability), packaging and shipping requirements, warranty terms and failure response expectations, and a compliance matrix template the vendor must complete with their proposal. Clearly distinguish between mandatory requirements (shall) and preferred requirements (should). Include a questions deadline and proposal format instructions.