EXAMPLEIllustrative example · fictional restaurant «Sazón de Origen». Not your data: your result is built with YOUR restaurant's.See the assistant →
Sazón de OrigenFictional contemporary Colombian restaurant in Medellín, 2 locations, 6 years in business. Every sample result in the library comes from this same case.
AI Community Manager

Sample result

Weekly Community Manager Plan Builder for Restaurants

The owner asked this:«We're Sazon de Origen, contemporary Colombian cooking in Medellín, two locations and 24 people. Everyone does the content and nobody does it: I film one video on Tuesday between orders, another on Thursday, and the pieces don't match. Strong lunch runs Tuesday to Friday from 12:00 to 14:30 and Sunday at noon; Monday drops. Across both locations I can free up 5 hours 30 minutes a week, and this year I have to take the operating margin from 8% to 14% without touching menu prices. Tell me what happens each day and what I stop doing.»

① The week's grid (7 blocks · 4 hours 50 minutes of the 5 hours 30 minutes available)

DayBlockLengthOwnerBlock deliverableDaypart or channel it feeds
MondayWeekly huddle20 minOwner + location head3-line minutes and deferred listThe whole cycle
MondayBatch production90 minLocation cook + manager16 photos and 4 videos for the weekThe slow Monday and Tuesday-to-Friday lunch
TuesdayScheduling40 minManager7 posts loaded at their exact hourLunch from 12:00 to 14:30
WednesdayInteraction25 minAfternoon-shift cashierWhatsApp messages and comments answeredOwn delivery
ThursdayBuffer60 minDeliberately unassignedWhatever fell throughWhichever one needs it
FridayInteraction25 minAfternoon-shift cashierMessages answered before 11:30Friday lunch
SundayNumber reading30 minManagerThe week's cutDecides Monday's plan

Why the batch lands on Monday and not Sunday: Monday is the only day with no declared strong lunch, the kitchen can plate the Bandeja de la casa, the Sancocho de tres carnes and the Trucha al ajillo without stalling orders, and Sunday noon runs full. 40 minutes stay unassigned on purpose: a plan at 100% of capacity breaks on the first odd day. Figures are illustrative; the real hours come from your week.

② The shooting sheet and the rescheduling rule

Batch shooting sheet — Monday, 3:00 p.m., 90 minutes, Laureles location. Planned shots: 16 photos (the Bandeja de la casa complete before it leaves for the table, the Sancocho de tres carnes served in the clay pot, the Trucha al ajillo coming out of the pan) and 4 videos of 20 seconds (the meat being cut, the rice landing on the plate, the in-house courier closing the thermal bag, the 12:15 line). Cooking: the location cook. On camera: the location head. What is NOT filmed this week gets written down: the Sunday menu waits for the next batch.

What landed on topWhich block gives wayWhich block freezes
Corporate lunch for 60 on MondayThe batch moves to Tuesday 3:00 p.m., identicalMonday's huddle and Sunday's reading
Commercial date: Mother's Day, Sunday noonFriday's 25 interaction minutes go to schedulingThe batch is untouched
The delivery marketplace goes down on a ThursdayThe buffer block is spent answering on WhatsAppThe batch and the huddle

The full example has 1 more part(s): you see them inside the library, with your account.