A retail fall may occur during a short period that is described by several independent systems. A receipt may identify a transaction, a shift schedule may identify who was assigned to work, a delivery log may place a vendor near the area, and an incident report may record when the event was reported. None of those records automatically shows who saw a condition, how long it existed, or why the fall occurred.

A store-activity timeline should identify what each record actually captures, whose activity it reflects, which clock it uses, and how closely it relates to the location and time of the fall.

Start with a precise event window and location

  • Store, entrance, department, aisle, register, restroom, walkway, parking area, or other specific zone, including direction of travel and nearby fixed reference points
  • Reported event time, first request for help, first employee response, incident-report time, emergency call, cleanup, warning placement, and later reopening kept as separate events
  • Time shown on a receipt, loyalty account, bank alert, mobile order, parking record, photograph, message, or device, with the source and displayed time preserved
  • A wider period before and after the fall that is defined by a reason, not selected merely because the record system can export it

Map each store system before combining the data

  • Staffing schedule, clock-in and clock-out, department assignment, break, task list, manager log, radio assignment, and any later correction
  • Point-of-sale transaction, self-checkout event, return, mobile order, loyalty or pickup entry, register identifier, and the person or account associated with it
  • Door counter, occupancy system, queue monitor, call button, sensor, access-control event, or other automated entry, including what the system measures and what it does not
  • Delivery appointment, vendor sign-in, stocking activity, service ticket, contractor visit, pallet or cart movement, and location within the store
  • Customer report, employee message, maintenance request, incident record, first-aid record, cleaning entry, photograph, and surveillance reference

Do not treat an assignment as an observation

A schedule can show that a person was assigned to a shift. A clock record can show that an account recorded an entry. A task list can show that work was planned or marked complete. Those records do not by themselves establish where the person was at every moment, what the person observed, or whether the entry describes the exact area. Preserve the underlying record, the system explanation, the person with knowledge, and any audit history.

Reconcile clocks without rewriting the source

  • System name, device or terminal, time zone, export date, displayed timestamp, underlying timestamp when available, and whether the time was automatic or manually entered
  • One shared event—such as the purchase, request for help, emergency call, or camera-visible action—used to evaluate any offset
  • Original time and any calculated adjustment stored in separate fields
  • Duplicate, missing, rounded, delayed, or corrected entries labeled rather than silently resolved

Use preservation requests and civil discovery for different purposes

A preservation request can identify potentially relevant records and ask a custodian not to discard them, but it does not by itself compel production or determine admissibility. In a filed civil action, North Carolina Rule of Civil Procedure 34 addresses requests for documents, electronically stored information, tangible things, and entry on land within its scope. Rule 45 addresses subpoenas to nonparties, production, objections, and protections. The correct process depends on who controls the record and the stage of the matter.

Keep business-record and authentication questions separate

North Carolina Rule of Evidence 803 includes a business-record provision with stated foundation and trustworthiness requirements. Rule 901 addresses evidence sufficient to support a finding that an item is what it is claimed to be. A logo, spreadsheet, screenshot, or employee signature does not answer every foundation, completeness, hearsay, relevance, notice, or responsibility question.

Build a source-linked chronology

  • Time as recorded, source system, event type, location, person or account, exact source location, and custodian
  • Whether the entry was automatic, manual, scheduled, completed, corrected, exported, summarized, or inferred
  • Record that agrees, conflicts, narrows the time, identifies another source, or remains unavailable
  • Open question and next record needed, without converting a gap into an accusation or a conclusion

The related guide to store inspection and cleaning records after a fall focuses on sweep systems, policies, inspections, work orders, and the condition itself. This page owns the separate task of reconstructing activity around the event from staffing, transaction, traffic, delivery, and access records.

Rosensteel Fleishman Car Accident & Injury Lawyers provides general information about working with a Charlotte slip-and-fall lawyer when store records are disputed. Record availability, legal significance, notice, causation, and responsibility depend on the complete facts and current law.

Sources