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
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
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 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.
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.
Write a Status Update for Your Boss When Your Project Is Behind Schedule
You get a short, decision-ready update that leads with the new date and its impact, explains the cause in one line, and offers two costed recovery options plus a recommendation.
Explain Your P&L and Balance Sheet in Five Plain-English Takeaways
Paste your profit and loss or balance sheet and get five ranked takeaways, each with the exact number behind it, plus questions to ask your accountant.
Rewrite Hospital Discharge Instructions in Plain Language for Patients
Turns pasted clinical discharge instructions into a sixth-grade-level handout with a medicine table, a 'call your doctor if' list and teach-back questions, keeping doses unchanged.
Summarize a Long Contract into Key Terms, Obligations and Risk Clauses
Turns a pasted contract into a cited table of parties, dates, payment, termination, liability and renewal terms, plus a list of unusual clauses to take to a lawyer.