The daily crop record is the highest-frequency entry in a poultry operation and the one most performance conversations eventually rest on. Mortality rate, target weight, actual weight, and water consumed, per house, per day, with the time it was recorded and the person who recorded it. It is also the record that feeds the processor console's benchmarking and week-over-week views more directly than any other, which is why how it gets logged matters as much as whether it gets logged.
What the Daily Crop Record Captures
Each entry is per house per day: the flock reference and placement date, the record time, who completed it, the daily mortality rate, the target weight in grams, the actual weight in grams, and water consumed with its declared unit in liters, US gallons, or imperial gallons. The unit declaration matters: because the console converts automatically, a grower network where one farm logs gallons and another logs liters still produces one comparable water series.
How the Processor Console Uses It
- House Benchmarking - mortality rate computed from recorded losses for the active flock, average daily water in liters, and water per bird in milliliters, per house.
- Week-over-Week - target versus actual weight per flock week, average mortality percentage, and average water use, across every consented grower.
- Alerts - threshold breaches on mortality and water against the processor's own warning and critical limits, per day, week, and flock period.
- Age pipeline - the daily entries place each flock in the console's age buckets, from brooding through heavy, so submissions can be read by stage.
Why Daily Resolution Beats Monthly Estimates
A monthly mortality estimate smooths over the day the problem started. A daily record shows it: a mortality spike on day nine, water per bird dropping two days before feed intake followed, a weight gap opening in week six rather than appearing at settlement. Because the entry is part of the daily routine rather than a reconstruction, the trend behind an alert or a benchmark finding can be traced to the day it happened, and the corrective action conversation starts from evidence rather than from memory.
What the Record Does Not Claim
The daily crop record documents what was recorded for the house on the day. It does not certify that the flock met a performance standard, and the console does not compute a compliance percentage or invent breed-specific target curves; the targets in the record are the ones the farm and program already set. Grower-supplied checklists support audit readiness; they do not certify legal compliance.
Where Poultry Log Fits
The daily crop record runs in the same grower app as the rest of the operation, so the processor's views are reading evidence the farm already produced. The water metrics are covered in the water use monitoring guide, mortality in the mortality and cull tracking guide, and the weekly trend in the week-over-week performance guide. Start free at poultrylog.com.
Frequently Asked Questions
What should a daily poultry crop record include?
The house and flock, placement date, record time and completer, daily mortality rate, target and actual weight in grams, and water consumed with its unit. Poultry Log's daily crop record captures exactly these fields, per house per day.
How do processors use daily crop records?
They feed house benchmarking (mortality rate, average daily water, water per bird), the week-over-week view (weight versus target, average mortality and water), and the alert engine's mortality and water thresholds, per day, week, and flock period.
Does the daily crop record calculate performance targets?
No. The record preserves the target weight the farm and program already set alongside the actual weight recorded. The processor console reports the gap; it does not invent breed-specific target curves or a compliance percentage.