Virtual assistant meeting cadence

Key takeaways

• Use a written brief and definition of done.
• Keep approvals and escalation rules visible.
• Review quality before expanding the workflow.

# Virtual assistant meeting cadence

Define purpose, participants, input, decision owner, frequency, and cancellation rule. Review decision latency, repeated agenda items, and stalled actions before keeping a recurring meeting.

Applying virtual assistant meeting cadence

Keep a recurring meeting only when its decisions or coordination cost justify the time. Track purpose, required inputs, decision owner, unresolved actions, cancellations, and repeated agenda items. If the same topic returns without a decision, change the prework or move the issue to the person who can resolve it.

Role boundary and review

The assistant can collect agenda inputs, identify missing decisions, and maintain an action log. The meeting owner decides what belongs on the agenda and who can close an item. Record the decision, owner, and due point immediately so the next meeting is not used to reconstruct the last one. the [services library](/services) helps identify coordination support, while the [[provider vetting guide](/provider-vetting)](/provider-vetting) frames role ownership. [NIST guidance](https://www.nist.gov/itl/smallbusinesscyber) is a useful general reference when meeting systems contain sensitive information. ### Meeting record Keep purpose, inputs, participants, decision owner, decision, action owner, due point, and cancellation reason.