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
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
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 like this
Explain a Technical Engineering Problem to Non-Technical Managers in a One-Page Brief
Turns your pasted technical notes into a one-page brief with plain-English context, business impact, a costed options table and one clear recommendation.
Turn Engineering Design Review Notes into Decisions, Actions and Open Risks
Paste your raw design review notes and get back a clean record of agreed decisions, owned and dated actions, severity-rated risks and unresolved questions.
Turn Rough Nursing Shift Notes into a Structured SBAR Handover
Get a per-patient SBAR handover built only from your own notes, with missing vitals, meds due and pending results flagged before you hand off.
Write a Plain-English Case Status Update Email to a Legal Client
Turns your case notes into a clear client email covering what happened, what it means, next steps and the client's to-do list, with no legalese or invented predictions.
Build a Raise Case and Meeting Script from Your Accomplishments
Turns your pasted accomplishments into a one-page evidence summary tied to business impact, a short meeting script, and ready answers to the three most likely pushbacks.
Turn a Rough Work Story into a Tight 90-Second STAR Interview Answer
You get a spoken-length STAR answer built only from your own facts, a list of missing results or numbers to fill in, and likely follow-up questions.