Quick orientation, where you operate and what you track

• Tell me briefly which inbound flows your team coordinates most days, for example inbound lanes to a plant, DC replenishment, or 3PL-managed cross-docks
• Which transport modes are in scope for those lanes right now Options: Ocean, Air, Rail, Long-haul truck, Regional truck/last-mile, Intermodal
• Which lanes are mission-critical, meaning a late arrival could stop production or miss a major retail window
• In a typical month, roughly how many inbound shipments across those mission-critical lanes do you track Options: Fewer than 50, 50–200, 201–1,000, 1,001–5,000, More than 5,000
• Which role on your team is the first responder when a shipment is late, and who gets escalated next Options: Logistics coordinator/dispatcher, Operations manager, Transportation planner, Supply chain director, Customer service/retail operations, Other
• When a late inbound shipment appears, which system does your team check first for status (pick one) Options: Carrier portal or app, TMS, ERP shipment record, Manual call to carrier/3PL, Internal tracking spreadsheet, Other

If a lane misses an ETA and production stops, what breaks first

• If your highest-volume lane missed its ETA and caused a line stop, what immediate operational or financial consequences would you expect to see that week
• Walk me through the last time that happened: who detected it, how long until recovery, and what was the visible impact
• How often in the past 12 months did late inbound shipments only become visible after the delivery window closed Options: More than monthly, Monthly, Quarterly, Less than quarterly, Never
• Which SKUs or product families cause the largest downstream pain when they are late, and why
• Estimate the largest recent single-incident loss in production hours or lost sales days from a late inbound shipment Options: Less than 8 hours, 8–24 hours, 1–3 days, More than 3 days, Unknown
• Which executive or business role would escalate this issue most strongly if it recurred Options: Plant/operations head, VP of Supply Chain, COO, Head of Merchandising/Retail Ops, CFO, Other

Where the current visibility actually breaks

• Which data sources currently give you frequent location updates, and which lanes rely primarily on carrier ETAs or milestone scans Options: Carrier GPS/telemetry, Carrier milestone scans (ETA updates), IoT trackers on pallets/containers, Port or terminal feeds, Manual phone/email updates, None of the above
• On the lanes you care about most, how long on average passes between a delay occurring and your team finding out Options: Under 30 minutes, 30–120 minutes, 2–8 hours, 8–24 hours, More than 24 hours, Unknown
• Which leg types consistently have the least reliable ETAs for you, choose all that apply Options: Ocean deep-sea legs, Port terminal/stevedore processing, Cross-border customs legs, Long-haul truck (FTL), Regional last-mile carriers, Rail ramps/intermodal transfers
• Give a concrete example of a lane where ETA updates are misleading or too infrequent and what that causes downstream
• If a vendor could improve your median ETA error on ocean lanes to under 6 hours and truck lanes to under 2 hours, would that be sufficient to change your approach Options: Yes, that would be sufficient, Possibly, depends on integration effort, No, we need tighter accuracy, Unsure
• Which single visibility failure (for example, no updates for 24 hours, wrong ETA by more than 12 hours, or missed handoff between carriers) would make you halt a pilot immediately

Who needs to know and who needs to act when things go wrong

• Which internal and external stakeholders must be informed within the first hour of a critical shipment exception, and who only needs a daily summary Options: Plant ops, Supply chain director, Customer service/retail operations, Carrier/3PL account rep, Procurement, Executive leadership
• Walk me through your current escalation path for a critical inbound delay, including expected response time at each step
• Which roles own approvals for connecting the platform to your TMS, ERP, carrier portals, and any IoT gateways Options: IT/security, Integration team, Supply chain operations, Procurement, Legal/compliance, Third-party carrier contacts
• How many full-time equivalents currently spend time chasing shipment status and what percentage of their weekly time is on status calls and emails Options: 0–1 FTE, <10%, 1–3 FTE, 10–30%, 3–6 FTE, 30–60%, More than 6 FTE, >60%, Unknown
• If a pilot required a daily 30-minute integration stand-up with your systems team for the first two weeks, could you commit that time Options: Yes, No, Need approval

What could stop the project before it starts

• Which implementation risks worry you most right now, pick up to three Options: Missing carrier feeds for key lanes, Legacy TMS without API support, Poor data quality in historical shipments, Alert fatigue from noisy thresholds, Lack of internal integration resources, Contractual/data-sharing limits with carriers
• For the top two risks you selected, describe a recent incident when that risk caused a missed deadline or rollout delay
• Do you have data retention or privacy rules that would block sharing 90 days of historical shipment data for analysis Options: Yes, No, I need to check
• Are there carrier or 3PL contracts that explicitly limit adding a third-party visibility provider or sharing tracking data Options: Yes, No, Unsure
• Which single unresolved constraint, if not cleared within 4 weeks, would stop you from running a pilot

The other options you are weighing right now

• Before we go further, why might you prefer sticking with carrier portals or building this capability internally instead of partnering with an external platform
• Which solution types are you currently evaluating or have evaluated in the last 18 months Options: Incumbent visibility vendor, TMS vendor add-on, Carrier portals only, Internal build (IT-led), Managed service from 3PL, Consulting/analysis engagement
• What would have to be true about your current approach for you to keep it instead of switching to a new platform
• Has anyone proposed solving this in-house, and if so which team would own it and what timeline did they estimate Options: Yes, IT owns it, Yes, Ops owns it, Yes, shared IT and Ops, No internal proposal, Unsure
• If a vendor matched your required ETA accuracy but required twice the integration work, which would you choose Options: Vendor with better accuracy despite more effort, Prefer lower integration effort even if accuracy slightly worse, Need to compare total cost and timeline

Can we actually connect to the systems that matter

• Which integration endpoints must be live for a pilot to proceed, pick all that apply Options: TMS (API/EDI), ERP shipment or order data, Carrier EDI/API portals, Carrier SFTP feed, IoT gateway or trackers, Port/terminal feeds
• For the endpoints you selected, are APIs available and are credentials already provisioned Options: APIs available and credentials ready, APIs available but credentials needed, No APIs, only SFTP or file drops, No direct access currently
• Do you have an internal technical contact who can provide API keys, SFTP credentials, or arrange carrier access within 2 weeks Options: Yes, contact is ready, Yes, but needs approval, No, will take longer, Unsure
• How mature is your historical shipment data for a 90-day ingest: consolidated with timestamps, partially consolidated, fragmented across teams, or not available Options: Consolidated and ready, Partially consolidated, Fragmented, Not available
• If your security team requires a vendor security assessment that takes longer than 6 weeks, will that pause the pilot Options: Yes, it will pause, No, we can run in parallel, Depends on scope

What success must look like and the acceptance gate

• If the pilot delivers the ETA accuracy and alert timeliness you need, what decision would you expect to be able to make immediately afterward
• Which three pilot metrics will determine success for your team, pick up to three Options: Median ETA error by mode, Percent of exceptions alerted within target window, Integration feed uptime, Reduction in manual status hours, Number of carrier integrations achieved, Improvement in on-time delivery %
• For the metrics you selected, give target thresholds you would require, for example median ETA error under 6 hours for ocean or alerts within 30 minutes
• Which role in your organization is authorized to accept pilot results and sign a production agreement without additional executive approval Options: Supply chain director, VP of Supply Chain, Procurement lead, CFO, Requires executive sign-off
• What procurement or budget constraints could delay a purchase by more than one quarter even if the pilot succeeds Options: Budget cycle timing, Formal RFP required, Executive approval needed, No constraints, ready to proceed, Other
• If the pilot proves the agreed improvements, what single organizational blocker would prevent moving to production within 30 days

Immediate next steps, pilot scope, and decision ownership

• If we move forward, which priority lanes must be included in a 90-day pilot and which lanes must be excluded
• Which stakeholders should join the kickoff call and who will own pilot acceptance on your side Options: Supply chain operations owner, Integration/IT owner, Carrier/3PL account rep, Procurement, Executive sponsor
• What is an acceptable pilot start window for you given carrier access and internal approvals Options: Immediately, Within 2 weeks, 2–4 weeks, 4–8 weeks, More than 8 weeks
• Would you be willing to provide a 90-day shipment history for analysis to prioritize lanes Options: Yes, ready to share, Yes, but needs approval, No, Unsure
• If we commit to a 90-day pilot starting within your preferred window and meeting agreed metrics, who on your side is enabled to sign the commercial terms at close

• Solution Experience: Predictive ETAs & Exception Workflows

• Confirm the current state and its cost
• Customer confirms the demonstrated predictive ETA reduces the time you would have had to react and would have prevented the example shutdown.
• Run the 90-day lane performance analysis and deliver an ETA accuracy comparison versus carrier estimates before the follow-up meeting.
• Provide the prioritized lane list and 90 days of shipment records in CSV or SFTP feed format along with the list of carriers used on those lanes.
• Show lane-level predictive ETA vs carrier ETA
• Customer confirms the exception workflow produces timely, prioritized alerts that they would act on instead of manual chasing.
• Demonstrate automated exception workflows on your scenario
• Agreement on the minimum pilot scope and the acceptance metrics needed to evaluate ETA accuracy and alert relevance.
• Confirm pilot acceptance metrics, for example target ETA accuracy window and acceptable alert-to-incident ratio.
• Validate TMS/ERP integration behavior on sample events
• Is this what you meant when you said you needed lane-level predictive alerts to prevent line shutdowns?
• Agree next steps toward a time-boxed pilot

• Solution Experience: Predictive ETAs & Exception Workflows
• Solution Experience Deck
• Solution Brief

• meeting
• slides
• document

• Ingest 90-Day Shipment History
• Activate Carrier Data Feeds
• Normalize and Map Shipment Data
• Calibrate Predictive ETA Models
• Configure Exception Detection Rules
• Integrate with TMS and ERP
• Onboard IoT and Telematics Devices
• Deploy Real-Time Tracking Dashboard
• Enable Automated Alerts and Escalations
• Implement Carrier and Lane Analytics
• Manage Scan-Only Carrier Coverage
• Train Logistics and Operations Users

Ingest 90-Day Shipment History

• How many shipments from your past 90 days should we ingest and which lanes and SKUs should be prioritized for the pilot?
• Provide the data sources for your 90-day export (for example: TMS export, carrier EDI 214/315, ERP shipment tables, SFTP folders). Options: TMS export, Carrier EDI 214/315, ERP shipment tables, SFTP file drops, Other
• List the file formats you will deliver for the historical export from your systems (CSV, JSON, EDIFACT/ANSI X12, database dump). Options: CSV, JSON, EDIFACT/ANSI X12, Database dump / SQL extract, Other
• Estimate your historical data completeness by lane (percentage of shipments with actual delivery timestamps vs planned ETAs) for the lanes in scope. Options: >95%, 80-95%, 60-80%, <60%
• What acceptance criteria will confirm a successful 90-day ingest for the pilot (minimum record count, percent field completeness, and number of lanes covered)?
• Who on your team will own providing access to the historical exports and resolving missing fields (role or contact)?

Activate Carrier Data Feeds

• Which carriers by lane do you require active data feeds for during the pilot and for production?
• Which feed types can each of your carriers provide for those lanes (push webhook/API, SFTP batch, EDI 214, HTTP polling)? Options: Push webhook/API, SFTP batch, EDI 214 / 315, HTTP polling, Other
• For carriers that provide only milestone scans, identify the lanes and partners that are scan-only in your network.
• What carrier onboarding SLA do you expect for activation (time to first successful message) for pilot lanes? Options: 3-5 business days, 1-2 weeks, 3-4 weeks, Custom
• Which carrier credentials or contact information will you provide for feed activation (API keys, SFTP credentials, EDI trading partner IDs)?
• Are there any carriers or lanes you explicitly want excluded from the pilot activation? Options: Yes, No
• If yes, list the carrier names or lane identifiers you want excluded from pilot activation.

Normalize and Map Shipment Data

• Which canonical shipment fields must be present after normalization for your operations (pro number, bill of lading, carrier SCAC, origin/destination ZIP, event timestamps)? Options: Pro number, Bill of lading (BOL), Carrier SCAC, Origin ZIP/Port, Destination ZIP/DC, Event timestamps
• Which SKU-level attributes must map to your ERP or warehouse item codes (SKU, UPC, internal part number) for accurate inventory linkage?
• Which reference identifiers do you use to tie shipments back to orders in your TMS/ERP (purchase order number, ASN, sales order ID)? Options: Purchase order number, ASN, Sales order ID, Other
• Do you require transformation rules for time zone normalization, location name mapping, or unit-of-measure conversions during normalization? Options: Yes, No
• What percent data accuracy or field completeness do you require before mapping is considered production-ready (for example, 95% of key fields populated)? Options: >98%, 95-98%, 90-95%, <90%
• Who will approve field mapping decisions and resolve mapping exceptions on your team (role or contact)?

Calibrate Predictive ETA Models

• Which lanes and shipment types should be used to calibrate predictive ETA models first (for example: ocean FCL lanes from Port A to DC X for SKU families Y)?
• Which external factors should the model weight for your lanes (port congestion, customs dwell, weather events, carrier-specific delay patterns)? Options: Port congestion, Customs dwell time, Weather events, Carrier historical delays, Terminal operations
• What target ETA accuracy will you accept for pilot validation (for example median ETA error within hours such as <=6 hours for ocean lanes)? Options: <=6 hours, 6-12 hours, 12-24 hours, Custom
• Which minimum sample size per lane do you require for calibration before model results are trusted (minimum shipments per lane)? Options: 50, 100, 250, Custom
• Do you require model explainability reports showing feature importance and drivers of ETA variance by lane? Options: Yes, No
• Who on your team will approve calibration results and own the model retraining cadence (role or contact)?

Configure Exception Detection Rules

• Which exception types are critical for your operations (ETA miss greater than X hours, missed delivery window, carrier delay at terminal, customs hold)? Options: ETA miss threshold, Missed delivery window, Carrier terminal delay, Customs hold, POD not received
• For ETA-miss exceptions, what lane- or SKU-level lead-time threshold should trigger an alert in your workflow (for example 6 hours, 12 hours)? Options: 3 hours, 6 hours, 12 hours, 24 hours, Custom
• Which downstream actions should exceptions trigger in your systems (create a TMS incident, flag ERP backorder, notify supply planner via Slack/email)? Options: Create TMS incident, Flag ERP backorder, Notify via email, Notify via Slack, Webhook to ticketing
• Who should receive severity-level alerts and what roles will acknowledge them (operations coordinator, transport manager, supply planner)?
• Do you require aggregation rules to reduce alert fatigue (for example group similar exceptions by carrier or lane within a rolling window)? Options: Yes, No
• What acceptance criteria will confirm exception rules are tuned for pilot (acceptable false positive rate, average time-to-acknowledge, and meaningfulness of alerts)?

Integrate with TMS and ERP

• Which TMS and ERP systems will we connect to and which integration methods do they support for your environment (REST API, SFTP batch, database view, EDI)?
• Which specific tables or API endpoints must receive real-time updates from tracking (shipment status, ETA, exception codes, proof of delivery)? Options: Shipment status endpoint/table, ETA field, Exception codes table, POD endpoint/table, Other
• What field-level keys must be used to match platform shipments to your TMS/ERP records (pro number, PO number, ASN)? Options: Pro number, PO number, ASN, Sales order ID, Other
• What success criteria define integration quality for you (target sync latency and percent of matched shipments to accept go-live)? Options: Latency <5 minutes & >95% matched, Latency <30 minutes & >90% matched, Custom
• When are your integration maintenance windows and any data-sharing blackout periods we must avoid?
• Who will provide API credentials and act as the technical contact for TMS/ERP integration tasks?

Onboard IoT and Telematics Devices

• Which shipment legs in your network use GPS telematics or IoT sensors and which device vendors are involved?
• What device telemetry fields do you require for operations (latitude/longitude, heading, speed, battery, geofence entry/exit, door status, temperature)? Options: Latitude/longitude, Heading/speed, Battery level, Geofence events, Door open/close, Temperature/humidity
• How frequently should device telemetry be ingested for production monitoring on your critical lanes (1 minute, 5 minutes, 15 minutes)? Options: 1 minute, 5 minutes, 15 minutes, 30 minutes, Custom
• Do you have cold-chain SKUs that require BLE or temperature sensors and threshold alerts tied to SKU-specific limits? Options: Yes, No
• Who will manage device enrollment, SIM provisioning, and device lifecycle on your side (role or contact)?
• Would you like device location accuracy validated against scan events during the pilot for selected lanes? Options: Yes, No

Deploy Real-Time Tracking Dashboard

• Which of your user roles should have access to the real-time tracking dashboard (operations coordinator, transport manager, supply planner, executive)? Options: Operations coordinator, Transport manager, Supply planner, Executive
• What lane-level KPIs must be visible on the dashboard for your daily operations (predicted ETA variance, on-time probability, open exceptions, average dwell)? Options: Predicted ETA variance, On-time probability, Open exceptions, Average dwell time, Carrier comparison
• Which custom filters or saved views do you need in the dashboard (by SKU family, DC, carrier, priority lanes)?
• Which refresh cadence do you require for dashboard widgets to support operational decision making? Options: Real-time (push), 1 minute, 5 minutes, 15 minutes
• Do you require embedding the dashboard inside your TMS/ERP and single sign-on (SSO) support for your users? Options: SSO only, Embedded iframe + SSO, No embedding required
• Which three representative shipments (lane + SKU family + pro number example) should we use to validate dashboard correctness during QA?

Enable Automated Alerts and Escalations

• Which communication channels should automated alerts use for your teams (email, SMS, Slack, webhook to ticketing)? Options: Email, SMS, Slack, Webhook to ticketing system, Other
• Describe the escalation paths and timing you want for high-severity exceptions (for example escalate to manager after 30 minutes unacknowledged).
• Do you require alert templates that include structured fields we must populate (carrier, pro number, ETA variance, recommended remediation steps)? Options: Yes, No
• Should alerts automatically create tickets in your incident management or TMS system when triggered? Options: Yes, No
• Which SLAs govern alert acknowledgement and resolution during the pilot for your team (acknowledge within X minutes, resolve within Y hours)? Options: Ack within 30 min, resolve within 24 hr, Ack within 2 hr, resolve within 48 hr, Custom
• Who is the on-call contact for escalations during the pilot (role and contact information)?

Implement Carrier and Lane Analytics

• Which analytics reports and dashboards do you need for decision making (lane-level ETA accuracy, carrier reliability, terminal dwell time, root cause by SKU)? Options: Lane-level ETA accuracy, Carrier reliability, Terminal dwell time, Root cause by SKU, Custom report
• What export formats and delivery cadence do you need for analytics (scheduled CSV, API feed, on-demand PDF, dashboard widgets)? Options: Scheduled CSV, API feed, On-demand PDF, Dashboard widgets
• Which executive KPIs must be included for monthly reporting (on-time delivery percentage, average ETA error hours, exception rate by carrier)? Options: On-time delivery %, Average ETA error (hours), Exception rate by carrier, Other
• How frequently should analytics be refreshed and rolled up for your teams (daily, weekly, monthly)? Options: Daily, Weekly, Monthly
• Do you require baseline reports that compare carrier-provided ETAs to predictive ETAs over the 90-day pilot window? Options: Yes, No

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

• Subscription Agreement
• Pilot Acceptance Addendum (90-Day Pilot)
• Order Form — Pilot & Production
• Data Access & Authorization
• Data Processing Agreement (DPA)
• Service Level Agreement (SLA) & Support Terms
• Roles, Responsibilities & Escalation Matrix
• Change Order Agreement

• Go-live health check (weeks 1-4)
• First measurement review (weeks 4-10)
• Acceptance gate meeting, pilot decision (around day 90)
• Quarterly realization review (ongoing operational cadence)
• Annual performance and continuous improvement review

• Update the shared backlog with prioritized items and target resolution windows.
• For conditional items, create a verification checklist and target dates for re-evaluation.
• Schedule a follow-up verification session to confirm remediation items are closed as agreed.
• KPI trend review since last meeting
• Confirm whether ETA prediction accuracy and integration uptime meet operational needs and document any lanes or carriers requiring intervention.
• Prioritize the shared backlog so the next quarter's work focuses on the highest business impact items.
• Ensure open critical issues have target closure dates and a clear verification plan.
• Re-confirm success criteria and owners
• Produce a one-page KPI summary for operations showing ETA accuracy, integration uptime, and recent incident counts.
• Escalate any unresolved production-critical defects with the agreed escalation path and deadline.
• Year-to-date KPI and SLA adherence
• Agree the quantified year-to-date outcome for ETA prediction accuracy and the weekly hours saved from reduced manual tracking.
• Document which long-lived issues remain and assign priority for next-year work.
• Produce a short, prioritized continuous improvement plan for the next 12 months.
• Deliver an annual impact summary with ETA accuracy, hours saved, and estimated cost avoidance.
• Publish the prioritized 12-month continuous improvement plan with target milestones.
• Close any remaining administrative items related to connector maintenance windows or archival of pilot datasets.
• All integration endpoints required for the pilot are active or have a documented remediation plan with dates.
• Critical blockers that prevent visibility or user access are assigned resolution dates and owners.
• Your operations team confirms basic dashboard access and the exception inbox is receiving real events.
• Publish a remediation plan for any inactive carrier or TMS connectors with target dates.
• Run a sample shipment trace for three high-priority lanes and circulate results for verification.
• Correct any missing feed credentials or mapping entries preventing milestone ingestion.
• Present KPI results vs Pilot Evaluation targets
• Confirm whether ETA prediction accuracy and exception alert lead time are improving toward the Pilot Evaluation targets and document any shortfalls.
• Produce a root-cause list for the largest KPI gaps with assigned corrective actions and resolution dates.
• Set a clear timeline to the acceptance gate with owners accountable for each remediation task.
• Deliver a lane-level KPI report showing ETA prediction error and alert lead time with annotated root causes.
• Implement agreed feed or mapping fixes and report back with evidence of improved update frequency.
• Adjust alert thresholds for two sample lanes and measure change in false-positive and true-positive alert rates.
• Restate acceptance criteria and numeric targets
• Produce a documented acceptance decision for the pilot against each numeric target recorded in Pilot Evaluation.
• If any criteria are conditional or failed, agree a remediation plan with completion dates and verification steps.
• Capture the named signatory or authorized buying owner who records the acceptance decision for audit purposes.
• Publish the acceptance decision record with pass/fail status, signatory name, and any conditional remediation items.
• Deployment and integration validation
• Operational incidents and detection review
• Business impact and operational efficiency
• Present outcome data for each acceptance criterion
• Root-cause diagnosis for KPI gaps
• Agree corrective actions and timelines
• Document pass/fail per criterion and formal decision
• Long-lived blockers and backlog outcomes
• Early adoption and usage signals
• Backlog grooming and prioritization
• Open defects and operational blockers
• Open issue burn-down and escalation review
• Agree continuous improvement priorities for next 12 months
• Confirm readiness timeline to acceptance gate
• Agree remediation plan and closure timeline for any failed or conditional items
• Agree immediate remediation actions