Virtual Assistant Provider Pilot Scorecard

Key takeaways

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

# Virtual Assistant Provider Pilot Scorecard

Published October 8, 2026.

Virtual Assistant Provider Pilot Scorecard: begin with the accountable outcome

Virtual Assistant Provider Pilot Scorecard turns provider pilot scorecard into a workflow a manager can inspect. Record task sample, expected result, quality evidence, exception, rework, owner time, access issue, and decision. The purpose is not to add administration around simple work. It is to give the assistant a clear source, a bounded action, a place for uncertainty, and a named owner for decisions that remain with the business. Start with one sentence that describes what should be reliably different after the work is complete. Name the systems, record types, service window, expected output, and excluded decisions. A candidate or provider cannot estimate capacity or demonstrate quality when the work is described only as helping, managing, or taking ownership.

Define authority before access

Use three authority levels. At level one, the assistant follows an approved rule and records the result. At level two, the assistant prepares options and a recommendation for review. At level three, the accountable owner makes the decision. Financial commitments, policy exceptions, legal interpretations, sensitive access changes, and promises outside an approved script normally remain at level three. Put an ordinary example and an ambiguous example beside each level. State who receives an escalation and how quickly that person must answer. If several managers can respond differently, the workflow does not yet have one source of truth. Record the rule version used so later corrections do not erase what the assistant knew at the time.

Build a representative work sample

Choose examples from normal volume, incomplete inputs, duplicates, urgent cases, and an out of scope request. Provide the same access limits, source records, deadline, and output format that would exist in production. Do not create a test whose difficulty comes from instructions that the real workflow should have supplied. Score observable outcomes: correct source used, required fields completed, uncertainty made visible, escalation sent to the right owner, and a handoff another person can continue. Keep tone and presentation separate from factual accuracy. A polished response that hides an unresolved exception should not outrank a plain response that stops safely.

Design the operating record

Use one record for each item or queue decision. Include task sample, expected result, quality evidence, exception, rework, owner time, access issue, and decision. Link the original input and preserve the final artifact or confirmation. A summary should help the manager sort work, but it should never replace a message, document, or system record when the exact wording matters. | Control | Evidence to retain | Owner question | |---|---|---| | Intake | Source, timestamp, required fields | Was enough context supplied? | | Authority | Rule and permitted action | Could the assistant decide this? | | Exception | Missing or conflicting fact | Who resolves it and by when? | | Review | Sample and acceptance result | Did the output meet the rule? | | Closure | Final artifact and disposition | Can another person continue? | The table should remain short enough to use. Extra notes belong in linked records. A dashboard without source evidence can look controlled while hiding incorrect assumptions.

Estimate capacity with ranges

Separate active handling time from waiting time. A record may remain open for two days while requiring only minutes of assistant work. Measure low, expected, and peak arrival volume. Include review, meetings, documentation, corrections, training, and interruptions instead of treating every paid hour as direct production. Coverage and total capacity are different. Work that must happen in a narrow window may require scheduled overlap even when weekly volume is small. Work that can be queued may fit asynchronous coverage. Define the service window, queue target, escalation target, and overflow rule separately.

Apply minimum access

List each system, the action required, the lowest permission that supports that action, the approver, and the removal trigger. Use named accounts and approved sharing methods. Do not place passwords in instructions or move customer data into a convenience sheet simply because it reduces setup time. The [NIST small business cybersecurity guidance](https://www.nist.gov/itl/smallbusinesscyber) provides a useful baseline for accounts, devices, backups, and incident preparation. Apply the questions to the actual systems and data in scope. A checklist supports review; it does not guarantee security. Record when access was granted, reviewed, changed, and removed. When the role narrows or the engagement ends, access that is no longer needed should not remain as an informal backup plan.

Review quality without rewarding silence

Track accepted work, rework, missing context returns, reopened items, exceptions, and time waiting for owner decisions. Publish the denominator with every rate. Review a sample of source records because a low exception count can mean the workflow improved, or it can mean people stopped recording exceptions. Use measures for coaching and system repair. If an error repeats, inspect intake, examples, ownership, access, and review timing before blaming attention. A good workflow makes the correct action easier and gives uncertainty somewhere visible to go.

Run a bounded pilot

During the first week, verify access and practice with bounded examples. During the second, run routine work with full review. Reduce review only for categories that repeatedly meet the acceptance rule. Preserve exceptions and correction history rather than rewriting earlier records as if the final instruction had always been known. At the decision gate, compare actual volume, quality, rework, exceptions, owner time, and access issues with the original assumptions. Choose whether to continue, narrow, expand, retrain, or stop. Unused hours are not a reason to add unrelated work. New scope needs its own outcome, authority, source, acceptance rule, and access review.

Prepare the handoff

The handoff should identify the request, source records, instruction version, completed work, open exceptions, decisions needed, and next owner. Ask a second person to continue using only that record. Each clarification they need reveals a missing field or rule. Use the [repeatable delegation brief](/blog/virtual-assistant-task-brief-for-repeatable-delegation) to define the work and the [security access checklist](/blog/virtual-assistant-security-access-checklist) to plan permissions. Those two records keep operating clarity and access control connected without collapsing them into one vague approval.

Decision checklist

1. State the business outcome and excluded decisions. 2. Record task sample, expected result, quality evidence, exception, rework, owner time, access issue, and decision. 3. Set authority levels and escalation ownership. 4. Test ordinary, ambiguous, urgent, and stop cases. 5. Estimate low, expected, and peak capacity. 6. Grant the minimum named access and set a removal trigger. 7. Review a sample against observable acceptance rules. 8. Decide whether to continue, narrow, expand, retrain, or stop.

Frequently asked questions

### Should the assistant make every routine decision? Only decisions covered by a current, approved rule should be delegated. Ambiguous, sensitive, financial, legal, and exception decisions need a named accountable owner. ### How many samples are enough for a pilot? Use enough examples to cover ordinary work and important exceptions. A small representative sample with clear acceptance rules is more useful than a large set of easy items. ### What should close the workflow? Close it with the final artifact, disposition, unresolved follow up, owner, and evidence that access or delivery occurred as intended.