Measuring VA Workload Without Surveillance: Five Practical Metrics

Measure the work, not the person

Some agencies try to manage a remote virtual assistant by monitoring activity: screen time, keystrokes, or message counts. Those numbers are easy to collect and hard to interpret. A VA who spends an hour untangling a carrier problem may look less productive than one who clears ten trivial items, even though the first person did the more valuable work.

A better approach measures the work rather than the worker. Queue metrics describe what is arriving, how long it takes to finish, and how often it comes back. They answer questions you actually need answered: Do we have enough capacity? Where is work getting stuck? Is a process creating rework? They also respect the VA's autonomy, which matters for retention.

This guide is administrative. It is not coverage advice, and it does not replace your agency's procedures or the judgment of licensed staff.

Metric 1: Arrival volume

Count how many items enter each queue over a period, for example per day or per week. Track it by task type so a busy certificate queue is not hidden inside a quiet claims queue.

• Why it matters. Arrivals are the demand side of your capacity math.
• How to keep it honest. Count from a single source, such as the work log or the task system, not from memory.

Metric 2: Completed volume

Count items closed in the same period, again by type. Compare it to arrivals rather than treating it as a scoreboard on its own.

• Why it matters. If arrivals consistently exceed completions, a backlog is building even when everyone is busy.
• A simple check. Subtract completions from arrivals over four weeks. A positive, growing gap is an early warning.

Metric 3: Cycle time

Measure the elapsed time from when an item arrives to when it is closed. Report the median or the middle value rather than only the average, because a few very old items can distort an average.

• Why it matters. Cycle time shows the client experience. A queue can look calm while individual items sit for days.
• Split the wait. Where you can, separate time waiting on the agency from time waiting on a carrier or the client. Only the first part is yours to fix.

Metric 4: Aging of open items

List open items by how long they have been open. A simple report might bucket them into same-day, two to five days, and more than five days.

• Why it matters. Age is the best early signal of a stuck process.
• What to look for. A cluster of items all waiting on the same carrier, the same missing document, or the same approval points to a single cause rather than a capacity problem.

Metric 5: Rework and reopen rate

Count items that had to be corrected or reopened after they were marked complete.

• Why it matters. Rework is the hidden tax on service capacity. It consumes time and it often means a client was contacted twice.
• What to add. When you reopen an item, record a short reason. Reasons turn a number into an action.

Put the five together on one page

A single weekly page is enough. For each task type, show arrivals, completions, median cycle time, count of items older than five days, and reopen count. That format gives a manager a fifteen-minute review instead of a data project.

| Task type | Arrived | Completed | Median cycle | Open > 5 days | Reopened | |---|---|---|---|---|---| | Certificate requests | 42 | 40 | 1 day | 3 | 2 | | Address changes | 18 | 18 | Same day | 0 | 0 | | Claims follow-ups | 25 | 22 | 2 days | 4 | 1 |

The numbers above are illustrative, not benchmarks. What matters is the trend in your own agency over time.

What to do with the numbers

Metrics are only useful if they lead to decisions.

• If arrivals exceed completions for several weeks, you have a capacity question. Consider adding hours, moving a task back in-house, or simplifying a step.
• If cycle time is long but the queue is small, something is waiting on a dependency. Find it and fix the handoff.
• If rework is concentrated in one task type, fix the process before adding people. More capacity applied to a broken process multiplies the problem.
• If everything looks healthy, resist the urge to add tracking. A stable queue is the goal, not a reason for more measurement.

Keep it fair and transparent

Explain the metrics to the VA before you start using them, and share the dashboard. Metrics used secretly feel like surveillance. Metrics used openly become a shared way to see the work. Focus feedback on the queue, not on the person, and treat a high rework count as a question about the process first.

Start with two numbers

You do not need all five on day one. Start with arrivals and completions for one task type, add aging next, and bring in cycle time and rework when the routine is stable. A small, consistent measurement habit beats a complex dashboard nobody maintains.

For context on the kinds of work that move through these queues, InsuranceYo's services page lists policy processing, customer service, and claims support tasks. To plan capacity around a role, book a call.

Scope and limitations

• The five metrics, the buckets, and the illustrative table are proposed administrative tools, not validated benchmarks or industry standards.
• Research limitation: this article does not provide statistical process-control guidance, and the illustrative numbers are hypothetical. Agencies that need a formal capacity model should involve someone with operations or data skills.

Sources

1. InsuranceYo — Services. https://insuranceyo.com/services
2. InsuranceYo — Home. https://insuranceyo.com/
3. U.S. Federal Trade Commission — FTC Safeguards Rule: What Your Business Needs to Know (context on monitoring and access). https://www.ftc.gov/business-guidance/resources/ftc-safeguards-rule-what-your-business-needs-know