3.10.2 - How to Keep an Evidence & Incident Log (Difficulty: Advanced | Path: Scale)

In the high-velocity world of e-commerce, memory is a liability. When you are shipping hundreds or thousands of orders a month, the specific details of a single damaged package or a lost shipment naturally fade within days. However, the financial and legal repercussions of those events often do not surface until weeks or even months later. A customer might file a chargeback 45 days after delivery, or a manufacturing defect might only reveal itself as a pattern after the fiftieth complaint. Relying on your inbox or your memory to reconstruct the facts at that late stage is a guaranteed way to lose revenue and damage your standing with payment processors.

This masterclass introduces the Evidence & Incident Log, a dedicated operational asset that serves as both your external memory and your legal shield. Unlike a standard support ticketing system, which focuses on communication and speed, an Incident Log is a forensic record. It is designed to capture the "who, what, where, when, and how" of every non-standard transaction—defects, returns, lost packages, and fraud attempts—in a structured format that stands up to scrutiny. It transforms ephemeral problems into permanent, auditable data points.

The strategic importance of this system cannot be overstated. For scaling brands, the Incident Log acts as the primary defense against "friendly fraud" and illegitimate chargebacks. When a bank reviews a dispute, they do not care about your narrative; they care about your evidence. A well-maintained log allows you to instantly retrieve the tracking number, the photo of the packed box, the customer's email admission, and the proof of delivery. This rapid retrieval capability turns a stressful dispute process into a routine administrative task where you have the upper hand.