Turn Meeting Notes into Owner-Assigned Actions
Extract who does what by when from unstructured meeting records
Your meeting notes mention tasks but not always who owns them or the deadline. Sending a summary without clear assignments means nothing gets done or people wait for someone else to act.
That is the gap this drop closes. It is a operations skill built for ChatGPT, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
Operations managers who chair meetings with multiple stakeholders and need to distribute follow-up tasks clearly
How it works
The skill file does five things, in this order.
1. Prepare your raw notes with context. Paste your meeting notes into ChatGPT along with the attendee list and any implicit responsibilities based on job titles.
2. Request task extraction with ownership logic. Ask ChatGPT to identify action items and assign an owner based on who spoke about it, whose department it affects, or who has relevant authority.
3. Add deadline inference rules. Tell ChatGPT to propose deadlines using phrases like 'by end of week', 'before the next meeting', or flagging tasks with no time clue as needing clarification.
4. Review for ambiguity and dependencies. Check the output for tasks assigned to the wrong person or tasks that depend on another finishing first, then edit or ask ChatGPT to reorder.
5. Export as a tracking table. Ask for the final list formatted as a table with columns for task, owner, deadline, and status, ready to paste into your project tracker or email.
What comes back
A table of named owners, concrete tasks, and inferred or flagged deadlines that you can send within an hour of the meeting ending
The mistake to avoid
If ChatGPT assigns a task to the wrong person, add a line like 'procurement tasks always go to Fatima' to build a reusable instruction set. Save that custom instruction for future meetings to reduce manual corrections.
Running it
Paste the prompt into the Instructions field of a new custom GPT, or use it directly in a chat. If the task involves files, turn on the code interpreter so calculations are executed rather than estimated.
Where this fits
On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.
In the file
I am attaching notes from a meeting. The attendees were:
{list names and job titles}
Please extract all action items from these notes and assign each one to a specific owner based on:
- Who discussed or volunteered for the task
- Whose department or function the task naturally belongs to
- Who has authority or expertise in that area
For each task, also infer a deadline using clues in the notes such as 'urgent', 'this week', 'before next session', or 'by end of month'. If no deadline is mentioned or implied, mark it as 'deadline to be confirmed'.
If a task depends on another task being completed first, note that dependency.
Format the output as a table with these columns:
Task | Owner | Deadline | Dependencies | Status
Set Status to 'Not started' for all items.
Here are the meeting notes:
{paste your notes here}
Additional rules for this team:
{add any standing assignments, e.g. 'IT requests go to Saeed', 'compliance issues go to Layla'}