Beta
Cluckiva
Poultry flock and hatchery software
Placements, daily egg counts, mortalities, feed weights, incubation and candling, and the stock remedy register that Act 36 requires you to keep. Production is plotted against the Hy-Line, Lohmann, Ross 308 and Cobb 500 breed curves, so a flock falling behind is visible the same day.
Most of the houses we visited lose power more often than they lose signal, so there is no subscription, no sync, and no cloud account that can lock a farmer out of their own records.
What else it carries
Hen-day and hen-housed
Production is reported both ways. The two figures separate as soon as mortality starts, and a house holding steady on the first can be losing ground on the second.
Feed conversion
Feed is weighed in per house and per flock, so the conversion ratio belongs to the birds that ate it.
The hatchery
Setter and hatcher are separate machines with separate records. Eggs set, storage days and storage temperature, candling split into fertile, infertile, early dead and late dead, then transfer and hatch of fertile against hatch of set.
Mortality coding
Mortalities and culls are recorded against DAFF disease classification codes, so the coding is already done on the day a notifiable disease has to be reported.
Movement permits
Movement permits sit with the stock remedy register, so the Act 36 file and the movement file are one file.
Load-shedding
A load-shedding event is logged against the house, with its start and its end. A later dip in lay then has something to be read against.
Hen-day production
Every flock against its breed standard, the day the eggs are counted.
A house of 40 000 layers over one cycle, plotted against the Hy-Line Brown standard inside a three point tolerance band. Weekly mortality runs underneath. A flock that leaves the band is flagged that day, not at depletion.
- Flagged
- No deviation
- Peak deviation
- 1.8 pp
- Birds lost to the event
- 0
- Eggs lost against standard
- 0
Illustrative. Standard curve shape from published Hy-Line Brown figures; flock size, background mortality and the event profile are modelled, not a customer's data.


