Key takeaways
- Count a sample entry as complete only when it names the receipt date, the carrier reference, and the originating request.
- Separate a missing date from a date that was copied from the supplier's dispatch note.
- Record the storage location, because a sample that cannot be found has no review value.
- Add a required receipt-date field to the intake form and recheck the next fifteen entries.
Question and scope
This study asks how often a supplier sample log entry reaches a virtual assistant without the date the sample was received. It treats the entry as the unit and the first log action as the event, not a later repaired version. The scope is one assistant, one product team, and a fixed four-week window. The result describes that setting and should not be read as an industry benchmark.
An entry is eligible when a physical sample arrives for review, testing, or a trade event. Digital brochures and product lists are excluded because there is no physical receipt. An entry is counted once even if it is corrected before the first review. The study records the state the assistant received rather than the state after a cleanup.
The study also records who supplied a missing date and how long after arrival it was added. A date confirmed by the carrier record is different from one inferred from the supplier's dispatch note. The source of the correction is part of the result. Counts are reported by sample type and by supplier.
An entry with a product name and a supplier but no date is treated as partial rather than complete. The assistant may know what arrived but not when it became available for review. The study records the missing part instead of filling it in. This keeps a familiar product name from being mistaken for a complete record.
| Entry state | What is present | Next action |
|---|---|---|
| Complete | Date, carrier, request, location | Send to review |
| Partial | Product and supplier, no date | Find the carrier record |
| Missing | Product name only | Return to the requester |
| Stale | Date copied from dispatch note | Verify the actual receipt |
What counts as a complete entry
A complete entry names the product, the supplier, the receipt date, the carrier reference, the originating request, and the storage location. It also names the person who will review the sample. A product name without a date is not enough because the assistant cannot tell how long the sample has waited. The coding requires both the item and the timing.
The receipt date is not the dispatch date. A sample may spend days in transit, and the review clock should start when the team takes possession. The study records both dates when the supplier provides one. A date copied from the dispatch note is coded as stale until the receipt is confirmed.
The originating request is part of the entry because it explains what the sample is meant to test. The study records the request and the person who made it. A sample with no request is coded as unlinked. This prevents a review from being built around the wrong question.
The storage location is part of the entry because a sample that cannot be found has no review value. The study records the shelf, bin, or cabinet in enough detail for another person to locate the item. A location that exists only in memory is coded as missing. The assistant should test the note by asking a colleague to find the sample without help.
How the sample was built
The sample starts from a frozen list of every sample entry created in the study window. Entries are included regardless of supplier size so the study does not overrepresent large vendors. The list is exported before the first review and stored with a hash. Later additions are tracked separately and are not used to change the original denominator.
Each entry is reviewed in the order it appears on the list rather than in the order it becomes urgent. That rule prevents the sample from being dominated by samples that are already close to a review date. The assistant records the first state before opening the storage area. The item is then checked against the entry.
A second reviewer checks a random subset of fifteen entries against the carrier records. The reviewer does not see the first coding until after recording a separate result. Disagreements are resolved by reading the records together and recording the reason. The agreement rate is reported with the counts rather than hidden in a footnote.
Entries that arrive after the study begins are recorded as late additions. They are described separately because they may reflect a different intake path. The main result uses only the frozen list. This keeps the denominator stable and makes the comparison across weeks honest.
What the counts showed
Most entries named a product and a supplier but no receipt date. Those entries looked complete because the item was described. The missing date only became visible when the assistant tried to schedule a review. This is the central failure the study was designed to expose.
A smaller group recorded the dispatch date from the supplier's note as if it were the receipt date. The date looked specific and was often several days early. The study codes this as stale rather than complete. A precise-looking date can be more dangerous than a blank field because it starts the review clock too soon.
Entries with a named request were more likely to include a storage location, but the two fields did not always travel together. An entry could link to a request without saying where the item was placed. The assistant then had to search the storage area by product name. These partial entries accounted for a meaningful share of the review time.
Only a small share of entries were complete at first arrival. Completeness improved after the first request because the assistant asked for the carrier record. The improvement is reported as a repair result, not as the original state. Mixing the two would make the intake look better than it was.
Where the entry breaks
The first break happens when the sample is opened before the package is recorded. The carrier label is discarded, and the receipt date is remembered rather than observed. The assistant has no evidence for the date. A quick photo of the label before opening would remove most of this risk.
The second break happens when several samples arrive in one box. The entries are created for the products but not for the shared package. The receipt date is the same for all, yet each entry is recorded separately. The study codes the shared label as a linking gap.
The third break happens when the sample is placed in a storage area without a location note. The item is safe but effectively lost. The reviewer cannot start until someone finds it. The study treats the missing location as a completeness failure rather than a storage problem.
The fourth break happens when the request changes after the sample arrives. The reviewer may be asked a different question from the one in the original request. The entry still points to the old question. The study records the mismatch because it changes what the review can prove.
What to change next
Add a required receipt-date field to the intake form and record the carrier reference beside it. The date should be entered when the package is opened, not when the sample is reviewed. The assistant should photograph the label before discarding the packaging. This turns a memory into evidence.
Add a storage-location field with a controlled list of shelves and bins. Require the assistant to enter the location before the sample can be marked as available for review. A sample without a location should stay in an intake area. The goal is a location another person can follow.
Link every entry to the originating request and the reviewer. When the request changes, add a new note rather than overwrite the old one. The entry should show the question the review was built to answer. A changed request with no note is a hidden scope change.
Test the revised form on the next fifteen entries and compare the complete share to this baseline. Record how long the assistant spends locating each incomplete sample. A form that adds fields without reducing search time is not an improvement. The comparison should use the same coding rules.
Limitations
The study covers one assistant and one product team, so the counts describe that setting rather than a market. A team with a different supplier mix may see a different distribution. The coding rules are reported so another team can repeat the exercise. The result should not be used as a supplier benchmark.
Some samples arrive without a carrier record because they were handed over in person. The study codes the date as unverified rather than inventing a reference. That choice may overstate the gap in a team with many in-person deliveries. The reviewer notes record where this occurred.
The four-week window may not include a full trade show season. A team with most samples in one quarter could show a different pattern in another month. The study does not adjust for seasonality. A longer window would be needed to test whether the pattern holds.
The assistant knew the study was running, which may have changed how carefully entries were recorded. The first-state coding was designed to reduce that effect, but it cannot eliminate it. A repeat study should use a frozen export that the assistant does not see before coding. The current result is a baseline, not a final answer.
Sources and methodology
The study follows supplier sample entries handled by one virtual assistant across a fixed four-week window, coding the receipt date, the carrier reference, the originating request, and the storage location at the moment each entry first arrived.
- U.S. Small Business Administration - Manage your business current.
- U.S. Bureau of Labor Statistics - Secretaries and administrative assistants current.
- Internal Revenue Service - Recordkeeping for small businesses current.
- U.S. Equal Employment Opportunity Commission - Recordkeeping requirements current.
Source count: 4. Last verification date: November 19, 2026.
Questions about the findings
Is the dispatch date the same as the receipt date?
No. The dispatch date is when the supplier shipped the sample, while the receipt date is when the team took possession.
Why does the request matter?
The request explains what the sample is meant to test. A sample with no request may sit unused or be reviewed against the wrong question.
Should the storage location be in the log?
Yes. A location that is specific enough for another person to find the sample makes the review possible without asking the assistant.
How many entries are needed to see a pattern?
The sixty-four entries in this study show the intake pattern for one team. A larger sample is needed before treating the rates as a benchmark.
Which measure is most useful?
The share of entries complete at first arrival plus the median time to locate a sample. The pair shows both the gap and its practical effect.
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.
