Submitting will save this BUILD tool to the restaurant database and update connected pages.
CL
ThreeStarOps restaurant operating system
Drop the clipboard. Let the kitchen ledger do the arithmetic.
Chef Ledger turns the work restaurants already do — counts, prep lists, station restocks, vendor orders, recipe cards, POS history, and employee submissions — into one clean, auditable workflow.
After the initial setup, the hours saved can pay for the subscription. Plug in the numbers, let the builder fill the site, and keep working while the app turns daily kitchen activity into order sheets, prep sheets, inventory history, and accountability.
No more chicken-scratch countsAutomatic order sheetsTraceable prep accountabilityPortable recipebook tools
Choose a tier
Simple monthly pricing for real kitchens
Start with the tier that fits your operation. Every tier is capped by included FILES storage so the website owner can control overhead while restaurants only pay for what they need.
Stripe paylinks can be configured per tier. In local preview, choosing a tier creates the account and keeps the workspace locked until the subscription is activated.
3★
subscription required
Choose a tier to unlock the kitchen.
Your profile is created. Select a monthly plan, complete checkout, then Chef Ledger opens the tools your tier includes. Until then, the account workspace stays protected.
Built for daily countsPrep sheets without guessingOrder sheets without retypingAuditable kitchen work
finish setup
Pick the plan that matches your operation
The first setup takes a little discipline. After that, the app is designed to save hours by replacing repeated paper counts, combined prep lists, unclear notes, and end-of-night spreadsheet entry.
Local preview activation
This button is only for testing the local build without a live Stripe webhook. Production should activate from Stripe checkout/webhooks.
Back of house command center
Dashboard
Chef Ledger command center
Plan. Prep. Profit.
Every station, count, prep list, schedule, and vendor deadline in one kitchen operating system.
Live inventoryStation prepVendor deadlinesSchedule control
Service in motionStation visibilityCounts into forecastsKitchen intelligenceChef-ready workflowPrep to profit
Needed now
Inventory risk
Open shifts
Expiring station batches
BUILD menu
Build the restaurant database once, then let every menu tool pull from it.
BUILD is the setup layer. The chef or team leader creates inventory items, vendors, recipes, dishes, stations, employee profiles, and schedule rules here. The main menu then becomes the live operating layer: employees count stations, prep is deducted from stock, deliveries update on-hand inventory, POS imports drive forecasts, and the scheduler respects employee availability.
Set up onceReuse everywhereLess pen-and-paper copyingCleaner employee permissions
Selected tool
BUILD tools
BUILD is the setup side of Chef Ledger. Each BUILD subpage creates the restaurant-specific database records that the live operating pages use during prep, service, ordering, and scheduling.
How to use
Pick one BUILD subpage from the dropdown, fill in the setup form, then use SUBMIT to confirm and propagate it.
It stops duplicate entry. A chef enters the setup once and every operating page pulls the same clean record.
BUILD landing
Use the BUILD dropdown in the top menu to open each builder page. The old side column was removed so this page follows the same navigation pattern as the rest of the app.
Start here when setting up a restaurant profile. BUILD pages are the database builders: they create the vendors, items, stations, recipes, plates, prep templates, employee permissions, and schedule blueprint that every live menu page uses later.
1. Build vendors and count locations
Vendors and locations create the supply-side structure for ordering, stock counts, and delivery receiving.
2. Build stations before inventory
Stations should be saved before Inventory Item Builder so inventory, recipes, prep, and schedule tools can use the same station dropdowns.
3. Build inventory, recipes, plates, employees, and schedule
Inventory feeds recipes and plates; employees and schedule blueprint prevent avoidable scheduling conflicts.
BUILD → Vendor Builder
Build vendors first. Vendor profiles feed Inventory Items, Order Day reminders, Delivery forecasts, and Vendor Orders.
How to use Vendor Builder
Enter vendor order days, delivery days, cutoff time, lead days, and contact info. Then Inventory Items can be tied to that vendor and Orders can group suggested quantities by vendor.
Why useful
The chef no longer has to remember who delivers what and when. Order-day reminders and vendor-specific order sheets pull from this one setup page.
BUILD → Location Builder
Create the stock rooms, shelves, coolers, freezer areas, and storage locations used by COUNT. Each location has a subclass and an IN ORDER number so COUNT tabs appear in the restaurant’s preferred walking order.
How to use Location Builder
Enter a location name, add a subclass like dairy, sauces cold, dry goods, #10 cans, or freezer, then enter IN ORDER N COUNT. Inventory Item Builder will use this list for each item’s LOCATION field.
Why useful
COUNT follows the same path every time. Employees do not bounce between random shelves or miss areas because the app orders tabs by the chef’s physical stockroom route.
BUILD → Inventory Item Builder
Create raw stock records: item name, LOCATION, amount per quantity, quantity in storage, par, reorder point, vendor, supplier pack, and shelf life. Saved items become selectable ingredients in Recipe Builder and components in Plate Builder.
How to use Inventory Item Builder
Add the item name, LOCATION from Location Builder, amount per quantity, quantity in storage, par level, reorder point, vendor, supplier pack, and shelf life. These items become the only selectable ingredients in Recipe Builder.
Why useful
Clean item setup keeps recipe costing, prep deductions, storage counts, and vendor orders using the same measurement system.
BUILD → Manual Inventory
Hard-count a product when the real walk-in / dry storage number is known. This corrects STORAGE and flows through On Hand, Prep Estimator, Until Next Delivery, and Orders.
How to use Manual Inventory
Choose the item and enter the hard count from the walk-in, dry storage, freezer, or stockroom. This replaces the calculated number with the real count.
Why useful
Manual inventory corrects drift from spills, waste, bad counts, or emergency use, so orders are based on actual stock.
BUILD → Station Builder
Create station names exactly how the restaurant uses them. Stations populate Prep, Recipe, Plate, Inventory, Scheduler, and Employee Profile dropdowns.
How to use Station Builder
Create the station names the restaurant actually uses, like Grill, Cold Prep, Pantry, Sauce, Expo, or Dessert.
Why useful
Stations organize recipes, plates, prep sheets, station closeout, schedule coverage, and employee qualifications.
BUILD → Recipe Builder
Recipes pull only from saved inventory items. Add containers so employees know what to store a recipe in after it is made and what station container should be stocked for service.
How to use Recipe Builder
Select inventory items from the search box, enter the amount used, add optional steps/sub-steps, and define storage and station containers.
Why useful
One recipe card now powers prep sheets, employee read-only recipe cards, ingredient deductions, and food-cost math.
BUILD → Menu Item / Plate Builder
Build sellable plates from recipes and direct items. Plate records drive per-plate cost, POS usage forecasting, station prep templates, and finished-plate picture reference.
How to use Menu Item / Plate Builder
Build a menu item from recipes and direct items, add portions, station, menu price, and optional plate picture URL.
Why useful
Plate setup connects POS plate counts to theoretical ingredient use, food cost, prep templates, and over/under-use analytics.
BUILD → Prep-Sheet Builder
Chef-only station template builder. Select a station, generate from Plates, and save the checklist employees will use in PREP.
How to use Prep-Sheet Builder
Choose a station and generate its recurring checklist from the plates assigned to that station. Save it as the employee PREP template.
Why useful
Employees no longer write random prep notes. The station checklist is standardized and feeds chef review, prep impact, and ordering risk.
BUILD → Employee Builder Overview
Employee Builder is the setup category for each team member. Use its subpages to decide who can receive messages, how many days off they have, and which stations / shifts they can work.
How to use Employee Builder
Start with the overview, then open Message Builder, Days-Off Profile, or Scheduling Profile. These BUILD pages create the employee rules that Teams, Scheduler, Access, Notifications, and Requests use during service.
Why useful
Employee setup is centralized. Managers do not have to copy station qualifications, time-off balances, message permissions, and schedule availability into separate notebooks.
BUILD → Employee Builder → Message Builder
Set what each employee is allowed to receive or act on when team posts are routed by task. This is employee setup, so it belongs in Employee Builder instead of the live message page.
How to use Message Builder
Select an employee, check the task categories they are eligible to receive, add any manager notes, and save. These settings control which posts, incidents, ordering notes, maintenance alerts, prep issues, and vote topics route to that employee.
Why useful
Restaurants can send the right problem to the right people without giving full manager access. A spilled item can alert ordering/manual-inventory helpers, while a broken fryer routes to maintenance-eligible staff.
Build each employee’s days-off bank here: allowed days, remaining balance, reset date, and rollover rule. The live Teams → Request Time Off page uses this profile when employees submit requests.
How to use Days-Off Profile
Select an employee, enter the number of days allowed, current remaining balance, reset date, and whether unused days roll over. Save the profile before approving requests.
Why useful
Time-off decisions stop being a notebook calculation. Approved requests deduct from the employee profile and create scheduler blocks automatically.
BUILD → Employee Builder → Scheduling Profile
Build the ongoing scheduling profile for each employee: color, station qualifications, eligible shifts, can-work patterns, and cannot-work patterns. Scheduler uses these records indefinitely until changed.
How to use Scheduling Profile
Choose an employee, set their unique color, qualified stations, eligible shifts, and weekly can-work / cannot-work patterns. These rules filter employees when a chef fills grey schedule blueprint slots.
Why useful
The chef can build schedules from valid people only, while still having override tools when needed. It keeps availability out of text threads and inside the schedule builder.
Team member profiles / schedule maker
Weekly can-work and can't-work shift patterns are saved inside each employee profile and used indefinitely until changed.
BUILD → Schedule BUILD
Create the restaurant's repeating schedule blueprint here: days open, shift labels, station coverage, hours, and employees needed. These saved blueprint slots appear as grey needed-shift boxes in the Scheduler UI for assignment/offering.
Demo restaurant hours loaded: Mon–Thu 11 AM–10 PM · Fri–Sat 11 AM–11:30 PM · Sun 9 AM–3 PM brunch. The demo scheduler is pre-filled so customers can click grey slots without building 80 shifts from scratch.
How to use Schedule BUILD
Create the weekly coverage blueprint by day, shift, station, start/end time, and employees needed.
Why useful
The scheduler starts with grey required slots instead of a blank calendar, so the chef only fills needed coverage.
Schedule BUILD → Blueprint Builder
Build the normal weekly coverage map: choose open days, shift type, station, hours, and how many employees are needed. These blueprint slots become grey boxes in the Scheduler UI and are assigned or offered there.
Inventory
This top-menu area is for USING inventory, not building it. ON HAND shows what is available across in-use and storage. STORAGE shows what is physically in-house but not stocked to stations. PREP ESTIMATOR projects what will be consumed when submitted prep sheets are completed. UNTIL NEXT DELIVERY subtracts prep and expected POS usage so the chef can see what will be left before the vendor shows up.
Selected tool
Inventory operating pages
Inventory is the live view of what the restaurant has, what is stocked into stations, what is still in storage, and what will remain after prep and forecasted usage.
How to use
Choose ON HAND, STORAGE, PREP ESTIMATOR, UNTIL NEXT DELIVERY, PAR, or WATCHLIST from the dropdown.
What it ties into
Manual Inventory, Prep uploads, Station closeout, Deliveries, Vendor Orders, Recipes, Plates, and POS usage.
Why it saves money
It shows shortages before they become 86s and helps prevent over-ordering items already sitting in storage.
Stockroom inventory checklist
Inventory Sheet
Live inventory split into storage, in-use, prep impact, total after prep, and PAR risk. This updates when prep is submitted, stations are restocked, or deliveries are received.
Watchlist / Order Risk
Inventory-only risk list. These are products that may hit par, reorder point, or shortage once prep sheets, POS forecast, and delivery timing are considered.
Order risk from look-ahead
At / below par after prep
COUNT
COUNT is the physical inventory and order-building workflow. Locations come from BUILD → Inventory Item Builder. The chef or authorized employee can count what is physically in each stock area, see estimated use until future deliveries, write order quantities, and turn those counts into vendor sheets.
COUNT subpage
All stock areas
Choose a stock area to count. HAVE and ORDER are writable; units and estimates are read-only calculations from Inventory, Prep, Plates, Recipes, Vendors, POS, and delivery timing.
ALL STOCK AREA(s)
Tabs are created from each item’s LOCATION in Inventory Builder. Use this for walk-in, dry storage, freezer, lowboy, and station storage counts.
SUGGESTED PAR TO ORDER
Items below PAR, below reorder, at 86 risk, or watchlist after prep/POS/delivery math. PAR TO ORDER is intentionally blank or editable because this is a chef decision, not a hard rule.
Vendor order sheets
Items from COUNT are grouped by each item’s vendor. Print, save, or download individual vendor sheets, or aggregate everything into one vendor-organized file.
VENDORS in forecast window
Delivery deadlines are calculated from the current date and selected forecast window. Flashing vendor cards indicate emergency order risk, expected 86 before delivery, or possible 86 between this delivery and the following delivery.
Use these buttons to jump to the page where order quantities are entered. Vendor cards and vendor sheets appear after ORDER / PAR TO ORDER values are entered.
PRICE OPTIMIZER
Estimator only. Enter a budget and Chef Ledger ranks items by 86 risk, need, watchlist, could-wait, and expected usage. It suggests adjusted order quantities to get close to budget, but actual performance can differ from algorithmic estimates.
COST IF ALL PAR FROM COUNT$0.00
Estimator notice: Chef Ledger is not responsible if service performance, sales, spoilage, delivery changes, vendor substitutions, or prep behavior differs from expected results determined by site algorithms.
Recipes & Plates
Recipes turn inventory items into costed batch cards. Plates combine recipes and items into sellable menu items so the chef can see cost per recipe, cost per plate, and which ingredient is driving margin.
This centralizes ingredient lookup, portion math, recipe cards, and food-cost analysis into one workflow instead of rewriting the same numbers across a notebook, spreadsheet, and POS export.
Selected tool
Recipes & Plates operating pages
Use this area to read recipe cards, view finished plate pictures, review menu-item cost, and adjust recipe or plate cost from the records built by the chef.
How to use
Choose a recipe-card, plate-picture, menu-item, or cost-adjustment subpage from the dropdown.
It makes portion cost visible before service, so chefs catch margin problems before the menu loses money.
Target-cost recipe optimizer
Select a recipe and enter a target recipe or plate cost. Chef Ledger scales every ingredient proportionally, then rounds to kitchen-friendly increments.
Dish / plate builder
Build a sellable menu item from multiple recipes and inventory items. This is what POS sales should map to for per-plate cost and portion-control analysis.
Recipe cards and cost breakdowns
Finished Plate Pictures
Pictures uploaded/linked in BUILD → Menu Item / Plate Builder appear here as a read-only plating reference for the kitchen.
Prep
PREPSHEET is the single station workflow for what needs prep, what was filled, what was closed out, and whether the station is ready for service. BUILD PREP still creates the recurring station template; this PREP page is where the restaurant uses it during the shift.
Selected tool
PREPSHEET
FILL / CLOSEOUT / PREP CHECK combines the old list-to-prepsheet and closeout steps into one station checklist. READY FOR SERVICE can be enabled by the chef profile if the restaurant wants a second manager/station-readiness check.
How to use
Choose a station, load the station list, enter what was left/restocked, check PREP? for items that need to be made, keep notes beside the item, then submit once.
What it ties into
BUILD PREP, Recipes, Plates, Inventory, Orders, Station closeout, Master Prep Sheet, and notifications.
Why it saves money
It turns one station check into prep demand, storage deduction estimates, in-use visibility, and order risk without employees filling out multiple forms.
Chef profile option
READY FOR SERVICE is optional. Turn it on if the restaurant wants a second readiness check after employees complete fill / closeout / prep check.
BUILD PREP → Station template from Plates
This is the chef setup page. Select a station and generate from the Menu Item / Plate Builder. Chef Ledger pulls every recipe and direct item used on that station's plates, then saves the recurring checklist employees will use on their PREP page.
For each station item, set the minimum amount to keep on station and the station unit/container. Examples: Grill can use steaks, burgers, cutlets, or breasts; Salad can use 1/9 pan, 1/6 pan, or dressing bottle; Dessert can use canisters, shallow half-pan, deep half-pan, or hotel pan. Recipe BUILD provides the default in-station container, but PREP BUILD can override it for the station.
BUILD PREP station template
This template is built from Plates assigned to the station. Checked rows are saved to the station template, populate the MASTER PREPSHEET, and update Prep Estimator / Inventory / PAR risk / Order suggestions. The minimum/unit fields are read-only on FILL / CLOSEOUT / PREP CHECK so employees know the station target without guessing.
PREP → Employee station checklist
Employees select their station and load the chef-built template. They check only the items that need to be prepped, optionally mark urgency, then upload the prep sheet to the chef profile.
Chef Prep Review → Station-organized uploads
Uploaded employee prep sheets collect here by station. Send them to next-shift employees, print, or save to device after every station has submitted.
FILL / CLOSEOUT / PREP CHECK
One station screen handles closeout, restock/fill, and the old list-to-prepsheet workflow. Employees enter what is left before restock, what is ready after restock, check PREP? for anything that needs to be made, and leave notes beside each station item. The Min. To Keep On Station and Unit columns come from BUILD PREP and are read-only for employees.
Use notes for real handoff events: spoiled product thrown out, spilled dressing, stocked what was left in the cooler, 86 in walk-in but enough for lunch, or anything that explains why the numbers changed. This keeps the end-of-shift protocol in one place instead of making staff restock, walk back and forth, write a prep sheet later, forget an item, and get blamed when it 86s during lunch.
CLAIM PREP ITEM
Employees assigned to the shift and physically in the building can claim prep work from the Master Prep List. This keeps high-priority prep visible and reduces the “I thought someone else was making it” problem.
READY FOR SERVICE → Master Prep Sheet / Live aggregated prep list
READY FOR SERVICE → Selected sheet tasks
PREP → FORECASTER
Upload saved FILES → POS CSV projection/special profiles, adjust expected plate counts, and add the forecast into prep, inventory, order sheet, and vendor math for a selected date range.
UPLOAD saved projection profile
Adjust expected plates
Active forecast / special events
UNDO reverses inventory impacts and order/vendor sheet pressure, then marks the special canceled.
Orders
Orders use live inventory, open prep tasks, POS sales, par levels, supplier pack sizes, and delivery schedules to estimate what should be ordered. The numbers are suggestions for the chef, not blind autopilot.
This replaces checking prep sheets, guessing tomorrow's sales, counting coolers, and hand-writing vendor orders with one Look Ahead workflow.
Selected tool
Orders operating pages
Orders uses inventory, prep, delivery timing, vendor setup, and POS sales to show what may need to be ordered now or before the next delivery.
How to use
Use NEEDED, VENDOR, DELIVERIES, or POS IMPORT from the dropdown.
It reduces emergency ordering and overbuying by showing expected use before the vendor arrives.
Next Deadline
Vendor deadlines are ranked by next order cutoff. Each vendor card shows the items that are below par, expected to 86 before delivery, or projected to fall below par before the following delivery.
Vendor Order Sheet
Open the order sheet created from COUNT for a specific vendor. The sheet can be printed, downloaded as CSV, or saved as a browser PDF/JPEG from the print dialog.
Order forecast
This is the main Chef Ledger difference: projected inventory subtracts open prep tasks and POS expected usage before the next delivery, then rounds the order to supplier pack units.
POS CSV moved to FILES
POS import/export now lives under FILES → POS CSV so all saved/imported documents stay together.
Vendor → Needed
Vendor-needed lists group order suggestions by the Vendor Builder profile. These estimates update from PREP, POS average plate sales, current STORAGE, and days until next delivery.
Suggested order sheet
Columns separate supplier pack ordering from kitchen usage math: supplier unit, pack size, current inventory, prep use, POS forecast use, projected inventory before delivery, par, and projected inventory after ordering.
Saved vendor orders
FILES
FILES is the restaurant document hub: POS CSVs, plate pictures, inventory snapshots, prep sheets, vendor order sheets, menus, and schedules. It keeps the paperwork that normally lives across clipboards, texts, office computers, POS exports, and bulletin boards in one searchable operating record.
Use this area to print, save, download, or prepare email-ready files. It helps catch waste early, cross-check who was working a station, and turn yesterday/today/tomorrow prep into one organized handoff.
FILES subpage
FILES landing
Choose a FILES subpage from the dropdown. Each page explains what it stores, how it saves time, and why it helps accountability.
Centralize the paperwork
Why useful
Prep sheets, count sheets, order sheets, schedules, menus, and POS files stop living in separate notebooks and computers.
How it saves money
Waste and missed prep show up earlier because FILES compares prep, count, POS, schedules, and vendor timing in one place.
How it saves time
Instead of asking three people for the right document, the chef opens the correct subpage, prints/saves/sends, and moves on.
FILES → POS CSV
Store nightly YTD POS CSV files, scan plates, project expected plate counts, and save profiles for PREP → FORECASTER.
Nightly POS library
Upload POS CSV files from yesterday, week-to-date, month-to-date, or year-to-date. Chef Ledger scans plate names, dates, quantities, prices, dayparts, and special/promo columns.
Forecast purpose
Projection profiles turn sold plates into expected plates by day, week, month, and season so prep and ordering can stop guessing.
Upload POS CSV file(s)
No CSV selected yet.
SHOW PLATES
PROJECTION
RAN SPECIAL
Projection/Profile folder
Saved profiles are ready for PREP → FORECASTER upload in the next workflow. They preserve selected plates, filters, projection values, and special-day stats.
Uploaded POS CSV files
FILES → Pictures
Upload recipe-card, plate, station, and location pictures into organized folders. Storage limits can be priced into the monthly subscription.
Folder builder
Click + to add photo(s), then MAKE FOLDER.
Top-tier: Create Post
Centralize linked social pages and generate a refined prompt to paste into your preferred AI model with the selected picture. Live auto-post integrations can attach here later.
FILES → Saved Inventories
Tier-based rolling file storage for inventory saves. PREP SHEET shows the rolling week. COUNT saves full inventory snapshots up to the tier limit; the oldest file rolls off when the cap is reached.
PREP SHEET · rolling week
COUNT tab · full inventory count saves
Saved inventory files
FILES → PREP SHEETs
Yesterday, Today, and Tomorrow prep sheets are grouped by station with notes attached. Red means 86, orange means needed now, green means no prep needed, and purple flags possible mismatch between station input, POS sales, and estimator math.
FILES → VENDOR
Choose a vendor and open the current order sheet created from COUNT. Print, download, or prepare an email-ready copy.
FILES → DELIVERIES
Save delivery/order files based on what was on the order sheet. Use VENDOR ORDERS to select a vendor and see delivery/order dates, with rolling retention by subscription tier.
VENDOR ORDERS · dates delivered/created
Saved delivery files
FILES → MENU
Menu access changes by subscription tier: starter CSV plate list, shift-grouped menus, picture/ingredient menus, then full recipe-card and social-prompt access.
FILES → QR CODE MAKER
Top-tier tool for attaching recipe QR codes to printed recipe cards/books. Employees scan the code to open the full portable recipe in the app instead of carrying around paper pages.
FILES → SCHEDULE(s)
Previous and current schedule files help pinpoint who was on a station when a waste, spoilage, or process issue happened. Schedules can be printed, posted, or sent without anyone driving in to check a bulletin board.
Manager → Schedule planner
The scheduler now works in two layers: the chef builds a weekly blueprint of the shifts and stations the restaurant needs, then the planner turns those blueprint slots into assigned shifts. Employee profile BUILD records control station qualifications, eligible shifts, weekly can-work / can't-work patterns, schedule colors, and override warnings.
The daily planner opens one day at a time for a larger, fine-dining control-room view. Grey boxes are required slots from the chef blueprint. Use the Day / Week / Station / Employee filter bar to break the schedule down, for example Wednesday next week + Grill. The demo schedule is pre-filled, with one extra grey demo slot left clickable; clicking any assigned shift opens a side panel showing the employee, rolling pay-period hours, overtime/request-off warnings, chef notes, and an OFFER SHIFT workflow.
Selected tool
Manager schedule operating pages
Scheduler uses the Schedule BUILD blueprint and Employee Profile BUILD availability to assign, offer, print, and send shifts.
How to use
Choose the schedule planner, fill-shift/offers view, shift approvals, or hours/overtime view. Employee availability setup lives under BUILD → Employee Profile BUILD.
It reduces accidental scheduling conflicts and makes weekly schedule changes visible to the team quickly.
Schedule BUILD lives in BUILD
Use BUILD → Schedule BUILD to create or adjust the grey needed-shift blueprint. This Scheduler page is for using those blueprint slots: click, assign, offer, send, print, or save the schedule.
Manager → Fill shifts / offers
Choose a day tab, click a grey needed slot, and assign or offer it without leaving the manager schedule planner. Employees are filtered from Employee Profile BUILD by station qualifications, eligible shift types, can-work rules, and cannot-work rules. Read-only profiles can view the planner; writable schedule access is required to save assignments, offers, notes, and output.
Read-only schedule access: you can view the manager schedule board, but only chef/team-leader profiles or employees granted scheduler-write access can assign shifts, offer shifts, write chef notes, or send the schedule.
Kitchen in motion
Plating and service
Costing with precision
Blueprint needed slot Can work Scheduled off / can't work Assigned shift
Selected needed shiftClick a grey needed shift above. The box turns white, then use SHIFT, EMPLOYEE, STATION, or OFFER SHIFT here inside the scheduler UI.
No grey slot selected yet.
Shift, start, and end come from BUILD → Scheduler Blueprint. Selecting a slot above fills this automatically.
Choose an employee from the filtered list. Availability comes from Employee Profile BUILD.
Stations come from BUILD → Station Tool. Employee choices narrow by the selected station and the selected shift.
Offered slots show as a split-color box until an employee accepts. The side panel lets the chef add respond-by time, auto-send to eligible employees, or manually choose who receives the offer.
My SCHEDULE
Employees see the posted schedule, open shift offers, and their own availability records. When the chef posts or changes the schedule, employees receive a notification and can accept offered shifts.
Employee Profile BUILD → Schedule availability
Employees submit the days, shifts, and stations they can work or cannot work as an ongoing profile. The chef scheduler keeps using this saved profile indefinitely until the employee or team leader changes it, so normal availability does not need to be rebuilt every week.
Manager → PREPLIST rank / assign
Authorized managers rank prep items by need, sort by station/shift/need-by, and assign work to employees scheduled for the shift. Suggested RANK uses open prep urgency, upcoming shifts, and POS-driven demand so tomorrow lunch needs can outrank a dinner-only 86.
Hours, overtime, and claims
Team schedule maker database
Chef view of everyone's can-work and can't-work records for the selected week.
Schedule and open shifts
Teams & Notes
Teams & Notes is the restaurant communication and clearance hub. BUILD pages create employees, permissions, stations, shifts, and task eligibility; this area is for using that information every day: granting temporary access, requesting time off, sending notes, reporting incidents, voting, and seeing employee-facing schedule information.
Instead of text chains, sticky notes, and word-of-mouth handoffs, Chef Ledger keeps messages tied to the tool they affect: inventory, ordering, scheduling, maintenance, prep, station closeout, votes, or manager-only records.
ACCESS
Use ACCESS when a person needs temporary clearance for a specific tool, not a permanent role change. A chef, sous, manager, or team leader can grant access for one shift, one day, one week, or indefinitely. This is useful when someone calls off, a vacation creates a coverage gap, or an emergency requires a trusted employee to complete a task they normally cannot access.
Temporary access is narrower than a role. Giving an employee access to Manual Inventory or Ordering does not make them a manager; it only unlocks that page or workflow for the selected duration. Active grants show in the employee portal and are used by Chef Ledger when deciding which menu items and pages are visible.
Active temporary access
These clearances are checked by the site before showing tools. Use this list to see who has access, why, and when it expires.
POST NOTE / SUGGESTIONS / REPORT INCIDENT
This page replaces loose texts and verbal reminders with a structured post tied to the tool it affects. A spilled #10 can of beans can go to Ordering / Manual Inventory eligible people; a broken fryer can go to Maintenance; a schedule question can go to Scheduling. The chef controls whether employees can message each other, whether all posts copy managers, and which task groups receive which messages.
Message Builder moved to BUILD
Message eligibility is employee setup. Open BUILD → Employee → Message Builder to assign which employees receive ordering, maintenance, prep, scheduling, station, manual inventory, and vote messages.
Team posts, incidents, and manager notes
MEMBERS
Member pages show the employee profile in one place: current and next week schedule, stations they can work, open/offered shifts, time-off balance, notification history, and a message box. Employees only see their own offers; leaders can view the whole team.
All team members
My / selected member home
REQUEST TIME OFF
Employees request time off from here. Team leaders set each employee's allowed days, remaining days, reset date, and rollover rule. Approved time off automatically subtracts days and creates a scheduler unavailable block.
Days-Off Profile moved to BUILD
Days-off banks are employee setup. Open BUILD → Employee → Days-Off Profile to set allowed days, remaining balance, reset date, and rollover before approving requests.
VOTE
Eligible employees can propose topics, but a designated vote captain approves what actually appears on the vote page. This keeps serious kitchen decisions organized without turning the app into a noisy group chat.
Vote captain review
Captains can edit/approve/deny pending topics. Use Edit note to send refinements back to the person who submitted it.
Approved vote topics
NOTIFICATIONS
Notifications show schedule posts, shift offers, access grants, time-off decisions, inventory messages, incident alerts, and vote decisions with timestamps.
Notifications
EMPLOYEE PROFILE BUILD
This is the BUILD side for employee scheduling. Set station qualifications, eligible shifts, unique color, can-work rules, can't-work rules, and the recurring weekly profile used by the Scheduler Builder.
Employee Scheduling Profile moved to BUILD
Station qualifications, eligible shifts, assigned color, can-work rules, and can't-work rules are now maintained under BUILD → Employee → Scheduling Profile.