VA Training, SOPs, and Onboarding (2026) for OFM

Hired a VA. Now you need to train them. Undocumented methods = bad output. This guide is the SOP-building approach.

1. Why SOPs matter for OFM

The unique OFM context

• VAs work without supervision in different timezones.
• Without documented procedure, output drifts.
• Quality crashes within weeks.

What SOPs prevent

• Off-brand content.
• Missed engagement windows.
• Platform rule violations.
• Output inconsistency across VAs.

---

2. Minimum viable SOP per role

Daily checklist

• What to do, in what order.
• Expected time per task.
• Morning / midday / end-of-day checkpoints.

Per-platform method

• Step-by-step posting procedure.
• Account-specific specifics.
• Login protocol via AD browser.

Quality standards

• What good output looks like (examples).
• What unacceptable output looks like.

Communication norms

• When to message you.
• When to decide independently.
• Escalation triggers.

Reporting format

• Daily / weekly template.
• Metrics to track.

---

3. Tool stack for SOPs

Notion

• Most popular for OFM SOPs.
• Shared workspace.
• Embeds video, images, tables.

Google Docs

• Universal.
• Familiar to VAs.
• Version-controlled.

Loom video walkthroughs

• Highest-leverage training tool.
• Record once, VA references infinitely.

Screen recordings

• Show correct procedure.
• VA can pause, re-watch.

---

4. Loom as highest-leverage training

Why Loom wins

• Record yourself doing the work once.
• VA watches.
• VA does it themselves.
• VA shows you their attempt.
• You adjust.

vs written docs

• Written: 1 hour to write, readers confused.
• Loom: 10 minutes to record, readers understand.

5-minute Loom example

• "This is how to find a good subreddit for posting."
• Show the process in real time.
• Explain as you go.
• Done.

---

5. Onboarding timeline expectations

Posting VA

• Week 1-2: training + first posts.
• Week 4: operating autonomously.
• Full productivity: ~1 month.

DA VA

• Weeks 2-4: training.
• Full productivity: ~6 weeks.
• Per-platform method complexity adds time.

Chatter

• Weeks 4-8: training.
• Full productivity: 2+ months.
• Chat skill takes practice.

Account creator

• Week 1: training.
• Full productivity: ~1 week.

---

6. The "experienced OFM VA" claim

From the community:

"There is no pre-experienced VA's with their own methods otherwise it's 99% scam. You have to come with working SOP and training to teach them what they should do."

Reality

• Even experienced VAs need your specific SOP.
• Every agency has different workflow.
• "My method is secret" = scam or unusable.

Your SOP > their claim

• Write your SOP.
• Test them against your SOP.
• Ignore their historical claims.

---

7. The "VA who refuses to follow SOP"

Pattern

• VA pushes back on your SOP.
• Wants to do things their way.

Interpretation

• SOP is poorly written, review and clarify.
• OR VA is going to leave, they're not invested.

Response

• Ask what specifically they'd change.
• Evaluate honestly.
• If valid feedback, incorporate.
• If not, they follow SOP or exit.

---

8. AI-assisted training

Use ChatGPT / Claude to draft SOPs

• Prompt: "I need an SOP for a Reddit posting VA. Here's a verbal walkthrough: [your notes]. Write it as a numbered SOP with clear steps."
• Saves hours.
• Refine output manually.

AI for translating SOPs

• Translate to VA's language if needed.
• Keep technical terms in English for consistency.

---

9. Feedback loops

First 2 weeks

• Daily check-ins, 5-15 minutes.
• Review yesterday's output.
• Clarify confusion.
• Adjust SOP as gaps emerge.

Week 3-4

• Every other day check-ins.
• Less hand-holding.

Month 2+

• Weekly check-ins.
• Monthly formal review.

---

10. Performance metrics by role

Posting VA

• Posts published (volume).
• Engagement rate (quality).
• Conversion to bio-link clicks (impact).

DA VA

• Matches per day.
• Conversation-to-funnel rate.
• OF subs generated.

Chatter

• Revenue per hour.
• PPV sale rate.
• Subscriber retention.

Account creator

• Accounts created per day.
• 7-day survival rate (ban resistance).

---

11. AI VA / AI chatter trend

From the community:

"Guys does anyone have experience with the reddit ai chatter? How'd it do?"

Current state (2026)

AI chatter works for

• Low-LTV transactional chats (repeat messaging).
• 24/7 coverage (sleep hours).
• High-volume, low-skill DMs.

AI chatter fails at

• High-LTV PPV sales.
• Complex emotional conversations.
• Relationship-building over months.

AI posting tools

• Content scheduling: OK.
• Platform-specific judgment: fails.
• Copy generation: mixed.

Hybrid human + AI

• 2026 standard.
• AI for volume + draft.
• Human for high-stakes + judgment.

---

12. Building team-level training

When 3+ VAs in same role

• Shared SOP, single source of truth.
• Group training calls, batch similar questions.
• Peer-review systems, VAs review each other's work.

Cross-training

• VAs learn each other's roles.
• Redundancy if one leaves.
• Career-path within team.

---

13. When to fire vs retrain

30-day output trend rule

• Trending toward target by day 30: retrain and keep.
• Not trending by day 30: fire.

Retrain signals

• Gaps in SOP.
• Communication issues (fixable).
• Tool learning curve.

Fire signals

• No effort.
• Ongoing attitude issues.
• Trust violations.
• No improvement despite feedback.

---

14. SOP template structure

## [Role] Standard Operating Procedure

## Daily Checklist
- [ ] 9am: Check model-X accounts for overnight activity
- [ ] 10am: Post to Reddit subs [list]
- [ ] 11am: Engage comments
- ...

## Tools
- AD browser: Dolphin Anty, profile link [X]
- Account list: [Google Sheet link]
- Content library: [Notion link]

## Per-Task Procedure
### Posting to Reddit
1. Open AD browser profile for model
2. Navigate to target subreddit
3. Copy post title from content library
4. ...

## Quality Standards
- Good title example: [X]
- Bad title example: [Y] (why: keyword stuffed)
- ...

## Escalation
- Ban on account: message operator immediately
- Shadowban suspicion: check with Cable.Ayra.ch first
- ...

## Daily Report Template
- Posts made: X/Y
- Bans: X
- Issues: [description]
- Tomorrow priority: [tasks]

---

15. Key SOP components

Login protocol

• Which AD browser profile.
• How to connect proxy.
• Pre-action fingerprint check.

Action procedure

• Step-by-step.
• Screenshots.

Edge cases

• What to do when platform error.
• What to do when content rejected.
• What to do when ban alert.

Escalation path

• When to message operator.
• Priority levels.

---

16. Documentation hygiene

Keep SOPs updated

• Platform changes → SOP changes.
• Monthly review minimum.
• Version-dated.

Shared repository

• One location all SOPs.
• Access control.
• Backup.

Training schedule

• Onboarding schedule per role.
• Timeline expectations.

---

17. Common training mistakes

No written SOP

VAs drift.

Training verbally only

Not retained. Loom/docs needed.

Expecting immediate productivity

Onboarding takes weeks.

Firing too soon

Before retraining opportunity.

Not updating SOP

Drift as platforms change.

---

18. Frequently asked questions

How long is reasonable onboarding?

Posting VA: 1 month. Chatter: 2 months.

Should I use Notion or Google Docs?

Either. Notion richer; Google simpler. Pick what your team will use.

Do I need a separate SOP per model?

Per-role is enough. Per-model specifics in daily checklist.

Can AI write my SOPs?

Drafts yes. Final version needs your review + specific methods.

What if VA isn't productive at 30 days?

Retrain week 4-5. If no improvement, fire.

---

Related guides

• Guide 3, Hiring + Vetting
• Guide 6, Account Access
• Guide 8, Managing at Scale

---

Built from a corpus of ~218 real operator discussions across 11 OFM Telegram communities (2024-2026). Usernames anonymized.