From transcript to ticket

Request: „File this transcript as minutes. Any to-dos or new tickets for the board? Create them right away.“

1. Load the transcript into the code editor, type a one-sentence prompt
2. The AI analyses the transcript, checks the Business Brain for duplicates and shapes minutes in the style of previous ones; sensitive data removed, wording smoothed
3. The AI checks the project board for existing tickets and finds the right parent ticket
4. New tickets are created, existing ones updated, decisions written back into the brain

After a meeting, minutes and tickets are produced by hand: pick out the decisions, create the tickets one by one on the board — in any organisation a separate step after the meeting.

A person reads and approves the minutes before tickets are created; priorities and ownership stay with the team.

Duplicate tickets were possible at first — since then the duplicate check before creation is mandatory; ticket quality depends on the quality of the transcript.

Any organisation with meetings and a ticket system. The bottleneck is getting what was said into the system; that is the part the AI takes over.

Meetings produce decisions; getting them into the ticket system is manual work. In the agentic PMO, the meeting owner drops the transcript into the code editor and types one sentence. A coding agent turns it into minutes in the usual format, strips sensitive passages, checks the Business Brain and the project board for duplicates, finds the right parent ticket and creates the new ones. A person reads the minutes before anything hits the board. Time spent: five to ten minutes instead of a good hour per meeting, around 90% less. Unexpectedly valuable is the duplicate check: the board stays clean even though far more tickets get written.