When something goes wrong in a plant yard, the first hour decides how the investigation ends. If the evidence is a photograph taken at the moment, with the time it was actually taken and a record of who has touched it since, the facts are settled quickly. If it is somebody’s memory and a spreadsheet updated the next morning, the argument can run for weeks. This guide covers which events should trigger evidence capture, the deadlines that start at the incident, how to keep a defensible chain of custody, and how linked evidence shortens investigations. It is written for trucks, trailers and the yards and docks they move through. To see how photo-backed records work in FleetRabbit, book a short walkthrough with our team.
The clock starts at the incident: five deadlines evidence has to meet
Some deadlines are measured in hours. OSHA requires a work-related fatality to be reported within eight hours and an in-patient hospitalization, amputation or loss of an eye within 24. Others run for years, like the motor carrier accident register and the OSHA 300 log. The evidence you capture in the first hour has to support all of them.
Two details matter for fleets. OSHA’s reporting rule generally excludes motor vehicle accidents on a public street or highway outside a construction work zone, but an incident in a plant yard is not on a public road. And FMCSA’s accident register must include copies of any accident reports required by states or insurers, so the evidence behind those reports needs to be findable three years later.
Trigger-based capture: six events that should start an evidence record
Evidence is only useful if it exists before anyone knows it will be needed. Decide in advance which events start a record, and make the capture part of the normal step rather than an extra task for someone already dealing with the incident.
Most of these triggers are routine events, not incidents. That is the point. When the seal number and photographs are captured at every dispatch, the one trailer that arrives with a broken seal already has its evidence. Nobody has to remember to take a photo on the day it matters.
Chain of custody: six practices drawn from forensic imaging, applied to a yard
The Scientific Working Group on Digital Evidence (SWGDE) publishes best practices for keeping imagery trustworthy. They were written for forensic work, but the principles apply directly to a photograph of a damaged trailer or a seal at a dock door. The table turns them into six yard practices and shows how Oneflow handles each today.
| Practice | What it means in a yard | How Oneflow handles it |
|---|---|---|
| Preserve the original | The photo taken at the door stays as taken; any marked-up copy is separate | Captures are stored with the record they belong to; every number can be opened to the photo behind it |
| Start custody at capture | The record begins when the image is taken, not when someone uploads it | Each capture carries the time it was actually taken, even if it was queued offline |
| Protect the metadata | Time, place and device are part of the evidence | Kiosk punches keep the photo, the device and its distance from its anchor point |
| Log what was sent and received | Anything passed to another system should be provable later | The exact message sent to the ERP and the exact reply are kept and can be replayed |
| Verify copies with hash values | A copy can be checked against the original | Not stated in the product walkthrough; ask in the demo |
| Limit access | Only the right roles can open or change evidence | Team members are invited with a role that sets what each may see |
Two further habits make the chain hold under challenge. Never let a record be silently restated: in Oneflow, dock dwell is measured from the occupied and released pair and only the change counts, so re-saving a door cannot rewrite an arrival. And never let a guess into the record: a reading the system isn’t sure of is held with its reason and reaches nothing until a person confirms it, because a guess in a system of record is worse than a gap.
A shortage, start to finish: how linked evidence settles a dispute in hours
This is the clearest example of evidence doing its job, taken from how a stock transfer runs in Oneflow. Before linked evidence, a short delivery between two sites was usually settled by whoever was more senior. With it, the shortage is a document with photographs from both ends.
If the seal number changed between the two ends, that is filed separately too. The investigation starts with the evidence already attached, so the first question is “what happened between 11:00 and 14:20?” rather than “did anything happen at all?”
When a truck is involved: the evidence to gather in the first hour
Yard incidents involving a tractor, trailer or chassis need a few things that a shop-floor incident doesn’t. Photograph the vehicle’s position against fixed references such as the dock door number, the drop row marking or the lane line. Record the unit numbers of the tractor, trailer and chassis, the seal number if the trailer was loaded, and the odometer if the truck was moving. Note the restraint and dock light status if it happened at a door. Pull the gate read that shows when the vehicle entered, and any driver safety event from the truck’s own camera. Then check the truck’s recent inspections, because a defect reported on yesterday’s DVIR changes the root cause completely.
When two companies are involved, as when a visiting carrier’s trailer is damaged at your dock, agree early on who holds which evidence. The plant usually holds the gate, yard and dock records; the carrier holds its own telematics and dash camera footage. Ask the carrier to preserve its footage at the same time you preserve yours, because routine deletion schedules on either side can remove the one clip that settles the claim.
Investigation turnaround: where the time actually goes
OSHA’s incident investigation guide sets out four steps: preserve and document the scene, collect information, determine root causes, and implement corrective actions. In most yards the slowest step is the second one, because the information is spread across a guard’s notebook, a dock spreadsheet, a driver’s phone and the telematics portal. Linked evidence shortens it.
OSHA also recommends investigating near misses and focusing on programmes rather than individuals. Evidence makes both easier. A near miss with a photograph and a time is taken seriously, and an investigation built on records rather than accusations is one people will cooperate with next time.
Retention: keep the decision for years and routine captures for as long as they are needed
Not every capture needs to be kept for years, and keeping everything forever creates its own privacy and storage problems. Write a retention schedule by record type, and make sure anything attached to an incident is kept for as long as the longest rule that applies to it.
When a claim or lawsuit is likely, stop routine deletion for the records involved. Destroying evidence after a claim is foreseeable can be treated as spoliation, so the retention schedule needs a clear way to place a hold. This is general guidance, not legal advice; check your obligations with your counsel.
Where Oneflow fits today, stated plainly
Every number in the record opens to the photograph behind it
Defects drivers find are evidence too. A digital DVIR records the defect with a photo and a time, and the repair that follows stays on the same unit in fleet maintenance records, so the history of a truck or trailer is one record from first report to closed job.
