[{"data":1,"prerenderedAt":456},["ShallowReactive",2],{"landing-homepage-md-en":3,"landing-team-md-en":185},{"title":4,"meta_description":5,"hero":6,"problem_solution":14,"doubts":22,"process":37,"moments":73,"industries":91,"contrast":110,"demo_video":113,"pricing":117,"faq":120,"cta_banner":153,"ui":157,"header":161,"footer":163},"Event operations for restaurants, venues, and hotel F&B | Manage My Restaurants Events","Kitchen, floor, and office on the same event plan — menu, shopping list, run-of-show, and who’s working. Start a 14-day free trial.",{"kicker":7,"title":8,"description":9,"cta_trial":10,"cta_demo":11,"friction":12,"visual_brief":13},"Event operations software for restaurants, banquet venues & hotels","One event. Menu, shopping list, run-of-show, and who’s working — same plan.","Office sees everything. Staff only open the nights they’re on — no prices, no client file.","Start your Free Trial","See how one event connects","14-day free trial · Card required · Converts to a paid plan after the trial · Cancel anytime","Dashboard month calendar of booked events (titles and start times), light office UI.",{"kicker":15,"title":16,"problem_label":17,"problem":18,"solution_label":19,"solution":20,"boundary":21,"cta":10},"The problem","Scattered tools. One night.","Scattered","Client details in email. Menu in a sheet. Run-of-show in a chat photo. Staff asking which version is live.","One event","The booking holds the menu that builds the shopping list, the templates that fill from the same fields, the timeline you can share, and the task board for that night — with role-appropriate access.","Built for restaurant, banquet, and hotel F&B event operations — not a POS, not inventory, not hotel PMS, not a venue marketplace, and not payments collected or a full P&L.",{"title":23,"items":24},"Who sees what",[25,28,31,34],{"title":26,"description":27},"Office","Owner or manager builds the event: client, prices, draft and published menu, shopping list, timeline, documents, and notes.",{"title":29,"description":30},"Kitchen","A separate login. Every upcoming event at the location: published menu and a read-only shopping list. No prices, no client file, and no run-of-show on the kitchen screen.",{"title":32,"description":33},"Floor","Opens an event only with a shift or a task. Published menu without prices, full timeline read-only, own tasks. No client file and no notes.",{"title":35,"description":36},"Share link","People without a login see the current run-of-show. Not a chat and not a password portal.",{"badge":38,"title":39,"description":40,"note":41,"button_trial":10,"steps":42},"On the event","The modules that night needs.","","Dining reservations are available as a beta module — separate from banquet\u002Fevent operations. Ask us or enable it when you’re ready to test.",[43,48,53,58,63,68],{"title":44,"description":45,"visual_brief":46,"icon":47},"Create the event","Client, date, status; history stays on the client.","Event header with client + date + status.","i-heroicons-calendar-days",{"title":49,"description":50,"visual_brief":51,"icon":52},"Build what you serve","Menu becomes a shopping list. Estimated plate cost on items — not warehouse stock.","Menu with shopping-list panel opening from the same event.","i-heroicons-clipboard-document-list",{"title":54,"description":55,"visual_brief":56,"icon":57},"Add non-food extras","AV, flowers, corkage — office sees rates; staff see what’s on without rates.","Services list on an event (office view with prices \u002F staff view without).","i-heroicons-sparkles",{"title":59,"description":60,"visual_brief":61,"icon":62},"Generate the paperwork","Templates and placeholders; guest vs kitchen layouts. Not e-sign.","Template with placeholder chips → filled guest\u002Fkitchen outputs.","i-heroicons-document-text",{"title":64,"description":65,"visual_brief":66,"icon":67},"Plan the minute and the prep","Timed run-of-show, a shareable link, and the task board.","Timeline + event Kanban side by side.","i-heroicons-clock",{"title":69,"description":70,"visual_brief":71,"icon":72},"Staff the night","Schedules on the event. Staff see their rows only — not payroll.","Event schedule with assigned vs unassigned nights; staff “my shifts” view.","i-heroicons-user-group",{"title":74,"items":75},"The connections that matter on the night",[76,81,86],{"title":77,"description":78,"cta":79,"to":80},"Change a dish — the shopping list follows","Menus on the event; ingredients become the list; plate cost is for office planning.","Features \u002F Menus","\u002Ffeatures\u002Fmenus",{"title":82,"description":83,"cta":84,"to":85},"Edit the exception — not the whole packet","Templates pull event and client fields; guest and kitchen versions. Not e-sign, and not a full document archive.","Features \u002F Documents","\u002Ffeatures\u002Fdocuments",{"title":87,"description":88,"cta":89,"to":90},"Kitchen and floor stay on the current plan","Publish the menu they cook and serve. Kitchen is its own login. Floor opens a shift or a task. No prices, client file, or event notes.","Features \u002F Team","\u002Ffeatures\u002Fteam",{"title":92,"items":93},"Who it’s for",[94,100,105],{"title":95,"description":96,"not_label":97,"not_text":98,"to":99},"Restaurants","Private dining, birthdays, corporate dinners.","Not","POS or inventory.","\u002Frestaurants",{"title":101,"description":102,"not_label":97,"not_text":103,"to":104},"Banquet venues","Weddings, corporate, private parties.","a venue marketplace.","\u002Fvenues",{"title":106,"description":107,"not_label":97,"not_text":108,"to":109},"Hotels","Galas, meeting dinners, coffee breaks (F&B).","room blocks, PMS, or front desk.","\u002Fhotels",{"title":111,"description":112,"link_label":40,"link_to":40},"Booking software gets the deposit. We run the night.","Sales CRMs help you quote and collect. MMRE keeps kitchen, floor, and office on the same event plan after the booking is won.",{"headline":40,"title":114,"description":115,"video_url":116},"Watch how one event connects","A short walkthrough of an event with menu, timeline, and documents working together.","https:\u002F\u002Fyoutu.be\u002Fmp6jygyljrc",{"title":118,"description":119},"Choose your plan.","Monthly or annual · USD or PLN",{"title":121,"items":122},"FAQ",[123,126,129,132,135,138,141,144,147,150],{"question":124,"answer":125},"Who is this for?","Restaurants, banquet venues, and hotel F&B teams that run planned events—private dining, functions, galas, corporate dinners, and similar. Not a replacement for POS, inventory, or hotel PMS.",{"question":127,"answer":128},"How does the 14-day trial work?","Start your Free Trial opens a 14-day trial with a card on file. After 14 days the subscription begins. Cancel anytime. If you cancel, you won’t be charged for the next period. Any month or year already paid stays available until that period ends. No setup fees.",{"question":130,"answer":131},"What do staff see?","Assigned events and shifts: menu and timing without prices, their tasks, and coworkers’ names\u002Froles. Not the client file, documents, notes, amounts, or cost journal. You can also share an unlisted timeline link without a staff login.",{"question":133,"answer":134},"Do menus create shopping lists?","Yes. Ingredients and quantities on the event menu become a shopping list for that menu. Plate cost is estimated. This is not inventory or stock counting.",{"question":136,"answer":137},"How do document templates work?","You write a template once, insert placeholders, and generate from the event. Guest and kitchen layouts can share the same source data.",{"question":139,"answer":140},"Is this a POS, inventory system, or hotel PMS?","No. Keep those systems for what they’re for. This product is for planned event operations.",{"question":142,"answer":143},"What about dining reservations?","A dining reservations module is available in beta, separate from banquet\u002Fevent operations. It is not a diner marketplace.",{"question":145,"answer":146},"Do you support tablets and phones?","The product is built for modern browsers on desktop and tablet. Native mobile apps are still in progress.",{"question":148,"answer":149},"How do I get support?","Email us and we’ll respond. Contact details are on the Contact page.",{"question":151,"answer":152},"Can I run more than one restaurant?","Current plans include 1 active restaurant and 10 seats. Multi-location packaging may change later; use the live plan details in your account\u002Fadmin.",{"title":154,"description":155,"cta_trial":10,"friction":156},"Ready to run the next private dining night on one plan?","No need to stitch sheets, chats, and reprints.","14 days · full features · USD or PLN",{"loading":158,"errorTitle":159,"errorDescription":160},"Loading...","Error Loading Content","Unable to load homepage content. Please try again later.",{"loginButton":162,"getStartedButton":10},"Log In",{"companyDescription":164,"product":165,"support":172,"resources":176,"copyright":180,"legal":181},"Plan menus, assign staff, track every task, and reuse document templates filled from the event -- from one dashboard where everything connects.",{"title":166,"links":167},"Product",[168,169,170,171],"Features","Industries","Blog","About",{"title":173,"links":174},"Support",[175],"Contact",{"title":177,"links":178},"Resources",[179],"Free BEO template","All rights reserved.",{"privacyPolicy":182,"termsOfService":183,"cookiePolicy":184},"Privacy Policy","Terms of Service","Cookie Policy",{"title":186,"meta_description":187,"page":188},"Team Access for Restaurant Events — Kitchen, Floor & Office | managemyrestaurants.events","Keep kitchen and floor on the current event plan. Manage who sees prices, published menus, shopping lists, and run-of-show — without team chat. 14-day free trial.",{"breadcrumb":189,"hero":192,"mess":199,"event":219,"who":269,"change":345,"access":361,"not_buying":380,"faq":399,"cta":438,"ui":453},{"home":190,"features":168,"current":191},"Home","Team access",{"badge":193,"title":194,"description":195,"cta_trial":196,"cta_secondary":197,"friction":198},"Team access \u002F Event ops","Keep kitchen, floor, and office on the current plan","Manage My Restaurants Events has no team chat. You run the night from one event plan — and each login only gets the slice their job needs, so the house stays on the latest plan version.","Try for free","See who sees what","14 days · full features · Start free trial",{"title":200,"intro":201,"cards":202},"The mess when the team is not on one plan","When the team is not on one current plan, the house runs on fragments — and group chat is not a system of record.",[203,207,211,215],{"title":204,"description":205,"icon":206},"Email threads","The “final” menu lives in someone’s inbox.","i-lucide-mail",{"title":208,"description":209,"icon":210},"Spreadsheets","Guest counts and duties drift between files.","i-lucide-sheet",{"title":212,"description":213,"icon":214},"A photo of the run-of-show in a group chat","Blurry, cropped, already outdated.","i-lucide-image",{"title":216,"description":217,"icon":218},"Which print is current?","Kitchen and floor argue from different paper.","i-lucide-printer",{"title":220,"body":221,"see_also_lead":222,"see_also":223,"items":237},"What the event plan holds","The booking is where title, times, status, category, labels, guest counts, client, menu, additional services, timeline, tasks, schedule, notes, and documents live. Office (owner or manager at the location) builds it on the dashboard. Kitchen and floor open the same event — each with the fields their job needs, not a separate “version in chat.”","See also",[224,226,229,232,235],{"label":225,"to":80},"Menus",{"label":227,"to":228},"Timelines","\u002Ffeatures\u002Ftimelines",{"label":230,"to":231},"Tasks","\u002Ffeatures\u002Ftasks",{"label":233,"to":234},"Schedules","\u002Ffeatures\u002Fschedules",{"label":168,"to":236},"\u002Ffeatures",[238,242,246,250,254,257,261,265],{"title":239,"description":240,"to":80,"icon":241},"Menu","Meals, drinks, packages, add-on food services; quantities; special notes. Office drafts and publishes.","i-lucide-utensils",{"title":243,"description":244,"icon":245},"Additional services","AV, flowers, corkage, and similar: office sees rates; floor sees name, description, quantity.","i-lucide-sparkles",{"title":247,"description":248,"to":80,"icon":249},"Shopping list","Produced from menu ingredients and quantities = what to buy, not a stockroom.","i-lucide-shopping-cart",{"title":251,"description":252,"to":228,"icon":253},"Run-of-show","Timed groups and steps with start\u002Fend and optional description.","i-lucide-clock",{"title":230,"description":255,"to":231,"icon":256},"On this event’s board; templates can copy when confirmed — this night, not a company backlog.","i-lucide-list-todo",{"title":258,"description":259,"to":234,"icon":260},"Work schedules","Attach employees; also how floor gets into the booking.","i-lucide-calendar",{"title":262,"description":263,"to":85,"icon":264},"Documents","Templates filled from event\u002Fclient; guest vs kitchen layouts.","i-lucide-file-text",{"title":266,"description":267,"icon":268},"Event notes","Office notepad only.","i-lucide-notebook-pen",{"title":23,"intro":270,"views":271,"table":288},"Four views. Kitchen is its own login — not “staff who cook.” Do not merge kitchen and floor. Managing access is how you keep everyone on the current plan.",[272,276,280,284],{"badge":26,"title":273,"description":274,"icon":275},"Owner or manager at the location","Builds the commercial and ops file: client, prices, draft + publish menu, generate shopping list, edit timeline and share link, full task board, whole rota, documents, event notes, analytics and cost journal where the plan includes them. Managers cannot invite or archive logins — only the organization owner hands out seats.","i-lucide-briefcase",{"badge":29,"title":277,"description":278,"icon":279},"Separate login","Sees every upcoming event at the location (not only nights they are rostered). Opens published menu (print\u002Fpreview), read-only shopping list, and own tasks (move between columns only). No client file, no prices, no event notes, no document editor, no run-of-show on the kitchen event screen. Prep guest count is the kitchen number.","i-lucide-cooking-pot",{"badge":32,"title":281,"description":282,"icon":283},"Staff","Never the office dashboard. Enter an event only with a shift or a task on that booking. See published menu without prices, services without rates, full timeline read-only, coworkers’ name + job title only, and own tasks to move. Own schedule screen. No client, documents, event notes, shopping-list editing, or plate cost.","i-lucide-concierge-bell",{"badge":35,"title":285,"description":286,"icon":287},"No login","Unlisted view of the current run-of-show (title, groups, step titles, descriptions, times). Not a password portal and not a place to reply. Default expiry: event end + 24 hours if unset. Regenerating the link kills the old URL; expired links are gone. Office can limit which timeline groups are included. Use this when someone needs timing without a seat.","i-lucide-link",{"caption":289,"columns":290,"rows":293},"Role comparison",[291,292,281,29],"Owner","Manager",[294,301,308,313,318,323,329,333,339],{"label":295,"cells":296},"Where",[297,298,299,300],"Every location + org","Office dashboard assigned","Staff home","Kitchen event list",{"label":302,"cells":303},"Events",[304,305,306,307],"All","All at location","Shift or task only","All upcoming at location",{"label":309,"cells":310},"Client \u002F prices \u002F notes \u002F docs",[311,311,312,312],"Yes","No",{"label":239,"cells":314},[315,315,316,317],"Draft + publish","Published, no prices","Published, print",{"label":247,"cells":319},[320,321,312,322],"Generate + mark purchased","Same","Read-only",{"label":324,"cells":325},"Timeline",[326,326,327,328],"Edit + share","Read-only when assigned","Not on their event screen",{"label":230,"cells":330},[331,331,332,332],"Full board","Own cards move",{"label":334,"cells":335},"Schedule",[336,336,337,338],"Whole rota","Own shifts","No schedule screen",{"label":340,"cells":341},"Team admin",[342,343,344,344],"Invite, roles, archive, billing","Roster only — no logins","Own password",{"title":346,"intro":347,"steps":348},"How a change lands","Nothing pushes into an open tab. The next open of the event, published menu, or share link loads what was last saved or published — that is how the team stays current.",[349,352,355,358],{"title":350,"description":351},"Publish the menu","Draft saves stay in the office. Publish stores a numbered kitchen version with time and author. Kitchen and floor read that version; if never published, kitchen has no current menu.",{"title":353,"description":354},"Generate the shopping list again when the menu changed","The list is produced from this menu. It does not rewrite itself when a dish changes. After menu changes, generate again so kitchen is not buying old dishes.",{"title":356,"description":357},"Share link loads current times","Not a photo from the briefing. Until expiry or replace, the link shows the timeline as it is now.",{"title":359,"description":360},"Assigned people move their own tasks","Kitchen and floor move only their cards on the same board. They cannot rename, rewrite, reassign, create, or delete cards.",{"title":362,"items":363},"How people get in",[364,368,372,376],{"title":365,"description":366,"icon":367},"Employee","A roster row at the location (name, email, job title, phone). Can exist with no login. Not a billed seat. Used for shifts and task assignment.","i-lucide-contact",{"title":369,"description":370,"icon":371},"Login","A user account with a role at one or more locations = a seat. Only the organization owner invites. Pending invites reserve a seat until accept, cancel, or expire (7 days). Archive frees the seat immediately. The owner is not counted as a seat. One person at several locations in the same org = one seat.","i-lucide-key-round",{"title":373,"description":374,"icon":375},"Invite flow","Owner picks active locations, then invites a new person (email, name, role, optional job title\u002Fphone) or — when a single location is selected — invites an existing employee to log in (email must match). Staff\u002Fkitchen emails say so; manager gets a generic team invite. Managers manage the roster only — they cannot create logins.","i-lucide-user-plus",{"title":377,"description":378,"icon":379},"Roles you can assign","Manager, Staff, Kitchen. Manager at one location cannot also be staff\u002Fkitchen anywhere in the same org. Staff and kitchen can combine across locations.","i-lucide-users",{"title":381,"items":382,"extras":395},"What you are not buying",[383,387,391],{"title":384,"description":385,"icon":386},"No team thread","Alignment is the shared plan, not a chat.","i-lucide-message-square-off",{"title":388,"description":389,"icon":390},"No warehouse","Shopping list is a buy-list from the menu, not stock.","i-lucide-warehouse",{"title":392,"description":393,"icon":394},"No payroll","Schedules and who is on the night; not HR pay runs.","i-lucide-banknote",[396,397,398],"Not a POS","Not a hotel PMS","Not guest messaging",{"title":400,"items":401},"Frequently asked questions",[402,405,408,411,414,417,420,423,426,429,432,435],{"question":403,"answer":404},"Is there a team chat?","No. Communication means the shared event plan: published menu, timeline, tasks, and optional unlisted share link — not a message thread.",{"question":406,"answer":407},"Does everyone see updates instantly in an open tab?","No live push. The next time someone opens the event, the published menu, or the share link, they see the last saved or published state.",{"question":409,"answer":410},"What is the difference between Save and Publish on the menu?","Save keeps a draft in the office. Publish stores the numbered kitchen version kitchen and floor read. If you never publish, kitchen has no current menu.",{"question":412,"answer":413},"Does the shopping list update by itself?","No. Office generates it from the current menu. After the menu changes, generate again so kitchen is not buying old dishes. It is a buy-list, not a storeroom.",{"question":415,"answer":416},"Is kitchen just staff with a filter?","No. Kitchen is a separate login. Kitchen sees upcoming events at the location; staff open nights they are on (shift or task). Kitchen’s event screen does not include the run-of-show.",{"question":418,"answer":419},"Who can invite people to log in?","Only the organization owner. Managers can manage the employee roster but cannot create or archive login accounts.",{"question":421,"answer":422},"What is an employee vs a login?","An employee is a roster row and can exist without a login (not a billed seat). A login is a seat with a role. Seat totals depend on your plan — we do not hard-code a number here.",{"question":424,"answer":425},"What does the share link show?","Current run-of-show fields (title, groups, steps, descriptions, times). It is not a reply portal. It expires (default: event end + 24h if unset); regenerating kills the old URL.",{"question":427,"answer":428},"Can staff see prices or the client file?","No. Kitchen neither. Those stay with office roles.",{"question":430,"answer":431},"How do I keep kitchen and floor on the current plan?","Publish the menu they should cook and serve, regenerate the shopping list after menu changes, and keep timeline edits in the event (or share link) — not in a group chat photo.",{"question":433,"answer":434},"Is there a free trial?","Yes — 14 days with full features. Try for free from this page.",{"question":436,"answer":437},"Do you have native apps?","Native apps exist for these roles in the product. This page does not claim App Store \u002F Play listing status — use the trial in the browser to evaluate.",{"title":439,"description":440,"cta_trial":196,"friction":441,"links":442},"Ready to run the next night with kitchen and floor on the current plan — without a team chat?","14 days, full features.","14 days · full features",[443,444,445,446,447,448,451],{"label":168,"to":236},{"label":225,"to":80},{"label":227,"to":228},{"label":230,"to":231},{"label":233,"to":234},{"label":449,"to":450},"Pricing","\u002Fpricing",{"label":171,"to":452},"\u002Fabout",{"loading":158,"errorTitle":454,"errorDescription":455},"Unable to load this page","Please try again in a moment.",1791234770074]