A flock's first week tells you almost nothing. Its tenth tells you almost everything. That is why poultry processors who manage grower networks increasingly review performance week over week rather than flock by flock at settlement: a mortality rate that is drifting, a weight gap that is widening, or an equipment pass rate that is slipping shows up in the weekly trend long before it shows up in the payout.
The Week-over-Week view in the Poultry Log processor console is built for exactly that review, covering flock weeks one through ten across every consented grower in the network.
What the Weekly View Reports
For each week, the console shows how many flocks are reporting, how many records were submitted, target versus actual weight in grams, average mortality percentage, average water use, equipment pass rate percentage, and rodent incident percentage. Water converts automatically from whatever unit the grower logged, whether liters, US gallons, or imperial gallons, so a network mixing units still compares cleanly.
Why Week over Week Beats Flock Averages
A flock average smooths over the story. A broiler flock that averaged 2.1 percent mortality across forty-two days looks acceptable in a single number; the weekly view shows whether that mortality concentrated in week one brooding losses, which are one problem, or spread across finishing, which is another. The same applies to weight: a final weight that missed target by fifty grams means something different if weeks one through five were on pace and weeks six through ten fell behind than if the gap was there from the start.
How Processors Use the Trend
- Compare growers on rates, not totals, so farm size does not distort the picture.
- Separate one farm's outlier week from a network-wide pattern, for example a hot stretch that lifted water use across every grower in the same region.
- Watch equipment pass rate against mortality, since a failing generator or foot dip line often precedes a health problem.
- Review rodent incident rate weekly rather than waiting for the quarterly audit.
Thresholds Make the Trend Actionable
Raw trends are interesting; policy makes them operational. In the console's admin view, the processor sets warning and critical limits for mortality, culls, and water use by day, week, and flock period, plus rise and drop percentage checks that catch sudden movement even inside an otherwise acceptable range. Breaches raise alerts with current versus previous rates attached, so the conversation starts from evidence rather than recollection.
Where Poultry Log Fits
The weekly numbers come from the checklists growers already submit in Poultry Log, so trend review does not add work to the farm. The house-level detail behind the trend is covered in the grower house benchmarking guide, and the alert flow in the processor biosecurity alerts guide. Start free at poultrylog.com.
Frequently Asked Questions
How do poultry integrators compare flock performance week by week?
By aggregating weekly grower submissions into one trend view. The Poultry Log processor console reports weeks one through ten with flocks reporting, target versus actual weight, average mortality, average water use, equipment pass rate, and rodent incident rate across every linked grower.
What is a target weight gap in broiler production?
The difference between the weight a flock should be at for its age and the weight actually recorded. In the processor console, target versus actual weight in grams is reported per week, so a widening gap is visible while there is still time to investigate feed, water, or health.
Can a processor set trend-based alert limits?
Yes. Threshold policy in the Poultry Log processor console includes rise and drop percentage limits per metric, on top of warning and critical levels by day, week, and flock period.