# Knowledge Base

URL: https://www.restaurantcodex.com/knowledge-base
Spanish: https://www.restaurantcodex.com/es/knowledge-base

## Write the standard once. Every location works from it.

Keep recipes, policies and house procedures current across your group, so each team gets the version written for its role and brand.

> On Tuesday, you change a recipe between prep and service, tell one GM, then spend the week answering which version your other locations should use and what changed.

### Keep every team on the same standard.

Write SOPs, policies and manual entries once, then share by role or team and pin them to a brand. Staff get new-recipe notifications.

- Large parties: At Northside, a host follows the large-party policy before confirming a booking.
- Cash handling: After Friday close, a GM updates the cash-handling entry for the next shift.
- Dress code: An area manager pins the private-event dress code to the brand before Saturday's event.

### Use the files you already have.

Import PDFs with their wording and structure intact. AI pulls recipe details from PDFs or photos, or drafts an SOP from notes for manager review.

- Opening checklist: A manager imports the opening checklist PDF, keeping its numbered steps.
- SOP draft: A GM reviews an AI draft for Riverside's Sunday opening before it is saved.
- Recipe photos: A chef submits brunch-tart photos to start a recipe import.

### Give each team its working recipe.

Servers get plate recipes with guest descriptions, allergens and Pair and Sell pairings. Kitchen gets batch ingredients, prep steps, yield, shelf life and storage notes.

- Guest description: A server reads the guest description for the salmon plate before dinner.
- Batch prep: At Friday prep, a prep cook measures ingredients against the batch recipe.
- Pair and Sell: A bartender uses Pair and Sell to suggest a dessert pairing before service.

### Answer staff questions from your own records.

Codex Bot answers from your recipes and manual, links the entry it used, labels general knowledge and never guesses prices or door codes.

- Closing: After close, a dishwasher asks Codex Bot what the dish-area closing policy says.
- Split checks: Before Saturday service, a host checks Codex Bot's guidance on split checks for large parties.
- Pairings: Before setup, a bartender confirms the birthday dessert pairing with Codex Bot.

### From recipe change to every shift

- Import: Import a manual PDF, or a recipe PDF or up to five photos.
- Review: A manager reviews recipe details or an AI-drafted SOP before saving.
- Share: Share an entry with the roles or teams that need it.
- Notify: Staff get a notification when a recipe is shared with their role or team.
- Ask: Staff ask Codex Bot and open the entry behind its answer.

### Set the group standard

- Organize SOPs and policies into sections and entries.
- Pin house-manual entries to a brand when needed.
- Review extracted recipe details before saving them.
- Ask Codex Copilot to edit recipes and share by role.

### Use the standard on shift

- Search manual sections and revisit favorites or recent entries.
- Open only recipes shared with your role or team.
- Read plate steps with photos and declared allergens flagged.
- Ask Codex Bot in your language and open its source.

### Codex Copilot: Change a recipe across the locations you manage.

Codex Copilot edits recipes and manual entries across the locations in your access, and shares recipes with selected roles or teams.

- "Rewrite the opening checklist entry for Northside using these notes."
- "Update the batch recipe yield for Riverside to match this prep sheet."
- "Share the revised batch recipe with kitchen teams at Northside and Lakeside."
- "Change the guest description for the birthday dessert at Downtown."
- "Draft a cash-handling SOP for GMs from these notes."
- "Which teams get the current private-event dress code?"

## FAQ

**What is Restaurant Codex Knowledge Base?**

Restaurant Codex Knowledge Base is a shared collection of your group's recipes, SOPs, policies and house-manual entries. You organize entries in the dashboard and share them with selected roles or teams. Staff see the content shared with them in the staff app.

**Will my staff use the recipes and manual?**

Staff search manual sections, save favorites, revisit recent entries and open recipes shared with their role or team in the staff app. Codex Bot answers in the language they write in and links to the manual entry or recipe it used.

**How long does setup take?**

The 8-Week Implementation Program with the Restaurant Codex team includes weekly one-on-one meetings, hands-on support and ongoing guidance. You work through setup with the team during the program.

**How do standards reach multiple locations and brands?**

Write entries once for the group, then share them with roles or teams across locations. In multi-brand groups, pin an entry to a brand. Staff see only the content shared with them.

**What should we bring, and which languages are available?**

Bring the SOPs, policies, house manual and recipes your group uses now. Import a manual PDF up to 45 MB or a recipe from a PDF or up to five photos. People choose English, Spanish (Latin America) or Portuguese (Latin America). AI manual drafts are in English or Spanish.

**How does Knowledge Base connect to other modules?**

Knowledge Base works with Operations, Training and LMS and Inventory. Manual entries linked to tasks or training open from the task or training path. Codex Copilot creates and edits recipes and manual entries, while Codex Bot reads shared recipes and manual entries without changing them.

Book a demo: https://www.restaurantcodex.com/book-a-demo