Recipe Platform Change Proposal

Change Proposal

Problem

The current corporate tools lack proper mass-to-volume conversion, hotel-pan/unconventional volume conversion, sub-recipe rollups, forecasting and production-record tie-in, automated ordering forecasts, and forecast-to-production accuracy analysis.

Desired Outcome

Establish a future-state operating loop where recipe data supports scaled production, menu forecasts become production records, production records support accuracy analysis, and menu and recipe demand informs ordering forecasts.

Options Considered

Option	Description	Tradeoff	Evidence Quality
A	Center the prototype narrative on conversion, hotel-pan scaling, sub-recipe rollups, forecast-to-production, ordering forecast, and accuracy analysis.	Directly matches user-provided future-state examples.	User-provided/Observed
B	Continue only the latest Inventory roadmap without reframing the broader product story.	Useful technically, but under-explains why the prototype exists.	Observed/Inferred
C	Jump to full accounting/receiving module.	Higher risk because invoice placement and count semantics are not formalized.	Inferred
D	Start Analytics before stabilizing forecast, production, inventory, purchasing, and cost contracts.	Risks consuming unstable facts.	Observed/Inferred

Recommended Change

Proceed with Option A as the product-analysis frame:

1. Use corporate current-state limitations as the problem statement.
2. Use the prototype's conversion, hotel-pan, scaling, rollup, forecasting, production record, and inventory planning features as the future-state response.
3. Validate the prototype against real corporate recipes, sub-recipes, hotel-pan production scenarios, menus, forecast records, and production actuals.
4. Keep vendor/invoice/accounting design as a downstream extension of the ordering forecast path, not the core reason the project exists.
5. Preserve deferred Analytics until posted production, usage, inventory, purchasing, and cost facts are stable.

Scope

In scope:

• Recipe conversion/scaling, hotel-pan production units, sub-recipe rollups, menu forecasting, production records, ordering forecast, forecast accuracy analysis, and the prototype evidence that supports them.

Out of scope unless separately approved:

• Full accounting module.
• Production purchase-order generation.
• Production deployment/auth replacement.
• Analytics algorithms beyond forecast accuracy/history already represented by the prototype.

BA Alignment

• Activity areas: Analyze strategy; evaluate solution; manage requirements lifecycle.
• Techniques used: Decision analysis, gap analysis, future-state modeling, roadmap analysis.