Keep Declared Freight Weight Separate from an Observed Reading

1. Make the desk question narrow

Use this guide when an internal freight desk has two weight-related statements about one job: a value declared by the consignor and a later observed reading documented from a named source. The operational purpose is to preserve what each source said, when it was recorded, and what it referred to. It is not a method for deciding physical weight, converting units, setting charges, or deciding whether a vehicle may move.

Start with one stable job reference and one stated goods scope. A job can contain several consignments, stops, packages, or changes. Same job alone is therefore insufficient. Write the declared value with its unit and source exactly as received. Write the observed value with its unit, document or record reference, observation time if available, and the person entering it. Neither entry should silently replace the other.

The cited Fleet workflow material distinguishes cargo weight from other operational requirements and separates operational states rather than collapsing them. That is a fleet-workflow example of clear record boundaries, not a rule for every fleet. This guide’s worksheet and decisions below are original suggested internal practice, not a fleet-provider requirement, universal industry standard, Malaysia service rule, or legal obligation.

Source: BossFlow Fleet workflow scope

2. Capture evidence before interpreting the difference

Create two labelled evidence blocks. The declared block answers: who declared it, what value and unit were stated, what goods scope was named, and where the declaration came from. The observed block answers: what was observed or reported, in which unit, from which document or record, at what documented time, and for what stated goods scope. Preserve attachments or references where your internal process permits.

Do not infer missing links. A reading described only as today’s load, for example, may not identify the same consignment, vehicle stage, packaging condition, or goods subset as a declaration. A unit label that is absent, unclear, or unlike the declared unit is not a minor formatting issue. Mark the comparison basis unconfirmed instead of calculating or assuming a relationship.

The GOV.UK material supports describing work through observable outcomes, actors, and goals. Applied narrowly here, a useful internal outcome is that a reviewer can see both observations, their sources, and the remaining question. It does not prescribe these freight fields or validate a comparison.

3. Follow the decision sequence

Use the same sequence every time so urgency does not turn an observation into an edit. First, identify the freight job and the intended goods scope. Second, preserve the original declared entry. Third, add the observed entry as a separate evidence item. Fourth, test the comparison basis: same goods scope, understandable units, and adequate source and time context. Fifth, record the outcome and name one verification owner if anything remains unresolved.

When the basis is confirmed, record that a comparison is permitted for desk review. State the difference as an unresolved discrepancy unless an authorised internal decision later explains it. Do not overwrite the declared entry, amend the observed source, or label either value as final merely because one arrived later. When the basis is not confirmed, record not comparable on current evidence and state what is missing.

A held update is a valid result. It means the record can truthfully show that two different observations exist without claiming they measure the same thing. The next action may be to obtain scope confirmation, a clearer source record, or a clarification from the named evidence owner. This guide does not direct vehicle movement or any physical action.

1. Identify one job reference and the exact goods scope under review.
2. Record the declaration unchanged with value, unit, source and received context.
3. Add the observed reading separately with unit, document reference and documented time.
4. Confirm or reject the same-basis comparison using only recorded evidence.
5. Hold or route the discrepancy to one named verification owner.

4. Suggested internal comparison worksheet

The following is an adaptable internal worksheet proposal. It is intentionally small: it makes the comparison boundary visible without turning the desk record into a weight calculation sheet. Teams can add their own identifiers, provided additions do not blur declared evidence and observed evidence.

A complete row should show the job reference; goods-scope description; declared value, unit and source; observed value, unit, document or record reference and time; comparison-basis status; discrepancy status; named verification owner; and the next review action. Record unknown rather than filling a gap with an assumption. Keeping an entry does not establish liability, a commercial amount, or the physical condition of goods.

5. Decision table for the current evidence

Use this table as a desk prompt. It is suggested internal practice only. Its purpose is to choose a record outcome, not to determine a weight or operational permission.

1. Table below: five evidence patterns and the corresponding record decision.

6. Fictional example / 虚构示例

Fictional example / 虚构示例: Job FIC-204 concerns one described palletised consignment from Harbour Parts to North Depot. A consignor email declares 18 tonnes for that named consignment. Later, a signed yard record for the same named consignment records an observed reading of 19 tonnes and includes a documented observation time. The desk clerk enters both values in separate blocks and links the email and yard record references.

The clerk confirms that the job reference, named consignor, destination and described palletised consignment match. The units are both stated as tonnes. The comparison-basis field is therefore marked confirmed for desk comparison, while the discrepancy field is marked open. The clerk does not replace 18 with 19, does not calculate a charge, and does not infer why the readings differ. The update is held and assigned to the freight records coordinator for source verification.

The coordinator later records an evidence-backed internal desk decision: retain both original observations; retain the same-basis discrepancy as reviewed; and attach a clarification that identifies which document each value belongs to. This closes the desk review only. It does not make a claim about physical measurement, loading, movement, liability, or any wider operational decision.

7. Close the evidence review, not unrelated work

Before closing this narrow review, check that the original declaration remains readable, the observed reading remains readable, and the comparison outcome says either confirmed or not confirmed. Check that an open question has one owner and a concrete next evidence request. If a later correction is needed, add a dated correction or decision entry rather than rewriting either original observation.

This is distinct from an odometer-distance record, a partial-pickup piece reconciliation, delivery-proof review, document-reference correction, load transfer, and dispatch readiness. Those questions may share a job reference but require different evidence boundaries. Reusing the existing AI conceptual fleet-yard illustration is appropriate only as illustrative context: it is not a photograph of this fictional job, an observed reading, or proof of any operational event.

Source: GOV.UK: writing user stories