{"id":697,"date":"2026-03-24T22:06:54","date_gmt":"2026-03-25T02:06:54","guid":{"rendered":"https:\/\/manageph.com\/blog\/?p=697"},"modified":"2026-03-24T22:06:54","modified_gmt":"2026-03-25T02:06:54","slug":"document-processes-filipino-va-teams","status":"publish","type":"post","link":"https:\/\/manageph.com\/blog\/document-processes-filipino-va-teams\/","title":{"rendered":"How to Document Processes for Filipino VA Teams"},"content":{"rendered":"\n

You hired someone great in the Philippines.<\/p>\n\n\n\n

Now what?<\/p>\n\n\n\n

Most people skip straight to Slack messages and scattered Google Docs. That works for a week. Maybe two.<\/p>\n\n\n\n

Then things break down.<\/p>\n\n\n\n

The real challenge isn’t finding good remote workers in the Philippines. <\/p>\n\n\n\n

It’s building systems that let them succeed without you micromanaging every hour of the day.<\/p>\n\n\n\n

Here’s what most people get wrong: they think documentation is about control. It’s not.<\/p>\n\n\n\n

Let me show you how to do this properly.<\/p>\n\n\n\n

\n
\n <\/svg> <\/div>\n
\n

Stop Juggling Five Different Tools to Manage your Remote Team.<\/h4>\n

ManagePH combines time tracking, invoicing, compliance management, team standups and more in one simple platform.<\/p>\n <\/div>\n

\n \n Get Started <\/a>\n <\/div>\n<\/div>\n\n\n\n

The Three Documents Every Role Needs<\/strong><\/h2>\n\n\n\n

Forget hundred-page handbooks. You need three specific documents for each person on your team, and you can create all three in an afternoon.<\/p>\n\n\n\n

Create a Role Card First<\/strong><\/h3>\n\n\n\n

Start with a single Google Doc titled “[Name]’s Role Card.”<\/p>\n\n\n\n

Include exactly six things:<\/p>\n\n\n\n

Core responsibilities.<\/strong> List 3-5 main outcomes this person owns. “Manage customer support inbox and maintain under 4-hour response time” not “answer emails.”<\/p>\n\n\n\n

Weekly hours.<\/strong> Approximate, not exact. “20-25 hours per week” gives flexibility while setting expectations.<\/p>\n\n\n\n

Time zone alignment.<\/strong> “Available for questions between 9am-12pm Eastern” or “Works Manila daytime, submits recap by 6pm Manila time for morning review.”<\/p>\n\n\n\n

Key tools and access.<\/strong> List what they need. Gmail, Asana, Slack, whatever. Include who grants access.<\/p>\n\n\n\n

Primary contact.<\/strong> Who approves their work? Who do they ask when stuck? Make this crystal clear.<\/p>\n\n\n\n

Definition of success.<\/strong> What does good performance look like? “All tickets resolved within SLA” or “Zero missed deadlines in a month.”<\/p>\n\n\n\n

That’s it. One page. Update it when responsibilities change, which they will.<\/p>\n\n\n\n

Save it in a shared folder everyone can access. This becomes your single source of truth when there’s confusion about scope.<\/p>\n\n\n\n

Write Task-Level SOPs for Recurring Work<\/strong><\/h3>\n\n\n\n

Pick the five tasks this person does most often. Create a separate Google Doc for each.<\/p>\n\n\n\n

Title format: “SOP: [Task Name]”<\/p>\n\n\n\n

Every SOP needs the same structure:<\/p>\n\n\n\n

What and Why.<\/strong> Two sentences maximum. “This process triages new support tickets so urgent issues get handled first. It runs every morning before the inbox piles up.”<\/p>\n\n\n\n

Prerequisites.<\/strong> What access, tools, or information does someone need before starting? “Gmail access, Asana project access, customer priority list.”<\/p>\n\n\n\n

Step-by-Step Instructions.<\/strong> Number each step. Be specific without being condescending. Include screenshots of any interface that might confuse someone.<\/p>\n\n\n\n

For example:<\/p>\n\n\n\n

    \n
  1. Open Gmail and go to the Support inbox<\/li>\n\n\n\n
  2. Sort by unread messages from the last 24 hours<\/li>\n\n\n\n
  3. Read the subject line and first paragraph of each message<\/li>\n\n\n\n
  4. Identify priority based on these keywords: “urgent,” “broken,” “can’t access,” “billing issue”<\/li>\n\n\n\n
  5. Create an Asana task for each email using this format: [Screenshot of task template]<\/li>\n\n\n\n
  6. Add priority tags: P1 for urgent (red), P2 for important (orange), P3 for standard (no tag)<\/li>\n\n\n\n
  7. Reply to the customer with our acknowledgment template [link to template]<\/li>\n\n\n\n
  8. Move the email to “Triaged” folder<\/li>\n<\/ol>\n\n\n\n

    Quality Check.<\/strong> What does “done” look like? “All emails from the last 24 hours have corresponding Asana tasks, all customers received acknowledgment replies within 1 hour of submission.”<\/p>\n\n\n\n

    Where to Ask Questions.<\/strong> Specific channel or person. “Post in #support-questions if stuck” or “DM Sarah for edge cases.”<\/p>\n\n\n\n

    Examples.<\/strong> Show a good example. Show a bad example. Call out the differences.<\/p>\n\n\n\n

    Don’t write SOPs for every possible task. Start with the recurring ones. Add more as patterns emerge.<\/p>\n\n\n\n

    Store all SOPs in one folder. Name them consistently so people can find them.<\/p>\n\n\n\n

    Map Multi-Person Workflows<\/strong><\/h3>\n\n\n\n

    Some processes involve handoffs between people. Those need visual maps.<\/p>\n\n\n\n

    Use Lucidchart, Miro, or even Google Slides. Keep it simple.<\/p>\n\n\n\n

    Show the trigger (what starts this process), each step, who owns it, and what happens next.<\/p>\n\n\n\n

    Example: Client Onboarding Workflow<\/p>\n\n\n\n