Inventory Shrink Root-Cause Investigation Form

Use it after a cycle count, wall-to-wall count, or spot check shows a variance between system on-hand and physical count. It is meant for shrink events that need a documented root-cause review, not for routine receiving or replenishment tasks. If the discrepancy is minor and clearly explained by a posting delay, you may not need the full investigation path. If the cause is unclear, this form creates a consistent record for follow-up.

Usually the store manager, inventory control lead, warehouse supervisor, or another designated operations owner completes it. The person filling it out should be able to review transactions, inspect the location, and assign corrective actions. If theft, fraud, or safety issues are suspected, the form should be escalated to the appropriate manager or security contact. The audit trail section helps show who reviewed and approved the outcome.

Yes, the submission notice includes an anonymous_submission option for cases where the reporter should not be identified. That is useful for theft concerns, policy violations, or sensitive internal issues. If contact details are collected, the form should clearly explain what happens after submission and who will see the information. Keep PII collection limited to what is needed for the investigation.

The form is designed to separate external theft, internal theft, administrative error, vendor discrepancy, damage/spoilage, and unknown causes. That makes it easier to route the issue to the right follow-up action instead of treating every shrink event the same. The cause-specific follow-up section changes the questions based on the selected category. This is where conditional logic and progressive disclosure matter most.

Complete one whenever a variance exceeds your review threshold or when the discrepancy cannot be explained during the count. Many teams use it after every significant cycle count exception and for recurring problem SKUs. The form can also support periodic trend reviews if you want to compare causes across locations or time periods. The right cadence depends on your inventory risk and count program.

Common mistakes include skipping the recount, leaving the variance explanation too vague, and selecting a root cause without evidence. Another frequent issue is collecting too many fields up front instead of using conditional logic to show only the relevant follow-up questions. Teams also sometimes forget to assign an owner and due date for corrective actions. A clear submit-confirmation line helps avoid confusion about next steps.

Yes, it can be linked to inventory management, ERP, ticketing, or audit trail systems if your workflow supports integrations. Typical connections include pulling item SKU details, storing the investigation record, and creating a follow-up task for the owner. If you integrate it, keep field names consistent with your inventory master data. That reduces duplicate entry and makes review easier.

Customize the location field, root-cause categories, and corrective action options to match the site type, such as retail store, warehouse, or distribution center. You can also adjust the evidence fields if some sites use CCTV while others rely more on transaction review or receiving logs. Keep required fields limited to the minimum necessary so the form stays usable during a busy shift. If a site has special controls, add them through conditional logic rather than making every field visible.