---
name: meeting-transcript-decision-log
description: Converts a meeting transcript into a cited decision and action register. It distinguishes decisions, proposals, questions, commitments, owners, deadlines, dependencies, and unresolved disagreements by speaker and timestamp. Use for meeting transcript decision log, evidence review, management reporting, and decision support.
license: Apache-2.0
metadata:
  adlass.categories: "executive-strategy/meetings-decisions"
  adlass.industries: ""
  adlass.tags: "transcript,decision,action,owner,deadline,timestamp"
  adlass.adaptation: "reference-doc"
  adlass.source: "original"
  adlass.version: "1"
---

# Meeting transcript decision log

## Purpose

Converts a meeting transcript into a cited decision and action register. It distinguishes decisions, proposals, questions, commitments, owners, deadlines, dependencies, and unresolved disagreements by speaker and timestamp.

## Scope

Work only on the named source records and the deliverable fields described here. Preserve source wording, identifiers, dates, amounts, statuses, and citations. **Excluded:** contacting people, changing source systems, making approvals, or presenting a conclusion as a completed business action. The source is a time-ordered conversation, so each decision and commitment retains speaker attribution and timestamp context.

## Data basis

- The process-specific documents, spreadsheets, and record tables in the skill scope.
- The company policy, rubric, control matrix, template, or prior-period output named by this process.
- Run-specific period, audience, project, or decision brief when supplied.
- The source is a time-ordered conversation, so each decision and commitment retains speaker attribution and timestamp context.

## Result

Decisions and actions with speaker and timestamp citations. Meeting decision summary {date}

## Quality criteria

- Every material fact and finding cites its document section, page, timestamp, table row, or record ID.
- Counts, amounts, dates, and statuses reconcile to the named source population.
- Rule outcomes show the rule and preserve source values beside normalized values.
- Missing, conflicting, excluded, and estimated items have explicit statuses.
- The written result and structured output use the same row-level findings.
- The source is a time-ordered conversation, so each decision and commitment retains speaker attribution and timestamp context.

## Instructions

Use speaker labels and timestamps to distinguish a resolved decision from a suggestion, question, or commitment that still lacks acceptance.

## Adapt before use
Treat “we should” as a proposal unless the transcript later records acceptance; capture the accepting speaker and timestamp when a decision is actually made.
A commitment row records the speaker’s stated action and deadline even when no decision was made. Mark “owner not stated” and “date not stated” explicitly, and retain adjacent disagreement as context.

- Add the company policy, rubric, control matrix, or approved format named in the Data basis.
- Map source column names, identifiers, status values, and date or currency conventions.
- Define the process threshold, escalation vocabulary, responsible review role, and retention rule.