Hatch Plan

Projected vs. actual hatch quantities organized by date, used to schedule and fulfill orders.

Compile note. The dates, detail columns, and projected/actual split below are the expected shape of a hatch plan; exact field/column names marked ‹confirm› should be read from the live model.

Fields

Field	Type	Description
`Id`	GUID	Unique identifier.
`HatchDate`	date	The date chicks hatch / become available. `‹confirm›`
`SetDate`	date	Date eggs are set (typically hatch date minus incubation period). `‹confirm›`
`Breed` / `Product`	relation	What the plan line is for. `‹confirm›`
`Details`	collection → Hatch Plan Detail	Per-breed/product rows (see below). `‹confirm›`
…additional fields	`‹confirm›`	To be read from the live model.

Detail columns (per row)

Column	Type	Description
`Breed` / `Product`	relation	The chick type this row covers. `‹confirm›`
`Projected`	integer	Planned/expected quantity for the hatch date. `‹confirm›`
`Actual`	integer	Actual quantity hatched. `‹confirm›`
`Committed` / `Ordered`	integer	Quantity already committed to orders. `‹confirm›`
`Available`	integer	Remaining quantity available to sell. `‹confirm›`
…additional columns	`‹confirm›`	To be read from the live model.

Projected vs. actual

Projected figures come from flock production expectations (Flock Production).
Actual figures are recorded after the hatch.
The gap between projected, committed, and actual is what order scheduling and availability draw against. ‹confirm the exact reconciliation rule›.

Relationships

Related entity	Via	Notes
Flock Production	projection source	Expected output feeds projections.
Sales Order	ship/hatch date	Orders fulfilled against hatch dates.
Product / Breed	detail rows	Each row is a chick type.