Found and Recovered Inventory Form

Use it when an item is discovered in the wrong storage location, turns up after being written off, or needs a formal correction in inventory records. It is also useful when the physical count does not match the system location and you need a clear reconciliation trail. If the item was never in inventory or is a new receipt, use a receiving or intake form instead.

It is usually completed by warehouse staff, inventory control, operations, or the person who found the item. A supervisor or inventory reviewer should then confirm the corrected location and disposition. If your process requires it, the submitter can be different from the reviewer so the audit trail stays clear.

There is no fixed cadence because it is event-driven, not scheduled. Teams typically use it whenever a discrepancy is found during cycle counts, put-away checks, returns processing, or cleanup of stale write-offs. If the same issue keeps recurring, that is a signal to review location labeling or inventory controls.

Capture the original expected location, the location where the item was actually found, the corrected location that should be recorded, and the reason for the mismatch. That combination gives you enough detail to reconcile the inventory record without over-collecting unnecessary information. Keep the wording specific so the reviewer can understand whether this was a put-away error, a mis-pick, or a recovery from a prior adjustment.

The reviewer checks the supporting attachment, confirms the item details and location correction, and approves or rejects the entry. After approval, the inventory record can be updated and the audit trail preserved for future counts or investigations. If the disposition is not clear, the form should be held until the item is assigned a final status.

The most common issues are vague location names, missing quantity units, and skipping the reason for the mismatch. Another frequent problem is selecting a disposition before the item condition has been reviewed. Clear field validation and a required attachment help reduce back-and-forth.

Yes. You can add conditional logic for item category, storage zone, or recovery method so users only see the fields that apply. Many teams also customize the disposition options, reviewer role, and attachment requirements based on how strict their reconciliation process needs to be.

It can be connected to inventory, ERP, or ticketing workflows so approved corrections trigger downstream updates. The supporting attachment and reviewer comments are especially useful when you need an audit trail or want to route exceptions for follow-up. If you integrate it, make sure the field mapping preserves item identifiers and location codes exactly.