In freight forwarding, customers experience the process as one promise: move the shipment accurately, compliantly, and on time. Internally, however, that promise travels through quotations, carrier bookings, documentation, terminals, customs, transport providers, and multiple digital systems.
Value Stream Mapping (VSM) makes this end-to-end flow visible. It captures both the material flow: the physical movement of cargo: and the information flow that authorises, schedules, and controls that movement.
The fundamental purpose is not to create a visually impressive diagram. It is to identify where customer value is created, where time is consumed without creating value, and which constraints limit throughput. The method aligns naturally with the DMAIC framework: define the problem, measure the current state, analyse root causes, improve the flow, and control the gains.
For practical guidance on VSM and Lean Six Sigma application, review the Lean Six Sigma Practitioner Guide and the process cycle efficiency calculator.
1. Select a Focused Freight Forwarding Scope
A useful VSM begins with a specific service family. Avoid mapping every shipment type, trade lane, and transport mode simultaneously.
For this worked example, the scope is:
- Service family: FCL import shipments from an Asian supplier to an Australian consignee
- Start point: Booking request received from the customer
- End point: Cargo delivered and customs cleared
- Volume: 20 shipments per week
- Customer requirement: Delivery within 14 calendar days
- Core CTQs: On-time delivery, customs clearance time, right-first-time documentation, and cost per shipment
A cross-functional team should include customer service, operations, documentation, customs, finance, transport coordination, and IT. Include a customer representative where possible. Then walk the process using real shipment records rather than relying only on standard operating procedures.
The project scope boundary calculator can help define the boundaries before the mapping workshop.
2. Build the Current-State Map
A typical current-state flow may look like this:
Booking request → Quote and approval → Carrier booking → Document collection → Origin pickup → Export customs → Main carriage → Destination terminal → Import customs clearance → Final delivery
Map the information flow above the process and the material flow below it. Record:
- Customer emails, portal submissions, and booking instructions
- TMS, ERP, carrier portals, and customs systems
- Commercial invoices, packing lists, bills of lading, and declarations
- Queue time between each step
- Processing time within each step
- Work in process, including shipments waiting for documents or customs release
- Rework, errors, approvals, and handoffs
A time observation sheet is valuable here because quoted processing times rarely match actual performance. Capture the average, range, and variation for each step.
Worked current-state example
The following data represents a hypothetical sample of 20 FCL shipments:
| Process step | Processing time | Average waiting time | Common issue |
|---|---|---|---|
| Booking and quotation | 45 min | 0.5 day | Incomplete shipment details |
| Carrier booking | 30 min | 0.75 day | Approval queue |
| Document collection and checking | 90 min | 2.0 days | Missing invoice or packing list |
| Origin pickup and terminal receiving | 2.0 hr | 0.5 day | Appointment mismatch |
| Export customs | 75 min | 0.75 day | Classification clarification |
| Main carriage | 5.0 days | : | Scheduled transport |
| Destination terminal handling | 6 hr | 1.0 day | Arrival notice delay |
| Import customs clearance | 3.0 hr | 2.0 days | Data correction or inspection |
| Final delivery and proof of delivery | 4.0 hr | 0.75 day | Vehicle scheduling |
The total lead time is approximately 14.25 days. Direct processing and transport time totals about 5.4 days, giving a process cycle efficiency of approximately 37.9%.
The remaining time is primarily waiting, handoff delay, batching, document correction, and approval. That distinction is important: making a 45-minute booking task five minutes faster will not solve a two-day documentation queue.
3. Analyse the Eight Wastes in the Freight Flow
The current-state map should now be examined through the eight DOWNTIME wastes:
- Defects: Incorrect HS codes, inconsistent consignee details, or missing certificates create customs rework.
- Overproduction: Preparing declarations or delivery instructions before shipment details are confirmed creates avoidable updates.
- Waiting: Shipments wait for customer documents, approvals, arrival notices, customs responses, or available trucks.
- Non-utilised talent: Experienced customs specialists spend time searching emails or re-entering data instead of solving complex exceptions.
- Transportation: Repeated movement of documents between systems, offices, agents, or warehouses adds no customer value.
- Inventory: Containers, uncleared shipments, and document queues represent work in process.
- Motion: Staff search across inboxes, portals, spreadsheets, and shared drives for the latest information.
- Extra-processing: The same data is entered into the TMS, carrier portal, customs platform, and invoice system.
The most significant constraint in this example is the combined document-readiness and import-clearance queue. It limits throughput because downstream delivery cannot proceed until customs releases the shipment.
Use visual and statistical tools to validate the pattern:
- A Pareto chart may show that missing documents and data mismatches account for 72% of clearance delays.
- A box plot can reveal that average clearance time of 1.8 days hides several six-day outliers.
- Attribute data, such as Pass/Fail documentation checks, can measure right-first-time performance.
- A run chart can identify whether delays are becoming more frequent.
- For stable measurement systems, an X-bar chart can monitor average clearance time alongside an R chart for within-sample range.
- Where several customer, broker, or lane groups are being compared, ANOVA can test whether their mean clearance times differ significantly. Bartlett’s Test can first assess whether group variances are sufficiently equal for that analysis.
The goal of the Analyse Phase is to move beyond symptoms. A fishbone diagram may reveal that repeated customs corrections are influenced by unclear ownership, inconsistent master data, insufficient validation rules, and late document submission.
4. Design the Future-State Map
The future state should improve flow without compromising compliance. It should also balance the Voice of the Customer, the Voice of the Business, and the Voice of the Process.
For example:
- The customer requires predictable delivery and rapid clearance.
- The business requires controlled cost, regulatory compliance, and sustainable capacity.
- The process data shows that document completeness and approval delay are the dominant constraints.
A future-state design could include:
- A standard digital booking form with mandatory fields
- An automated document checklist issued at booking confirmation
- A single source of shipment data, with controlled interfaces to carrier and customs systems
- Risk-based approval rules, so standard shipments move without unnecessary escalation
- Pre-clearance preparation before vessel arrival where regulations permit
- A visual Andon-style alert when a shipment is missing a CTQ document or approaching a cut-off
- Clear pull signals, such as “documents complete,” “ready for filing,” and “customs released”
- Parallel delivery planning once arrival and release conditions are known
- Standard work for HS-code validation and exception handling
This is where autonomation, or Jidoka, can add value: system rules detect an invalid field or missing document and stop the transaction for correction before the error reaches customs.
Agile practices can complement the improvement effort. Instead of waiting for a large technology programme, the team can test a document checklist, review results after one week, and iteratively improve the workflow. The method is flexible, while DMAIC provides the measurement discipline.
5. Current State Versus Future State
The following target state assumes a six-month improvement programme:
| Performance measure | Current state | Future-state target | Improvement |
|---|---|---|---|
| End-to-end lead time | 14.25 days | 9.0 days | 36.8% reduction |
| Processing and transport time | 5.4 days | 5.1 days | More stable flow |
| Waiting time | 8.85 days | 3.9 days | 55.9% reduction |
| Documentation right-first-time | 85% | 97% | +12 percentage points |
| Average customs clearance time | 2.4 days | 1.1 days | 54.2% reduction |
| Shipments delivered on time | 76% | 94% | +18 percentage points |
| Active work in process | 42 shipments | 18 shipments | 57.1% reduction |
| Weekly throughput | 15 shipments | 20 shipments | 33.3% increase |
Takt time should be used to set the operating rhythm. With 2,400 available working minutes per week and demand of 20 shipments, the process takt is 120 minutes per shipment at the selected pacemaker activity. This does not mean every shipment takes exactly two hours; it establishes the required release pace and highlights when queues are accumulating.
6. Sequence Kaizen Work
Do not launch every improvement simultaneously. Sequence actions according to impact, dependency, and control risk.
Wave 1: Stabilise the process
- Define standard booking data requirements.
- Establish a document completeness checklist.
- Create ownership rules for each handoff.
- Measure daily queue age and customs rework.
Wave 2: Remove the primary bottleneck
- Introduce pre-clearance document preparation.
- Apply exception-only approval for standard shipments.
- Create a customs escalation trigger for ageing work.
- Standardise HS-code and consignee-data validation.
Wave 3: Improve flow and automation
- Integrate the TMS with carrier and customs platforms.
- Use visual dashboards and Andon alerts.
- Level shipment releases against available customs and delivery capacity.
- Reduce work in process through explicit pull signals.
Wave 4: Control and sustain
- Monitor on-time delivery, clearance time, right-first-time yield, and queue age.
- Review variation weekly using control charts.
- Audit standard work monthly.
- Re-map the value stream after six months.
The business case should quantify avoided storage, demurrage, rework, and customer-service effort. A break-even analysis can then determine how many shipments are required before technology or training investment is recovered.
Build Your Capability to Improve End-to-End Flow
Value Stream Mapping is most powerful when it connects operational observation with rigorous analysis. It reveals that freight forwarding performance is rarely determined by transport time alone. Waiting, variation, approvals, incomplete information, and work in process often determine the customer’s actual experience.
White Belts and Yellow Belts can support data collection, waste identification, and local kaizen. Green Belts can lead the DMAIC project, while Black Belts mentor teams through advanced statistical analysis and complex cross-functional change.
Lean 6 Sigma Hub offers CSSC-accredited Lean Six Sigma Green Belt training with practical tools, case studies, and self-paced learning. Explore the Lean Six Sigma project storyboard toolkit to structure your own improvement project.
Start your Lean Six Sigma certification journey and learn to convert complex freight flows into measurable, controlled performance improvement.
Kaizen. Kai-Care. Kai-Done. ( Lean Six Sigma)
