You install time tracking software.
Your Filipino VA starts logging hours.
The dashboard shows “active time,” “idle time,” and “keystrokes per hour.”
You feel reassured. The numbers are high. They must be working hard.
But are they actually getting anything done?
Keystrokes-per-hour tells you how much someone is typing.
It doesn’t tell you if they’re producing valuable work, completing tasks on time, or moving your business forward.
And it creates serious problems.
Some Filipino VAs learn to game the system. Employers who rely on keystroke tracking end up with inflated metrics and zero clarity on actual productivity.
Here’s why keystroke monitoring is a bad idea and here’s a better option.
Keystroke Monitoring Measures Activity Instead of Results
Keystrokes per hour sounds like a productivity metric.
It’s not.
The OECD defines productivity as output per unit of input. Goods produced. Services delivered. Tasks completed. Not “keyboard movements per hour.”
A VA spending 30 minutes reading through customer support tickets to identify patterns isn’t typing much.
But that analysis might reveal a process bottleneck that saves you 10 hours per week once fixed.
Another VA might type furiously for hours, copying data between spreadsheets, while a better-structured workflow could eliminate that task entirely.
Keystrokes tell you nothing about which scenario you’re dealing with.
Gaming Activity Metrics Is Trivially Easy
Filipino remote workers on Reddit threads in communities like r/buhaydigital and r/WFH discuss keystroke and activity trackers openly.
The consensus: everyone knows how to beat them.
Mouse jigglers. Macro tools. Apps that simulate keyboard activity. Scripts that open and close windows. Hardware devices that physically move the mouse.
Some VAs describe running YouTube videos in the background or typing random text into a notepad file while doing something else entirely.
Keystroke Tracking Damages Trust and Increases Turnover
Filipino VAs consistently describe keystroke loggers and screenshot-heavy monitoring tools as anxiety-inducing forms of micromanagement.
In threads across online platforms, VAs talk about rejecting otherwise good job offers because the employer required invasive activity tracking. T
hey describe the mental strain of knowing every click is watched. The pressure to “look busy” rather than focus on outcomes.
Good VAs have options. They choose employers who treat them like professionals, not surveillance subjects.
When you install keystroke monitoring, you’re not just measuring activity. You’re signaling distrust. You’re telling your VA that you assume they’ll slack off unless watched constantly.
What Outcome-Based Tracking Actually Looks Like
Outcome-based tracking shifts focus from “what are they doing right now” to “what did they deliver.”
You define clear outputs tied to business value. You set timelines and service-level expectations. You track whether work gets done on time and meets quality standards.
Defining Clear Outputs for VA Roles
For admin and operations VAs:
- Number of records updated correctly per day
- Bookings completed with error rate below 2%
- Turnaround time from request to completion for standard tasks
For customer support VAs:
- Tickets resolved per day with first-response time targets
- Customer satisfaction scores where available
- Queue health metrics like open vs closed tasks and backlog age
For marketing and content VAs:
- Number of assets produced that meet acceptance criteria
- Required revisions per piece as a quality indicator
- Traffic or engagement metrics tied to campaigns
For research and project support:
- Decision-ready memos or spreadsheets delivered per week
- Milestones achieved in project plans
- Completeness and usefulness evaluated in weekly reviews
Notice none of these require watching what the VA does minute-by-minute. They measure what comes out at the end.
Using Service-Level Agreements Instead of Presence Monitoring
Instead of “must be actively typing,” outcome-based systems use service-level expectations.
“Respond to customer emails within 4 hours during business hours.”
“Produce 5 blog post outlines per week that meet our content brief template.”
“Complete expense report processing within 48 hours of submission with 95% accuracy.”
These expectations anchor performance to timelines and quality standards, not busy-looking activity.
How to Implement Outcome-Based Tracking with Filipino VAs
Start with the Work That Matters
Before choosing tools or setting metrics, define what your VA role exists to produce.
Break this into 3 to 7 core outputs with either numeric targets or qualitative standards.
Examples:
- “Process 40 customer support tickets per week with average first-response time under 2 hours”
- “Deliver 3 fully researched vendor comparison memos per week”
- “Maintain social media posting schedule with all content drafted 48 hours before publication”
Weekly or bi-weekly one-on-ones review progress against these outputs, identify blockers, and adjust as needed.
Choose Tools That Track Deliverables
Use project management or ticketing systems as your source of truth for what’s getting done.
Tools like Asana, Trello, Monday, or ClickUp let you create tasks, assign them, set due dates, and track completion. The system shows you throughput automatically.
Helpdesk tools like Zendesk or Freshdesk track customer support metrics natively. CRM systems like HubSpot or Pipedrive show sales and lead management activity by deliverable.
If you need time tracking, many platforms now offer simple timer-based systems where the VA logs hours against specific tasks or projects. This gives you visibility into how time is allocated without invasive monitoring.
Build Privacy-Compliant Policies
Even if your VA is a contractor, good practice includes clear documentation about what you’re tracking and why.
Under Philippine Data Privacy Act requirements, this means:
- A written clause describing what tools you use, what data you collect, and for what purposes
- Avoiding always-on monitoring like keylogging, webcam, or audio capture
- Limiting data collection to what you actually need
For time tracking tools, document:
- What gets logged (hours worked, tasks completed, project tags)
- What doesn’t get logged (keystrokes, URLs visited, continuous screenshots)
- Who has access to the data
- How long you retain it (30 to 90 days for activity logs is typical)
Moving from Surveillance to Results
Keystrokes per hour is surveillance theater.
It gives you data that looks like productivity but measures the wrong thing. It’s easily gamed. It damages trust and retention. And it creates legal and privacy risks across multiple jurisdictions.
Outcome-based tracking gives you what you actually need: clarity on whether work is getting done on time and meeting quality standards.
You define clear outputs. You set service-level expectations. You track deliverables and deadlines using project tools that show you real progress.
Your Filipino VA gets autonomy over how they work. You get results you can measure and evaluate.
No keystroke counting required.