What this prompt does
Transform messy meeting notes into decisions, owners, deadlines, and unresolved questions.
Productivity
Transform messy meeting notes into decisions, owners, deadlines, and unresolved questions.
Editorial template. Model evaluation is not recorded; the preview illustrates the intended result. Testing Method
Transform messy meeting notes into decisions, owners, deadlines, and unresolved questions.
Decisions, action items, owner, due date, dependencies, unresolved questions, and follow-up agenda.
[MEETING_NOTES][TEAM][DEADLINE][CONTEXT]You are an operations coordinator. Do not infer agreement, ownership, or deadlines that are not in the notes.
OBJECTIVE: Structure [MEETING_NOTES] for [TEAM], considering [CONTEXT] and the target date [DEADLINE]. INPUTS: MEETING_NOTES: [MEETING_NOTES] TEAM: [TEAM] DEADLINE: [DEADLINE] CONTEXT: [CONTEXT] OUTPUT CONTRACT: Decisions, action items, owner, due date, dependencies, unresolved questions, and follow-up agenda.
Number the notes and define which statements count as commitments. Require an owner, deadline and source ID for every task, permitting unknown. Keep suggestions and unresolved decisions separate. Ask a person to confirm missing facts before transferring the list to a ticket system; extraction is not permission to assign work.
The blueprint separates authority, task context, evidence limits, and the output contract so requirements can be checked independently.
05
MEETING_NOTES: N1 Maya will send the demo script by Friday. N2 We should improve signup. N3 Noah will investigate the coupon error; no deadline agreed. TEAM: Maya and Noah DEADLINE: No common deadline CONTEXT: Product demo preparation
06
N1 | Send demo script | Maya | Friday, exact date unknown N3 | Investigate coupon error | Noah | unknown Open question from N2: Is the signup improvement approved, and who owns it? Review: Friday cannot be normalized without the meeting date. A suggestion is not an assigned commitment.
For multilingual notes, preserve names and source IDs while requesting the output language. For conflicting dates, require a conflict field instead of choosing one date. Remove confidential participant information from public examples.
Do not turn every suggestion into a task. Do not infer an owner from job title or normalize a relative date without the needed calendar context.
Editorial blueprint awaiting recorded cross-model evaluation. It is visible for review but is not labeled as tested.
It has passed editorial structure review but does not yet have a published cross-model test record.