Key takeaways
- Count only corrections made after the first delivery.
- Separate a missing approval from a missing instruction or a changed request.
- Record the evidence for the cause code so a second reviewer can repeat it.
- Test one control with the same cause definitions.
Question and scope
This study asks what share of a virtual assistant's first-month rework traces to a missing approval. It treats rework as a correction made after the first delivery and the cause as the condition that made the correction necessary. The scope is one role, one client, and a fixed onboarding window. The result describes that setting and should not be read as a measure of assistant quality.
The unit is one rework event tied to one task. An event is eligible when the task was delivered and later changed. Changes made before the first delivery are excluded because they are part of drafting. Record the inclusion rule before reviewing so the denominator is not built from convenient examples.
The study also records whether the rework was requested by the client, the manager, or the reviewer. A client request may reflect a changed need, while a reviewer request may reflect a quality check. Report the requester with the cause. That distinction keeps a legitimate change from being counted as a process failure.
| Cause | Observable sign | Evidence | Repair |
|---|---|---|---|
| Missing approval | No sign-off before delivery | Approval record | Define the category |
| Missing instruction | Format or source unknown | Task brief | Add the example |
| Changed request | Outcome moved after delivery | Client message | Confirm the scope |
Definitions and evidence standard
Define a missing approval as a case where the work needed a named person's sign-off before delivery and that sign-off did not happen or was not recorded. Distinguish it from a missing instruction, where the assistant did not know the required format or source, and from a changed request, where the client or manager changed the outcome after delivery. Record the evidence for that decision so a second reviewer can apply the same test. Use the same evidence standard for every event in the review.
Use the draft, the delivery message, the correction request, and the approval record as the evidence. Record the cause code and a short reason. If more than one cause applies, choose the one that triggered the rework and note the secondary cause. A single event should not be counted twice.
Sampling and measurement
Collect rework events from the first month and freeze the list before coding. Include events from routine and sensitive work. If the role has more than one client, report each client separately. Record the number of tasks delivered in the same period so the rework share has a denominator.
Measure the number of rework events, the number caused by a missing approval, the number caused by a missing instruction, and the number caused by a changed request. Report the counts and the share of delivered tasks affected. Add the number of events that could not be classified because the record was incomplete. Keep the counts beside the share so a small denominator is visible.
If a task was delivered to more than one recipient, record whether each recipient received the same version. A correction to one copy may not reach the other. Report the distribution separately. A version gap is a different problem from a missing approval.
Findings and interpretation
Present the distribution before suggesting a cause. A cluster of missing approvals in client-facing work may mean the approval category is too narrow. A cluster in internal work may mean the reviewer was not named. A cluster of changed requests may mean the intake process did not confirm the outcome. Read the actual updates behind the largest cluster before naming a reason.
Read the events behind the largest category and compare the draft with the correction. Record whether the assistant had the information needed to seek approval. A missing approval can be an assistant error, a reviewer gap, or a rule that never required approval. The finding should point to the specific control that failed.
Compare the rework share with the number of approval steps in each task. A task with several approvers has more chances for a missed sign-off but also more checks. Report the step count beside the rate. Do not compare a simple task with a multi-step approval as if they carried the same risk.
Limitations
The study sees recorded rework, not every correction made in conversation. A quick fix in a chat may never appear in the task record. The cause code also depends on the reviewer's interpretation. A correction can have more than one cause, and the chosen primary cause may be debated.
The first month may include normal learning that would not occur later. If the approval rule changed during the window, the events may not be comparable. Record these limits with the result and keep the evidence in a restricted file. Report the result by period rather than treating the whole month as one block.
Record whether the correction changed the deliverable, the audience, or only the wording. A wording change may be a quality improvement rather than rework caused by a missing approval. Report the change type with the cause. That distinction keeps the rework count meaningful.
Practical next step
Choose one repair that matches the most common cause, such as an approval category, a named reviewer, or an outcome confirmation at intake. Write the change, the owner, and the date it starts. Define the measure that will show whether it helped, using the same cause codes. Test it on the next month's events.
Keep the before and after events separate so the comparison is honest. Record the events that were excluded and why. Review the result with the assistant, the reviewer, and the client owner. If the change does not help, record that result too. The purpose is to reduce avoidable rework, not to assign blame.
Choose the test period from tasks that use the same client and approval guide as the baseline. If the change also alters the guide, the result cannot separate the effect of the new category from the effect of the training. Record the first task that used the revised path. Keep the baseline events in the comparison so the new category can be tested.
Comparing task types
Client-facing deliverables may carry a higher approval risk than internal updates. A sensitive document may need two approvals, while a routine status note may need none. Report the rework share by task type and label small groups as descriptive only. Report the type view beside the overall share so the risk is not hidden.
If one type dominates the missing-approval count, check whether its category is defined in the approval guide. A type that looks riskier may simply have more opportunities for a missed sign-off. Compare the process, not the person. The next study can test a type-specific approval rule before applying it to all work.
Keep the approval guide version with each event. A rule change can make an earlier event look like a miss when the rule did not exist at the time. If the guide changed during the window, split the result by version. That split is more honest than a single rate across two rules.
What the evidence does not show
The study does not establish that the rework harmed the client or that the assistant was careless. It also does not measure whether the final work was better after the correction. Those questions need a quality review. A cause code is a process observation, not a performance verdict.
Do not use the result to promise a client that no deliverable will ever need correction or that every approval will be recorded. Do not publish client names or task details. Keep the sample size, the cause definitions, and the review decisions with the result. If the client needs a quality conclusion, use a separate review.
Keep the rework records in a restricted workspace because they may contain client and employee details. Publish only the aggregate counts and the cause categories. If a client asks for the result, describe the method and the control rather than sharing raw corrections. The study is an internal improvement tool, not a client-facing audit.
Using the result in a client conversation
A client may ask how the team controls rework, and the study supports a careful answer. Describe the window, the number of delivered tasks, the rework share, and the approval control that was added. Do not say that every task will be right the first time or that no correction will ever be needed. Explain that the measure covers recorded rework and that the reviewer confirms open items.
If the client asks for a commitment, offer a process commitment such as a defined approval category, a named reviewer, and an intake confirmation. Record the commitment and the measure that will show whether it was met. Keep client-specific details out of any public write-up. The study is an internal quality tool, not a guarantee about any deliverable.
Compare the missing-approval share with the number of approval categories in the guide. A narrow guide may push work through a route that never required a sign-off. Report the number of categories and the share together. That comparison points to a rule repair rather than a reminder.
Sources and methodology
The study traces first-month rework events to a primary cause and reports the share tied to a missing approval. Each event is linked to the draft, delivery, correction, and approval record.
- U.S. Small Business Administration — Hire and manage employees current.
- U.S. Office of Personnel Management — Training and development current.
- U.S. Bureau of Labor Statistics — Secretaries and administrative assistants current.
- CISA — Secure Our World current.
Source count: 4. Last verification date: November 8, 2026.
Questions about the findings
Does this measure prove that the assistant's work was correct?
No. It describes a documented pattern in one role and one window. A separate quality review is needed to judge the work itself.
Can the result be compared across clients?
Only when the definitions, the task mix, and the review method stay the same. Small groups should be described rather than ranked.
What should the team do first?
Pick one repair that matches the most common gap, record the change, and retest with the same definitions before claiming improvement.
Put the finding to work
Review the full research library, compare cluster coverage inside Onboarding And Retention Research, and pair these findings with our VA candidate screening support.
