Skip to content

This is an internal working record, not an everyday instruction. It was written while the system was being rebuilt, for whoever maintains it. If you are here to do today's work, use the everyday documents instead: Procedures · Processes · Runbooks · The working day, step by step

CTC Final Loading Review — Current Source Addendum

  • Status: CURRENT SOURCE-RECONCILED OPERATOR ADDENDUM / FIELD EVIDENCE REQUIRED
  • Current maintenance successor: CURRENT_SOURCE_DOCUMENTATION_MAINTENANCE_2026-08-11.md
  • Parent Runbook: CTC_FINAL_LOADING_REVIEW_OPERATOR_RUNBOOK.md
  • Source delta: FINAL_LOADING_REVIEW_SOURCE_DELTA_2026-08-08.md
  • Current source baseline: qa/master@13991b627eb95b5b675a4eb05048d56f20538439
  • Evidence: RBR-FLR-001, RBR-FLR-002
  • Current Wiki: not independently read

This addendum controls the latest Shipper/CTC comparison and Edit Outbound procedure. The parent Runbook remains the normal Final Review procedure for Confirm, Reopen, Source, Leftover, and recovery.

1. Read The Four Measurements Separately

The current review displays:

Shipper
CTC Inbound
Loading Difference
CTC Outbound

Interpretation:

  • Shipper: external/reference quantity and weight.
  • CTC Inbound: current system inbound baseline; may show an identified initial fallback.
  • Loading Difference: CTC Outbound - CTC Inbound.
  • CTC Outbound: current final outbound quantity and weight.

Do not use Shipper variance as a substitute for Loading Difference.

Shipper mismatch
!= automatic workflow failure

The server-provided review state remains the workflow authority.

2. Shipper Comparison

The page may display:

Matches shipper
Comparison unavailable
Variance present

Before acting on a variance, verify:

  • Shipper values are present and belong to the same load;
  • CTC Inbound provenance/fallback is visible;
  • quantity and weight UOM are comparable;
  • the variance is not being confused with Loading Difference;
  • current Review state and outcome.

Do not edit outbound solely to make the Shipper values match unless the actual loading result is confirmed and the correction is operationally valid.

3. Avg/Bale

Avg/Bale is a Pending-review aid derived from Loading Difference.

Current display behavior:

  • quantity difference zero or weight difference zero: no normal average;
  • opposite signs: Inconsistent difference;
  • same non-zero sign: absolute weight difference / quantity difference;
  • average greater than 2,000 lb/bale: High avg. weight warning.

The warning currently indicates review attention. It does not by itself prove that Confirm is blocked.

When the average is unexpected:

  1. verify CTC Inbound baseline and fallback;
  2. verify CTC Outbound quantity/weight;
  3. verify the difference signs;
  4. check whether weight is optional for the current row;
  5. correct the owning values only through the approved command;
  6. reread the server state.

4. Edit Outbound — When To Use

Use Edit Outbound only when the recorded CTC Outbound result is wrong and the actual completed loading result is known.

Current eligibility:

review status = PENDING
operational status = TRANSLOADED or SPARE
review remains mutable

Do not use Edit Outbound to:

  • bypass Source/Leftover handling;
  • make a review appear Ready without actual evidence;
  • change a Confirmed review;
  • change Loader completion history;
  • change Inventory Lot/Ledger directly;
  • correct Shipper source data.

5. Edit Outbound Procedure

  1. Keep the intended Pending load selected.
  2. Review current CTC Inbound and current CTC Outbound.
  3. Select Edit Outbound.
  4. Enter the actual positive whole outbound quantity.
  5. Enter positive outbound weight when required.
  6. For a current weight-optional row, confirm the UI explicitly identifies that policy before omitting weight.
  7. Select Save Outbound once.
  8. Reread:
  9. current outbound quantity and weight;
  10. Loading Difference;
  11. Avg/Bale and warnings;
  12. server-provided Review state/outcome;
  13. Source/Leftover requirements;
  14. available next action.
  15. Confirm only after the corrected review is operationally valid.

6. Validation

Current quantity rules:

required
numeric
positive
whole number

Current normal weight rules:

required
numeric
positive

A current compatibility rule can make weight optional for a specific customer-name condition. Treat this as current behavior requiring policy migration, not as a general operator exception.

If the UI and server disagree about weight requirement, do not bypass the server. Record the exact row/customer/policy result and escalate.

7. Conflict / Stale Values

The command compares the values that were shown when editing began with the current database values.

A conflict means another action changed the review.

Procedure:

  1. refresh the selected review;
  2. compare current outbound values;
  3. determine whether the intended correction is still needed;
  4. re-enter the correction only from current values;
  5. do not use a generic editor to overwrite the conflict.

8. Save Response Missing

Do not select Save again immediately.

Refresh the selected Pending review.

Committed

Current outbound equals the submitted values and the review state is recalculated.

no retry

Not committed

Current outbound still equals the old values and no other change occurred.

controlled retry after revalidation

Conflict

Current outbound differs from both old and submitted values, or the review is no longer Pending.

stop and review concurrent change

9. Resulting State

Saving outbound values may change the derived state.

Examples:

ACTION REQUIRED -> READY
READY -> ACTION REQUIRED
WEIGHT REVIEW -> READY
LEFTOVER REQUIRED -> READY only after the difference and inventory evidence are valid

Do not assume Save means Ready. Read the returned server state.

10. Reason And Audit Limitation

Current source clears the existing weight-review reason when outbound values are updated.

Current source does not establish a dedicated immutable outbound-correction history containing old/new values and reason.

Therefore support escalation should capture:

  • old displayed quantity/weight;
  • submitted quantity/weight;
  • actor/time;
  • response/result;
  • resulting review state;
  • request/correlation ID when available.

Do not claim complete correction history from the current row alone.

11. Confirm / Reopen Interaction

Edit Outbound
= correct Pending CTC Outbound values

Confirm
= approve the current Final Loading Review result

Reopen
= return review status to Pending

Reopen does not reverse Source/Leftover ledger evidence or restore old outbound values.

After Reopen, reread all four measurements and current inventory evidence before another correction or Confirm.

12. Selected-Row Behavior

Current UI is expected to keep the affected Pending review selected after in-place actions and visually de-emphasize other rows.

If selection is lost:

  • use the load/reference identity to reopen the exact review;
  • do not continue on the first visible row;
  • confirm the row identity before any write.

13. Escalation Packet

environment/source SHA
tenant
operator/role
review/transload ID and references
Shipper quantity/weight
CTC Inbound value and fallback label
old CTC Outbound values
submitted values
Loading Difference
Avg/Bale/warning
review state before/after
weight-optional result
exact error or missing response
request/correlation ID
whether Save was repeated

14. Current Evidence State

Source display/edit contract: SOURCE-RECONCILED
Current target-role behavior: NOT_RUN
Current DB scenarios: NOT_RUN
Current Wiki: NOT_READ
Field acceptance: NO

This addendum is not a substitute for current role/browser/database evidence.

---

Source: docs/runbooks/CTC_FINAL_LOADING_REVIEW_CURRENT_SOURCE_ADDENDUM.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.