VA Delegation Audit

1. Record the work as it happens

Track tasks through a representative working week. Include frequency, active time, interruptions, systems used and the person who currently handles each task. Add monthly or quarterly work separately so a quiet week does not hide it.

Use specific task names. “Admin” is difficult to scope; “update contact records after sales calls” has a trigger, an input and a visible result. Group related activities into workflows when they share an owner and process.

Record the actual steps rather than the ideal process. If the team repeatedly searches for missing information or fixes avoidable errors, that is part of the current workload and an opportunity to simplify before delegating.

2. Decide whether the task should continue

For each task, ask whether it is still needed, whether the output is used and whether a simpler process would remove the work. Eliminate unnecessary steps before assigning them to another person.

Some work is a good candidate for automation because the inputs and rules are stable. Other work needs a person to resolve exceptions or interpret context. Avoid automating an unclear process, and avoid using a VA simply to preserve a task that no longer serves the business.

3. Identify what can be handed over safely

Look for work that recurs, follows a teachable process and has an output someone can review. Examples may include CRM maintenance, calendar coordination, approved inbox routing, data cleanup, document organization and recurring report preparation.

Tasks involving major spending, contract commitments, sensitive decisions or specialist judgment need explicit authority limits and an appropriate internal owner. A VA may prepare the information while the authorized person retains approval.

Access is part of readiness. NIST’s least-privilege principle limits access to what is needed for the assigned task. Apply that principle by defining the systems, records and permissions the person needs rather than sharing unrestricted accounts. [S5]

4. Assess readiness before choosing a priority

Use the following prompts as a discussion tool. They are a practical framework, not a scientifically validated score. A task can be time-consuming and still be unsuitable to delegate until its risks and decision boundaries are resolved.

Start with tasks that are ready, frequent enough to matter and easy to pilot. Where time value is high but readiness is low, create a preparation task first: document the process, resolve permissions or agree on the acceptance standard.

5. Complete the task inventory

Use one row per recurring task or coherent workflow. Keep the detailed procedure in a separate SOP so the audit stays readable.

This worksheet is available as an editable version below. Go to the worksheet

For the first task selected for delegation, complete this brief.

This worksheet is available as an editable version below. Go to the worksheet

6. Estimate useful time released

Gross time available to reassign equals occurrences in the period multiplied by current minutes per occurrence, divided by 60. Then subtract the internal review, coordination and rework time that will remain after delegation.

Fictional example: a CRM update workflow happens 100 times per month and takes six minutes each, totaling ten hours. After delegation, the internal owner expects two hours of review and coordination. Modeled ongoing time released is eight hours per month.

If initial documentation and training take three internal hours, first-month net time released is five hours, assuming all other conditions hold. Track actual time during the pilot instead of treating the estimate as a guaranteed result.

Time released is not automatically cash saved. It becomes useful when the team redirects it to work that matters, such as client delivery, qualified sales conversations or decisions only the internal owner can make. If the time remains scattered across interruptions, the business benefit may be smaller than the raw hours suggest.

7. Write a short SOP and test it

Document the trigger, required inputs, steps, completed output, acceptance criteria and escalation rules. Use a sample that shows a correct result and one that shows an exception. Explain where work is recorded and how the next person knows it is ready.

Run a small batch with the person who will own the workflow. Review the result against the agreed standard and identify whether errors come from missing instructions, unclear inputs, insufficient access or a training gap.

Expand the scope when the output is consistent and the review effort is manageable. Measure timeliness, first-pass acceptance, rework and internal time released. Avoid adding unrelated tasks so quickly that the process loses a clear owner.

8. Keep responsibility visible after the handoff

Agree on the update rhythm, escalation route and backup arrangement. A shared task list should show what is due, what is blocked and who needs to decide. The internal manager remains responsible for priorities and any decisions outside the delegated authority.