Skip to main content

Every change to a document is on the record.

Who uploaded it, who approved it, who replaced it, and when. A DOT audit trail that starts the day you start.

In short

VPB writes every document change to an audit log: created, approved, rejected, replaced or deleted, with the person who did it and the timestamp. QR scans are recorded with the time they happened. The log starts the day you start using VPB. It records what happens from then on and does not reconstruct earlier history.

The problem

The question a binder can't answer.

Audits and insurers ask who had what and when. Binders don't answer that. Inboxes answer it badly, after hours of digging, and "the file says it was replaced, we think in March" is not an answer.

How it works

How VPB keeps a DOT audit trail.

Every document event, attributed

Created, approved, rejected, replaced, deleted. Actor and timestamp on each one.

Approvals on the record

With review turned on, nothing a driver uploads goes live until an admin approves it, and the approval or the rejection reason is logged.

Scans recorded

See when a code was scanned.

The detail that matters

The log is written by the database on the change itself, not by someone remembering to note it.

The limits

VPB records what happens from day one. It does not reconstruct history you never had, and your own retention obligations stay with you.

Put the binder down.

Every permit, every truck, every driver's phone. Current from day one.