You hire someone in the Philippines. They do great work.<\/p>\n\n\n\n
Six months in, you realize you can’t prove they’re classified correctly, have no documentation for tax purposes, and your time tracking setup might violate Philippine privacy law.<\/p>\n\n\n\n
This happens constantly.<\/p>\n\n\n\n
Most companies either track everything \u2014 screenshots every five minutes, keystroke logs \u2014 or almost nothing \u2014 just monthly invoices. Both create problems.<\/p>\n\n\n\n
By 2026, 82% of high-performing remote teams have shifted from active-minute tracking to milestone achievement tracking. <\/p>\n\n\n\n
The managers still obsessing over activity scores are the ones losing good workers to employers who don’t.<\/p>\n\n\n\n
Here’s what you actually need to track \u2014 and what you don’t.<\/p>\n\n\n\n
Before anything else, document how you’ve classified this person.<\/p>\n\n\n\n
Keep on file:<\/p>\n\n\n\n
If your records say “independent contractor” but your payment structure, supervision level, and schedule control say “employee,” you have a classification problem waiting to surface.<\/p>\n\n\n\n
For contractors, time data ties to invoicing and project scope. For employees, Philippine labor law requires accurate tracking to calculate overtime, night shift premiums, and rest day pay.<\/p>\n\n\n\n
Track:<\/strong><\/p>\n\n\n\n Don’t track:<\/strong><\/p>\n\n\n\n The Philippine Data Privacy Act requires monitoring to be proportionate and transparent. Screenshots every few minutes without a documented business reason violate this standard. The National Privacy Commission has been explicit about it.<\/p>\n\n\n\n A better system: simple time tracker + daily EOD recap + weekly summary. Full visibility without treating people like suspects.<\/p>\n\n\n\n Track what they actually produce. This is your primary accountability tool in 2026 \u2014 and your best protection for classification purposes.<\/p>\n\n\n\n Document:<\/p>\n\n\n\n Deliverable-focused records serve two purposes. They prove the relationship is output-based rather than hours-based (supporting contractor classification), and they tell you whether the relationship is actually working.<\/p>\n\n\n\n Many experienced Filipino remote workers send EOD recaps without being asked. They understand it protects both sides. For guidance on measuring this systematically, see our guide on measuring remote worker productivity<\/a>.<\/p>\n\n\n\n The metrics that matter in 2026 go beyond “did they clock eight hours.”<\/p>\n\n\n\n Async response time<\/strong> \u2014 How quickly does your remote worker respond to messages, requests, and blockers during their agreed working window? For Filipino remote workers operating on US time alignment, a reasonable standard is response within two hours during overlap windows. Track this pattern, not individual messages.<\/p>\n\n\n\n Sprint or milestone completion rate<\/strong> \u2014 What percentage of committed deliverables for a given week or sprint actually shipped? A worker consistently hitting 85\u201390% of committed work is performing. One consistently below 60% with no explanation needs a direct conversation.<\/p>\n\n\n\n Recap consistency<\/strong> \u2014 Are daily or weekly summaries being submitted on time, with sufficient detail? This is a leading indicator of engagement and a lagging indicator of output quality.<\/p>\n\n\n\n Sample daily recap template:<\/strong><\/p>\n\n\n\n “[Date] \u2014 Completed: [specific deliverables]. In progress: [current tasks, estimated completion]. Blockers: [anything preventing progress, with deadline for response needed]. Tomorrow: [planned priorities].”<\/em><\/p>\n<\/blockquote>\n\n\n\n\n
\n
Work Output and Deliverables<\/h2>\n\n\n\n
\n
Beyond Hours: Tracking Async Velocity and Sprint Completion Rates<\/h3>\n\n\n\n
\n