Retrospective coverage of the week ending May 21, 2026. This article was prepared later and is first published now. Sources were rechecked October 1, 2026. Memphis Security Insider is independent and unaffiliated with the Memphis Police Department, U.S. Customs and Border Protection, or the National Institute of Standards and Technology. This public-source analysis is not legal or forensic advice.
One police bulletin. Four missing times.
Memphis police said officers responded at 10:27 a.m. on May 14 to a reported theft from a semi-trailer at 4406 Malone Road. According to the agency’s May 20 bulletin, officers were advised that unknown people had entered a commercial trailer and taken several window-mounted air-conditioning units. The public account identifies what was reported, where officers responded and when that response occurred. MPD semi-trailer theft bulletin
It does not identify the last time the trailer was verified as sealed, the last confirmed inventory count, the first observed shortage or the time shown on any available camera system. It does not establish who committed an offense, how entry occurred, whether the report led to charges or whether any business procedure failed.
That boundary matters. A warehouse manager cannot extract an explanation from a short agency notice. A manager can make the underlying records easier to compare.
The useful question is narrow: can the facility produce a defensible loss window without overwriting what each record actually says?
Build the window before building a theory
For this review, a “loss window” means the interval between the last documented point when the load was verified and the first documented point when a discrepancy was found. That is our proposed working definition, not a finding in the MPD report.
Start with two columns: verified time and source. A seal check at 6:12 p.m. belongs beside the seal log or photograph that supports it. A shortage noticed at 8:05 a.m. belongs beside the physical count, scan report or signed receiving record that supports it. If a time comes only from a person’s recollection, label it as a recollection. Do not quietly promote it to a system timestamp.
Keep unknowns visible. The public bulletin’s 10:27 a.m. response time is not automatically the discovery time, the call time or the time of the reported entry. Treating those moments as interchangeable can shrink or shift the window before anyone has reviewed the business records.
The first pass might look like this:
| Record | Time or identifier to capture | Question it can help answer | Limit |
|---|---|---|---|
| Seal log and shipping document | Seal number, issuer, check time, replacement entry | Was the recorded seal consistent at each documented handoff? | A matching or mismatched number does not by itself establish when or how a loss occurred. |
| Inventory and receiving record | Last verified quantity, first verified shortage, adjustment time | When did the documented quantity change? | A software adjustment time may differ from the time of a physical count. |
| Gate and visitor record | Credential, vehicle identifier, entry and exit times | Which recorded movements overlap the loss window? | A missing entry can reflect a record gap or system outage; it is not proof that no movement occurred. |
| Dispatch or trailer tracking | Trailer identifier, stops, arrival, departure, exception | Where does the documented movement sequence begin and end? | Tractor and trailer records may be separate, and a dispatch time is not necessarily a gate time. |
| Video system | Camera, coverage area, displayed time, export time, clock offset | Which recorded views cover a relevant place and period? | The displayed clock may not match a trusted external time source. |
This table is an editorial worksheet. It is not an evidence-collection order. Follow applicable legal process, company policy, insurer requirements and advice from qualified counsel or forensic personnel when those apply.
Seal, dispatch and camera records need one handoff
U.S. Customs and Border Protection’s Customs Trade Partnership Against Terrorism provides a useful comparison point, with an important limit. CTPAT is a voluntary program for eligible supply-chain companies. Its highway-carrier minimum security criteria concern participating carriers and international supply chains; they are not a universal rule for every Memphis warehouse. CBP CTPAT overview
Within that framework, the recordkeeping sequence is concrete. The highway-carrier criteria call for written seal procedures, a seal log that tracks receipt and issuance, verification of a seal number against shipping documents and documentation when a seal is altered or does not match. They also recommend retaining electronic dispatch logs long enough for audits and investigations, and they require participating carriers to compare tracking logs with time-indicative documents during management reviews. CBP highway-carrier criteria, sections 5 and 6
The point for a manager outside that program is not to copy a federal checklist and call the site compliant. It is to notice the handoffs.
Who records the seal number? Who records a replacement? Can a supervisor connect the dispatch entry to the trailer identifier and receiving record without guessing? If the security desk uses one naming convention and the warehouse system uses another, write down the cross-reference before an incident makes it urgent.
One trailer may appear under a trailer number, shipment number, purchase order, seal number and camera location. Capture each identifier once, then link it in a working chronology. Changing old entries to make the systems look uniform destroys the distinction a reviewer needs to see.
Put every clock on the page
Video can create false precision when the displayed time is accepted without checking it.
NIST’s Revision 1 recommendation for CCTV video export explains the problem in technical terms. It defines a system clock offset by comparing the recorder’s time with a reliable external reference at the time of export. NIST recommends taking those two observations as close to simultaneously as possible because the offset can support a corrected video start time. The report was prepared with the FBI and the CCTV/DVR community for law-enforcement video exchange. NISTIR 8161 Revision 1, section 3.4
For a facility, the immediate task is simpler. Record the camera or recorder name, its displayed time, the external reference time, the time zone and who made the observation. Do that before anyone changes the recorder clock. Ask the investigator or trained system operator how the export should proceed.
Then keep both values. Do not replace the original display time in a worksheet with a silently “corrected” time. Add a separate adjusted-time column and show the offset used. The same discipline can help when comparing gate, access-control, warehouse and dispatch logs, although NISTIR 8161 addresses CCTV export specifically. Extending the method to those other records is our suggested reconciliation practice.
Clock disagreement is not evidence of wrongdoing. A device can drift, a time zone can be configured incorrectly or one system can record an event at a different stage of the transaction. The record should show the difference before anyone tries to explain it.
Preserve the file and its history
Finding the right video is only half the job. A clip can be copied, renamed, compressed, messaged and copied again before a manager realizes nobody recorded where the first export came from.
NISTIR 8387 says digital files are easy to change and identifies integrity as a central preservation concern. Its guidance calls for documenting the original source and how a file was created or transferred. It describes hashing as a best practice, says early copies and transfers should be documented when a hash is not made, and advises secure storage with authentication, access controls and logging. For surveillance video, it says law enforcement should collect both the native proprietary format and an open format when possible. NIST digital-evidence preservation guidance
This is guidance for evidence professionals, not an invitation for an untrained manager to conduct a forensic examination. A business can still prepare for a clean handoff:
- Identify the system and relevant camera without changing settings.
- Note the retention or overwrite risk shown by the system or vendor documentation.
- Limit access to people authorized by the business’s incident procedure.
- Record who exported or received a file, when, from which system and by what method.
- Preserve the native file and required player when trained personnel say the system permits it; make a viewing copy separately.
- Keep the original export out of routine messaging and editing tools.
If an authorized investigator specifies a particular export or transfer method, route the request through the facility’s designated contact and any legal process, company policy or counsel review that applies. Document what was requested, what the organization released, when and to whom. If an employee has already sent a clip by email or chat, document that fact. Do not hide an imperfect first step by recreating the history.
Give investigators a chronology, not a conclusion
A useful handoff can fit on one page. List the MPD identifier displayed on the public bulletin, 2605024668ME, along with the facility contact and each relevant business identifier. Then list events in time order.
Each row should say whether the entry is a system record, physical observation, employee report or outside agency time. Include the time zone. Name the original record and its current custodian. Put disputed or unverified entries in a separate column rather than deleting them.
End with open questions. Examples: Was the seal number photographed at the previous handoff? Does the gate log use the tractor plate while dispatch uses the trailer number? Was the first shortage identified by a scan exception or a physical count? Which camera views the trailer doors, and what is that recorder’s observed clock offset?
Those questions do not accuse a driver, guard, employee, vendor or customer. They expose the gaps a qualified investigator may need to resolve.
The May bulletin cannot support claims about organized cargo theft, route knowledge, insider involvement or a Memphis trend. It cannot establish guilt or business fault. What it can do is show why a response time alone is not a loss window.
Seal, inventory, gate, dispatch and camera records each tell a partial story. A manager’s job after a report is to preserve those parts, label their limits and make the handoff traceable. Explanation comes later, if the evidence supports one.