MDMoveDefense

See it before you sign up

This is the packet

When a delivery gets disputed, this is what a MoveDefense driver sends back: the day's record — stops, times, device GPS, notes, photos, and mileage — assembled into one PDF and sealed with an integrity code. Below is a complete packet filled with example data, exactly as the app builds it.

Save this packet as PDF Open MoveDefense
MoveDefense
DISPUTE PACKET
MD-20260708-S4-169D
GEN Jul 8, 5:02 PM
SAMPLE · EXAMPLE DATA
Driver Dispute Packet
Driver Marcus Riveradelivery / gig modeTuesday, July 8, 2026 · Maple Ridge Apartments
ToPlatform support / account review team
FromMarcus Rivera · independent driver
ReDelivery record dispute · Maple Ridge Apartments · Tuesday, July 8, 2026 · Order / case #4821-D
DateJuly 8, 2026

What is being disputed

The order at this stop was marked "not delivered" by the customer. The record below shows the delivery was completed at the address at 2:41 PM, with photos of the package at the door.

Resolution requested

Remove the not-delivered violation from my account record and release the withheld pay for this order.

Summary of record

  1. Arrived at Maple Ridge Apartments, 2318 Maple Ridge Dr NE, Grand Rapids, MI at 2:38 PM EDT. Device GPS 42.98841, -85.58722.
  2. Stop note recorded at the stop: "Gate code failed. Customer confirmed by text: leave at door of building 3."
  3. 2 photo records were captured at the stop at 2:41 PM EDT (Exhibits A and B).
  4. Departed at 2:43 PM EDT after 5m on site.
  5. This was stop 4 of 7 logged that day.

Event timeline · Tuesday, July 8, 2026 · times in EDT

2:38 PM
Arrived · Stop 4
Maple Ridge Apartments · 2318 Maple Ridge Dr NE, Grand Rapids, MIDevice GPS 42.98841, -85.58722
Stop note · Stop 4
Gate code failed. Customer confirmed by text: leave at door of building 3.
2:41 PM
Photo captured
Exhibit A
2:41 PM
Photo captured
Exhibit B
2:43 PM
Departed · Stop 4
Time on site 5m

Course of work

This delivery was stop 4 of 7 logged on Tuesday, July 8, 2026. First arrival of the day 9:12 AM EDT; last recorded activity 4:48 PM EDT; total day mileage 68 miles. The full day's log is available on request. This packet is drawn from the driver's regular log: 214 stops recorded across 38 days since May 31, 2026.

Exhibits · 2 image records

3B
EXHIBIT A · Stop photo · Stop 4 · Maple Ridge Apartments
Tuesday, July 8, 2026 · 2:41 PM EDT
Sample illustration — a real packet shows the driver's photo as captured
BUILDING 3
EXHIBIT B · Stop photo · Stop 4 · Maple Ridge Apartments
Tuesday, July 8, 2026 · 2:41 PM EDT
Sample illustration — a real packet shows the driver's photo as captured

Records in this packet were captured with the MoveDefense driver app at or near the time of the events shown, by the driver named above, in the ordinary course of that driver's work; they were not reconstructed after the fact. Times are device-recorded local times (America/Detroit). Coordinates marked "Device GPS" were reported by the device at capture. Stop and fuel photo exhibits are presented as captured.

PACKET MD-20260708-S4-169D
GENERATED Jul 8, 2026, 5:02 PM · America/Detroit
RECORDS INTEGRITY CODE SHA-256 169d407d084896c9796515bce1b0b882d7971912b9c89c4573b61f1d1a67c189
The integrity code is the SHA-256 digest of this packet's record data, statement, and attached images. Any change to them produces a different code.
PREPARED WITH MoveDefense · movedefense.com
PRODUCT OF BIBBS TECHNOLOGY LLC

Declaration

I, Marcus Rivera, am the driver identified in this packet and have personal knowledge of the records it contains. These records were made at or near the time of the events shown, in the ordinary course of my regularly conducted driving and delivery work, and keeping such records was a regular practice of that work.

I declare under penalty of perjury that the foregoing, including the records and exhibits in this packet, is true and correct.

/s/ Marcus Rivera
Driver signature · electronically signed
July 8, 2026
Executed on
This packet presents driver-captured activity records assembled for a dispute. It is the driver's own record, not legal advice, and not an ELD or Hours-of-Service document. This copy is a sample: the driver, stops, times, coordinates, and images are example data.

How this packet gets made

Nothing here is written after the fact. The driver logs the day as it happens — arrive, photo, note, depart — and MoveDefense keeps each entry with its device time and GPS. When a dispute shows up, the driver picks the day and the stop, and the packet assembles itself from those records: the timeline, the exhibits, the day context, and a SHA-256 integrity code over the record data. One tap, one PDF.

No app can guarantee a dispute outcome. The point is narrower and more useful: when the question comes, the driver is not answering from memory, screenshots, and a camera roll.

Your packet builds itself

Log your stops with MoveDefense and this packet is sitting there on the day you need it. Read how drivers use it for delivery disputes and account reviews, or open MoveDefense and start your first day free — no email required.