A quick look at your routing day

• Walk me through a typical delivery day from order cut to driver sign-off, who does what and when?
• How many active routes and drivers run on an average weekday in your operation? Options: 1-10, 11-50, 51-200, 201-500, 501-2,000
• Which daily KPIs does your team actually review or report on each morning? Options: Miles driven, Stops completed, On-time deliveries, Driver hours, Fuel spend, Customer ETAs
• Tell me about a recent day when routing felt unusually difficult, what happened and what did it cost you that day?
• Who notices first when a route breaks and how is that issue typically escalated? Options: Dispatcher, Driver, Customer service, Operations manager, Telematics alert, Other

Where the minute-to-minute friction hides

• If you could eliminate the single task that steals the most dispatcher time each day, what would it be?
• How often do mid-day changes such as cancellations, rush orders, or major traffic events force your team to rebuild routes? Options: Multiple times per day, Daily, A few times per week, Weekly, Rarely
• When those mid-day changes happen, which downstream failures show up most often: missed pickups, late deliveries, overtime, or customer fallout? Options: Missed pickups, Late deliveries, Driver overtime, Customer complaints, Other
• How many hours per day does your lead dispatcher spend on manual route adjustments and firefighting? Options: > 4 hours, 2-4 hours, 1-2 hours, < 1 hour
• What improvement in dispatcher time or error rate would make you feel this friction was solved?

Hard gates and failure points

• Which technical or organizational failure would stop a rollout before it gets past pilot?
• Which internal approvals or external constraints typically delay projects like this at your company? Options: IT security review, Legal or compliance, Finance sign-off, Regional manager approval, Operational readiness, None
• How clean are your core data elements—addresses, customer time windows, and vehicle capacities—on a 1 to 5 scale? Options: 1 - fragmented, 2 - several gaps, 3 - usable with fixes, 4 - mostly clean, 5 - production quality
• What would be the immediate consequence if one of those data elements proved unreliable during the pilot?
• Who inside your organization can pause or stop a pilot once it is running? Options: Operations lead, IT/Security, Finance, Legal/Procurement, Regional director, Other

The alternatives you're weighing

• If you chose to keep your current routing approach, what measurable condition would have to hold true for you to stay with it?
• Which of the following options are you actively evaluating right now? Options: Another third-party routing vendor, Keep manual dispatch processes, Build an internal routing tool, TMS or ERP routing module, Telematics provider add-on, Consulting services
• How would your team measure the cost of staying with the incumbent versus switching—what specific metric would you compare? Options: Cost per stop, Miles per stop, On-time percentage, Driver labor hours, Fuel spend
• Has anyone proposed solving this problem internally? If so, what timeline and headcount were estimated?
• What single change to your current approach would make you keep it rather than move to a partner?

Integrations, data, and the reality of readiness

• Which integration must work from day one for a pilot to be meaningful, and why would its failure break the test?
• Which system categories must we connect to during onboarding? Options: Order management/OMS, Telematics provider, TMS/ERP, Driver scheduling or payroll, Customer notifications system, None/Unsure
• Who will be the technical owner for integrations and how many hours per week can they dedicate during onboarding? Options: Dedicated engineer >= 20 hrs/week, Shared IT resource ~10 hrs/week, Ops lead with technical support, No internal resources available, Unsure
• How will you provide daily stop data during the pilot: API push, scheduled CSV export, manual uploads, or another method? Options: API / automated feed, Scheduled CSV export, Manual file upload, Ad hoc messages, Unsure
• What security or vendor approvals must we complete before we can access production or staging data? Options: IT security questionnaire, Network access window, Vendor token issuance, Legal NDAs, None

Designing a pilot that proves value or fails fast

• If the pilot shows no measurable mile savings, what evidence would still make you continue evaluating the platform?
• Which pilot size and duration would be convincing to your finance team? Options: 30 days, limited route set (5-10 routes), 60 days, limited route set, 30 days, representative sample across depots, 60 days, representative sample
• Which metrics will be used to accept or reject the pilot? Options: Miles driven, Stops per route, On-time percentage, Driver overtime, Fuel spend, Customer complaints
• Who will sign pilot acceptance, and what single acceptance gate will they require?
• How are you planning to run parallel comparison—software routes compared to actual driven routes, dual dispatch, or shadow mode? Options: Software vs actuals (no driver change), Dispatcher uses manual, software runs in parallel, Test drivers follow software routes, Other
• What risk during the pilot would force you to stop the test immediately? Options: Driver safety incident, Major SLA breaches, Integration failure, Poor data quality, Other

Who holds the keys and their timeline

• Who has veto power on this initiative even if operations and finance are aligned?
• Which stakeholders must provide formal approval before production rollout? Options: Operations manager, Dispatch leads, IT/Security, Finance/CFO, Legal/Procurement, Regional directors
• What timeline does your leadership expect from pilot kickoff to fleet-wide go-live if the pilot is successful? Options: Less than 2 months, 2-3 months, 3-6 months, More than 6 months
• How does procurement prefer to structure a pilot and follow-on commercial agreement? Options: Pilot agreement then enterprise contract, Enterprise contract before pilot, PO-based engagement, Other
• If the pilot proves the expected savings, how quickly could you sign and allocate budget for rollout? Options: Within 2 weeks, Within 1 month, 1-3 months, Longer / depends on integrations

What success looks like and the first operational habits

• Which operational change must stick after go-live so the savings are sustained?
• Which review cadence would best surface issues and tuning opportunities after deployment? Options: Daily route review for 30 days, Weekly tuning, Monthly performance review, Quarterly business review
• Who will own ongoing constraint tuning and how many hours per month can they commit? Options: Dispatcher lead, Operations analyst, Shared IT/Ops, No dedicated owner
• Which training approach will get dispatchers and drivers up to speed fastest? Options: Live virtual training, Onsite training, Train-the-trainer, Self-paced modules, Combination
• What operational risk among drivers or dispatchers worries you most after go-live?

Final check: showstoppers and next steps

• What single answer here would make you stop the project immediately?
• Based on this conversation, are you ready to schedule a pilot kickoff within the next 30 days? Options: Yes, ready, Need internal approvals, Need a technical assessment first, Not ready
• Which artifacts would help your decision makers say yes: pilot plan, integration spec, ROI model, security questionnaire, or reference calls? Options: Pilot plan, Integration spec, ROI model, Security questionnaire, Reference calls
• Who should join the pilot kickoff from your side and what role should each person play? Options: Operations lead, Lead dispatcher, IT/integration owner, Finance representative, Regional manager
• Are there any other constraints, timelines, or upcoming events we should know now that would change how we scope the pilot?

• Solution Experience — Routing Outcomes

• Confirm the current state and its cost
• You confirm the restated current state and the quantified operational cost (fuel, hours, on-time impact).
• Provide three representative daily stop lists with time windows and vehicle assignments for the proposed pilot routes.
• You confirm the demonstrated optimization output shows projected miles reduction, on-time percentage improvement, and stops-per-route gains for at least one real scenario.
• Walk through representative routing scenarios
• Provide telematics endpoint details or a sample GPS trace for one depot to validate route telemetry alignment.
• Deliver a scenario comparison report that models projected miles, on-time percentage, and stops-per-route for the validated scenarios within three business days after this session.
• You agree on pilot acceptance metrics and a concrete pilot route set to validate savings.
• Show the platform route for the same scenarios and compare outcomes
• Validate constraint fidelity
• You identify any remaining data or constraint gaps required to run a live pilot.
• Confirm the internal pilot decision owners and acceptance gate reviewers and their availability for pilot evaluation reviews.
• Agree pilot acceptance metrics and route set
• Forced validation, confirm the fit

• Solution Experience — Routing Outcomes
• Solution Experience Deck
• Solution Brief — Routing Outcomes

• meeting
• slides
• document

• Integrate Order Management Feed
• Connect Telematics Provider
• Import Vehicle and Driver Data
• Configure Route Constraints and Time Windows
• Enable Multi-Depot and Multi-Temperature Routing
• Implement Capacity and Load Balancing per Vehicle
• Configure Hours-of-Service and Driver Rules
• Daily Automated Route Generation
• Real-Time Re-optimization and Dynamic Dispatch
• Deploy Driver Mobile App with Navigation and POD
• Execute 30–60 Day Parallel Pilot (Subset of Routes)
• Dispatcher Training and Go-Live Support
• Automated Route Delivery and API Export Setup

Integrate Order Management Feed

• Do you have a daily stop list feed we can ingest from your order management system? Options: Yes, No
• Which integration method do you prefer for the order feed? Options: API (JSON/REST), SFTP (CSV/CSV.gz), Database replication (SQL), Manual file upload, Other
• What fields are included in your daily stop file (for example: order_id, stop_id, customer_id, address, time_window_start, time_window_end, sku_temp_flag)?
• How often does your order system publish changes during the delivery day (e.g., new orders, cancellations)? Options: Once per day after cutover, Hourly, Every 15 minutes, Real-time/event-driven, Other
• Who in your team owns the source feed (system owner and an alternate) and who will be our technical contact for mapping?
• Are there mandatory data quality thresholds we must meet for the pilot (for example: 98% valid geocodes, address standardization rate)? Options: Yes, No

Connect Telematics Provider

• Which telematics provider(s) supply your vehicle GPS and odometer data for routing (list provider names or 'custom OEM')?
• Which telematics data points do you require in routes and post-trip reporting (for example: VIN, timestamped latitude/longitude, odometer, engine-hours, harsh-braking events)?
• What integration method is available for telematics (provider API, SFTP export, OEM broker)? Options: Provider API, SFTP export, OEM broker feed, No direct feed available
• How frequently do you need telematics updates for dynamic dispatch (options tied to intraday re-optimization: 30s, 1min, 5min, 15min)? Options: 30 seconds, 1 minute, 5 minutes, 15 minutes, Other
• Who will approve access to telematics data and provide API keys or SFTP credentials (role or team name)?
• Are there any data privacy or redaction requirements for telematics traces (for example: truncate to depot-level during off-hours)? Options: Yes, No

Import Vehicle and Driver Data

• What format do you have vehicle master records in (example fields: depot_id, VIN, vehicle_type, capacity_cu_ft, max_weight_kg, refrigeration_flag)? Options: Spreadsheet (CSV/XLSX), ERP/Asset DB export, Telematics vehicle registry, Other
• How many active vehicles will be part of the pilot route set and how many across the fleet? Options: Less than 25, 25-100, 101-500, 501-2,000
• Which driver attributes must we import for rules (for example: driver_id, license_class, shift_start, shift_end, break_windows, preferred_zones)?
• Do any vehicles require special handling due to temperature control, tail-lift, or pallet capacity that affects routing? Options: Yes, No
• Who owns the canonical vehicle and driver lists in your systems (role/team) and how frequently are they updated?
• Are VIN-level or asset-tag barcodes captured on the driver device for proof and should those be mapped to vehicle records? Options: Yes, No

Configure Route Constraints and Time Windows

• What customer delivery time-window conventions do you use (examples: fixed window 09:00-12:00, AM/PM, 'deliver by' dates) and which should be enforced in routing?
• Which constraint types must be enforced per stop or order (options include: hard time window, soft preferred window, delivery appointment duration, pallet restrictions)? Options: Hard time window, Soft preferred window, Appointment duration, Pallet/door restrictions, Other
• How should missed-window exceptions be handled by the dispatcher workflow (for example: auto-reschedule next slot, escalate to operations, notify customer)? Options: Auto-reschedule, Escalate to operations, Notify customer, Manual dispatcher decision
• What average service time per stop should we seed the optimizer with (minutes per stop or lookup by SKU/type)?
• Do you require geographic zone preferences or forbidden-turn constraints for routes around specific depot IDs or geofences? Options: Yes, No
• Which SLA thresholds must routes meet in the pilot for on-time deliveries and maximum route duration (for example: 95% on-time, route <=10 hours)?

Enable Multi-Depot and Multi-Temperature Routing

• How many depots will participate in the pilot and what are their depot IDs or names?
• Which SKUs or orders require temperature control and what temperature class labels do you use (for example: ambient, chilled, frozen)?
• Do you need the optimizer to prevent mixing incompatible temperature classes on the same vehicle (Yes/No)? Options: Yes, No
• What cross-depot transfer rules exist (for example: allow split loads, require return to origin depot, time windows for transfers)? Options: Allow split loads, Require return to origin, Time-windowed transfers, Other
• Which depot-level constraints should appear in planning (for example: vehicle staging windows, loading dock availability slots)?
• Who is responsible for coordinating multi-depot load assignments on the operations side (role or team)?

Implement Capacity and Load Balancing per Vehicle

• What capacity attributes must be modeled per vehicle (for example: cubic feet, payload kg, pallet positions, number of roll cages)?
• How do you calculate load size at the order level (volume dimension fields, weight fields, or item counts)? Options: Volume and weight fields, Item count only, Pallet count, Other
• What target metric do you use for balancing driver workload (for example: stops-per-route, drive time, estimated labor minutes)? Options: Stops-per-route, Drive time, Labor minutes, Other
• Do you require hard load limits per vehicle or allow soft overfill with manual approval? Options: Hard limits only, Soft overfill allowed with approval, Mixed by vehicle type
• Which routes or route groups should be prioritized for balancing during pilot (provide route IDs or criteria)?
• Who will review and approve load balancing overrides during the pilot (role or team)?

Configure Hours-of-Service and Driver Rules

• Which driver hours-of-service regulation or internal policy applies (for example: 8-hour shift + 30-minute break, local HOS rule reference)?
• How are driver shift patterns represented in your system (shift_start/shift_end per driver, rolling schedule, fixed weekly roster)? Options: Fixed shifts, Rolling schedule, Weekly roster, Other
• Do you require automatic driver break enforcement by the optimizer and how should breaks be scheduled within routes? Options: Yes, fixed break windows, Yes, flexible break placement, No automatic enforcement
• Which driver qualifications affect routing assignments (for example: hazmat endorsement, CDL class, language skills)?
• How should overtime be handled in route planning and reporting (allow overtime, cap at X hours, notify supervisor)? Options: Allow with cap, Disallow, Notify supervisor for approval
• Who maintains driver payroll/overtime rules that we must mirror in the optimizer (role or team)?

Daily Automated Route Generation

• What is your target cutover time for daily route generation (for example: generate routes at 03:00 local, 05:00 local)?
• Which stops should be included in automated generation versus held for manual scheduling (criteria such as same-day orders, appointment-based stops)?
• How many concurrent route-generation jobs do you expect per depot on peak days? Options: 1-5, 6-20, 21-50, 50+
• Do you require an approval step where a dispatcher reviews generated routes before publish? Options: Yes, mandatory approval, Optional review, No, auto-publish
• How should generated routes be tagged for analytics (for example: pilot_route, manual_control, test_group)?
• Which KPIs should be included in the daily route summary report (for example: estimated miles, estimated drive time, stops-per-route)? Options: Estimated miles, Estimated drive time, Stops-per-route, Estimated fuel

Real-Time Re-optimization and Dynamic Dispatch

• Which intraday events should trigger automatic re-optimization (new order, cancellation, driver delay > X minutes, telematics deviation)? Options: New order, Cancellation, Driver delay threshold, Telematics deviation, Other
• What delay threshold should trigger re-optimization for an en-route driver (for example: 10 minutes late, 30 minutes late)? Options: 10 minutes, 15 minutes, 30 minutes, Custom
• Do you permit automatic route edits to be pushed to driver devices without dispatcher confirmation during the pilot? Options: Yes, auto-push allowed, No, require dispatcher approval, Only for high-priority orders
• How should we surface re-optimization recommendations to dispatchers (visual diff, impact on miles/time, accept/reject buttons)? Options: Visual diff with impacts, Automated apply, Accept/reject workflow, Other
• Who will own monitoring of dynamic dispatch events during pilot (role or team) and what escalation path is required?
• Which telematics or driver-device signals indicate a failed re-optimization that should roll back changes (for example: loss of GPS, driver app offline)?

Deploy Driver Mobile App with Navigation and POD

• Which driver device types and OS versions will be used for the mobile app (for example: Android 11+, iOS 14+, ruggedized Android model X)?
• What proof-of-delivery artifacts are required at stop completion (for example: photo, signature, barcode scan, POD image)? Options: Photo, Signature, Barcode/QR scan, POD image, Other
• Do you require native turn-by-turn navigation integrated or allow external navigation apps to open from the driver app? Options: Native navigation, Open external navigation app, Either
• What driver adoption rate will you consider acceptable for the pilot (for example: 80% of scheduled drivers using the app daily)?
• Who will handle driver enrollment, device provisioning, and mobile app support during the pilot (role or team)?
• Which offline behaviors are required (for example: cache route details, queue POD submissions until network available)? Options: Cache route details, Queue POD submissions, No offline required

• success_criteria
• current_state
• gaps
• decision_readiness
• desired_state
• stakeholders
• desired_state
• success_criteria
• stakeholders
• gaps
• current_state
• decision_readiness
• stakeholders
• decision_readiness
• current_state
• desired_state
• success_criteria
• gaps
• decision_readiness
• decision_readiness
• decision_readiness
• decision_readiness

• Subscription Agreement
• Order Form — Pilot & Production
• Statement of Work (Pilot Implementation)
• Data Processing Agreement (DPA)
• Pilot Acceptance Criteria Addendum
• Service Level Agreement (SLA) & Support Terms
• Master Services Agreement (MSA)
• Mutual Non‑Disclosure Agreement (NDA)

• Go-live Health Check
• First Measurement Review
• Pilot Acceptance Gate
• Quarterly Operational Review

• Run a targeted training refresh or playbook update for dispatchers if adoption or execution issues persist.
• Produce a documented pass or fail for each acceptance criterion recorded in Pilot Evaluation.
• If conditional, enumerate remediation items with resolution dates to reach full acceptance.
• Publish the acceptance decision and the signed acceptance record where required by the engagement.
• Publish the formal acceptance record with outcome tables and signatory details.
• If conditional, open remediation tickets with timelines and closure criteria.
• Schedule the first Quarterly Operational Review following acceptance or remediation closure.
• Trend review of key metrics
• Maintain or improve the trend for miles saved and on-time delivery percentage versus targets recorded in Pilot Evaluation.
• Reduce the count of persistent operational exceptions and close high-priority tickets each quarter.
• Agree prioritized enhancement items and the schedule for constraint tuning or training refresh.
• Prioritize and schedule work for the top enhancement or tuning items from the backlog.
• Deliver a quarterly metrics pack showing miles driven, miles saved, stops completed per route, and on-time delivery percentage.
• Re-confirm success criteria and owners
• Deployment integrations and feeds validated or explicit remediation plan recorded.
• Top 3 operational blockers identified with remediation actions and target dates.
• Date confirmed for the First Measurement Review within the weeks 4 to 10 window.
• Publish a deployment runbook and current integration status for the team to reference.
• Log and prioritize open defects with target resolution dates.
• Schedule the First Measurement Review and circulate required data extracts ahead of that meeting.
• Present first-period outcome data
• Confirm the direction of travel for miles driven and on-time delivery percentage versus the targets recorded in Pilot Evaluation.
• Identify root causes for any shortfalls and record corrective actions with dates to reach the acceptance gate.
• Agree the next measurement window and the data extracts required for the Acceptance Gate meeting.
• Deliver cleaned measurement reports for miles driven, on-time delivery percentage, and stops per route for the agreed period.
• Implement the prioritized tuning changes and document configuration updates.
• Run a validation pass on integration data feeds ahead of the acceptance gate.
• Restate acceptance criteria and numeric targets
• Deployment and integration validation
• Present final pilot outcomes versus each target
• Operational exceptions and driver feedback
• Diagnose root causes for observed gaps
• Open issues burn-down and enhancement queue
• Agree corrective actions and timeline to acceptance gate
• Early adoption signals and usage patterns
• Document acceptance decision
• Confirm next measurement window and data responsibilities
• Agree remediation items and closure timeline if conditional
• Next quarter actions and measurement checks
• Blockers and open issues triage
• Agree next steps and cadence to first measurement