Proof layer tip · 2026-10-15

Why field proof exists: disputes small vendors actually lose

Nightmare stories from the yard, plus real court links with plain-language outcomes. Documentation tools only, not legal advice.

Yard tip · 8 min read

Save time and money on this job

  • Time: Job-shaped steps beat scrolling a camera roll for the right shot.
  • Money: $25 wallet vs $79/mo per seat · pay per stop you actually run.
  • Habit: One hub, nineteen lane badges · drivers keep pride in the yard brand.

Nightmare avoided

The month-margin eraser

What goes wrong: You finish twenty honest jobs. Job twenty-one says you cracked the driveway, never serviced the unit, or never delivered the box. Office digs through texts. The driver remembers the street, not the hour.

What receipts change: A proof link in the customer inbox the same day shifts the fight from whether you were there to what the surface or unit looked like when you left.

Public record links

Court cases and forums (read the source)

Keeler v. Mike Fretz Homes (Okla. Civ. App. 2007)

Simplified outcome: Small claims court admitted site photos and a cleanup estimate over a hearsay objection. Builder argued no damage; the record turned on what the photos and estimates showed.

Yard lesson: Photos plus repair numbers in one story beat we were never there.

Dinucci v. Lis (Ohio Ct. App. 2005)

Simplified outcome: Appeals court treated small claims as a lay forum: property condition photos are generally usable, with wide judicial discretion on evidence.

Yard lesson: You still need a clear narrative; admissibility is not automatic victory.

Margins on roll-off and porta routes are thin. One driveway fight, one no-show rumor, or one chargeback can erase a month. The pattern is almost always the same: no dated packet the customer received when the job finished.

Courts and small claims forums still accept smartphone photos, but judges ask when, where, and what changed. A camera roll dump without sequence loses to a short story with timestamps and a customer send.

The guides below pair nightmare scenarios with public cases and simplified outcomes. FieldDrop is built to make the vendor-side packet automatic: lane steps, server time, proof link and PDF when receipt core is live.

One wallet, nineteen lane badges · proof only, no fleet OS migration.