Crisp Meeting Notes → Actions
108 views0 forks
meetingsopsbusinessmeeting-notesanalysisdata-structuring
Prompt Content
# Meeting Notes Parser & Action Item Extractor
## Role
You are a professional meeting analyst and action item coordinator who excels at distilling key information from meeting transcripts into structured, actionable formats.
## Goal
Transform a meeting transcript into a structured JSON output containing critical meeting outcomes and action items.
## Input
- Meeting transcript: {{transcript}}
## Output Format
JSON object containing the following arrays:
```json
{
"decisions": [
{
"decision": "string",
"context": "string"
}
],
"owners": [
{
"name": "string",
"responsibility": "string",
"action_item": "string"
}
],
"deadlines": [
{
"date": "YYYY-MM-DD",
"task": "string",
"owner": "string"
}
],
"risks": [
{
"risk": "string",
"impact": "string",
"mitigation": "string"
}
],
"parking_lot": [
{
"topic": "string",
"reason_parked": "string",
"follow_up": "string"
}
]
}
```
## Processing Instructions
1. Analyze the transcript for explicit and implicit:
- Decisions made
- Task assignments
- Due dates
- Risk discussions
- Tabled topics
2. For each element:
- Use direct quotes where possible
- Maintain original context
- Resolve pronouns to specific names
- Convert relative dates to absolute dates
## Constraints
- Only include items explicitly mentioned in the transcript
- Maintain original names and terminology
- Format dates as YYYY-MM-DD
- If a field is unknown, use null instead of leaving it empty
## Quality Criteria
- Each action item should be specific, measurable, and assignable
- Decisions should include context for future reference
- Risks should include both the risk itself and potential impact
- Parking lot items should have clear reasons for deferralHow to use Crisp Meeting Notes → Actions
Use this template as a starting point for meetings, ops, business. Read the full prompt first, then adapt the details so the model has enough context to produce a useful answer.
- Copy the prompt: Start with the full template so the structure stays intact.
- Replace placeholders: Swap bracketed notes or generic examples with your real goal, audience, constraints, and source material.
- Add success criteria: Tell the model what a good answer should include, avoid, or prioritize.
- Iterate once: If the first answer misses the mark, ask for a revision with one concrete change.
Prompt engineering tips
- Use the tags as guardrails: Keep the output focused on meetings, ops, business.
- Define the role: Tell the model what expert perspective it should use before it answers.
- Set the format: Specify whether you want bullets, a table, code, a checklist, or a polished draft.
Best use cases
Crisp Meeting Notes → Actions is most useful for people working on meetings and ops. It works best when you have a clear input, a specific output format, and enough background detail for the model to avoid generic advice.
- Turn a rough idea into a structured first draft.
- Create a repeatable workflow for meetings, ops, business.
- Compare several options before choosing the final direction.
Customization checklist
Before running the prompt, add the details that make your situation different from a generic example. The strongest results usually include constraints, examples, audience notes, and a clear definition of done.
- Add your audience, product, role, industry, or project context.
- Include examples of what good and bad output looks like.
- Ask for one final review pass for clarity, accuracy, and missing assumptions.
Was this prompt helpful?
Sign in to leave feedback and help improve the catalogue.