Yield Is a Number, Not a Feeling
Every soaking vat in a food processing line has a target yield. The product goes in at a known weight, sits in brine or marinade at a specified concentration for a controlled duration, and comes out heavier. That weight gain is the yield — the metric that determines whether the batch is profitable, whether the brine ratio was correctly maintained, and whether the product meets spec for the next stage of processing.
The problem in most small-to-mid processing facilities is that these numbers are tracked on paper logs at the vat, transcribed to a daily report, and reviewed — if reviewed at all — a day later. By the time someone notices that yield has been running 2% below target for three consecutive shifts, the cause is already five batches back. You're chasing a ghost.
A digital soaking log, logged per batch in real time, closes that gap.
What Gets Measured Every Batch
The Processing Soaking Report template captures the complete picture of a single soaking run, structured around the variables that actually drive yield.
Konsentrasi Larutan (%) — brine or marinade concentration — is the starting point. Concentration drift is one of the most common causes of yield variance that operators attribute to product inconsistency. If the solution is being made up by volume rather than by precise weight measurement, the actual salt or marinade percentage can vary significantly across shifts. Logging the measured concentration per batch, not the nominal recipe concentration, makes this visible.
Volume Larutan (Liter) tracks the actual solution volume used. This matters because the ratio of product mass to solution volume affects brine uptake rate. An underfilled vat — someone started the batch short on solution — changes the equilibration dynamics. Combined with the product weight before soaking (Berat Produk Sebelum Soaking), you can retrospectively calculate the product-to-brine ratio per batch and correlate it with yield outcomes.
Suhu Larutan and Suhu Produk Setelah Soaking — solution temperature at start and product temperature after soaking — are the thermal record. Temperature management is critical in cold-chain processing. A solution that has warmed beyond the safe zone, or a product that came off refrigerated holding warmer than target, changes both yield and food safety status. These aren't just quality parameters; they're the data points a QA auditor will ask for during a facility inspection.
When Yield Drift Becomes Visible
The template captures the full before/after weight pair: Berat Produk Sebelum Soaking and Berat Produk Setelah Soaking, with Kenaikan Berat Setelah Soaking as the weight gain in kilograms. Yield Soaking (%) is the final calculated number — weight gain as a percentage of pre-soak weight.
When you're running this template across 30 batches a week, the Yield Soaking field becomes a filter. Sort by yield. The low-performing batches cluster. Pull their records and the pattern is almost always in one of four fields: concentration out of spec, solution volume short, soak time cut, or product temperature at start. The template makes the investigation a matter of reading the data rather than interviewing shift operators who may or may not remember what happened three days ago.
Waktu Start Soaking, Waktu Selesai Soaking, and Total Waktu Soaking — start time, end time, and total duration — add the time dimension. Shortened soak times are the most common unauthorized shortcut in a facility running behind schedule. When a batch comes in with 18% yield against a 22% target and the total soak time is 40 minutes short, the record tells you what happened without needing a conversation.