Small-business outsourcing research
What share of new assistant assignments have a named trainer and a first-week check?
A protocol for measuring onboarding coverage, with tests for a named trainer, a first-week review, and a record the next supervisor can use.

Research question and scope
This protocol asks what share of new assistant assignments have a named trainer and a first-week check. The unit is one assignment of a virtual assistant to a queue, identified by the assistant, the queue, and the start date. The study measures whether the record names a trainer, whether the trainer met the assistant in the first week, and whether a written review exists by the end of that week. It does not evaluate the assistant's performance.
Set the scope to one small business, one onboarding process, and one set of assigned queues. Record the roles that may act as trainer and the person who owns the review. If the onboarding process changes during the window, keep the earlier definition for the full sample or analyze the change as a separate period. A new checklist can look like better coverage when it is only a new form.
Population and unit of analysis
Define the population as every assistant assignment that started during the window, including assignments that ended before the first week closed. The unit is the assignment, not the assistant, because one assistant can start on several queues. An assignment that changes trainer remains one unit with a handoff date. A second assignment to the same queue later is a separate unit linked to the first.
Record the queue, the service line, and whether the assistant is new to the business or new only to the queue. These strata matter because a new hire and an internal transfer carry different onboarding needs. Include assignments created without a formal start date, because the base rate is part of the finding. Test the unit definition on two ordinary assignments before collection begins.
An assistant can be assigned to a queue while the trainer is on leave, which produces an assignment with a trainer named on paper but no first-week contact. Record both the named trainer and the person who actually met the assistant. A record that names only the manager is not proof of training. The unit should preserve the difference between assignment and contact.
Definitions that make the measure reproducible
Define a named trainer as a specific person recorded before the start date, not a team or a role title. Define a first-week check as a meeting or a written review that happened within seven calendar days of the start. Define a completed review as a note that states what the assistant did well, what needs practice, and what changes in week two. Define an uncovered assignment as one missing the trainer or the check.
Do not count a welcome message as a first-week check. Do not count a trainer who is named but never contacted as coverage. An assignment that was paused before the first week should be reported separately rather than counted as covered. Each definition should include a positive example and a boundary example so a second reviewer can apply it the same way.
Evidence standard and data dictionary
For each assignment, capture the assistant, the queue, the start date, and the trainer. Add the date the trainer was named, the date of the first meeting, and the date of the written review. Record who wrote the review and whether the assistant received it. Keep the review with the assignment record rather than in a personal folder.
Also capture whether the assistant had access to the queue on the first day and whether a backup trainer was named. Record any change of trainer and the date it happened. If the assignment ended early, record the reason and whether a review was still completed. A second reviewer should be able to rebuild the first week from the record.
If the business uses a standard onboarding form, keep the version that was used for the assignment. A form updated after the start can make the record look more complete than it was. Record the date the form was used. The evidence should describe the week as it happened, not as it was reconstructed later.
Sampling and collection
Draw the sample from the assignment log rather than from a list of completed onboardings. Record the export date, the filters, the row count, and the selection rule. Include assignments from every queue and every start week so the result is not dominated by one hiring push. If the list is ordered by start date, a fixed interval spreads the sample across the window.
Collect the assignment record and the review as they existed at the end of the first week. If a review was added later, record the addition date and analyze the original coverage separately. Do not infer a meeting from a calendar invitation that was never accepted. Note the collection date separately from the start date.
Record the trainer's own queue and whether that person had a backup during the week. A trainer with an unmanaged queue may be named on the record but unavailable in practice. Use the staffing note for the same week, not a later recollection. If the note is missing, mark the assignment as unverified rather than assuming coverage.
Analysis and reporting
Report the number of assignments, the share with a named trainer, the share with a first-week meeting, and the share with a written review. Show the counts by queue, service line, and assistant type. Present the median days from start to first meeting. Use the same denominator for every rate.
Inspect the uncovered assignments and describe the pattern without naming the assistant or the trainer. A cluster in one queue may point to a missing trainer, while a cluster in one start week may point to a hiring push that outpaced onboarding. Compare the result with the trainer's own workload. Report paused assignments separately.
A useful additional view is the share of assignments where the trainer changed during the first week. That view separates a coverage problem from a continuity problem. Show it beside the coverage rate and describe the difference. The owner can then decide whether to name a backup trainer or reduce the trainer's queue.
Report the result by start week and by service line so a reader can see whether gaps cluster around a hiring push or a single queue. Add the number of assignments that ended before the first week closed, because those can distort the coverage rate. Present the review completion rate beside the meeting rate. A meeting without a written review is only partial coverage.
Limitations and sources of error
The record cannot show whether the training was useful or whether the assistant understood it. It can show only that a person was named and a review was written. A covered assignment is not proof of good performance, and an uncovered one is not proof of failure. The protocol also cannot capture a trainer who helped every day without a recorded meeting.
Calendar records can be deleted, and a review can be written from memory after the week ends. Record those cases and their treatment instead of dropping them silently. If the same person is the trainer and the reviewer, note the independence limitation and analyze that subgroup separately. A missing name in the log may be a recording problem rather than a real gap.
Review cadence and next action
Give the result to the owner and the person who coordinates assignments and ask them to choose one observable change. The change might be a named backup trainer, a first-week review template, or a start-date rule that requires a trainer before access is granted. Record the owner, the effective date, and the measure that will show whether the change worked. Avoid changing the trainer role and the review form at the same time.
Repeat the protocol with the same definitions after the change and compare the same fields. If coverage rose but the review quality did not, the team may be meeting without a useful note. If reviews improved but coverage fell, the new template may be too heavy for a busy week. Close the review when the owner accepts the finding and the next sample is scheduled.
Sources
- U.S. Department of Labor, Wage and Hour Division, U.S. Department of Labor; checked 2026-11-07
- U.S. Small Business Administration, manage your business, U.S. Small Business Administration; checked 2026-11-07
- NIST Cybersecurity Framework 2.0, National Institute of Standards and Technology; checked 2026-11-07
- U.S. Government Accountability Office, internal control standards, U.S. Government Accountability Office; checked 2026-11-07
Frequently asked questions
Does a favorable sample prove the routine caused the result?
No. The design is observational and supports a bounded operating decision, not a universal causal claim.
What should an owner review first?
Start with high-consequence defects, missing denominators, exceptions, and cases that required the owner to reconstruct the evidence.
Related research
How long do supplier bank-detail changes wait for independent verification?
A protocol for measuring the delay between a supplier bank-detail change and the independent check that confirms it.
What share of damaged-order claims include a usable photo and order reference?
A protocol for measuring claim evidence quality, with clear tests for a usable photo, a linked order, and a recorded delivery condition.
How often do support macros cite a policy version that is no longer current?
A protocol for auditing saved replies against the current policy register, with a test for stale wording, missing versions, and untested macros.