Maritime Logistics
High-touch engagements where experience, trust, and multi-party logistics determine satisfaction.
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Trade‑Lane Discovery
Align on trade lanes, shipment volumes, transit constraints, customs requirements, stakeholders, and measurable success signals.
Discovery Questions
Start Here: Quick Lane Snapshot
- How many sea trade lanes do you actively move cargo on today?
- Which three lanes create the most volume or cost pressure for you?
- Estimate the monthly TEU or metric ton volume on those top lanes
- Who on your team is the day-to-day contact for carrier bookings and exceptions?
- Pinpoint the single lane, account, or timing constraint that would make you postpone evaluating a new logistics partner
Where the Work Actually Lives
- When a lane misses its transit promise, what downstream process breaks first at your plant or warehouse?
- Describe the typical handoffs from carrier to port agent to inland haulier on that lane
- How often do documentation errors, such as bill of lading, commercial invoice, or HS codes, trigger a hold at origin or destination?
- Which document or data field causes the most rework in your experience?
- Do you have a standard booking cutoff window and how strictly is it enforced?
What's Causing the Most Headaches?
- What single failure in your current lane setup would make you stop a pilot or walk away?
- Tell me about a recent demurrage or detention charge event, what caused it, and how it was resolved
- Approximately how much do exception handling costs add to a container on affected lanes?
- Who ends up owning claims and recovery work when cargo is lost or damaged?
- List the frequent triggers for customs delays on your import lanes over the past 12 months
The Alternatives You're Weighing
- If you keep your incumbent arrangement, what would have to be true about its performance for you not to select a new partner?
- Name the external options you have evaluated so far, including different forwarders, carriers, or an in-house solution
- Is anyone inside your organization advocating to solve this without an external partner, and why?
- What conditions would have to hold for you to stay with the incumbent rather than change providers?
- Select the primary reasons you are considering a change now
If Everything Went Right, What Would That Unlock?
- Identify one measurable outcome that would make a new logistics relationship unquestionably better than your current setup
- Describe how you currently measure on-time delivery by lane, and the targets you expect from a partner
- List the KPIs beyond transit time that matter most to you, for example customs clearance time, claims rate, or demurrage exposure
- If a pilot proves the numbers, what internal approvals or procurement steps would accelerate signing within two weeks?
- Select the financial or operational thresholds that would be a pass for you in a pilot
Are You Ready to Execute?
- Identify any technical or regulatory blocker on your side that could prevent onboarding within 6 weeks
- Confirm whether you can provide an EDI or API endpoint for booking and shipment status, or if you will need file uploads and email feeds
- Name the team or role that owns your TMS and customs broker integrations, and whether they can commit resources during onboarding
- Estimate how clean and accessible your shipment master data is, for example party addresses, HS codes, and product descriptions
- Choose the regulatory or compliance approvals that could gate go-live
- Point to the single constraint that would immediately stop the project
Pilot Shipment: The Proof That Matters
- Imagine the pilot meets transit times but still requires manual document corrections at destination, would you accept that as a successful proof of concept?
- Specify the transit time variance versus schedule that would be acceptable for the pilot lane
- Provide the document sets that must be validated during the pilot, for example master bill of lading, arrival notice, commercial invoice, packing list
- Explain how you will measure exception handling success during the pilot, and who has final sign off
- Choose the pilot acceptance criteria that would allow rapid scaling to other lanes
Timelines, Decision Triggers, and Next Steps
- Pinpoint the internal approvals that would still delay signature beyond 30 days even if the pilot meets your targets
- When do you need the new lane cover in place to avoid operational risk, month and year?
- Provide the essential stakeholders that must be engaged before pilot approval
- Rank the criteria you would use to prioritize lanes for follow-on pilots
- State your target decision date after the pilot completes
- Assuming the pilot delivers the agreed KPIs, what single remaining objection could still prevent you from signing within two weeks?
-
Pilot Shipment Experience
Plan and execute a trial shipment on a target lane to validate transit time, documentation accuracy, and exception handling in the buyer's context.
Solution Experience
- Pilot Shipment Experience Session
- Confirm the current state and its cost
- You confirm the documented current state and the concrete cost (demurrage, detention, manual hours) these incidents create.
- Confirm pilot lane and shipment window (date range) within 3 business days.
- You agree the pilot lane, shipment window, and measurable acceptance criteria for transit, documentation accuracy, and exception resolution.
- Agree pilot scope and success metrics
- Provide final shipper documentation set for the pilot, including commercial invoice, packing list, and any required export declarations.
- You validate that the runbook and escalation path, when executed, will demonstrate the future state described.
- Provide last-mile contact matrix and receiving facility access instructions required for delivery.
- Walk through the pilot runbook and documentation checklist
- You commit to the immediate action items required to execute the pilot within the agreed window.
- Simulate exceptions and escalation paths
- Deliver the pilot runbook including nominated carrier/agent details, expected transit milestones, required document templates, and exception escalation steps within 3 business days.
- Execute the pilot shipment and collect evidence: ETA variance, document discrepancy count, and time-to-resolution for any exceptions, then present results in a follow-up review within two business days of delivery.
- Confirm acceptance criteria and data collection plan
- Forced validation, confirm this maps to your need
- Next steps and commitments
- Pilot Shipment Experience Session
- Pilot Shipment Experience Deck
- Pilot Shipment Solution Brief
- meeting
- slides
- document
-
Solution Scope
Define lanes, service components (forwarding, port agency, customs clearance, inland moves), responsibilities, SLAs, and acceptance criteria.
Scope Configuration
- Ocean Freight Booking and Rate Negotiation
- Voyage Chartering and Vessel Contract Execution
- Port Agency Representation and Terminal Handling
- Export and Import Customs Declarations
- Bills of Lading Issuance and Document Management
- Container Stuffing, Stripping, and Lashing
- Port-to-Door Multimodal Transportation
- Demurrage and Detention Charge Negotiation
- Cargo Tracking and Exception Management
- Claims Handling for Damage and Loss
- Hazardous Goods Handling and Compliance
- Project and Breakbulk Heavy-Lift Coordination
- Consolidation and Deconsolidation (LCL/FCL) Services
- Customs Bonding and Duty Payment Facilitation
Scope Questions
Ocean Freight Booking and Rate Negotiation
- Which trade lanes and container equipment (20ft dry, 40ft dry, 40ft high-cube, reefer, flat-rack, open-top, bulk/breakbulk) should bookings and rate negotiations cover?
- What target transit time windows (door-to-door in days) should negotiated rates guarantee per lane?
- Do you require fixed-rate contracts, seasonal spot pricing, or a hybrid tiered pricing model?
- How should peak-season surcharges and bunker adjustment factors be applied and reconciled in invoices?
- Who in your organization is authorized to approve rate cards, volume tiers, and routing exceptions?
- Where should booking confirmations, executed rate cards, and SLA attachments be delivered or integrated (your transport management system (TMS), procurement system, API endpoint, email, shared drive)?
Voyage Chartering and Vessel Contract Execution
- When do you require vessel nomination and laycan windows to be locked relative to cargo readiness?
- List cargo characteristics that affect chartering (out-of-gauge dimensions, single-piece weights, palletized vs floor-loaded, hazardous) and provide typical dimensions and weights.
- Provide acceptable vessel types and minimum deadweight or TEU capacity thresholds per route.
- Specify charter party clause preferences for demurrage, despatch, and off-hire you require for voyage contracts.
- Are there pre-existing slot charter agreements, space-sharing arrangements, or co-loading constraints we must honor?
- Confirm required insurance limits and exposure thresholds for time or voyage charters relevant to your cargo values.
Port Agency Representation and Terminal Handling
- Identify the primary ports and terminals per trade lane where port agency representation and terminal coordination will be required.
- Estimate average call frequency per port and expected berth-processing hours that will affect agent staffing.
- Select terminal services required at each port: stevedoring, pilot/port dues handling, husbandry, linehandling, cargo watch, shore power for reefers.
- Indicate any special terminal permits, ISPS access credentials, or port passes your personnel require to execute agency tasks.
- State standard turnaround expectations at the terminal for vessel turnaround and for container pick-up from berth.
- Will you require live vessel status updates via EDI/API webhooks or periodic email bulletins from the agent?
Export and Import Customs Declarations
- For which commodity groups and HS codes do you move goods that require special duty treatment, licenses, or permits?
- Describe your current customs registrations, bonded warehouse authorizations, and any fiscal representation arrangements used for imports and exports.
- Include the target customs clearance SLA per shipment (time from arrival to release) that you require for each lane.
- Attach or list the commercial invoice, packing list, export license, and certificate of origin templates we must use for declarations.
- Outline the acceptance criteria that will validate successful customs declaration processing for pilot shipments (examples: release within 48 hours of arrival, 95% tariff classification accuracy, duties invoiced within 5 business days).
- Measure your partners' preferred customs message formats and endpoints (UN/EDIFACT, ANSI X12, XML API, broker EDI) and indicate available credentials.
Bills of Lading Issuance and Document Management
- Name the bill of lading types you require per lane: negotiable/master BL, house BL, sea waybill, or electronic bill of lading.
- Flag which parties must be named on the bill of lading (shipper, consignee, notify party) and any mandatory address or tax ID formats.
- Have you standardized whether original paper bills must be couriered or if an electronic Bill of Lading is acceptable for banks and consignees?
- Prioritize how document corrections, endorsements, and release confirmations should be handled and logged during transit.
- Assign the evidence that will confirm document management readiness for go-live (bank acceptance of eBL, consignee receipt of documents, zero bill of lading corrections during pilot).
- Define where finalized shipping documents should be archived and who needs access (legal, customs broker, finance, carriers).
Container Stuffing, Stripping, and Lashing
- List the typical stuffing and lashing configurations you use (palletized, floor-loaded, dunnage, blocking and bracing) with maximum piece weights and dimensions.
- Recommend your standard VGM process and timing for declaring container Verified Gross Mass relative to gate-in or vessel cut-off.
- Choose whether stuffing will occur at shipper premises, nominated stuffing facilities, or at terminal and whether we should provide labor and materials.
- Determine special lashing or moisture-control requirements for reefers, project cargo, or vulnerable commodities and any required certificates.
- Validate required stuffing/stripping artifacts to capture (weight tickets, photos, tamper-evident seal numbers, stuffing checklist).
- Schedule who in your operations approves stuffing plans and signs off on weight and lashing certificates.
Port-to-Door Multimodal Transportation
- Record the inland transport modes and container equipment you require per origin/destination (truck, rail, barge; chassis types; ADR-compliant trailers).
- Route the expected weekly pickup and delivery frequency and preferred appointment booking rules.
- Align final delivery addresses, receiving windows, and limited-access site requirements that carriers must adhere to.
- Break down the on-time pickup and delivery acceptance thresholds you will accept for port-to-door legs (for example, 95% pickups within 24 hours and 90% deliveries within appointment).
- Clarify who coordinates appointment booking and detention avoidance at the consignee site and who should receive carrier exception notifications.
- Capture required proof-of-delivery artifacts and integration endpoints for delivery confirmation (signed POD, delivery photo, GPS trace, API webhook).
Demurrage and Detention Charge Negotiation
- Which historical demurrage and detention drivers have most affected you (late docs, customs delay, container availability, port congestion)?
- What free-time allowances for import and export containers per port do you target as part of negotiations (number of free days)?
- Do you have recent demurrage invoices or dispute cases we should review to set negotiation priorities?
- How should mitigation mechanisms be prioritized: pre-paid detention, carrier debit arrangements, terminal appeals, or bonded storage?
- Who is authorized to escalate and sign off disputed demurrage invoices and what timeframe do they require for review?
- Where do you want demurrage and detention KPIs reported and how often (weekly, monthly)?
Cargo Tracking and Exception Management
- When you analyze performance which primary tracking identifier do you use for reconciliation (booking reference, bill of lading, container number, purchase order)?
- List the top exception types you want automated alerts for (ETA changes, customs hold, damaged container, reconsignment, gate-out delay).
- Provide whether you have a standardized event taxonomy or if you will adopt our event map for milestones (vessel departure, arrival, container gate-in/out, EDI status codes).
- Specify which stakeholders should receive each exception notification (operations, procurement, compliance, finance) and preferred escalation order.
- Are target response and resolution SLAs required for exceptions (acknowledgement within 1 hour, resolution within 48 hours)?
- Confirm integration endpoints for real-time tracking updates (your API webhooks, SFTP feeds, EDI status messages) and whether credentials are available.
Claims Handling for Damage and Loss
- Identify your preferred claims notification timeline and required evidence formats (photos, survey report, bill of lading, delivery receipts).
- Estimate typical claim frequency and average claim value by lane to size reserves and liability handling.
- Select immediate actions required on damaged cargo at port (survey, repair, temporary storage, on-site corrective stuffing).
- Indicate whether the first course of action should be carrier recovery, insurer filing, or customer-led restitution for different claim types.
- State any pre-existing contractual liability limits or declared values per container that will affect claims processing and recovery.
- Schedule expected claim-handling milestones for a typical incident (initial report, survey, provisional payment, closure) and target days for each milestone.
-
Mutual Commit
Finalize commercial terms, liability and claims handling, SLAs, onboarding timeline, and mutual obligations for execution.
Agreement Modules
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Service Level Agreement (SLA)
- Pricing & Order Form
- Claims, Liability & Indemnity Agreement
- Onboarding Timeline & Acceptance Schedule
- Agent Appointment & Operational Authority
- Insurance Confirmation & Cargo Cover
- Customs & Regulatory Compliance Addendum
- Data Processing & Privacy Addendum (conditional)
-
Operational Onboarding
Operationalize port-to-door onboarding with readiness checks, configuration, and execution.
-
Pre-Deployment Readiness
Confirm concrete readiness facts — customs registrations, nominated carriers/agents, access, owners, and go‑live timing before operations begin.
Pre-Deployment Questions
Environment and site access
- Are production customs registrations, broker authorizations, and any required customs bonds in place for each origin and destination site we will operate on (so we can confirm clearance capability)?
- If some sites are missing registrations or authorizations, list the site name/code and the planned completion date for each (so we can schedule go‑live windows).
Data and integration readiness
- Have the buyer and the seller nominated carriers and local port agents for each trade lane covered by this rollout (so we can confirm operational handoffs)?
- Is production EDI/API connectivity available for booking and status messages for the lanes in scope, or will you rely on manual exchanges at go‑live (this determines test cadence)?
People and ownership
- Who is the named operational owner (day‑to‑day) and who is the escalation owner for go‑live issues? Provide name and role/title (so the deployment team has a single contact per stream).
- Do all nominated users have the system and portal access required for execution (booking portal, track & trace, customs broker portal)?
Timing and constraints
- What is the target go‑live date for operational handover on the nominated lanes (we'll use this to schedule training, cutovers, and the pilot shipment)?
- Are there blackout windows, regulatory freezes, or critical business dates we must avoid for cutover? If yes, list the window(s) and the controlling authority or reason (so we can avoid scheduling conflicts).
-
Configuration Details
Capture exact operational configurations: documentation templates, EDI/API endpoints, contact matrices, carrier instructions, and billing/claims routing.
Configuration Details
Environments & Integration Endpoints
- Primary production EDI/API endpoint URL (enter exact URL used by your systems; format: https://hostname/path — this value is consumed by the integration connector)
- Supported integration protocol for the production endpoint (select the single protocol the connector will use)
- Authentication method for the production EDI/API endpoint (select one; we will request only non-secret identifiers here)
- Credential identifier for the production integration (enter non-secret identifier only — e.g., client_id, integration username, or key NAME). The secret/value will be exchanged via your secrets manager at deployment.
Document Templates & Data Formats
- Bill of Lading (B/L) template variant to apply for this relationship (select one)
- Electronic shipping document formats the platform should accept from the buyer or seller (select all that apply)
- Exact repository or URL where document templates and versioned paperwork are stored (enter full path or repository URL; this is consumed by the document-sync step)
Contacts, Notifications & Escalation
- Primary operations contact role for shipments (enter exact role title as used internally; e.g., 'Logistics Manager - Export')
- Preferred operational notification channel for shipment events (select one — if you choose webhook, you will provide the URL in the next question)
- Webhook URL for operational notifications (enter full URL format: https://... — leave blank if not applicable)
- Time to first escalation for unresolved operational incidents (enter numeric hours; Default is 4 hours — confirm or specify another value)
Carrier Instructions, Billing & Claims Routing
- Carrier instruction set to apply by default for tendered shipments (select one)
- Default billing party for inland movement charges (select one — value consumed by billing routing rules)
- Billing / claims routing identifier (enter routable AP/Claims email or account name exactly as it must appear on invoices and claims)
Monitoring, SLAs & Retention
- Shipment event monitoring cadence in seconds (numeric; Default is 900 for 15 minutes — confirm or specify another value)
- On-time delivery SLA target as a percentage (numeric; Default is 95 — enter an integer between 0 and 100)
- Incident and event data retention period in days (numeric; Default is 365 days — confirm or specify another value)
-
Operational Launch
Execute onboarding and initial shipments with task sequencing, monitoring cadence, escalation paths, and terminal/carrier coordination.
-
-
Performance & Success
Continuously monitor on-time delivery, claims, demurrage/detention incidents, and drive improvements through recurring reviews and issue tracking.
Success Reviews
- Go-live Health Check (Week 1-4)
- First Performance Measurement (Weeks 4-10)
- Acceptance Gate Review (Around Day 90)
- Quarterly Performance Review
- Operational Improvement Sprint Review (Monthly)
Issues & Enhancements
- Produce a prioritized remediation plan for the top recurring exceptions with target completion windows.
- Publish the formal acceptance record showing pass/fail per criterion and any conditional remediation items.
- If remediation is required, create a tracked remediation log with resolution dates and verification steps.
- Execute the incumbent decommission or read-only archiving steps and produce confirmation artifacts.
- Trend review for core metrics
- Confirm whether core metrics meet the targets recorded in Solution Scope and document any SLA breaches.
- Agree remediation priorities for the persistent exceptions that most affect delivery and cost.
- Ensure claims trends are understood and that a plan is in place to reduce claim frequency and resolution time.
- Re-confirm success criteria and owners
- Compile a claims trend report with root-cause examples and proposed process or documentation changes.
- Update the SLA exception log with any required contractual notifications or remedies.
- Sprint retro and status
- Confirm whether documentation accuracy rate and claims per 1,000 shipments improved following recent sprint activities.
- Agree the next sprint scope focused on the highest-impact operational fixes and document verification criteria.
- Ensure every open operational task has a clear completion condition and verification data to be reviewed next month.
- Update documentation templates and circulate revised carrier instructions for validation in the next sprint.
- Run a targeted training or runbook refresh for the top 2 operational handoffs responsible for the most errors.
- Publish the sprint verification checklist and required data artifacts to demonstrate metric impact at next review.
- Confirm the deployment components required for operations are live and validated.
- Create a prioritized list of blockers with agreed remediation actions and target dates.
- Agree who tracks each open issue and how progress is reported ahead of the first measurement meeting.
- Publish a deployment validation checklist showing integration status and message exchange logs.
- Record and circulate the prioritized blocker list with remediation steps and target completion dates.
- Run an initial sample shipment through the end-to-end flow and capture any documentation or handoff exceptions.
- Present first-period metric results
- Determine whether on-time delivery rate and average customs clearance time are moving toward the targets recorded in Solution Scope.
- Document root causes for each out-of-target metric and agree a prioritized set of corrective actions with target dates.
- Confirm the evidence package and timeline required for the Acceptance Gate review.
- Produce a metric pack with shipment-level examples for each flagged exception and distribute before the Acceptance Gate meeting.
- Implement agreed quick fixes for the highest-impact root causes and log progress updates in the shared issue tracker.
- Prepare documentation audit showing documentation accuracy rate improvements or outstanding gaps.
- Restate acceptance criteria and numeric targets
- Produce a documented pass or fail result for each numeric acceptance criterion recorded in Solution Scope.
- If any criterion failed or is conditional, agree a remediation plan with concrete dates and verification evidence.
- Confirm the incumbent system wind-down plan is executed or scheduled with archive/migration evidence captured.
- Detailed review on top recurring exceptions
- Metric movement for operational levers
- Present outcome data against each criterion
- Root-cause diagnosis for gaps
- Deployment and integration validation
- Claims and financial impact summary
- Document pass or fail per criterion
- Root-cause work and corrective tasks
- Agree corrective actions and owners
- Early adoption and processing signals
- Backlog grooming and next sprint plan
- Open issues and blockers
- Confirm timeline to acceptance gate
- Open issue burn-down and backlog prioritization
- Formal acceptance decision and signatory capture
- Immediate remediation actions and timeline
- Incumbent wind-down and data handover