The clock that costs you money is the berth window. Get your operators in front of it.

Who this is for

This page is written for the people who own a vessel's clock without owning the vessel. Specifically:

• Terminal and operations managers — the people running berth allocation, yard planning, and gang scheduling shift to shift.
• Vessel and ship superintendents — who plan the discharge/load sequence, write the vessel recap, and own turnaround time at the berth.
• Stevedoring and labor coordinators — who order ILA/ILWU gangs, reconcile timesheets, and live in the labor-cost line.
• Billing and claims desks — the people who defend demurrage, detention, and per-diem disputes against carriers and BCOs (Beneficial Cargo Owners).
• Terminal GMs and ownership — operating principals, and the private equity and infrastructure funds that own marine-terminal and logistics platforms.

This is not a frontline-labor program and it does not touch the contract. The longshore work is the longshore work. This is for the salaried operating layer above the gang — the planners, superintendents, coordinators, and managers whose output is decisions and documents, not container moves.

The opportunity cost

A marine terminal makes money when the berth turns and loses money when it sits. Everything expensive on a terminal — gang labor ordered by the shift, crane hours, yard space, the carrier's patience — is priced by time. The operating layer spends its day translating between those clocks, and most of that translation happens in tools that don't talk to each other.

Two places where the cost is unsentimental. First, labor ordering: a gang ordered and not worked, or worked short and held over into overtime, is real money decided hours ahead on imperfect information. Second, demurrage and detention. Nine ocean carriers collected roughly $15.4 billion in D&D charges between April 2020 and March 2025, and since the FMC's May 2024 billing rule took effect, a disputed invoice that isn't answered cleanly and on time is a charge you eat. The desk that can produce a documented, timestamped rebuttal in minutes recovers money the desk that takes a day simply concedes.

We don't put a dollar figure in the hero, because the right number depends on your throughput and your labor mix. But for a mid-size terminal, recovering a single gang's worth of avoided overtime per week, plus a modest lift in D&D dispute win-rate, clears the cost of a full operating team's seats inside a quarter. The worksheet at the bottom lets you run it on your own numbers.

What changes for your desk in six weeks

This is a behavior change, not a software install. It does not replace your TOS (Terminal Operating System) and it does not require IT. Here's what the operating layer looks like at each checkpoint.

Week 1 — the recap stops being homework

Your team learns the four-part prompting framework — Context, Task, Format, Constraints (CTFC) — and the redaction discipline for anything carrier-confidential or labor-sensitive before it goes into Claude. By the end of the week, the superintendent who used to write the vessel recap from memory after the ship sails has a saved prompt that turns shift notes and the move count into a clean recap before they leave the gate.

Week 2 — the email backlog clears

Carrier line notices, BCO status requests, port authority correspondence — the operating layer answers dozens a day and each one used to interrupt the actual work. You build saved prompts that draft accurate, on-register replies from the underlying facts, so the ops desk spends its attention on the exceptions instead of the routine.

Week 3 — demurrage and detention disputes get answered same-day

You build a saved D&D rebuttal prompt that takes the invoice, the gate and availability timestamps, and the relevant free-time terms and produces a documented, FMC-rule-aware dispute letter — your first pass, ready for the billing lead to verify and send. The dispute that used to wait a day, or get conceded for lack of time, goes out the same shift.

Week 4 — gang-order decisions get written down

You build a labor-order justification prompt — given the expected workload, the vessel schedule, and the constraints, it drafts the reasoning behind the gang order so the decision is documented, reviewable, and consistent shift to shift. The point is not to automate the call. It's to stop losing the reasoning when the person who made it goes home.

Week 5 — the daily operations brief becomes a product

A one-page morning brief — vessels working, berth windows, yard utilization, labor ordered, open disputes — drafted in fifteen minutes from the overnight numbers. It goes to ownership and to the carriers who want a status read. The terminal that communicates this cleanly is the terminal lines route their next vessel to.

Week 6 — the Playbook compounds

Every prompt your team wrote in weeks one through five lives in the Playbook, tagged and pinned. The new superintendent inherits the recap prompt instead of relearning the format. The billing desk's dispute language gets sharper every cycle. The program ends. The leverage stays on the terminal.

The Playbook for the operating layer

The Playbook is the part of this program that keeps paying after the cohort ends. It's a structured, tagged set of saved prompts your team builds itself during the program — not a generic template pack, and crucially not tied to one person. By week six, a terminal's operating Playbook usually has these pinned at the top:

• vessel-recap-v1 — discharge/load recap from shift notes and move counts, before the ship sails.
• dd-dispute-rebuttal-v1 — FMC-rule-aware demurrage/detention dispute letter from invoice and timestamps.
• gang-order-justification-v1 — documented reasoning behind the labor order for a given vessel and shift.
• carrier-notice-reply-v1 — on-register replies to line and BCO correspondence from the underlying facts.
• daily-ops-brief-v1 — one-page morning brief for ownership and key accounts.
• incident-writeup-v1 — first-pass safety or equipment incident narrative from the facts on the ground.

The Playbook compounds because the prompts get sharper every time they're used, and because they belong to the terminal rather than to whoever happened to be on shift. The recap format you saved last month is the one the new hire uses on day one.

The ownership and PE angle

If you own a terminal — or a portfolio of marine-terminal and logistics platforms — the math shifts from a training spend to an operating-leverage play.

The Team tier ($1,400/seat, five-seat minimum) unlocks two pieces a single operator doesn't need: a leaderboard showing which managers are actually completing the lessons and using the prompts, and manager reporting that surfaces adoption and usage by seat from week one. There's a completion credential that proves your managers finished, so the program seats that actually finish.

Frame it honestly with the team. It's not surveillance. It's adoption pull-through. Most terminal AI initiatives die in the same place — ownership buys a license, two superintendents engage, the rest let it rot. The leaderboard solves the social problem; the reporting answers the owner's actual question: am I getting the operating lift I paid for, and from whom?

For a fund running an operational-improvement thesis across a logistics platform, this is one of the cheaper levers available — it standardizes how the operating layer communicates and decides across sites, and it surfaces which sites and which managers are pulling the change through. That visibility is portfolio-level, not just terminal-level.

Why this versus the alternatives

You have other options. Each has a real purpose. None of them does what this program does for the operating layer.

Generic AI courses

Plenty exist. None of them know what a vessel recap is, none teach the berth window or the D&D clock as a curriculum chapter, and none produce a Playbook tied to the specific moves a terminal makes in a shift. They teach Claude. We teach your operators to run a terminal with Claude.

Your TOS vendor's AI features

Navis and the other Terminal Operating System platforms are bolting AI into planning and yard optimization. That's real and valuable — but it optimizes the moves inside the system. It doesn't teach the superintendent to write the recap, the billing desk to win the dispute, or the coordinator to document the labor call. The operating layer's output is decisions and documents, and the TOS doesn't touch those.

Hiring more operators

The experienced terminal-operations talent pool is thin and getting thinner as a generation of superintendents retires. This program doesn't replace that hire — it makes the people you already have more leveraged, and it captures the institutional knowledge that currently walks out the door at retirement into a Playbook that stays.

This program teaches the system. The Playbook is the asset that stays on the terminal.

Pricing

Operator — $1,200/year. All eight modules, Hayes, the Playbook, and the credential. The full daily-fundamentals stack: prompting, email and correspondence, recaps and briefs, and long-form drafting. Lifetime access to the Playbook tooling. The right tier for an individual superintendent or coordinator who wants to run ahead of the rest of the desk.

Team — $1,400/seat/year, 5-seat minimum. Same content as Operator, plus the admin console, leaderboard, and manager reporting — adds the manager and frontier track, plus the Master credential on completion. The right tier for a terminal manager or GM who'll set the standard others follow.

Team — $1,400/seat (five-seat minimum). All eight modules for the operating layer, plus the leaderboard, manager reporting, and a $100 completion credit per credentialed seat. The right tier for a terminal rolling this out across its operating staff, or a fund standardizing across a platform.

The owner ask

If you're a GM, owner, or fund operating partner looking at the operating layer across one terminal or several, the conversation shifts from a course purchase to an operating-improvement investment. Two resources are written for you specifically:

• The champion one-pager — the page you forward to your operating partner or your most trusted superintendent before you commit. Three minutes to read, structured the way an internal pitch is structured.
• The ROI worksheet — a finance-defensible model you edit with your own throughput, labor mix, and D&D dispute volume. Conservative assumptions throughout. The output is a per-seat payback period and an annual operating-lift estimate.

What you get on day one

The moment you enroll, the following are live in your account:

1. Access to Modules 1 and 2 in full — the prompting fundamentals and the email-and-correspondence stack.
2. The Playbook tool, pre-loaded with three terminal-specific starter prompts you can edit (vessel recap, D&D dispute rebuttal, daily ops brief). You build the rest.
3. A confidentiality preflight — every prompt flags sensitive data (carrier-rate, labor, or personal information) and offers a redacted version before sending to Claude. Built for the reality that carrier and labor data is not yours to leak.
4. The cohort channel — a peer space with other terminal operators and superintendents running the same week. This is where the messy real questions get asked.
5. A scheduled office-hours invite for week one. Live, recorded, optional.

Modules 3 through 8 ship on the published cadence; all subscribers receive each as it lands.

Ready to begin?

You already know what a backed-up yard and a conceded dispute cost you. Six weeks from now, the operating layer runs differently — recaps before the ship sails, disputes answered the same shift, labor calls documented, a daily brief ownership actually reads, and a Playbook that keeps compounding after the program ends. Tomorrow morning's first vessel gets handled by a desk that has its time back.