PortCommand

The Challenge

Port ops teams were running multi-million-dollar container flows out of shared spreadsheets, group texts and phone calls. Drivers showed up at the wrong terminal. Status checks meant calling the yard.

Every team had its own version of the truth, and any audit question — 'where was this container last Tuesday?' — was a forensic exercise.

Our Solution

PortCommand is a single web-based command center for the entire NY/NJ container operation. Containers, drivers, clients and terminals all live in one place, with a real-time view that the dispatcher, the driver and the client all share.

Every state change is audit-logged, so the answer to 'where was this container last Tuesday?' is one click instead of one afternoon.

What We Built

• Real-time container tracking across NY/NJ terminals.
• Driver dispatch coordination with mobile-friendly assignments.
• Client-linked records — every container tied to the right account, the right invoice and the right contact.
• Terminal-specific status checking that surfaces the right info per terminal.
• Full audit trail for every container, dispatch and status change.

The Approach — What We Weighed

The spreadsheets weren't the disease — they were the symptom of three teams keeping three versions of the truth. So the real decision was where the single source of truth would live, and how much to trust an off-the-shelf logistics suite to hold it.

Options on the table

• Adopt a packaged TMS — feature-rich, but built for generic freight, heavy to bend to NY/NJ terminal quirks, and the audit trail lives in the vendor's schema.
• Keep the spreadsheets and add a reporting layer on top — cheapest, but it papers over the split-truth problem instead of fixing it.
• Build a purpose-built command center where containers, drivers, clients and terminals share one live record — more up-front work, exact fit, full ownership of the audit trail.

What we proposed

We built the custom command center. A packaged TMS would have forced the operation to match the tool instead of the terminals, and a reporting layer over spreadsheets leaves everyone still reading stale data. Owning the model let 'where was this container last Tuesday?' become one query against one audit log — and let the dispatcher, driver and client finally read from the same screen.

Results & Value Delivered

One source of truth

Dispatchers, drivers and clients now read from the same live data instead of three stale spreadsheets.

Fewer wrong-terminal trips

Status checks happen in the app before the truck rolls, not after.

Audit-ready

Container history is exportable per client, per date range, per terminal.

Capabilities Used