Pause when the result does not fit the visit
A returning truck is on the platform, the second weight is available, and the calculated load is far from what the desk expected. The useful next step is a short investigation. An order quantity, a driver's estimate and a measured load answer different questions; disagreement is a reason to check the visit, not a reason to replace the measured figure with the expected one.
LionLoad truck scale software provides saved customers and trucks, an open-ticket queue and material-on-hand workflows. Those features organize the visit, but the operator still needs a procedure for exceptions. This review is a recommended desk routine, not a claim that LionLoad automatically diagnoses unusual weights or approves a load for dispatch.
Confirm that both weights belong to this truck
Start with identity before arithmetic. Compare the vehicle in front of the desk with the selected open ticket, including its customer and license plate. A contractor may have several vehicles in the yard, and one vehicle may make repeated trips. A familiar company name alone cannot establish that the selected first weight belongs to the current visit.
Ask whether anything about the vehicle combination changed between weighments. A different trailer or equipment added or removed can change what is being compared. Keep the explanation with the yard's agreed supporting records. If the pairing is uncertain, leave the visit unresolved while the responsible person checks it; do not attach a convenient earlier weight simply because it gives a plausible result.
Check the values and units before judging the load
Read the first and second recorded weights with their units. Check the selected scale and compare the current received value with the indicator under the installation's validated procedure. An unexpected decimal position, unit or weight mode deserves investigation before the transaction is completed. A number that updates on screen is not, by itself, proof that the incoming stream is interpreted correctly.
NIST's Weighing and Scales FAQs distinguishes subtracting two separate gross truck weighments in a computer from an indicator's tare operation. Preserve that distinction when reviewing a record: the name printed beside a number does not explain how it was obtained. Use the actual weighing method documented for the installation.
For an illustrative pickup, a first weight of 30,000 lb and a return weight of 66,000 lb differ by 36,000 lb. If the order was for 40,000 lb, the 4,000 lb difference from the order is a question to resolve. It is not an instruction to change either recorded weighment. These figures illustrate arithmetic, not permissible vehicle loads.
Establish what moved, and in which direction
Confirm the selected material and whether the visit represents a delivery into the yard or a pickup leaving it. Weigh-in and weigh-out describe the sequence of the visit. They do not, on their own, say whether stock should increase or decrease. A valid weight paired with the wrong material or direction can still produce a misleading inventory record.
Ask the loading or receiving team to confirm what happened physically. Was the intended material loaded? Was the delivery fully discharged? Was there a change to the order? Treat those as questions for the people responsible, not facts the software can infer from weight alone. Where a further weighing is needed, follow the site's approved exception procedure and preserve the reason for it.
LionLoad updates material on hand once when a delivery or pickup is completed. That makes the review before completion useful: resolving the visit first avoids treating an uncertain transaction as a settled stock movement.
Keep the evidence separate from the explanation
Keep the original weighing information available alongside the explanation for the discrepancy. A useful exception note identifies the visit, the question raised, who checked it and the agreed next action. Use the business's established recordkeeping process for information that is not held in the software. Do not imply that a handwritten explanation is another measurement.
After the issue is resolved, check the saved transaction and its printed output separately. LionLoad's save-weigh-out-and-print action submits to the configured printer; it does not prove that a readable sheet emerged. A missing printout calls for checking the saved record and printer, not capturing another load solely to obtain paper.
- Match customer, vehicle and open visit.
- Check both weight values, their units and the selected scale.
- Confirm material, delivery or pickup, and what physically occurred.
- Record the explanation and the person responsible for the decision.
- Verify the completed record and the actual printed ticket.
Practice exceptions before the busy shift
Use Demo visits to rehearse an incorrect vehicle selection, an order quantity that differs from the measured load and a printer that is unavailable. Ask another operator to explain what they would check before completing each visit. The exercise should reveal whether the procedure is understandable, not whether staff can guess the expected answer.
LionLoad connects truck weighing, tickets and material records in one yard workspace. LionLoad workstations joined to one yard host share open visits, records and stock over the local network. The host must remain running; standalone installations stay independent. Multiple-yard support is planned for later. The LionLoad software overview linked below describes the product scope.
The Jo Way is to resolve the question while the evidence is still at the desk: identify the visit, understand the weights and leave a record the next person can follow.
Further reading
Useful records. Clearer workflows.
Put your weighing data to work.
Explore Jo-Weigh’s scale capture, ticket printing and record export workflows.
Compare Jo-Weigh & LionLoad ↗