MERIDIAN · TRACK

For freight forwarders and the teams coordinating their shipments

Keep shipment flow clear, from document to handoff.

Meridian is an operational platform for freight teams. It is designed to bring shipment documents, milestones and responsibilities into a shared working record, so people can see the current position, address exceptions and coordinate the next handoff with the supporting context close at hand.

A precision route instrument connects sparse waypoints above a glass map, with shipment documents held beside its base.
MERIDIAN · The route instrument · Concept illustration

The problem

A shipment moves through many hands. Its context needs to travel with it.

Documents apart from the operation

Bookings, transport documents and updates arrive through different channels, leaving teams to reconstruct the shipment story.

Unclear current position

A status update means little without its source, timing and the changes that came before it.

Handoffs without ownership

When an exception crosses teams, its context and the responsibility for the next step can become separated.

What it does

What you get.

A connected basis for running shipments, reviewing their documents and coordinating follow-up.

Bring the shipment together

  • Connect relevant documents, milestones and working notes to the shipment they describe.
  • Keep source references and timing beside the current operational picture.
  • Make missing information and conflicting updates visible for review.

Give documents a working role

  • Organise shipment documents alongside the tasks and decisions they support.
  • Review extracted or supplied information before it changes the record.
  • Keep corrections and the reasons for them available to the team.

Coordinate the next handoff

  • Bring exceptions, responsibilities and next steps into a shared context.
  • Prepare customer updates from material approved for sharing.
  • Carry the operational reasoning forward as work moves between teams.

Why this matters

Freight coordination depends on people understanding the same shipment at the right moment. When documents, updates and responsibilities stay connected, teams have a clearer basis for addressing exceptions and keeping work moving. Meridian is designed around that continuity.

How the record works

Keep the basis for a decision in view.

What is the source?

Keep the document, supplied event or operator entry behind a shipment update in view.

What is the current position?

Distinguish the recorded position from an estimate or an update still awaiting review.

Who reviewed the change?

Retain the assessment and responsibility behind a material change.

What happens next?

Carry the exception, responsible team and next action into the handoff.

Who uses it

The same record, seen from every chair.

Operations teams

Work from the shipment context when planning tasks and handling exceptions.

Customer-service teams

Prepare clear updates with the source and sharing context available.

Operational leaders

Review how responsibilities, exceptions and handoffs are being handled.

Evaluation

Start with a focused workflow.

Choose a shipment workflow and agree the documents, source connections and review responsibilities needed to evaluate it alongside current operations.

Agree the scope

  • Shipment scope and the sources available for review
  • Document handling, permissions and customer-sharing boundaries
  • Responsibilities for exceptions and operational handoffs
Discuss a pilot

Questions to evaluate together

  • Can the team reconstruct the current shipment position?
  • Are document gaps and conflicting updates clear?
  • Does each handoff preserve context and responsibility?

Evidence for the questions that matter.

Evaluate the relevant product and conditions. Request scoped evidence for access, provenance, recovery, human review and offboarding before agreeing a pilot.

Who can access the information?
Ask for the product's access boundaries and applicable isolation tests.
Where does the information come from?
Agree the sources and inspect a representative source-to-record example.
What happens when something fails?
Agree operational ownership and request relevant monitoring and recovery evidence.
What can we review and take with us?
Confirm review history, retention, export formats and offboarding within the agreed scope.
Technical evaluation

For investors and partners

A practical foundation for freight coordination.

Meridian gives the Optimized Core portfolio a clear operational focus: the movement of shipments and the information needed to manage them. For investors and partners, its value proposition is grounded in a recognisable coordination problem, with a focused workflow that can be evaluated against real working requirements. Product scope and connections are agreed through that evaluation.

Partnership discussion

Identity

Meridian brings the Optimized Core principles of source context, traceability and human review to freight operations. Its focus is continuity from the shipment record to the next responsible handoff.

locate → record → connect → report

Shipment records, connected by design.

A precision route instrument connects sparse waypoints above a glass map, with shipment documents held beside its base.
MERIDIAN · The route instrument · Concept illustration

Bring your shipment workflow into focus.

Describe your team and the workflow you want to evaluate, with an anonymised example if you like. We discuss scope, connections and readiness before any data is shared.

JPH van Mastrigt · Founder & Technical Director