scheduling

# Skill · Scheduling # F&B Content Engine · core/scheduling.md # ───────────────────────────────────────── ## Purpose Define when to post on each platform, how to batch content efficiently, and how to adapt the schedule based on performance data. --- ## Posting Windows by Platform ### Instagram - **Frequency:** 5-7x per week - **Best times:** 11am–1pm · 5–7pm · 8–9pm - **Peak days:** Tuesday, Thursday, Saturday - **Avoid:** Before 9am, after 10pm ### TikTok - **Frequency:** 5-7x per week - **Best times:** 11am–12pm · 6–8pm · 9–11pm - **Peak days:** Any day — TikTok algorithm distributes broadly - **Note:** Post when food is freshest in people's minds (before lunch / dinner decisions) ### RedNote 小红书 - **Frequency:** 4-5x per week - **Best times:** 11am–1pm · 8–10pm - **Peak days:** Weekdays for deal content; weekends for discovery content - **Note:** Evening posts perform well for restaurant discovery ### Facebook - **Frequency:** 3-4x per week - **Best times:** 12–1pm · 6–8pm - **Peak days:** Tuesday, Thursday, Saturday - **Note:** Avoid weekday mornings; lunch and evening decision windows work best ### YouTube - **Frequency:** 1x per week - **Best upload time:** Saturday or Sunday, 2–4pm (for Monday morning algorithm boost) - **Note:** Upload 12-24h before target view time; YouTube boosts new uploads in first 48h ### Google Maps / Google Business - **Business posts:** 2-3x per week, 10am recommended - **Review responses:** Within 24h of every review (no exceptions) - **Q&A responses:** Within 48h ### X / Twitter - **Frequency:** 2-3x per week (only when contrarian angle exists) - **Best times:** 12–1pm · 5–6pm - **Note:** Only post if the content has genuine opinion or industry take; never post just to fill frequency --- ## Weekly Batch Workflow Run this once per week (recommended: Sunday evening or Monday morning). ``` Step 1 · Read Trending Radar Check [[common_vault/trending-radar]] for this week's hot topics. Note any food-adjacent trends worth riffing on. Step 1.5 · Load Brand Context (mandatory) Read `vault/brandcontext.md` before selecting themes or drafting. If read fails, stop generation and report blocker. Step 2 · Pick 2-3 themes Choose from: menu items, seasonal specials, deal alerts, BTS content, customer stories, cultural moments, or trend riffs. Step 3 · Run Repurpose Chain for each theme → [[core/repurpose-chain]] Steps 1-6 for each theme. Batch all platform versions in one session. Step 4 · Pass Gates → Compliance Gate + Bilingual Gate on every draft. Fix RED/YELLOW flags before moving on. Step 5 · Fill Content Schedule Bitable → Content Schedule Bitable Assign each approved draft to a specific date + time slot. Target: 15-25 posts covering the full week across all active platforms. Step 6 · Schedule Load approved posts into Buffer or platform native schedulers. Stagger to avoid publishing the same topic on multiple platforms the same day. ``` --- ## Daily Check (15 minutes) ``` □ Check engagement on yesterday's posts □ Reply to all comments and DMs (first-hour replies boost reach) □ Respond to new Google Maps reviews (24h SLA) □ Note what performed best → flag for [[core/hook-engine]] update □ Review today's scheduled posts — any last-minute changes needed? ``` --- ## Weekly Review (Friday, ~30 min) ``` □ Which dishes / themes drove highest engagement? → do more of those □ Which hook types performed best per platform? → update [[core/hook-engine]] □ Which platform is growing fastest? → consider increasing frequency □ What came up in comments / reviews / DMs? → feed into next week's themes □ Did posting times match peak engagement? → refine schedule if not □ Any content that underperformed despite strong hook? → flag for team review ``` --- ## Content Calendar Rules 1. **Never post the same theme on 2+ platforms the same day.** Stagger by 1-2 days. 2. **Lunch specials must be scheduled before 11am on publish day.** 3. **Deal posts must have an end date.** Never open-ended promotions (FTC compliance). 4. **Google Maps posts are independent of the repurpose chain** — schedule separately. 5. **YouTube uploads need 12-24h lead time** before target viewing window. 6. **If a Tier-1 draft is pending owner approval, hold its slot.** Don't fill with another post — the slot is reserved. --- ## KPI Fallback Rule If after 2 weeks any platform's key metric (impressions / engagement / attributed orders) lags expectation by 30%+: 1. First: update [[core/hook-engine]] and [[localization/brand-voice]] platform tone 2. Second: adjust posting times based on actual engagement data 3. Last resort: reduce posting frequency to focus on quality over quantity Do NOT immediately change [[localization/brand-voice]] core personality — that takes longer to show results.