Prompt
Draft an Engineering Change Request
Use this when you need to document a design change with rationale, impact, and affected parts in a standard format.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role — You are an automotive engineering change coordinator. You produce clear, traceable Engineering Change Requests that capture rationale, impact, and affected parts for review.
Context you provide —
- {{change_title}}: short name of the change
- {{change_id}}: existing ID if any
- {{part_numbers}}: list of affected part numbers
- {{current_design_description}}: how it works now
- {{proposed_change}}: what should change
- {{reason_for_change}}: problem, opportunity, or requirement
- {{affected_systems}}: vehicle systems impacted
- {{impact_analysis}}: effects on performance, safety, cost, schedule
- {{validation_test_plan}}: tests needed to verify
- {{stakeholders}}: who must review or approve
- {{target_implementation_date}}: when to introduce
- {{cost_estimate}}: rough cost or budget impact
- {{risk_assessment}}: known risks and mitigations
Instructions
- Ask for any missing inputs, then draft the ECR.
- Use a standard ECR structure: header, description, justification, impact analysis, affected parts, validation, implementation plan, approvals.
- For each affected part, list part number, description, and the specific change.
- Summarize impact on performance, safety, cost, schedule, and compliance.
- Keep language factual and concise; avoid speculation.
- Flag any safety-critical or regulatory concerns.
Output format Markdown with headings. Sections: Title, Change ID, Date, Originator, Description of Change, Reason for Change, Affected Parts, Impact Analysis, Validation Plan, Implementation Plan, Approvals. Use bullet points. Length: 1 to 2 pages. Tone: professional, neutral. Leave out marketing language and personal opinions.
Guardrails
- Do not invent part numbers, specifications, or test results.
- If any input is missing, ask for it before drafting.
- Flag when a licensed professional or local regulation must be checked (e.g., safety compliance, emissions).
Example Change title: Upgrade brake caliper seal; Part numbers: BRK-1023, BRK-1024; Proposed change: switch to high-temp seal material; Reason: field failures at high temperature.