Design Review Feedback Organizer
Organize and analyze client or stakeholder feedback from a design review meeting into actionable categories. This prompt helps architects transform raw feedback — often a mix of specific requests, general impressions, and contradictory preferences — into a prioritized action list that drives the next design iteration.
This prompt takes pasted meeting feedback notes and returns a structured document separating approved design elements (preserve these), specific actionable change requests, directional-only feedback requiring design team interpretation, contradictions and conflicts that must be resolved with the client before revision begins, and a consolidated design team action list with an effort estimate (minor / moderate / significant rework) for each item. The organized feedback document is shared with the client within 24–48 hours of the meeting to confirm the architect's understanding before the team acts. It is for licensed architects managing iterative design review cycles on commercial, institutional, or residential projects.
The prompt
You are a licensed architect experienced in managing design iteration cycles, client feedback synthesis, and directing design team revisions based on client input. Organize the following design review feedback: Meeting context: - Project name: [PROJECT_NAME] - Design phase: [DESIGN_PHASE] - Meeting date: [DATE] - Attendees: [ATTENDEES] Feedback received: [PASTE ALL FEEDBACK NOTES FROM THE DESIGN REVIEW MEETING] Organize and analyze the feedback into: ## Approved Design Decisions Elements the client has explicitly approved or positively affirmed — document these clearly so the team knows what to preserve in the next iteration. ## Requested Changes — Specific Feedback that is specific and actionable: a clear request to change, add, or remove something specific in the design. ## Requested Changes — General Directional Feedback that expresses a general dissatisfaction or directional preference without specifying a particular change — requires design team interpretation. ## Conflicts and Contradictions Feedback items that conflict with each other or with previously confirmed design decisions — flag these for clarification before proceeding. ## Questions Requiring Client Response Items raised in the meeting that require the client to provide additional information or make a specific decision before the design can proceed. ## Design Team Action List Consolidated action list: what needs to change, how much design work it involves (minor / moderate / significant rework), and which team members need to act. ## Items to Preserve (Do Not Change) A specific list of approved elements to ensure the team does not inadvertently revise elements the client has accepted.
Runner beta coming — join the waitlist.
In-product execution isn't live yet. Leave your email and we'll let you know if the Runner beta opens.
How to use this prompt
1. Organize feedback immediately after the meeting while it is fresh — waiting diminishes the accuracy of the context for ambiguous comments.
2. Share the organized feedback document with the client within 24-48 hours as a meeting follow-up — this confirms your understanding and allows corrections before the team acts.
3. Use the design team action list to brief the team and assign work, with a clear note on which items are approved vs. in progress.
Customization tips
Sample output
Related prompts
Frequently asked questions
This AI-generated content is for informational and educational purposes only. It does not replace the professional judgment of a licensed architect. Always verify code compliance, structural calculations, and design decisions with qualified professionals.