A supplier sample tracking log is not a shelf with a stack of boxes. For a virtual assistant, the log is the record that says what arrived, what it was requested for, and what decision it supports. A sample that cannot be found when a reviewer asks delays the whole evaluation. The log makes the physical item and the decision visible in one place.
Record the sample at the moment it arrives
Write the arrival date, the carrier, and the condition of the package before the box is opened. A damaged sample should be photographed before anything is removed. The assistant should record the supplier and the tracking reference. A sample recorded a day later may lose the details that matter.
Label the sample with a log identifier as soon as it is unpacked. The identifier should be short, unique, and visible without opening the box again. The assistant should record the label in the log and on the item. A sample with no identifier is a sample that will be misplaced.
Check the contents against the packing note and record any difference. A missing part or an extra item changes what the reviewer can test. The assistant should note the difference and inform the supplier contact. A silent shortage produces a review that is not about the product.
Store the sample where the log says it is stored. The location should be specific enough for another person to find it without asking. The assistant should record the shelf, bin, or cabinet in the entry. A location that exists only in memory is not a location.
Link each sample to the request and the supplier
Record the original request and the person who made it. A sample may arrive for a product review, a quality check, or a trade event. The assistant should link the entry to the request rather than retype the story. A sample with no request has no purpose.
Keep the supplier contact and the account owner in the entry. The contact may change during a long evaluation, and the account owner is the person who can answer a commercial question. The assistant should record both. A sample that cannot be traced to a contact is hard to return.
Note the terms that came with the sample, such as a return requirement or a use restriction. The assistant should record the terms in plain language and attach the message. A sample that must be returned cannot be disposed of like a gift. A use restriction can affect what the team may publish.
Mark whether the sample is a duplicate of one already on file. A duplicate should be recorded and either stored or returned under the same rule. The assistant should link the two entries. A duplicate that is logged as new distorts the review count.
Track the review and the decision
Record who will review the sample and the date the review is due. A sample that sits with no reviewer is not in progress. The assistant should set a reminder for the due date. A reviewer who is not named will assume someone else has it.
Write the questions the review must answer before the sample is sent. A test with no question produces an opinion rather than evidence. The assistant should record the questions and the expected output. A clear question makes the reviewer's note useful.
Record the decision and the evidence behind it. The decision may be to approve, reject, request a change, or hold for more information. The assistant should quote the reviewer's reason rather than paraphrase it. A decision without a reason is hard to revisit.
Update the supplier contact with the outcome when the review is complete. The message should state the decision and the next step, if any. The assistant should record the send date and the contact. A supplier who hears nothing will keep asking.
Handle returns, storage, and disposal
Check the return terms before a sample leaves the building. Some samples must be returned in the original packaging, while others may be kept or destroyed. The assistant should record the deadline and the method. A return sent after the deadline may not be accepted.
Record the condition of a returned item and the carrier reference. A dispute about damage is easier to resolve with a photo and a tracking number. The assistant should keep the receipt with the log entry. A return without proof is only a claim.
Set a storage limit for samples that are kept. A shelf that fills with old samples hides the current ones. The assistant should record the date a sample becomes eligible for disposal. A limit turns an accumulation into a decision.
Dispose of a sample only with the approval named in the log. The assistant should record the date, the method, and the person who approved it. A sample that may contain personal or confidential material needs a secure method. A disposal without a record cannot be defended.
Report the pipeline weekly
Count the samples by stage, such as received, in review, decided, returned, and disposed. A count by stage shows where the work is waiting. The assistant should record the count on the same day each week. A count that changes its method cannot be compared.
List the samples that passed their review date and the reason for the delay. The assistant should name the reviewer and the next action. A list of late items is more useful than a general warning. A weekly list keeps the delay visible.
Show the decisions that are waiting on the supplier or on the team. The assistant should separate the two so the next action is clear. A decision that is waiting on both is usually waiting on neither. The report should name one owner per item.
Send the report to the people who can act on it and keep it with the log. A report that goes to a wide list with no owner will be read and ignored. The assistant should record the recipients and the date. A short report with owners is better than a long one.
Close the loop with the supplier
Send a short summary to the supplier when a batch of samples has been reviewed. The summary should state the decisions and the next step for each item. The assistant should not share internal notes or unconfirmed plans. A clear summary reduces repeated follow-up.
Return or dispose of the samples on the agreed schedule before the summary is sent. A supplier who is told a sample was kept may ask for it back. The assistant should record the final state in the log. A summary that conflicts with the physical state creates confusion.
Ask the supplier for one improvement to the sample process, such as better labelling or a smaller package. The assistant should record the suggestion and the response. A small improvement reduces the next arrival's work. The log becomes a source of process change.
Archive the closed entries and keep the open ones in the active view. The assistant should record the archive date and the rule used. A log that keeps every entry in one list becomes hard to read. A clean active view keeps the next review visible.
Key takeaways
Record each sample on arrival with the date, carrier, condition, and tracking reference. Label it with a unique identifier and store it where the log says. Check the contents against the packing note and record any difference. A sample with no identifier is a sample that will be misplaced.
Link every sample to the request, the requester, and the supplier contact. Record any return or use terms that came with it. Mark duplicates and link them to the original entry. A sample that cannot be traced to a contact is hard to return.
Name the reviewer and the review date, and write the questions before the sample is sent. Record the decision with the reviewer's reason. Tell the supplier the outcome and the next step. A decision without a reason is hard to revisit.
Set a storage limit and a recorded disposal rule. Report the pipeline weekly by stage and by owner. Close the loop with a short supplier summary. A log that keeps every entry in one active list becomes hard to read.
Continue building the workflow
Related support: onboarding operations support, contact us. The U.S. Small Business Administration - Manage your business publishes guidance on managing business records and day-to-day operations.
Related reading
Set a refund request log for a virtual assistant
A refund log that ties each request to the original transaction, the written policy, the evidence, the approval limit, and the confirmation the customer receives.
Create a client offboarding checklist for a virtual assistant
A closeout checklist that fixes the last day, final deliverables, access removal, records transfer, and the confirmation the client receives.
Build a newsletter production checklist for a virtual assistant
A production checklist that fixes the send date, gathers source material, checks links and claims, routes review to the right owner, and archives the sent issue.
