Write a Clear Engineering Change Request from a Problem Description

Turns your rough problem notes into a structured engineering change request with problem, proposed change, affected parts, verification, rollback and flagged impacts you missed.

You getECR title, 1. Problem statement and 2. Proposed change

Prompt

Prompt
Act as a senior design and manufacturing engineer who reviews engineering change requests (ECRs) before they go to the change board.

I will paste a problem description right after this prompt: what is wrong, what I think should change, and any part numbers, systems or test data I have. Turn it into a clear ECR.

Rules:
1. State the problem as observed fact (what, where, how often, since when) and keep it separate from the proposed fix.
2. Use only part numbers, values and test results I give you. Where something is missing, write "TBD - confirm" instead of guessing.
3. Every verification step names the test or inspection, the sample size and the pass/fail criterion.
4. The rollback plan states what triggers it and how existing stock, work in progress and field units are handled.
5. Add an "Unstated impacts" list: effects I did not mention that a reviewer will ask about (cost, tooling, inventory, suppliers, drawings, regulatory, service, software versions), each with one question to resolve it.

Output format:
- ECR title (one line)
- 1. Problem statement
- 2. Proposed change (before vs after table)
- 3. Affected parts and systems (table: item, current rev, change, owner)
- 4. Verification plan (numbered)
- 5. Rollback plan
- 6. Unstated impacts and open questions
- 7. Priority and recommended disposition

End with one line naming the biggest assumption you made and the missing information that would most change this request.

Example output

Example for: a mechanical engineer reporting cracked motor mounting brackets on a coolant pump assembly, with a plan to increase sheet thickness.

ECR title: Increase thickness of motor mounting bracket BRK-2214 from 2.0 mm to 3.0 mm to stop fatigue cracking

1. Problem statement

Cracks at the inner bend radius of bracket BRK-2214 (Rev C) were found on 14 of 220 pump assemblies (6.4%) returned from field units since March. Cracks appear after roughly 900-1,400 run hours. No cracks found on units under 600 hours.

2. Proposed change
BeforeAfter
Material2.0 mm CR steel3.0 mm CR steel
Inner bend radius2.0 mm3.0 mm
FastenersM6 x 12M6 x 14 (TBD - confirm thread engagement)
3. Affected parts and systems
ItemCurrent revChangeOwner
BRK-2214 bracketCNew thickness, radiusDesign (R. Okafor)
PMP-500 pump assemblyFUpdated BOM, fastener lengthDesign
Fastener FST-0612AReplace with M6 x 14Purchasing
Assembly work instruction WI-118DTorque value TBD - confirmManufacturing
4. Verification plan
  1. Vibration fatigue test per existing pump test spec: 5 brackets, 2,000 equivalent hours; pass = no cracks under 10x inspection.
  2. Fit check on 3 assemblies; pass = no interference with motor housing or hoses.
  3. Torque audit on 10 assemblies; pass = all fasteners within spec after 24 h.
5. Rollback plan

Trigger: any crack in fatigue test or fit interference. Action: revert BOM to Rev C. Existing 2.0 mm stock stays usable; WIP is not reworked; field units are replaced only on failure.

6. Unstated impacts and open questions
  • Tooling: Does the press brake die handle 3.0 mm at the new radius?
  • Weight: Does added mass shift the pump's resonance frequency?
  • Cost: What is the per-unit price change from the supplier?
  • Inventory: How many Rev C brackets are on hand, and use up or scrap?
  • Service: Should field service stock the new bracket as a retrofit kit?
  • Drawings: Do any customer-facing manuals show bracket dimensions?
7. Priority and recommended disposition

Priority: High (field failures, repeat returns). Recommend: approve pending fatigue test results and tooling confirmation.

Biggest assumption: the root cause is bending fatigue at the radius; a failure analysis of one cracked part would confirm or change this fix.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Separating observed problem from the proposed fix stops the ECR from assuming its own conclusion.
  • "TBD - confirm" instead of guessing keeps invented part numbers and values out of a controlled document.
  • The unstated impacts list surfaces tooling, inventory and service questions a change board will ask anyway.

Use when you have a known issue and a fix in mind but need a board-ready ECR. Paste your notes, part numbers and any test results into ChatGPT, Claude or Gemini right after the prompt.

Common edits

  • Add your company's ECR form fields or numbering scheme so the output matches your system.
  • Swap the impact checklist for software terms like release version, migration and feature flags.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Career & Job Search