1. Vehicle Inspection App
  2. Features
  3. Evidence and review
Feature · Evidence and review

Evidence and review

Keep supporting files, human decisions and recorded outcomes available for reconciliation.

OverviewReview Decisions
Vehicle Inspection App · Evidence and review

Review Decisions

Review decisions

New
Record numberSource tableSource recordRevisionDecisionDecided at
RD-17546ST-289SR-218660Approved20 Oct
RD-83115ST-696SR-284830Returned25 Oct
RD-64434ST-554SR-539440Escalated21 Oct
RD-68358ST-899SR-420810Approved27 Oct
RD-24307ST-691SR-774720Returned09 Oct
6 of 6 records
ST-289Review decisions · RD-17546
Approved
Source recordSR-218
Revision660
Decided at20 Oct
RationaleRTN-838
Example screen with sample data

What you can do

Explain what happened and who decided

Evidence Reviewer needs to connect an operating result to the record it describes. Operational receipts carry an event, source reference and recorded time, with an amount or quantity where relevant. Review decisions retain the deciding owner, rationale and revision. Attachments provide documents, photographs or signature evidence, identified by the related record and operating organization.

These records help the team investigate a case after a shift handoff. A recorded receipt starts a check; Verified indicates the review outcome. Failed and Corrected keep unresolved or amended results visible until the reviewer has enough evidence to verify them. Operations Overview brings exceptions together and provides linked-record detail for follow-up.

How the work is organized

  • Identify the source. Match each receipt and decision to the intended operating record. Use the source table where available and confirm the revision when a review relates to changing load details.
  • Keep the supporting file useful. Give a photograph or document a name the team can recognize. Check the related record before treating it as support for a repair, dispatch or delivery outcome.
  • Resolve the exception. Evidence Reviewer checks the result, records the appropriate receipt status and follows correction work through to verification. Operations Manager owns the load decision when the issue changes the authorized transport scope.

What to agree during setup

Agree the convention for source references and related-record values. A document with a similar filename can belong to another vehicle or trip, so the team needs a consistent way to confirm identity. Decide who can access operational evidence and who may update the review result for each organization.

For amounts and quantities, record enough event context for the reviewer to understand the meaning. Do not combine a receipt quantity with a financial amount in a shared total. Freight charges carry their own currency and status; confirm the accounting handoff separately before using them for financial reconciliation. Define who investigates a delivery dispute and what evidence resolves it.

Check the handoff on an actual case

A departure receipt is Recorded, but the linked assignment still appears Assigned while the load is Executed. Evidence Reviewer asks Dispatcher to compare the assignment, departure event and actual vehicle movement. The receipt becomes Failed while the discrepancy is investigated. Corrected identifies the resolved record before the reviewer verifies the final outcome.

Operations Manager separately inspects the original load decision and its revision. If the transport scope changed, record the new decision with its rationale rather than attaching the old approval to different work. Rehearse the case with a photograph from another vehicle: a useful filename does not establish that the attachment belongs to this inspection or load. Confirm the source reference before using it to close the review.

What your team sees

  • Receipt Review — Find recorded, failed and corrected outcomes awaiting reconciliation.
  • Review Decisions — Read the decision owner, source revision and rationale together.
  • Delivery Evidence — Identify confirmations that are captured, verified or disputed.

Follow the work through

Evidence to verification covers review and correction. Return to dispatch to delivery when the trip history needs attention. Use the data model to agree reference conventions before importing evidence.

What it keeps track of

Data model
Operation receipts
Recorded operational outcomes awaiting verification
Review decisions
Approval, rejection and escalation decisions on records
Record attachments
Documents, photos and signature evidence attached to records
Proof of delivery
Delivery confirmation captured at the stop
Loads
Planned and executed transport loads
Load assignments
Driver and vehicle assignment for a load
Tracking events
Position and milestone events reported against a load

Who uses it

Permissions
Evidence Reviewer
, Operations Manager, Dispatcher.
Evidence Reviewer
Reconciles outcomes; Operations Manager decides changes to load scope; Dispatcher supplies the trip context.

Set up Vehicle Inspection App your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started