Connect meetings

Meetings are often the richest record of what was agreed on a project. ddx PMO reads your meeting notes — and any paired transcript — and turns each meeting into an entry in the Meeting Register, with actions, decisions and stakeholders extracted automatically.

What you can bring in

ddx PMO reads meetings from Markdown (.md) files:

• Meeting notes — your curated write-up of the meeting (for example an exported Obsidian or Granola note). This is the content that gets classified.
• Transcripts — the verbatim capture (for example a Granola transcript). Optional, and most meetings won’t have one.

A note and its transcript are treated as one meeting. The note is the record that’s read for risks, decisions and actions; the transcript is kept alongside as an audit trail and is not classified, so the two never disagree.

A markdown file is read as a transcript (rather than a note) when it’s tagged type/transcript or links back to a note; a transcript on its own is never made into a meeting.

How to import

Open a project and go to Import in the sidebar. Then drag your files onto the drop zone, or click to choose them.

• You can drop several .md files at once, or a .zip of them — a zipped folder of notes and transcripts is fine. (The same drop zone also accepts email and document files; see Connecting your tools.)
• Notes and transcripts are paired automatically — by meeting id, by the note’s transcript: link, or by matching filename — so you don’t have to upload them in any particular order.
• Re-importing the same meeting is safe — it’s recognised as a duplicate rather than added twice. (A meeting is matched by its Granola meeting id, or by a hash of the note when there’s no id, so an edited note comes in as a new version.)

After upload you’ll see an import summary — Parsed, Imported, Replaced, Duplicates and Failed — with a separate Meetings line breaking out imported, duplicate and replaced meetings. Classification then runs in the background, and the status panel below the drop zone updates live.

Note

If a transcript has no matching note, it’s reported as an orphan transcript and isn’t turned into a meeting — a transcript on its own isn’t enough. (Orphan transcripts also count toward the Failed total in the summary.)

Tip

If you’re loading old meetings, tick This is historical data before you drop the files. Extracted actions that are long overdue (or, with no due date, years old) come in retired — kept for the knowledge graph but kept out of My Work and the registers, and you can un-retire any of them later. Everyday inbound is never affected. See Import your data.

What you get

Each meeting becomes a card in the Meeting Register showing:

• a summary of the meeting,
• the attendees (with their email where known),
• the key decisions, and
• the action items as written in the note.

The register opens on the current version of each meeting; switch to All to see every version, including superseded recaps and duplicates. Expand a card to see its history and how it relates to other meetings.

The actions and decisions ddx PMO extracts also flow into the Actions and Decisions registers and the project’s knowledge graph, the same way email does. See Connecting your tools for the full list of sources.