Organized Retail Crime Incident Log

Use it any time a theft or coordinated retail crime event involves planning, multiple suspects, repeat behavior, or a clear attempt to evade detection. It is also useful when the store needs a consistent record for internal review, insurance, or law enforcement follow-up. For a simple shoplifting note, a lighter incident form may be enough. If the event includes evidence, losses, or a police report number, this log is the better fit.

A store manager, loss prevention associate, shift lead, or another designated incident owner should complete it as soon as practical after the event. The person filling it out should record only what they observed or can verify from video, witnesses, or reports. If multiple people saw different parts of the incident, one person can compile the final entry while preserving source details. That helps keep the audit trail clear.

Use it for each qualifying incident, not as a weekly summary. A per-incident log makes it easier to compare patterns across locations, identify repeat suspects, and attach the right evidence. If your organization also tracks trends, you can roll these entries into a separate monthly review. The template is designed for event-level documentation first.

Keep the summary factual and short: what happened, where it happened, what was taken or attempted, and whether anyone was detained, recovered, or reported to police. Avoid speculation about motive or identity unless it is directly supported by evidence. The goal is to create a clean record that another reviewer can understand without needing the full narrative. Specificity matters more than length.

It creates a single place to capture video documentation references, witness details, and the law enforcement report number. That makes it easier to hand off the case, revisit the facts later, and connect the incident to store footage or external reports. If your team uses a case management system, the log can serve as the intake record that points to the source files. A clear reference field is better than burying evidence in free text.

Common mistakes include leaving the suspect description too vague, estimating loss without listing the items involved, and forgetting to note whether video exists. Another frequent issue is mixing confirmed facts with assumptions, which makes the record harder to trust. Stores also sometimes omit the police report number or witness names when they are available. This template is designed to reduce those gaps.

Yes. You can add fields for department, register lane, camera ID, security guard name, or local case number if those are useful in your workflow. Some retailers may also add conditional logic for recovery details, vehicle involvement, or whether a suspect was identified. Keep the form lean enough that associates can complete it quickly after the incident. Only collect fields you will actually use.

An ad hoc message is easy to send, but it is hard to search, compare, and audit later. This template standardizes the same facts every time, which improves consistency across stores and shifts. It also reduces the chance that key details like video references or report numbers get lost in a thread. For repeat incidents, structured logging is much easier to review than scattered notes.