build@food4education.org
Skip to main content

Application Views

App Menu Overview

A quick summary of the Kitchen Operations app's main menu items — toggle each one to see what it does and which roles can access it.

🏠 Home — All roles

The main dashboard. Shows the Kitchen Manager panel (Inventory Management, Projections), Logistics (Dispatch), and Tap2Eat shortcuts. The right panel shows Daily Watch — a live view of all active kitchens with status, meal type and date — and Reports (Daily Summary, Stock Movement). Starting point for all flows.

🚌 Schools — Admin, KM

Lists all schools linked to each kitchen. Used to verify school-to-kitchen mapping and headcounts. KMs reference this when filling projected students per school in the Projection flow.

👥 User Mapping — Admin

Manages the kitchen_mapping table — assigns users to kitchens and controls which roles (KM, WHSE, Finance) can see which views. Changes here affect view visibility across the entire app.

📅 Planning — Admin

The meal schedule management view. Admins create plan entries (date, menu code, holiday flag, kitchen model), edit menus inline, and confirm or re-open plans. Plans flow through Open → Active → Closed. KMs see confirmed plans in their Projection flow.

🍳 Kitchen Consumption — KM, Admin

Tracks post-cooking consumption data per kitchen — actual students fed, food remaining, missed meals, loaves, and milk. Feeds into the actuals recorded in the Projection flow and used for daily reporting and reconciliation.

📋 Menu Plan — Admin

Displays the structured weekly/monthly menu plan — the combination of menu codes (R&B, R&G, R&W, etc.) across all kitchens. Provides an overview of what is planned to be cooked each day and allows admins to review distribution across kitchen models.

📊 Reports — Admin, Finance

Two main reports: Daily Summary — combines projections, Tap2Eat data, and stock summaries for a full daily picture. Stock Movement — tracks ingredient movement per kitchen per day. Finance and Admin use these for reconciliation and to monitor meal delivery.

🥗 Menu — Admin

Manages the master list of meal menu codes — R&B (Rice & Beans), R&G (Rice & Githeri), R&W (Rice & Waru), R&B-M, R&G(P), R&B(T), etc. Each menu code defines what is cooked. Used by Admins when assigning menus to plan entries.

🌿 Ingredients — Admin

The master ingredient register — Rice, Mahindi Beans, Machemaria, Green Grams, W/Ndengu, Cooking Oil, Salt, Maize, and non-stock items (Cabbage, Turmeric, Tomatoes, etc.). Defines ingredient types (Stock vs Non-Stock), units, and consumption ratios used to auto-calculate kg quantities in stock requisitions.


This document catalogs the AppSheet app's UX views — what shows up in the navigation bar and on each role's home dashboard, and who can see it. It's generated from the AppSheet app definition export and should be re-synced whenever the app's view/navigation structure changes.

Source: AppSheet app definition export, synced 2026-07-01. The app defines ~180 views in total, but most are AppSheet's auto-generated Detail/Form/Inline pages (one per table, used for viewing/editing a single record) — those aren't listed individually here since users don't navigate to them directly. This page covers the ~15 top-level navigation entries and the role-based home dashboard tabs.

Role legend

Visibility below is driven by each user's role in the kitchen_mapping table:

RoleDescription
AdminFull system access, including meal plan authoring
KMKitchen Manager
WHSEWarehouse
FinanceFinance team
CollabCollaborator / cluster-level lead

Top-level navigation

These are the views pinned to the app's main navigation bar (left, center, right, and the overflow menu).

ViewTypePositionVisible toPurpose
home_tabbedDashboardLeft mostEveryone except WHSELanding dashboard; hosts the role-specific home tabs below
warehouse_requestsTableCenterWHSEWarehouse's queue of pending kitchen requests
schoolsDeckLeftAdmin, KM, CollabSchool directory
User MappingTableLeftAdminManage staff-to-role/kitchen assignments
monthly-planDeckRightAdmin, CollabMonthly meal plan deck view
Batch RequestDeckMenuAdmin, WHSEWarehouse batch stock request queue
Direct IssuanceFormMenuAdmin, WHSEDirect stock issuance form
My ClusterDetailMenuAdmin, CollabCluster-level rollup
Projection HistoryTableMenuAdmin, KM, CollabHistorical meal projections
Uji cups per dayTableMenuEveryoneDaily uji (porridge) cup counts
monthly-plan-viewCalendarMenuEveryoneCalendar view of the monthly meal plan
ReportsDeckMenuEveryoneReports & analytics hub
MealsTableMenuAdminMeals master data
IngredientsTableMenuAdminIngredients master data
Part MasterTableMenuAdmin, WHSENon-food parts/items master data

Home dashboard tabs

home_tabbed shows a different set of tabs to each user depending on role — each tab is its own view, individually gated by a Show if condition:

TabTypeVisible toPurpose
HomeCardAdminAdmin home dashboard
HomePlannerCardAdminSecondary admin home dashboard (planning-focused variant)
HomeKMCardKMKitchen Manager home dashboard
HomeFinanceCardFinanceFinance home dashboard
area_lead_schoolsTableArea Lead's assigned schools
up_comming_plansTableAdminUpcoming plans widget
ReportsDeckEveryoneSame Reports view as the main nav entry
warehouse_requestsTableWHSESame warehouse queue as the main nav entry

Recent changes

Compared against the previous app definition export (2026-06-17):

  • Added: Batch Request (replaces the old Secondary Issuance flow — see below), My Cluster, Projection History, Uji Cups per Kitchen, Uji cups per day.
  • Removed: Secondary Issuance and its supporting views (Secondary_Issuance_Form 2, WHSE_Issuance_Form, WHSE_Issue_Queue, KM_Receive_Secondary_Form, batch_receive_form, batch_stock_request), and Closed Plans with its Detail/Form pages.
  • Renamed: Kitchen plansKitchen Plans, School historySchools History.

The Secondary Issuance workflow has been fully replaced by the Batch Request view — see the Batch Issuance video for the current process.