SystemInflight Services & Supply Chain

Galley Planning

Galley planning that re-plans every galley a change touches — checked, cited and approved before a caterer loads it

Every galley loaded to spec: no cabin short of a meal, no weight flown for nothing.

See one case, screen by screen ↓
demo214plansre-planned by the agents from one menu change; 207 passed every check, 7 came to a person
demo−38kgoff one 787-9 galley load plan: a spare trolley that came back untouched on 71% of flights
demo23short-loadsstopped before a station in 30 days on the sample airline; none reached an aircraft
target0plan-caused short-loads reaching an aircraft: every plan checked against its tail and bookings first
In short

What is Galley Planning?

Galley planning is deciding what goes in every position of every aircraft galley — ovens, compartments, cart bays and chillers — for each aircraft layout, route and cabin, and publishing that galley load plan to the caterers who load it. Galley Planning brings that airline catering load planning into one place, with six AI agents: when a menu cycle, an equipment change or a tail swap lands, they re-plan every affected galley, check space, ovens, placards, weight and service flow by cabin, and write each caterer's change list. The galley planner answers the questions only a person can and approves every plan before a caterer sees it.

How to choose AI for airlines: a buyer's guide to agentic AI solutions →

Updated

The problem

Why galley planning still means redrawing galleys by hand

Galley planning decides what goes in every fixed position of every galley — each cart bay, oven insert, standard-unit compartment and chiller — for every aircraft layout, route and cabin, and publishes that galley load plan to the caterer at each station, who loads to it as the galley loading plan for every flight. The plans live in galley drawings, a legacy galley system and spreadsheets, and the catering weight of each galley feeds the standard catering weights load control uses on every flight.

Then something changes. A new menu cycle, a lighter trolley, a tail swap to an aircraft with a different galley layout or a new aircraft type can make hundreds of plans wrong at once. The planner works out which galleys are touched, counts oven loads and placards again, recomputes the weights and writes a notice to every caterer — over weeks, or in hours when operations swaps a tail before the caterer cut-off. A wrong plan leaves a cabin short of meals, or flies weight nobody uses: almost a quarter of cabin waste is food and drink nobody touched.

typical23%of cabin waste is untouched food and drink
typical0.94kgof cabin waste per passenger, on average
Where a menu cycle's galley planning days goestimated
By hand18 days
With the solution0.9 days
  • Working out which galley plans the change touches2 → 0.1 d
  • Re-planning each galley, position by position8 → 0.3 d
  • Checking ovens, placards, restraint and chilled bays3 → 0.1 d
  • Recomputing catering weights for load control2 → 0.1 d
  • Writing caterer notices and chasing acknowledgements3 → 0.3 d

Estimated split, in planner days, for one widebody menu cycle re-planned by hand and with the agents. These are estimates, not measurements.

How it works

How a change becomes a loaded galley

Six agents re-plan every galley a change touches, check each other and simulate the service; the planner answers one question and publishes.

What comes in
Change inper change · menu spec, drawings, tail swap, bookings
Agents at work
Change watcherfinds every affected plan
Then
Planner agentre-plans each position
Then
Fit and weight checkerspace, ovens, weight
Service flow agentsimulates the service
Then
Short-load guardplan × tail × bookings
Caterer brief writerplain change lists
A person decides
Galley planneranswers the question, approves, publishes
What comes out
Approved galley plan, every position cited
Change list each caterer acknowledges
Weights kept current for load control
One case, step by step

Galley planning for one menu change, from spec sheet to caterer

Corvane Airways' winter business menu W27-J2 replaces the cold starter with a hot starter in a casserole on long-haul Asia and Europe flights from December 1. Here is how Dana Whitfield, Galley Planner, Widebody, works through it with the agents on Thursday, October 15, screen by screen, in the working solution.

  1. 0110:40 am

    The agents did the morning's work; nine things need her

    Dana Whitfield · Galley Planner, Widebody

    Dana's Today screen shows 9 items that need her — 2 today, 7 from the winter menu — 405 plans re-planned by the agents this week, and 23 short-loads stopped before a station in the last 30 days, none of which reached an aircraft. Beside the list, the agents report in the conversation: what they read, what they changed and the one thing each needs from her.

    Planner agent, 8:31 am: “On ORD–NRT the new menu needs six oven loads and G1 holds four. I moved two to G2 and removed a spare trolley that comes back untouched: −38 kg. One timing question for you.”

  2. 028:12 am

    One menu spec, 214 galley plans re-planned

    Change watcher

    The change watcher read Marcus Lindqvist's spec sheet and found 214 plans on 31 routes that the menu touches: 118 on the 787-9 C layout, 6 on the 787-9 P layout from the acquired Pellmar fleet and 90 on the 777-300ER. The planner agent re-planned all 214, the fit and weight checker re-checked each from the drawings and placards, and the service flow agent ran each service. 207 pass every check and can be approved in bulk with a reason; 7 have a question.

    “7 questions for Dana Whitfield · 207 ready to approve.”

  3. 03The galley builder

    CV 881/882 Chicago–Tokyo, already re-planned

    Planner agent

    The first of the seven opens on the 787-9 N818CV — 48 business, 24 premium economy and 218 economy seats — drawn in plan view with G1 to G4 marked, and G2 at door 2, aft-facing, in front elevation. The new menu needs 96 business casseroles, 16 to an oven load: six loads, and G1 has four ovens. The planner agent moved two loads to G2's OV3 and OV4, serves business rows 9–12 from there, and marked every position it changed.

    Checks under the galley: Space, all 88 positions fit · Ovens, 6 loads, G1 4 + G2 2 · Weight, −38 kg, W&B approved · Short-load, every cabin loaded to seats.

  4. 04One question

    She asks why, in plain words

    Dana Whitfield · Galley Planner, Widebody

    Dana types “Why remove the spare trolley?” beside the galley. The planner agent answers from Northmere Flight Kitchen's September return-load report: the spare bread and dessert half-trolley in G1 T5 came back untouched on 22 of 31 flights, 71%. The new menu plates dessert from galley stowage, so the trolley has no job, and removing it takes 38 kg off every flight. Each source is numbered and opens the passage.

  5. 05One click

    Every position explains itself, with its source

    Planner agent

    Dana opens G2's T7. It holds chiller drawers with the 32 casseroles for rows 9–12, 22 kg, where the duty-free cart used to stand. The reason is one sentence with three sources — the galley drawing, the equipment library and food safety rule FS-3 — and the duty-free cart, which needs no chilling, has moved to the free full-size bay T9 in G4.

    “The only chilled bay in G2. It held the duty-free cart, which needs no chill; the 32 casseroles must stay chilled until the ovens.”

  6. 06Drag to ask

    She moves a cart; the agent says what that breaks

    Planner agent

    Dana tries the chiller drawers in T6 instead. A move is a question, not a silent edit, and the planner agent answers at once with its sources: T6 is not chilled, so the casseroles would sit out of chill for about 55 minutes before OV3 starts, and FS-3 allows 30. She undoes it. A move that breaks nothing can be kept, with a reason.

    “That breaks the chill rule. T6 is not chilled… Undo it, or ask me for another way.”

  7. 078:52 am

    The service is simulated, and one question is asked

    Service flow agent

    G2 is worked by one flight attendant at 2L. Its two ovens heat the starters first, then the mains, so business mains for rows 9–12 are ready at T+1:05, ten minutes later than today's T+0:55. Service standard IS-J-04 allows business mains to start up to T+1:15 on flights over 10 hours, so the call is Dana's. The fit and weight checker, working from the drawings and never from the planner agent's working, agrees: 3,019 kg becomes 2,981 kg, the index moves +0.9 against a ±1.5 tolerance, and Tom Okafor approved the new standard catering weight at 10:22 am.

    “Can the aft business service start 10 minutes later?”

  8. 08Approved

    She says yes, and signs with a reason

    Dana Whitfield · Galley Planner, Widebody

    Dana answers “Yes, start at T+1:05”. Approve and publish opens the sign-off: effective December 1 from Chicago and December 2 from Tokyo, 6 lines, −38 kg, aft business service +10 minutes, 5 of 5 checks passed. She picks the reason code “Within service standard IS-J-04”, keeps the statement for the record, confirms she reviewed the six changes and the weights, and publishes to Northmere Flight Kitchen at ORD and Hanazono Inflight Catering at NRT.

    “Checked the proposal, the checker's agreement and the service-flow answer.”

  9. 09Sent

    Each caterer gets a plain six-line change list

    Caterer brief writer

    Hanazono's change list says what changes from December 1, position by position: hot starters and mains in G1's ovens for rows 1–8, chiller drawers in G1 T6, rows 9–12 served from G2's ovens and T7, the spare half-trolley removed, the duty-free cart moved from G2 T7 to G4 T9, desserts plated from galley stowage. The flight's catering weight goes from 3,019 kg to 2,981 kg. The caterer brief writer sent it only after Dana approved, and tracks the acknowledgment against the 48-hour SLA.

  10. 10Decide by 4:00 pm

    The same morning, a tail swap before the cut-off

    Short-load guard

    Operations swapped N829CV, a 787-9 in the P layout, onto CV 917 Chicago–London Heathrow for Friday at 6:20 pm. With the old plan, premium economy would be 3 meals short against 27 booked, 6 business meal sets would fly unused, and 2 economy breakfast carts would not fit the smaller G4. The agents re-planned for the P layout — −22 kg, under the W&B threshold — and Dana approves, edits or rejects before Northmere's cut-off at 6:20 am tomorrow.

    Short-load guard: “3 passengers without a meal. Business would carry 6 unused sets, and 2 economy carts do not fit its G4.”

Who it’s for

Built for everyone who touches a galley load plan.

The same winter menu, seen by four of the people who carry it — what a menu cycle looked like, and what it looks like now.

DW
Dana WhitfieldGalley Planner, Widebody · approves and publishes within the service standard
Galley Planner, Widebody
Before
Owns about 400 widebody galley plans; every menu cycle and equipment change means weeks of redrawing galleys and re-typing loading lists.
Now
Opens each galley already re-planned and checked, answers the one question only she can, and publishes with a reason. “I don't want to redraw a galley. I want to decide the three things only I can decide.”
ML
Marcus LindqvistInflight Product Manager · menus, service standards, timing beyond the standard
Inflight Product Manager
Before
Issues a menu cycle and waits to learn which galleys cannot serve it, and whether the main course will be late.
Now
Sees his menu land on every galley the same day, and any service timing beyond the standard comes to him. “If the business main course is served late, nobody remembers how good the menu was.”
EB
Elena BrandtCatering Operations Manager · 37 caterers at 64 stations
Catering Operations Manager
Before
Sends notices by email and portal and chases acknowledgements station by station.
Now
Every station gets a plain change list after approval, acknowledgements are tracked against the 48-hour SLA, and caterer questions come with a cited draft answer. “A caterer can only load what we told them, and we have to tell them in time.”
TO
Tom OkaforWeight and Balance Engineer · standard catering weights (pantry codes)
Weight and Balance Engineer
Before
Finds out about galley changes after load control has been computing with the old weights.
Now
Sees each plan's weight change by galley and the index shift, and approves any change over 25 kg per galley or 0.5 index units before it publishes. “Thirty-eight kilograms is fine. Thirty-eight kilograms I didn't know about is not.”
Built on the engine

6 agents. Each with one job, and hard limits.

Six agents re-plan every galley a change touches, check each other and simulate the service; the planner answers one question and publishes.

Change watcher

Reads menu specs, equipment notices, tail swaps from operations control and new-type drawings, and opens a change case listing every affected galley plan.

  • Never changes a plan
  • Never guesses a menu's equipment; where the spec is silent, it asks Inflight Product
Planner agent

Re-plans each affected galley position by position — ovens, compartments, cart bays and chillers — moves items between galleys when one is full, and takes out what the caterers' return-load reports show flies back untouched.

  • Never publishes
  • Never uses a non-certified position
  • Never removes a special meal
Fit and weight checker

Re-derives space, oven loads, placard and restraint limits, and the weight by galley and index, from the drawings, placards and equipment library alone, and agrees or disagrees in writing.

  • Never reads the planner agent's working
  • Any disagreement goes to a person; over 25 kg or 0.5 index units, to the W&B engineer
Service flow agent

Simulates the service by cabin, minute by minute — oven cycles, cart runs and crew positions — against the service standards, and asks the one timing question a person must answer.

  • Never accepts a timing beyond the standard; routes it to Inflight Product
Short-load guard

Checks plan, tail and bookings by cabin 72 hours ahead, and reads the caterers' return-load reports for over-loads.

  • Never changes a caterer order inside the cut-off without a person
  • Top-ups go by rule; anything else goes to a person
Caterer brief writer

Writes each station's change list in plain words, one line per change with where, what and from when, sends it after approval, tracks the acknowledgment and drafts cited answers to caterer questions.

  • Never sends before a person approves
  • Never promises a commercial term
Galley planner and weight and balance engineer

The planner answers the agents' question and publishes; the W&B engineer approves weight changes over the threshold. The agents propose; a named person decides.

Ask in plain words

Ask about any galley, plan, caterer or weight

Ask in plain words, or tell the agents what to do. Every answer cites the menu spec, drawing, booking or report it came from, and nothing changes in a plan until a person approves it.

Why does ORD–NRT need G2's ovens?

The winter menu adds a hot starter: 96 business casseroles, 16 a load, so six oven loads. G1 has four ovens. The planner agent moved two loads to G2 and the duty-free cart to G4, and removed a spare trolley that came back untouched on 71% of flights: −38 kg.

Which flights could be short of meals in the next 72 hours?

Three need a person. CV 917 ORD–LHR: the swap to N829CV leaves premium economy 3 meals short. CV 455 SFO–FRA: premium economy 26 booked, 24 loaded. CV 301 ORD–SFO: first class, with Jordan Pike. Six more were handled by rule.

What did the lightweight trolley change for weight and balance?

The new trolley weighs 17.2 kg instead of 21.3 kg. With 34 trolleys, the 787-9 economy figure falls 139 kg, index −0.3: over the 25 kg threshold, so Tom Okafor approves it. Standard weights must stay current.

Draft the change list for the Tokyo caterer

Done: six lines for Hanazono (NRT), effective Dec 1, flight weight 3,019 → 2,981 kg. It goes when you approve LP-881; they acknowledge within 48 hours.

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

TodayGalley planning at a glance: what needs the galley planner today, plans re-planned by the agents this week, short-loads stopped before a station, and the agents' reports in the conversation.
One menu change, every planA menu cycle change opened as a case: the spec sheet cited, 214 galley load plans re-planned by fleet and layout, 207 passing every check for bulk approval and the 7 with a question.
The galley builderThe airline galley load plan for a 787-9: the aircraft in plan view with G1 to G4, G2 in front elevation with every oven, compartment and cart bay filled in, the five checks and the conversation with the agents.
Ask whyA question in plain words beside the galley layout, answered by the planner agent with numbered sources from the caterer's return-load report and the menu spec.
Every position explains itselfOne galley position opened: what it holds, its weight, what it held before, and why it is there, with its sources in the galley drawing, the equipment library and the chill rule.
Drag to askThe planner moves the chiller drawers to another bay and the agent replies that it breaks the chill rule, with the source and an Undo.
Service flow by cabinThe service simulated minute by minute for each galley: oven cycles, drinks and meal service by crew position, against the business mains limit in the service standard.
Approve and publishThe sign-off for a galley load plan: effective dates, changes, checks and weight approval, the caterers it publishes to, a reason code and a statement for the record.
The caterer's change listThe galley loading list changes as the caterer sees them: six plain lines, position by position, with weights, the effective date and the 48-hour acknowledgment.
A tail swap, re-planned before the cut-offA tail swap to a different galley layout: seats, bookings and the old plan by cabin, the short-load and the carts that do not fit, the agents' re-plan and the approval before the caterer cut-off.
Short-load watch, next 72 hoursEvery plan checked against its tail and bookings by cabin, so an inflight catering short-load is caught before a station loads: flags that need a person with the proposed fix, and top-ups handled by rule.
Standard catering weightsStandard catering weights by pantry code with before and after weights and the index shift, approvals by the weight and balance engineer, and one plan's weight by galley.
Audit trailEvery agent step and every human decision with the time, the actor, the plan and the reason, with the evidence pack to export.
Governance

Built so that only approved, checked galley plans reach a caterer.

Agents propose; people publishThe agents propose; a galley planner approves, edits or rejects every plan with a reason code and a statement, and no caterer sees a plan before that. A change list goes to a caterer only after a person approves the plan, and answers to caterer questions are drafts for Catering Operations to approve.
Every position cites its sourceEach position's reason, each agent message and each number cites a passage — the menu spec, the galley drawing, the placard, the equipment library, the service standard, the bookings or the return-load report — and one click opens it.
A second agent checks the firstThe fit and weight checker re-derives every plan from the drawings, placards and equipment library alone, never from the planner agent's working. If the two disagree, a person decides.
Weight changes reach load controlA change over 25 kg per galley or 0.5 index units waits for the weight and balance engineer, so the standard catering weights load control uses stay current, as FAA AC 120-27F expects of an operator using standard weights.
Hard rules the agents cannot bendEvery cart goes in a certified bay of its size, within its placard — the restraint 14 CFR 121.576 asks of galley equipment and serving carts. Chilled items stay in chilled bays, special meals are never moved or removed without a person, and timing beyond the service standard goes to Inflight Product.
Every step on the audit trailEvery agent step and every human decision is recorded with the time, the actor, the plan and the reason; nothing is edited or deleted. Each plan's evidence pack exports, and every change to a setting is logged with its old and new value.
Configuration

Your galleys, your standards, your thresholds

The thresholds and rules the agents escalate by are settings Corvane's administrator owns. Every change is logged with the old and new value.

SettingDefaultChoose from
W&B sign-off above (kg per galley)25 kgAny number of kilograms
W&B sign-off above (index units)0.5Any number of index units
Over-load flag above booked5%Any percentage
Caterer notice for a menu cycle21 daysAny number of days
Caterer notice for a swap12 hoursAny number of hours
Acknowledgment SLA48 hoursAny number of hours
Agent confidence below which a person decides0.85Any value from 0 to 1
RulesAll seven onChilled items only in chilled positions (FS-3) · Business mains by T+1:15 on flights over 10 hours (IS-J-04) · Items returned untouched on more than 60% of flights proposed for removal · Any cabin loaded below booked blocks publication · Always on: certified bay within its placard (14 CFR 121.576), special meals never moved or removed without a person, agents never publish, send or change a caterer order inside the cut-off
Connections

Works with the records galley plans are built from

Menu spec library and service standardsmenu cycles, service sequences and standards such as IS-J-04, from Inflight Product
Galley drawings and equipment libraryelevations, placards and equipment per configuration, from Engineering
Schedule and tail assignmenttail swaps from operations control
Reservationsbooked loads by cabin for the next 72 hours
Weight and balance · load controlstandard catering weights and the index
Caterer portal, email and return-load reportschange lists, acknowledgements, questions and what came back untouched
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
0
plan-caused short-loads reaching an aircraft: plan, tail and bookings checked first
96 of 96 hot dishes
business, ORD–NRT
estimated
12t
of fuel a year, estimated, from 38 kg off one 787-9 plan on one daily route pair
Before3,019 kg
Proposed2,981 kg
target
1day
for a menu, equipment or tail change to be re-planned and published, not weeks
By handweeks
Targetsame day

“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in the live solution · “estimated” = our estimate (the days split) · “typical” = published figures (IATA cabin waste: 0.94 kg per passenger, 23% of it untouched food and drink). Regulations are named as context: 14 CFR 121.576 (galley equipment secured) and FAA AC 120-27F (standard weights kept current). Corvane Airways, its caterers and the people named on this page are fictional — characters and sample data in the working solution.

Questions

What inflight and catering teams ask about galley planning.

What is Galley Planning?

Galley planning is deciding what goes in every position of every aircraft galley — ovens, compartments, cart bays and chillers — for each aircraft layout, route and cabin, and publishing that galley load plan to the caterers who load it. Galley Planning brings that airline catering load planning into one place, with six AI agents: when a menu cycle, an equipment change or a tail swap lands, they re-plan every affected galley, check space, ovens, placards, weight and service flow by cabin, and write each caterer's change list. The galley planner answers the questions only a person can and approves every plan before a caterer sees it.

How does galley planning software re-plan galleys when the menu changes?

The change watcher reads the menu spec and finds every plan it touches; the planner agent re-plans each galley position by position; the fit and weight checker re-derives each plan independently; and the service flow agent simulates the service. In the working solution, one winter business menu touched 214 plans: 207 passed every check and 7 came to the galley planner with one question each.

What happens to the galley load plan when an aircraft is swapped?

The short-load guard checks the new tail's galley layout against the plan and the bookings by cabin, and the planner agent re-plans for the new layout. In the working solution, a swap to a 787-9 in another layout would have left premium economy 3 meals short and 2 economy carts that did not fit; the agents re-planned it for the new galley layout, and the galley planner approves, edits or rejects the re-plan before the caterer cut-off.

How are standard catering weights kept current for weight and balance?

Every plan carries its catering weight by galley and the index shift. A change over 25 kg per galley or 0.5 index units waits for the weight and balance engineer's approval before it publishes, so load control never computes with a weight nobody told it about. FAA AC 120-27F expects an operator using standard weights to keep them current.

Does it check placards, restraint and chilled bays?

Yes. The planner agent puts every cart in a certified bay of its size, within its placard, and the fit and weight checker re-checks each position against the drawings, placards and restraint — 14 CFR 121.576 requires galley equipment and serving carts not in use to be secured against shifting. Chilled items stay in chilled bays, and the agents never use a non-certified position. If the planner moves a cart, the agents say what the move breaks, with the source.

How do caterers know what to load in each galley position?

The catering loading plan a station works from changes only after the galley planner approves it. Then the caterer brief writer sends each station a plain change list — one line per change, with where, what and from when — plus the weights, through the caterer portal or by email. It tracks the acknowledgment against the SLA, sends reminders, and drafts cited answers to caterer questions for Catering Operations to approve.

Do people stay in control of the galley plans?

Yes. The agents never publish a plan, send anything before a person approves, change a caterer order inside the cut-off without a person, remove a special meal or accept a timing beyond the service standard. The galley planner approves, edits or rejects every plan with a reason code; the weight and balance engineer approves weight changes over the threshold; Inflight Product decides timing beyond the standard. Every step is on the audit trail.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements and documents — your galley drawings, equipment library, menu specs, service standards and current loading lists — and it goes live once every quality gate has passed. Setup goes in order: fleet layouts, equipment library, service standards, caterers and stations, rules and thresholds, then connections.

See it on
your galleys.

We'll run Galley Planning on your own galley drawings, menu specs and loading lists, for one fleet and one menu cycle.