Trip Package Report

Introduces the TMS Trip Package Report, a real-time operational traceability report that shows how packages are associated with trips across first-mile, middle-mile, last-mile, and hyperlocal movements.

Version: 1.0
Owner: TMS Product Team

Summary

This release introduces the TMS Trip Package Report, a detailed operational report designed to provide complete visibility into how packages are associated with trips across the transportation lifecycle.

The report acts as a single source of truth for tracking package-to-trip relationships across first-mile, middle-mile, last-mile, and hyperlocal movements.

Each row in the report represents one unique package per trip leg, ensuring granular traceability of how a package moves across different transportation stages.

The primary objective of this report is to improve operational transparency by clearly mapping:

• Which trip a package was assigned to
• Which driver and vehicle handled the package
• Where the package was picked up and dropped
• When each movement occurred
• Any exceptions or rejection details captured during execution

This enables Fleet Planning, Operations, Warehouse Teams, Customer Support, and Analytics teams to monitor execution performance, investigate discrepancies, validate movement history, and support data-driven decision-making.

How It Works

The TMS Trip Package Report consolidates data that already exists within trip execution records and package movement logs.

No additional setup or configuration is required for users who have access to TMS reports.

Workflow

1. As packages are assigned to trips and move through different legs—first-mile, middle-mile, last-mile, and hyperlocal—the system records each association.
2. Each package-trip-leg combination is captured as a separate row in the report.
3. Users can apply filters such as date range, trip type, or trip status to narrow results.
4. The report is available in the Reports section.
5. Users can export the report for offline analysis or audit purposes.
6. Because each movement leg is recorded independently, a single package may appear multiple times in the report if it has passed through multiple trips.

This structure ensures full lifecycle traceability without affecting operational workflows.

Technical Details

The TMS Trip Package Report is built on top of existing TMS trip execution and package data models and follows standard reporting architecture to ensure reliability and consistency.

Key Technical Highlights

• Report Type: Operational / Traceability Report
• Data Granularity: One row per Package × Trip Leg
• Data Coverage:
  • First-Mile Trips
  • Middle-Mile Trips
  • Last-Mile Trips
  • Hyperlocal Trips
• Core Data Included:
  • Package identifiers and status
  • Trip ID and trip type
  • Trip status
  • Pickup and drop location details
  • Driver details
  • Vehicle details
  • Trip start and end timestamps
  • Package delivery timestamp
  • Proof of Pickup / Proof of Delivery references
  • Rejection reason and driver comments, when applicable
  • Trip and handling tags
• Data Refresh: Real-time
• Access Control: Governed by user roles and permissions configured in Settings
• Availability: Accessible to all tenants with TMS enabled
• Output Format: On-screen table view with export capability

The report does not introduce any changes to trip creation, package assignment, or execution logic. It is a read-only analytical view intended for monitoring, traceability, investigation, and operational analytics.