Home/Guides/CargoWise process reengineering
Process and people

CargoWise process reengineering: standardizing how teams work in the system

When CargoWise feels broken, the cause is often how it's being used. A reengineering program fixes the way teams work, then makes the system support it.

By Rob Petti, Founder, Lading CorporationUpdated November 18, 20263 min read
Short answer

When CargoWise feels broken, the cause is often inconsistent process: teams registering shipments in different ways, duplicated charge codes, fragmented master data, manual workarounds, and unclear handoffs. Process reengineering agrees standard ways of working with the people who run them, with room for the variations customers and regions need, aligns finance controls first, configures CargoWise to support the agreed process, and trains teams on it. The program stabilizes your existing setup rather than reimplementing CargoWise.

Signs you need it

  • The same job type is handled differently by different branches or teams.
  • Month-end close relies on spreadsheets and manual corrections.
  • Charge codes have multiplied and don't map cleanly to the chart of accounts.
  • Nobody can say with confidence when a job is ready to bill.
  • Customs holds, exceptions, or changes don't reach the people who need them.
  • Written procedures exist but don't match what happens in the system.

What we usually find

When we run discovery with a forwarder, we rarely find a single system fault. More often, the operating model has drifted. The system has evolved differently across teams, which shows up as inconsistent shipment registration, several methods for similar processes, fragmented master data, duplicated charge code structures, manual workarounds, inconsistent handoffs, and unclear ownership of procedures. Configuration changes alone don't fix that, because the problem is how people work.

How a program runs

  1. Discovery workshops. Structured sessions with every team to map how work flows today, where it breaks, and who owns each step. The sessions focus on how work is done today.
  2. Ownership and governance. A named business owner for each process, a steering committee for decisions, and clear change control so scope doesn't drift.
  3. Finance and control alignment first. Charge codes, the chart of accounts, billing readiness, work in progress, accruals, and the handoffs between operations and finance. Every operational procedure depends on these, so they come first.
  4. A pilot process. One department, such as air export, defines its future-state procedure, tests it in a copy of the live system, and signs it off.
  5. Roll out. The approach proven in the pilot is applied to the other departments, adjusting procedures as you go.
  6. Training and adoption. System basics first, then training on approved procedures only. Nobody is trained on a process that hasn't been signed off.

What you get

DeliverableWhat it does
Process ownership matrixShows who owns each process and decision
Standard operating proceduresAgreed, signed-off ways of handling each job type, including approved variations, executable in the system
Aligned charge codes and chart of accountsCharges flow to the right accounts without manual fixes
Targeted configuration changesThe system enforces the agreed procedures
Training programBasics for everyone, then procedure training by audience
Decision log and backlogWhat was agreed, and what is deferred to later phases

Scope limits

It isn't a reimplementation, and it doesn't try to fix every historical issue at once. Requirements outside the agreed scope go to a backlog for later phases, through change control. This keeps the program focused on the highest-priority workflows.

The same approach works on other forwarding systems. CargoWise is where we spent most of our years as a partner, so it's where we see these patterns most often.

Common questions

How long does a program take?

It runs in phases. A recent stabilization phase for a multi-country forwarder was planned as a 12-week program, with broader requirements moved to a backlog for later phases.

Why does finance come first?

Because every operational procedure depends on it. If charge codes, billing readiness, and accruals aren't agreed, every process you standardize afterwards has to be revisited.

Do our people have to be involved?

Yes. The procedures only stick if the people who run them help design them and sign them off. We facilitate the sessions, document the procedures, and configure the system. Your teams own the procedures once they're signed off.

Will you change our CargoWise configuration?

Yes, where the agreed procedures need it, tested in a copy of your live system first and deployed only after sign-off.

Talk it through with us

Tell us the problem you'd solve first, and people who have built, implemented, and supported forwarding systems will reply with how they would approach it.

Get in touch →