Grain Milling, Dry Bulk Food & Feed Handling worked example
Moisture Loss at 2.88% target moisture loss: a worked example in grain milling, dry bulk food & feed handling
This scenario runs the moisture loss calculation on the strong side: 2.88% target moisture loss, with every other input held at its documented default. Use it when quality, elevator, or production teams need to quantify shrink from drying, tempering, storage, cooling, or handling before updating yield and cost assumptions.
The inputs for this scenario
- Moisture loss weight: 1,800 lb (unchanged)
- Starting product weight: 60,000 lb (unchanged)
- Target moisture loss: 2.88 % (raised for this scenario; the documented default is 2.5)
Working through the calculation
- Applying the documented formula (Moisture loss rate = moisture loss weight ÷ starting product weight × 100) to the inputs above produces each figure below.
- At this operating point the engine returns 3 % for moisture loss rate, the number this scenario is built around.
- At this operating point the engine returns -0.12 points for moisture loss gap to target.
- At this operating point the engine returns 1,800 count for moisture loss weight.
- At this operating point the engine returns 60,000 count for starting product weight.
How this compares with the baseline
- Against the tool's baseline example, where target moisture loss sits at 2.5% and the headline result is 3 %, this scenario lands almost exactly on the baseline at 3 %.
- Use it after drying or conditioning to confirm a lot hit its moisture target, or to investigate yield loss that traces back to over-drying. Treat this as a target state: the delta against the baseline quantifies what the improvement is worth before you commit to chasing it.
Results at a glance
- Moisture loss rate: 3 % (headline result)
- Moisture loss gap to target: -0.12 points
- Moisture loss weight: 1,800 count
- Starting product weight: 60,000 count
Run it with your numbers
- Every input above is editable in the live Moisture Loss calculator, which recalculates instantly and can be shared with the inputs intact.
Last reviewed 2026-05-12.