PRD Template for Logistics Products

Example: "Last-mile delivery costs average $8.40 per package, representing 53% of total shipping cost. Route planning is done manually by dispatchers using spreadsheets, resulting in an average of 22% excess mileage per route compared to optimized paths. Drivers make an average of 3.2 failed delivery attempts per 100 stops due to inaccurate address data and missing delivery instructions. Each failed attempt costs $4.20 in fuel, time, and re-routing."

Example: "Primary: Reduce average last-mile delivery cost from $8.40 to $6.50 per package within 90 days of deployment (23% reduction). Secondary: Reduce failed first-attempt delivery rate from 3.2% to under 1.5%. Efficiency: Increase average stops per route from 42 to 55 without extending driver hours. Guardrail: On-time delivery rate must remain above 95%. Compliance: All route plans must respect DOT hours-of-service regulations."

Example: "As a dispatcher, I want the system to generate optimized routes for 15 drivers within 2 minutes of the daily cutoff so that drivers can start their routes by 7:00 AM. Acceptance criteria: routes respect vehicle capacity limits, driver hours-of-service constraints, and customer delivery windows; dispatcher can manually override any stop assignment; route changes after driver departure are pushed in real-time via mobile app. As a driver, I want turn-by-turn navigation that accounts for truck height restrictions so that I do not encounter low bridges on my route."

Example: "FR-1: Route optimization engine must generate routes minimizing total drive time while respecting: vehicle capacity (weight and volume), delivery time windows, driver hours-of-service (11-hour driving limit per DOT), and road restrictions (height, weight, hazmat). FR-2: Real-time GPS tracking with position updates every 30 seconds, accurate to within 10 meters. FR-3: Proof-of-delivery capture: photo, signature, and GPS coordinates with timestamp. FR-4: Dynamic re-routing must recalculate remaining stops within 15 seconds when a stop is added, removed, or skipped."

Example: "NFR-1: Route optimization for 50 stops must complete in under 30 seconds; for 200 stops in under 2 minutes. NFR-2: System must handle 10,000 concurrent GPS tracking streams with under 5-second display latency. NFR-3: Mobile app must function offline for up to 4 hours, syncing all delivery data when connectivity resumes. NFR-4: 99.9% uptime for dispatch and tracking services; 99.5% for reporting and analytics. NFR-5: Data retention: delivery records and GPS tracks retained for 7 years for regulatory compliance."

Example: "Efficiency: Average stops per driver per day. Baseline: 42. Target: 55. Cost: Cost per delivery. Baseline: $8.40. Target: $6.50. Service: On-time delivery rate. Baseline: 92%. Target: 96%. Driver: Failed first-attempt rate. Baseline: 3.2%. Target: under 1.5%. Adoption: Percentage of dispatchers using automated route optimization vs manual planning. Target: 90% within 60 days."

Example: "Phase 1 (Weeks 1-4): Route optimization engine with static constraints. Milestone: Optimized routes outperform manual routes on historical data. Phase 2 (Weeks 5-8): Real-time tracking and dynamic re-routing. Milestone: GPS tracking live for 10 test vehicles. Phase 3 (Weeks 9-10): Proof-of-delivery and mobile app. Milestone: Driver app tested in field conditions for 1 week. Phase 4 (Weeks 11-14): Pilot with one depot (25 drivers). Milestone: Cost per delivery reduction validated. Phase 5 (Weeks 15-20): Rollout to remaining depots."

Example: "Risk: Route optimizer produces routes that violate truck height or weight restrictions, causing driver safety incidents. Likelihood: Medium. Impact: Critical. Mitigation: Integrate road restriction database (HERE or TomTom); require dispatcher review for first 30 days; implement driver feedback mechanism for unreported restrictions. Risk: Driver adoption drops below target because app is too slow or complex to use during deliveries. Likelihood: Medium. Impact: High. Mitigation: Field-test with 5 drivers during design phase; target 3-tap maximum for any delivery action; offline mode for areas with poor connectivity."

Example: "Integration 1: WMS (warehouse management system) — receive pick/pack completion events and package dimensions/weight. Sync: real-time via webhook. Integration 2: Fleet management (Samsara/Geotab) — receive vehicle telematics, fuel level, and maintenance alerts. Sync: 30-second polling. Integration 3: Mapping (Google Maps Platform or HERE) — geocoding, routing, traffic data, road restrictions. SLA: 99.9%. Integration 4: ERP (SAP/NetSuite) — order data inbound, delivery confirmation outbound. Sync: batch every 15 minutes."

Example: "Q1: Should route optimization prioritize minimizing total drive time or minimizing total distance? They produce different routes — time-optimized avoids traffic but may add miles. Decision owner: Operations VP. Needed by: Week 2. Q2: Do we require company-issued GPS devices or rely on driver smartphones? Cost vs accuracy tradeoff. Decision owner: Fleet manager. Needed by: Week 3. Q3: Should proof-of-delivery photos be mandatory for all deliveries or only for high-value packages? Driver friction concern. Decision owner: Product. Needed by: Week 4."