The final bill is more useful than a vague recipe estimate
FireHousePal prefers an actual recorded meal total when one exists. When a verified total is not available, the cost view can fall back to available recipe or pricing estimates and clearly distinguish estimated data from verified cost data.
Cost per person stays tied to the meal
The cost view uses the meal total and eater or serving count to calculate cost per person. That makes a completed meal useful later: the crew can see whether a favorite was inexpensive, costly, or worth repeating for a similar headcount.
What the cost history can show
- Average tracked cost per person.
- Total tracked meal spend.
- Cheapest and most expensive tracked meals per person.
- Cost-per-serving trend over time when enough meal history exists.
- A meal-by-meal distinction between verified and estimated costs.
Cost tracking completes the FireHousePal meal loop
Planning, crew response, grocery work, and cooking all happen before the meal. Recording the final cost turns that completed meal into useful station knowledge for the next shift instead of letting the information disappear after cleanup.
