Virtual assistant role scorecards

Key takeaways

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

# Virtual assistant role scorecards

Connect responsibilities to accepted outputs, evidence, cadence, escalation triggers, and owner decisions. Use reproducible measures and record context instead of scoring activity alone.

Applying virtual assistant role scorecards

A role scorecard should measure accepted outputs and the conditions around them. Define cadence, evidence, review sample, escalation triggers, and owner decisions before collecting numbers. If volume rises because the source is poor or priorities changed, the score should preserve that context rather than blaming the operator.

Role boundary and review

The assistant can report completed work, exceptions, and evidence for review. The owner interprets trends, adjusts scope, and decides whether coaching or process repair is needed. Keep the scorecard from becoming a hidden incentive to close easy tasks while difficult but important work waits. the [services library](/services) helps clarify the outputs being measured, while the [[provider vetting guide](/provider-vetting)](/provider-vetting) frames review and backup questions. [NIST guidance](https://www.nist.gov/itl/smallbusinesscyber) is a useful access baseline. ### Scorecard record Keep accepted outputs, sample basis, exceptions, context, owner interpretation, agreed action, and next review.