Philippines staffing guide · Published
A 30 Day Trial Scorecard for a Philippines VA
Measure evidence, not enthusiasm. Use four checkpoints, a small rubric, and a decision that expands one lane at a time.
On this page
A trial period is useful when it produces evidence about the work, not just a feeling about the person. A VA who is pleasant on calls but misses source checks is not ready for more authority. A VA who is quiet but accurate may be exactly what the queue needs.
Build the scorecard before the trial starts. Use the real task lane, the real tools, and a reviewer who can compare the work with the standard. Keep the number of criteria small enough to apply consistently. The decision at day 30 should be expand, continue with a narrower lane, or stop.
1. Set four checkpoints
Week one is orientation: can the VA explain the lane, find the sources, and recognize a stop? Week two is supervised work: can they complete routine tasks with review? Week three is gated independence: can they handle the queue with a sample check and a clear exception route? Week four is an independent sample: does the work meet the standard without line-by-line correction?
Each checkpoint needs a different evidence set. Do not use the same ticket count for all four. Record the review intensity, the error types, and the questions the VA asked. A question that repeats may indicate a missing rule, not a weak hire. The checkpoint should test the system as well as the person.
2. Use a small, observable rubric
Four criteria are enough for most lanes: accuracy, source and evidence use, boundary compliance, and communication. For each, write what a pass looks like and what a fail looks like. Cite the specific record. A score without evidence is an opinion.
Include a correct stop as a pass. If the VA refuses an unverified reset or routes a refund without approval, that is the behavior you want. A scorecard that rewards only speed and closure will teach the wrong lesson. Review the adverse cases deliberately.
3. Separate person, process, and product
A missed source may be a training issue, a broken link, or a source that no longer exists. A slow response may be an access problem or a queue design problem. Classify the cause before deciding on coaching. The trial should improve the brief as well as the VA.
Keep a short log of the changes made during the trial: a new template, a clarified rule, a permission added, a source updated. At day 30, review whether those changes improved the evidence. If the same failure persists after the repair, the fit may be wrong.
4. Make the day 30 decision explicit
Meet with the VA, the reviewer, and the business owner. Review the four checkpoints, the sample, the error pattern, and the changes made. Decide whether to expand, continue with a narrower lane, or stop. Record the reason and the next review date.
If the decision is to expand, add one lane and keep a review gate. If the decision is to continue narrowly, state what evidence would support expansion. If the decision is to stop, follow the contract and the offboarding checklist. A clear decision is fairer than a trial that drifts without feedback.
Questions and operating boundary
How many tasks should a trial cover?
Start with one stable lane. Add a second only after the first produces accepted evidence and the reviewer can support the additional review load.
Should the trial be paid?
Yes. A trial that performs real work should be paid under the applicable agreement and local requirements.
What if the VA is strong but slow?
Check whether the delay comes from tooling, unclear rules, or review bottlenecks before treating it as a performance issue. Speed usually improves after the lane is stable.
Source
ilo.org provides authoritative background and does not endorse this service.