Frequently Asked Questions

We operate asset-backed freight programs across truckload and specialized equipment profiles, plus cross-border lane execution between Canada, the United States, and Mexico. Program scope is aligned to lane requirements, commodity constraints, and service commitments.

We support domestic and cross-border freight execution across Canada, the United States, and Mexico. Coverage is lane-dependent, and final operating design is confirmed during onboarding based on origin-destination profile, commodity, and service cadence.

Yes. We support recurring lane structures, defined service standards, and governance cadence for enterprise programs. Operating design is built around forecasted volume, equipment fit, service windows, and exception handling requirements.

Submit lane origin and destination, commodity profile, pickup and delivery windows, target volume, and any compliance constraints. We use that input to return an execution model with clear assumptions, responsibilities, and service controls.

Yes. Cross-border execution is a core part of SSP's operating footprint. Programs are structured around corridor requirements, document readiness, handoff control, and communication cadence from dispatch through delivery.

Broker-of-record and importer responsibilities are determined by shipment structure and customer setup. We coordinate operational handoffs and document discipline, while formal customs roles remain aligned to the agreed commercial model and applicable broker instructions.

Requirements vary by lane and commodity, but commonly include commercial invoice data, bill of lading details, and any required customs or commodity documentation. Final document requirements are determined by corridor rules, customs authorities, and broker guidance. We confirm required document sets before release to reduce border delays.

Risk is reduced through pre-move document checks, lane-specific operating controls, and active milestone governance during transit. When conditions change, escalation ownership and communication remain defined.

Shipment visibility is provided through our tracking workflows and operations communication cadence. Milestone updates, status changes, and exception notices are tied to defined points in the move lifecycle.

Exceptions are managed through accountable escalation: issue identification, corrective action, updated ETA, and documented communication. We prioritize decision-ready updates so customer teams can act quickly.

Yes. SSP's operating model is structured around named ownership across planning, dispatch, in-transit governance, and closeout. That reduces handoff ambiguity and accelerates escalation response.

Yes. Communication cadence can be aligned to your internal operating rhythm, including milestone updates, escalation thresholds, and stakeholder notification requirements.

We manage safety and compliance as an operating framework across planning, dispatch readiness, in-transit oversight, and closeout. The focus is consistent control before and during movement, not reactive fixes after exceptions occur.

We can support shipment profiles that require elevated handling discipline, documentation quality, and operating controls. Lane and commodity requirements are validated before movement is authorized.

Documentation requirements are reviewed at shipment level against lane and commodity context. We apply pre-release checks and closeout discipline to improve completeness and audit readiness.

Regulatory requirements differ by jurisdiction and shipment type. We align operational controls to active corridor requirements and keeps responsibilities visible throughout the execution lifecycle. Regulatory references are informational; formal legal and customs determinations are made by authorized entities.

We support direct shipper programs and partner-led models, including 3PL and broker relationships. Operating governance and accountability are maintained regardless of commercial channel.

Billing structure and terms are defined at onboarding or quoting stage. We align invoicing workflow to the agreed commercial model so finance and operations teams have clear documentation and reconciliation flow.

Claims are handled through a documented review process with shipment records, supporting documentation, and defined response steps. We coordinate investigation and resolution in alignment with agreed terms and applicable requirements.

Integration support is discussed during onboarding. Based on workflow scope, we can align operational data exchange and reporting expectations to customer system requirements.