Web-forensics use case
Acquire logistics, shipping and fleet portal evidence
Eviquire can preserve authorized logistics and fleet information presented through a browser: consignment identity, tracking events, dispatch and route context, vehicle or driver presentation, delivery confirmation, supporting documents and generated exports. Portal evidence should be distinguished from direct telematics, vehicle, warehouse, scanner, carrier backend or geospatial-system acquisition.
What this use case means
Eviquire can preserve authorized logistics and fleet information presented through a browser: consignment identity, tracking events, dispatch and route context, vehicle or driver presentation, delivery confirmation, supporting documents and generated exports. Portal evidence should be distinguished from direct telematics, vehicle, warehouse, scanner, carrier backend or geospatial-system acquisition.
Tracking portals aggregate events from multiple systems, normalize locations and timezones, and update estimated or actual milestones after the event. Map displays and filtered tables can omit detail. A reliable acquisition connects each displayed event to the consignment, vehicle, route, source system presentation, selected interval and timezone.
Common situations
When this workflow is useful
- Delivery, cargo, route, accident, employment, fraud, theft or service disputes
- Preserving tracking history before portal retention or correction
- Documenting dispatch, proof of delivery and related files available to an authorized account
Recommended process
A documented acquisition workflow
- Identify the movement
Define consignments, orders, vehicles, drivers, routes, dates, sites and relevant event types.
- Record account and time context
Preserve provider, role, tenant, filters, map layer, locale and timezone.
- Acquire the chronology
Navigate from shipment or fleet overview to event history, route, stops, status, exceptions and proof of delivery.
- Preserve documents and reports
Download authorized manifests, delivery documents, photos, statements and exports in supplied formats.
- Correlate critical events
Hash files and compare disputed time or location with telematics, scanner, warehouse, carrier or witness records.
Technical guidance
Conditions that affect logistics evidence
Confirm these points during a short pre-acquisition validation on the authorized workstation.
Time and event semantics
Created, scanned, transmitted, estimated and displayed times can represent different events and zones.
- Record labels and timezone.
- Avoid treating estimates as observations.
- Preserve later corrections separately.
Maps and location
Rendered maps may generalize, snap or interpolate locations and can change with zoom or provider data.
- Capture coordinates where shown.
- Record filters and zoom.
- Use source telemetry for precise conclusions.
Personal and commercial data
Routes and delivery records can reveal homes, workers, customers and valuable cargo.
- Minimize collection.
- Protect originals.
- Redact disclosure copies appropriately.
Reviewable output
What the evidence package should explain
Movement context
Provider, consignment, order, vehicle, route, role, filters and timezone.
Event chronology
Status, scans, stops, exceptions, route and proof-of-delivery presentation.
Supporting files
Authorized manifests, images, documents and reports preserved with hashes.
Review record
Session video, acquisition time, limitations, correlation and custody history.
The exact artifacts depend on the source, plan, configuration, authority, and investigation. A report should identify what was and was not collected.
Professional considerations
Authority, proportionality, and limitations
- Location and worker data require proportionate scope and access controls.
- Portal maps and status labels may be derived rather than raw sensor evidence.
- Keep original exported records unchanged and document later mapping or analytical derivatives.
Important: Eviquire supports a documented technical process. It does not establish identity, truth, culpability, infringement, or admissibility, and it does not replace legal advice or a validated organizational procedure.
Standards and primary guidance
Online evidence procedures should be validated for the organization and matter. Useful starting points include SWGDE guidance for acquiring online content, ISO/IEC 27037:2012, and NIST digital-evidence resources.
Frequently asked questions
Can Eviquire acquire vehicle telematics directly?
No. It preserves browser-presented portal evidence; direct device or API acquisition is separate.
Does a tracking event prove physical location?
Not necessarily. Understand the event source and corroborate important conclusions.
Should map settings be recorded?
Yes, including filters, time range, layer and zoom.
Can delivery documents be downloaded?
Yes when authorized, preserving the supplied originals and hashes.
Why can portal times differ?
Events may use device, site, account or normalized timezones and may be transmitted later.
Who uses this workflow?
Relevant professional roles
This acquisition workflow is commonly relevant to these teams. The appropriate authority, scope, procedure, and review requirements still depend on the matter.
Forensic experts
Acquire online evidence with technical context, integrity verification, custody records, and reporting.
See role-specific guidance →
Law enforcement
Preserve volatile online evidence for authorized criminal and intelligence investigations.
See role-specific guidance →
Law firms
Preserve websites and online content for litigation, disclosure, legal holds, and expert review.
See role-specific guidance →In-house legal teams
Preserve early evidence for disputes, compliance, legal holds, and outside-counsel review.
See role-specific guidance →