Philippines staffing guide · Published
A Social Scheduling Flow With Real Approval
Drafting, asset rights, scheduling, and community replies are separate permissions. Do not collapse them into one login.
On this page
Social media looks like a scheduling task until a post with the wrong image or an unapproved claim goes live. A VA can prepare a month of drafts, organize assets, and schedule approved content. The approval step is what keeps the account from becoming a liability.
Build the flow around a content calendar and a simple status model: idea, drafted, fact checked, approved, scheduled, published, and reviewed. Each status has an owner. The assistant can move work through the first stages and schedule only what the owner has approved.
1. Draft from an approved brief
Give the assistant the audience, the goal, the key message, the proof points, and the call to action. Require a source for every factual claim, including product features, prices, and dates. If the post needs a customer story, use an approved case study rather than inventing a quote.
Draft the caption, the alt text, and the image description together. Alt text is not a place to repeat the caption. It should describe the image for someone who cannot see it. Check that the post makes sense without the image and that the image does not contain text that is missing from the caption.
2. Check asset rights before scheduling
Record where each image, video, or font came from and what license covers it. Do not use a stock image outside its license or a customer photo without permission. If the asset was generated with an AI tool, follow the company's disclosure and usage rules. The assistant should be able to show the source for every asset in the calendar.
Keep the original file and the exported version. Check the dimensions and the file size for each platform. A cropped image may cut off a face or a logo. Review the mobile preview, not only the desktop composer. A post that looks fine in the tool can look broken in the feed.
3. Separate scheduling from community replies
Scheduling approved posts is a different permission from replying to comments and messages. A VA may draft replies to routine questions, but complaints, legal threats, safety issues, and press inquiries should go to the named owner. The assistant should not delete criticism or block a user without a written rule.
If the assistant handles replies, give them a response library and a stop list. Record the response time and the escalation path. A fast reply that promises a refund or shares private account information can create a bigger problem than a short delay.
4. Review performance without chasing vanity
Track reach, engagement, clicks, and conversions with the same definitions each month. A post with high likes but no qualified traffic may not be worth repeating. Check the comments for questions that reveal a product or policy gap. Share those with the owner rather than answering them ad hoc.
After each cycle, review the approval flow. Were posts delayed because the approver was unavailable? Did an unapproved claim slip through? Was an asset missing rights? Fix the step that failed. The goal is a reliable publishing rhythm, not a viral post.
Questions and operating boundary
Can a VA post without approval?
Only for pre-approved content types and only if the company has written that rule. Sensitive topics, new claims, and crisis replies need an owner.
Who owns the social accounts?
The company. The assistant should use a named, least-privilege login and never a shared personal account.
How should comments be handled?
Routine questions can use an approved reply library. Complaints, threats, legal issues, and press inquiries go to the named owner.
Source
w3.org provides authoritative background and does not endorse this service.