Tell the AI how to organize your meeting notes before you share them. Build a prompt that keeps decisions, action items, and unanswered questions distinct.
Describe what you need, or load an example. You can edit and export the result.
Up to 3 previous results stay in this page session. Refreshing clears them.
Turn meeting notes into action items, but keep unresolved questions separate.
Read the meeting notes in [notes]. Create three sections: decisions, action items, and open questions. For each action item, list the task, explicitly named owner, and explicitly stated deadline. Use “not specified” when an owner or date is missing. Do not infer agreement from discussion. End with ambiguities that require confirmation.
Summarize a client discovery call for a designer who did not attend.
Summarize [call transcript] for a designer joining the project. Include the client goal, confirmed requirements, constraints, and follow-up questions. Distinguish client statements from team suggestions. Quote short supporting phrases for disputed requirements. Do not invent budget, schedule, or approval. Limit the summary to 300 words.
Ask the model to preserve uncertainty and to mark missing owners or dates rather than invent them. Use clear section headings so readers can distinguish a proposal from a confirmed decision. For sensitive meetings, remove private details before using any AI service.
A generated summary is a draft. Compare each action with the source notes and ask the team to confirm responsibilities. For long meetings, summarize by topic and then reconcile duplicated tasks. This tool generates the instructions, not a recording or transcription.
