The record should follow physical reality

A movement entry should correspond to a real, authorized physical event. A useful generic movement record includes the identity of what moved, source, destination, time, applicable count/quantity, and the responsible person or system.

The exact legal data fields vary by jurisdiction. This course therefore teaches the stable operational logic rather than pretending one software interface is universal.

Reconciliation is comparison, not forced agreement

Inventory reconciliation compares the physical state with the controlled record. If the system expects 48 plants and the physical count is 47, do not change either side simply to make the numbers agree. Recount and verify within procedure, preserve the discrepancy, and escalate if it cannot be resolved.

A discrepancy can indicate:

• counting error;
• delayed record entry;
• wrong identifier;
• unrecorded movement;
• loss/damage;
• software or synchronization issue;
• another process failure.

Scientific foundation — reconciliation is an error-detection process

Reconciliation works because two representations of reality are compared: the physical state and the recorded state. Agreement increases confidence but does not prove perfection; disagreement is information that something needs investigation.

A strong reconciliation process avoids immediately editing the record to make the mismatch disappear. Instead, it preserves the observation, repeats or verifies measurements where appropriate, checks recent movement events and identities, and records the resolution path. This turns discrepancies into process-improvement evidence instead of hidden errors.

Technician I gathers permitted facts; a supervisor/compliance/QA role may own the investigation or final correction.

Worked case

A room move is complete physically, but the digital platform is unavailable. The site has a controlled downtime procedure. Record the event using the approved contingency method so the true time and identity are preserved, then reconcile when the system returns. Do not wait until the end of the day and reconstruct multiple movements from memory if the procedure provides a better method.

Guided practice — movement packet

Complete two simulated movements:

1. a normal movement with matching identity/count;
2. a movement containing a physical-versus-record discrepancy.

For the second, document what you verified, what remained uncertain, what you did not change, and who was notified.

Retrieval check

1. What is the difference between reconciliation and changing a record until it matches expectations?
2. Which movement facts are stable across software platforms?
3. Why is a controlled downtime process better than retrospective memory entry?