Transaction Video Review Preparation Checklist

Establish the question before searching video

When a point-of-sale transaction is disputed, the first task is to define the business question, not to search an entire shift for something suspicious. A transaction record may show a refund, void, price change, or time of sale, while camera footage may show only a limited view of surrounding activity. The two sources must be reconciled carefully. This guide helps authorized store managers and investigators organize a review without overinterpreting footage or exposing payment data. Follow employer policy, privacy rules, and any legal hold or evidence-preservation requirements.

Create a minimal event reference

Record the store, register ID, date, local time, transaction or case reference, requesting manager, and type of exception. Do not copy full card numbers, customer account credentials, or unnecessary personal information into a general incident note. Record what question is being answered, such as whether merchandise was present at the counter during a particular void. Assign an authorized reviewer and document the request. This reduces both the search burden and the risk that staff informally inspect unrelated customer footage simply because they have access.

Check clocks and time zones before selecting clips

Compare the displayed timestamp in the POS report with the recorder’s current time and the relevant local time zone. Note whether either system uses daylight saving adjustments or an uncorrected clock. Do not silently alter the original transaction time to make video align. Instead, preserve the reported time and record an observed offset, the method used to determine it, and the reviewer. If the discrepancy changes over time, involve the technical owner. Timestamp disagreement is common enough that a clear adjustment note can be more important than searching several extra cameras.

Map transaction locations to available camera views

Maintain a register-to-camera map with lane, camera name, field of view, and known blind spots. A wide overview can show movement near several registers but may not provide enough detail to identify a small object or validate a particular action. A narrower view might capture the counter yet exclude a customer’s hands at a different position. Record what each view can and cannot demonstrate. Do not assume that a megapixel specification guarantees readable receipt text or identifiable conduct. Test representative scenes and retain those limitations in the operating procedures.

Review enough context to avoid misleading conclusions

Examine a bounded period before, during, and after the event when the authorized scope permits it. Record visible actions separately from interpretation. A person reaching toward a counter does not, by itself, establish that a transaction was dishonest. Likewise, a POS exception may reflect training, workflow, or a technical issue. Compare the record and available footage for sequence, not presumed intent. If the evidence does not answer the question, state that clearly. Escalate allegations of misconduct through the organization’s established process rather than making accusations in the review worksheet.

Preserve relevant footage and its provenance

Check the system’s retention period before assuming a recording will remain available. Export only the relevant time range and viewpoints under approved permissions, and preserve the original file or native export when feasible. Log the reviewer, export time, camera IDs, event range, case reference, destination, and any subsequent transfer. Avoid editing or recompressing the only retained copy. Where a clip is shared for an authorized investigation, maintain a record of who received it and why. Follow any evidence preservation instructions from counsel or the responsible investigating authority.

Protect sensitive transactions and staff access

Limit POS reports and video search permissions to designated roles. Do not send raw clips through personal messaging accounts or keep copies on unmanaged devices. Ensure reports exclude unnecessary customer and payment information. Ask whether a proposed POS-to-video integration reveals more data than the investigation needs. The system administrator should review access after staff departures, role changes, or contractor work. A useful audit trail records access and export activity without publishing a public list of investigations or affected individuals.

Audit failures and improve the review process

After a completed case, ask whether the register-to-camera map was accurate, times aligned, the needed recording was retained, and staff understood the escalation process. Record camera obstructions, mislabeled inputs, offline periods, and missing transaction identifiers as separate service issues. Test the procedure with a benign example before relying on it during a loss investigation. For broader coverage planning within a retail environment, consult NERSA’s retail security systems guide. The point here is disciplined review and evidence handling, not a promotional equipment recommendation.

Transaction review worksheet

Store and register; case reference; reason for review; POS timestamp and timezone; recorder timestamp and offset; relevant camera IDs; review window; factual observations; unresolved questions; video export reference; approved recipients; retention or hold instruction; completed reviewer sign-off; and technical follow-ups. Preserve the original record so another authorized reviewer can reproduce the reasoning without relying on memory.

Test retrieval using a representative transaction; the historical retail account provides context. Continue with Recorded Video Retrieval Drill and Mr. Bills Poultry: Legacy Camera Project Notes.