Productivity · Specialized agent role

Meeting Assistant

The Meeting Assistant supports preparing agendas and turning meeting records into decisions, actions, owners, deadlines, and unresolved questions. It works from approved agendas, participant list, meeting transcript or notes, linked documents, project context, and prior actions, applies explicit operating rules, and makes incomplete or uncertain work visible instead of silently guessing.

Get StartedReview the workflow

Best for

  • Teams that repeatedly handle preparing agendas and turning meeting records into decisions, actions, owners, deadlines, and unresolved questions and can describe a dependable operating path
  • meeting chairs and named action owners who need consistent preparation, explicit ownership, and visible exception handling

Typical inputs

  • Authoritative inputs such as approved agendas, participant list, meeting transcript or notes, linked documents, project context, and prior actions, with access restricted to what the role needs
  • Definitions, required fields, service expectations, approval thresholds, and checks for speaker attribution, decision wording, owner agreement, due dates, confidentiality, and conflicting interpretations

Input quality determines output quality. Source permissions, retention, and field-level access should be settled before the workflow begins.

Core workflow

Each stage has a defined purpose, visible evidence, and a named owner for exceptions.

1

Frame the request

Confirm the request, responsible owner, permitted sources, and definition of completion for preparing agendas and turning meeting records into decisions, actions, owners, deadlines, and unresolved questions

2

Gather context

Collect approved agendas, participant list, meeting transcript or notes, linked documents, project context, and prior actions and retain enough context to trace material facts and decisions

3

Prepare the work

Apply the configured rules, validate speaker attribution, decision wording, owner agreement, due dates, confidentiality, and conflicting interpretations, and prepare meeting briefs, decision records, action registers, follow-up drafts, and open-question lists

4

Review and hand off

Send the result to meeting chairs and named action owners, pausing exceptions or consequential actions for an accountable person

Actions it can perform

  • Organize and prepare preparing agendas and turning meeting records into decisions, actions, owners, deadlines, and unresolved questions using the permitted sources and documented operating rules
  • Validate speaker attribution, decision wording, owner agreement, due dates, confidentiality, and conflicting interpretations, preserve source context, and route exceptions before consequential action

Actions should be restricted to the systems, records, and channels required for this role. Broader access is not a substitute for a well-designed workflow.

Outputs

  • A reviewable package of meeting briefs, decision records, action registers, follow-up drafts, and open-question lists with ownership, status, sources, and unresolved questions
  • An exception queue explaining which rule, field, source, or approval prevented safe completion

Every output should make its status clear: prepared, awaiting approval, completed under policy, or escalated with an explanation.

Role-specific configuration details

Use these role-specific terms to make the implementation brief concrete: resolve the relevant definitions, permissions, routes, and exception conditions before the role touches live work.

  • meeting-assistant
  • assistant-supports
  • supports-preparing
  • preparing-agendas
  • turning-meeting
  • meeting-records
  • decisions-actions
  • unresolved-questions
  • agendas-participant
  • participant-list
  • list-meeting
  • meeting-transcript
  • notes-linked
  • linked-documents
  • documents-project
  • prior-actions
  • actions-applies
  • applies-explicit
  • explicit-operating
  • operating-rules
  • makes-incomplete
  • visible-instead
  • silently-guessing
  • guessing-produce
  • produce-meeting
  • meeting-briefs
  • briefs-decision
  • decision-records
  • records-action
  • action-registers
  • registers-follow
  • open-question
  • question-lists
  • meeting-chairs
  • named-action
  • trace-back
  • authoritative-inputs
  • inputs-such
  • access-restricted
  • needs-definitions
  • definitions-required
  • required-fields
  • fields-service
  • service-expectations
  • speaker-attribution
  • attribution-decision
  • decision-wording
  • dates-confidentiality
  • conflicting-interpretations
  • interpretations-confirm
  • request-responsible
  • questions-collect
  • retain-enough
  • trace-material
  • material-facts
  • decisions-apply

Human approval and escalation

Approval boundary

meeting chairs and named action owners approve consequential external actions, policy exceptions, irreversible record changes, and any output that represents a business commitment.

Escalation rule

Sensitive conversations, disputed decisions, unclear ownership, employment matters, and commitments absent from the record are routed with the source context, work completed, uncertainty, and requested decision intact.

What remains under human control

  • People define the source authority, permissions, quality rules, review gates, and acceptable boundaries for preparing agendas and turning meeting records into decisions, actions, owners, deadlines, and unresolved questions
  • meeting chairs and named action owners resolve ambiguity, approve consequential actions, and remain accountable for the final business outcome

Teams should review permissions and outcomes over time, especially when policies, data sources, responsibilities, or customer expectations change.

Recommended integrations

Connections are workflow building blocks, not proof of automatic availability. Confirm authentication, permissions, supported actions, and error handling during implementation.

Google WorkspaceReview integration scopeMicrosoft 365Review integration scopeNotionReview integration scopeSlackReview integration scope

Example workflow

A recurring request involving preparing agendas and turning meeting records into decisions, actions, owners, deadlines, and unresolved questions is checked against speaker attribution, decision wording, owner agreement, due dates, confidentiality, and conflicting interpretations; routine preparation is completed, while exceptions are sent to meeting chairs and named action owners with the evidence needed to decide.

The implementation should record the source, owner, decision boundary, and recovery route for each important stage. That makes the workflow easier to review and improve without hiding responsibility.

Related agents

Use related roles only when responsibility and handoff boundaries are genuinely distinct.

Calendar Manager

See the responsibilities, controls, and handoffs for this related specialist role.

Explore Calendar Manager

Related use cases

Explore outcome-led workflows that can combine this role with approved systems and human review.

Design a responsible Meeting Assistant workflow

Define the sources, controls, connected tools, exceptions, and owners before implementation.

Get Started