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.

Prompt

Prompt
You are a senior engineering program manager who writes design review minutes that teams actually act on.

I will paste my raw notes from an engineering design review right after this prompt. Turn them into a clear record of decisions, actions and open risks.

Rules:
1. Count something as a decision only if the notes show agreement or a named approver. Move preferences, suggestions and unresolved debates to "Opinions and open questions".
2. Every action starts with a verb and has exactly one owner and a due date. If the notes lack either, write "TBD" and flag it. Never guess a name or date.
3. Rate each risk High, Medium or Low by impact on safety, schedule or cost, and state the trigger that would make it happen.
4. Keep technical terms, part numbers and figures exactly as written. Do not add numbers that are not in the notes.
5. Link each action to the decision or risk it supports.

Output format:## Summary (max 3 sentences)
## Decisions (table: #, Decision, Rationale, Approved by)
## Actions (table: #, Action, Owner, Due, Linked to)
## Open risks (table: #, Risk, Severity, Trigger, Proposed mitigation, Owner)
## Opinions and open questions (bullets)## Gaps to resolve before next review (bullets)

End with one line listing the assumptions you made and anything missing from the notes.

Example output

Example for: a preliminary design review of a battery enclosure for an electric cargo bike, notes from the mechanical lead.

Summary

The team approved the aluminum 6061 enclosure and the IP67 sealing target. Thermal margin at 40°C ambient is unproven and is the top open risk. Two actions have no owner and need assignment before the CDR.

Decisions

#DecisionRationaleApproved by
D1Use 6061-T6 aluminum for enclosure bodyWeight within 1.8 kg budget, existing supplierPriya N. (chief engineer)
D2Target IP67 sealingCustomer spec rev C requires submersion testPriya N.
D3Drop the quick-release latch from v1Adds 3 weeks of toolingTeam agreement, Priya N. confirmed

Actions

#ActionOwnerDueLinked to
A1Run thermal sim at 40°C ambient, 25 A continuousMarco D.14 MarR1
A2Request gasket samples (EPDM and silicone)Lena K.10 MarD2
A3Update BOM to remove latch part BK-2207TBD ⚠️12 MarD3
A4Confirm vibration test profile with test labMarco D.TBD ⚠️R2

Open risks

#RiskSeverityTriggerProposed mitigationOwner
R1Cell temperature exceeds 60°C limitHighSim shows <5°C marginAdd thermal pad or vent pathMarco D.
R2Fastener loosening under vibrationMediumTorque loss after test cycleThread-locker or nyloc nutsMarco D.
R3Gasket supplier lead time over 6 weeksMediumQuote received after 15 MarQualify second supplierLena K.

Opinions and open questions

  • Sam suggested a magnesium body for weight; not discussed further.
  • Unclear whether IP67 test needs third-party certification or in-house is enough.
  • Some preference for black anodize over powder coat; no decision.

Gaps to resolve before next review

  • Assign owner for A3 and due date for A4.
  • Confirm who signs off on the thermal sim results.
  • Agree on CDR date (notes say "early April").

Assumptions: "Priya OK'd" treated as approval; dates assume the current year; notes did not mention cost targets.

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

Tips and common edits

Why this works

  • Requiring agreement or a named approver stops casual opinions from being recorded as decisions.
  • Writing TBD instead of guessing owners exposes gaps the team must fix rather than hiding them.
  • Severity plus a concrete trigger makes each risk testable instead of a vague worry.

Use right after a design review, PDR or CDR while details are fresh. Have your raw notes or transcript ready to paste into ChatGPT, Claude or Gemini. Messy shorthand is fine.

Common edits

  • Add a column for requirement IDs if your team traces decisions to a spec.
  • Ask for a short email version to send to attendees after the table output.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Career & Job Search